O RBITAL V IRTUAL

T ERMINAL
U SER G UIDE

August 2010
Version 4.2
Orbital Virtual Terminal
Version 4.2

Orbital Gateway on the Web: Orbital Integration Library

Orbital Gateway Support: 1-866-645-1314
[email protected]

Orbital Virtual Terminal User Guide

Version 4.2
August 2010
© 2009 Chase Paymentech Solutions, LLC. All rights reserved.
This document contains information which is proprietary to Chase Paymentech Solutions, LLC. This information
may not be reproduced in any way, or shared with a third party, without the written permission of Chase
Paymentech Solutions, LLC.
Some of the materials contained within have been provided by agreement from processing and financial
exchange partners. This information, materials, trademarks and or product names are the property of their
respective owners and may be covered by additional copyrights.
All brand names and product names used in this document are trade names, service marks, or registered
trademarks of their respective owners.
All information and features contained herein are subject to change without notice.

Revision History
Date Version Action Description
07/20/05 VT 3.0 Original Creation Original Creation
11/05/05 VT 3.2 Add New Reporting functionality
11/05/05 VT 3.2 Change Different Logon Page
11/05/05 VT 3.2 Add New Multi Merchant Logon
11/05/05 VT 3.2 Add New Reporting Admin
11/05/05 VT 3.2 Add New General Admin
11/05/05 VT 3.2 Change Different Purchase card prompt
06/01/06 VT 3.5 Change New logo and Gateway Support e-mail address
06/01/06 VT 3.5 Add New Order – Purchase Card Level III section
Open Batch – Purchase Card Level III section
Purchase Card III Admin section
01/31/07 VT 3.10 Change Updated all screenshots
01/31/07 VT 3.10 Add Added VT File Import section and new Profile features (Auto-
Suggest and Reuse)
02/26/08 VT. 4.0 Add Added Managed Billing, Cardholder E-mail Service, and
Authorization Recycle sections.
06/03/08 VT 4.1 Change Expanded information on Scheduled Reports, Managed Billing
Profiles, and Authorization Recycling. Gift Card language added.
07/09/09 VT 4.1.1 Reformat Put into new template, modified style for usability.
08/09/10 VT 4.2 Add Added Account Updater and Partial Authorization information

Page 2 of 214
Orbital Virtual Terminal
Version 4.2

Table of Contents
Common Tasks ....................................................................................................... 9

List of Tables........................................................................................................ 10

How to Use this Guide .......................................................................................... 11

Who Should Read this Guide ............................................................................... 11
Organization of this Guide .................................................................................. 11
Related Documentation ...................................................................................... 11
What's New in this Release ................................................................................. 12
Using the PDF Version of this Guide ..................................................................... 12
Conventions Used in this Guide ........................................................................... 12

Chapter 1 Introduction ...................................................................................... 14

Features and Benefits ........................................................................................ 14
Payment Methods and Tools .......................................................................... 14
Auto-Settle Feature ...................................................................................... 15
Duplicate Checking ....................................................................................... 15
Security Features ......................................................................................... 15
Profiles and Managed Billing........................................................................... 16
Merchant Selectable Response (MSR).............................................................. 17
Authorization Recycling ................................................................................. 17
Reporting.................................................................................................... 17
Data Storage ............................................................................................... 18
24-Hour Technical Support ................................................................................. 18
Merchant Requirements ..................................................................................... 18
Setup Process................................................................................................... 18

Chapter 2 Getting Started .................................................................................. 19

Initial Account Setup ......................................................................................... 19
About User IDs and Passwords ............................................................................ 19
Authorized Contact Security........................................................................... 19
Functional Access Security............................................................................. 20
Login and Password Delivery.......................................................................... 20
Accessing the Virtual Terminal ............................................................................ 22
Overview of VT Usage........................................................................................ 24
The User Interface........................................................................................ 25
Searching ................................................................................................... 27
Using the Online Help ................................................................................... 29
About Batches ............................................................................................. 29

Chapter 3 Working with New Orders.................................................................. 30

Processing a Credit Card Purchase (Authorization and Capture) ............................... 30

Page 3 of 214
Orbital Virtual Terminal
Version 4.2

Processing a Credit Card Refund.......................................................................... 34

Processing a Prior Authorization .......................................................................... 36
Processing Account Verification ........................................................................... 39
Processing an Electronic Check Transaction........................................................... 41
Processing a UK Maestro/Solo Transaction ............................................................ 44
Processing European Direct Debit ........................................................................ 48
Processing a Bill Me Later Purchase...................................................................... 50
Processing a Bill Me Later Refund ........................................................................ 53
Processing a PINless Debit Transaction................................................................. 54
Advanced Features for Transaction Processing....................................................... 56
Use Profiles ................................................................................................. 57
Add Profiles ................................................................................................. 58
Add Managed Billing ..................................................................................... 58
Selecting Soft Descriptors.............................................................................. 58

Chapter 4 Working with the Open Batch ............................................................ 59

Searching for a Transaction in the Open Batch ...................................................... 59
Results Output............................................................................................. 60
Viewing Transaction Details ................................................................................ 62
Adding a Profile............................................................................................ 65
Viewing the Order History (Audit Trail) ............................................................ 66
Marking a Successful Authorization for Capture ..................................................... 67
Unmarking a Captured Transaction ...................................................................... 67
Adjusting Purchasing Card Data .......................................................................... 68
Voiding a Transaction ........................................................................................ 69
Settling All Marked for Capture, Credit, and Force Transactions................................ 71
Splitting a Transaction into Separate Shipments .................................................... 72

Chapter 5 Reviewing Post-Settlement Data ....................................................... 76

Searching for Batches ........................................................................................ 76
Results Output............................................................................................. 76
Reviewing a Closed or Pending Batch .............................................................. 79
Reviewing a Rejected Batch ........................................................................... 80
Viewing a Transaction in a Closed, Pending, or Rejected Batch............................ 82
Searching for Transactions ................................................................................. 83
Results Output............................................................................................. 84
Viewing Transaction Details ................................................................................ 86
Adding a Profile............................................................................................ 88
Initiating a Credit from an Order (Quick Credit) ................................................ 89
Viewing the Order History (Audit Trail) ............................................................ 90

Page 4 of 214
Orbital Virtual Terminal
Version 4.2

Chapter 6 Administering the Virtual Terminal .................................................... 92

Profile Management........................................................................................... 92
Configuring Account Updater .............................................................................. 92
Schedule of AU Requests............................................................................... 95
AU Default Merchant Number ......................................................................... 96
Configuring Automatic E-mail Messages to Cardholders .......................................... 97
Setting Preferences for Managed Billing ...............................................................101
Setting Preferences for PINless Debit ..................................................................101
Setting Preferences for Authorization Recycling ....................................................102
Setting Preferences Related to Gift Card Redemptions ...........................................103
Partial Redemption Auto Authorization ...........................................................103
Remaining Balance Capture Setting ...............................................................103
Setting General Preferences...............................................................................104
Purchase Card Prompt on Mark For Capture ....................................................106
View/Enter Card Number..............................................................................107
Remove Auth or Auth/Capture Button ............................................................107
Mandatory AVS ...........................................................................................107
Two Step Settlement Process ........................................................................107
Auto Settle.................................................................................................107
Attempt Authorization Reversal When Voiding .................................................108
Partial Authorization ....................................................................................108
Selecting Purchasing Card 3 Units of Measure ......................................................109
Specifying Information to Appear on Receipts.......................................................109
Configuring Scheduled Reports...........................................................................111
Card Account Truncation ..............................................................................111
Scheduled Reports ......................................................................................111
On Demand Reports ....................................................................................114
Chain Level Reports.....................................................................................115
Selecting Response Codes to Automatically Decline ...............................................116
Setting Preferences for Soft Descriptors ..............................................................118
Salem Support............................................................................................119
PNS/Tampa Support ....................................................................................120
Setting Descriptors......................................................................................120

Chapter 7 Working with Reports ...................................................................... 124

About Reports .................................................................................................124
Locating Reports .........................................................................................124
Retrieving and Saving Reports ......................................................................125

Chapter 8 Working With Profiles...................................................................... 126

About Profiles and Managed Billing .....................................................................126

Page 5 of 214
Orbital Virtual Terminal
Version 4.2

Creating a Profile .............................................................................................126

Creating a Profile as a Distinct Action .............................................................126
Creating a Profile When Processing a Transaction.............................................129
Locating an Existing Profile ................................................................................131
Search by ADMIN > Profile Management.........................................................131
Search by NEW ORDER ................................................................................132
Using a Profile in a Transaction ..........................................................................133
Editing a Profile ...............................................................................................134
Profile Status...................................................................................................135
Change Log .....................................................................................................137

Chapter 9 Managed Billing ............................................................................... 139

Billing Schedule ..........................................................................................139
Scheduled Billings .......................................................................................145
Completed Billings.......................................................................................148
Change Log ................................................................................................148

Chapter 10 Working with Purchasing Cards ..................................................... 150

Entering Purchasing Card Data for a Purchase ......................................................150
Entering Purchasing Card Data for a Purchase Card Credit/Refund...........................155

Chapter 11 Working with Gift Cards................................................................. 157

Merchant Account Set up..............................................................................157
Processing a New Gift Card Transaction ...............................................................157
Performing a Gift Card Authorization ..............................................................158
Performing a Gift Card Sale (Redemption) ......................................................159
Performing a Prior Redemption......................................................................159
Adding Funds to a Gift Card Balance ..............................................................160
Performing a Prior Add Value ........................................................................160
Refunding a Purchase Value to a Gift Card ......................................................161
Viewing the Balance Available on a Gift Card ........................................................161
Gift Card Activation ..........................................................................................162
Activating a Single Gift Card .........................................................................162
Activating a Block of Gift Cards .....................................................................164
Reactivating a Gift Card ...............................................................................166
Deactivating a Gift Card ...............................................................................166
Prior Activation of a Gift Card........................................................................167
Working with Gift Card Batches ..........................................................................167
Viewing Current Transactions (Open Batch) ....................................................168
Viewing Historical Transactions (Closed Batches) .............................................173

Chapter 12 Importing a File ............................................................................. 179

Creating a CSV File......................................................................................179

Page 6 of 214
Orbital Virtual Terminal
Version 4.2

Importing a CSV file ....................................................................................179

Checking the Status of a CSV file...................................................................180
CSV-generated Reporting .............................................................................180
Limitations of the File Import feature .............................................................180

Appendix A Partial Authorizations ................................................................... 181

Appendix B Codes Reference ........................................................................... 183

Response Codes...............................................................................................183
AVS Response Codes ........................................................................................190
CVV2/CVC2/CID Response Codes .......................................................................191

Appendix C Merchant Selectable Response Codes............................................ 193

AVS Response Codes ...................................................................................193
Verification Response Codes .........................................................................194

Appendix D Profile Response Codes ................................................................. 196

Appendix E Overview of Credit Card Processing............................................... 198

What are Credit Cards? .....................................................................................198
What is Payment Processing?.............................................................................198
Credit Card Transaction Flow .............................................................................198

Appendix F Split Shipment Process Flow.......................................................... 200

Appendix G Auto E-mail Cardholder Text ......................................................... 201

CARDHOLDER E-MAILS .....................................................................................201
EXPIRING CARD..........................................................................................201
TRANSACTION DECLINED.............................................................................201
SUCCESSFUL BILLING..................................................................................201
AMOUNT TO BE CHARGED ............................................................................202
ACCOUNT CLOSED ......................................................................................202
NEW ACCOUNT NUMBER/EXP DATE ...............................................................202
MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL ...203
EXPIRING CARD..........................................................................................203
TRANSACTION DECLINED.............................................................................203
SUCCESSFUL BILLING..................................................................................204
AMOUNT TO BE CHARGED ............................................................................204

Appendix H Reporting ...................................................................................... 205

OPEN BATCH REPORTS ................................................................................205
REVIEW BATCH REPORTS .............................................................................205
PROFILE QUERIES .......................................................................................207
EVENT DRIVEN REPORTS .............................................................................208
SCHEDULED REPORTS – MERCHANT LEVEL.....................................................209
SCHEDULED REPORTS – MERCHANT LEVEL – MANAGED BILLING.......................212

Page 7 of 214
Orbital Virtual Terminal
Version 4.2

SCHEDULED REPORTS – CHAIN LEVEL ...........................................................212

Page 8 of 214
Orbital Virtual Terminal
Version 4.2

Common Tasks
To log on to the Virtual Terminal .............................................................................. 22
To process a basic credit card purchase..................................................................... 31
To process a credit card refund ................................................................................ 35
To locate a generated report...................................................................................124
To Retrieve and Save Reports .................................................................................125
To create a profile .................................................................................................126
To Process a Transaction........................................................................................134
To edit a profile ....................................................................................................134
To change a profile status ......................................................................................136
To delete a profile .................................................................................................136
To view the history of profile changes ......................................................................137
To establish a Merchant Level recurring billing pattern................................................140
To establish a Merchant Level recurring billing pattern................................................141
To establish the Order Number parameter ................................................................143
To add Deferred Managed Billing to a profile .............................................................143
To remove Managed Billing at the Profile level...........................................................147
To remove Managed Billing at the Merchant level.......................................................147
To view the history of profile changes ......................................................................148

Page 9 of 214
Orbital Virtual Terminal
Version 4.2

List of Tables
Table 1 Orbital Gateway Support Center contact details............................................. 18
Table 2 Response code values ..............................................................................183
Table 3 AVS response code values ........................................................................190
Table 4 CVV request response code values .............................................................191
Table 5 AVS Response Codes for MSR ....................................................................193
Table 6 Verification Response Codes for MSR ..........................................................194
Table 7 Profile Response Codes.............................................................................196

Page 10 of 214
Orbital Virtual Terminal How to Use this Guide
Version 4.2 Who Should Read this Guide

How to Use this Guide

This guide describes the Chase Paymentech Orbital Virtual Terminal Web application. It
describes the features and functionality of the application and provides step-by-step
instructions for most of the tasks you can perform.

Who Should Read this Guide

Use this documentation if your job involves using the Orbital Virtual Terminal application.
This documentation assumes you are familiar with the following:
General credit card and payment processing concepts.

Organization of this Guide

The information in this documentation is presented as follows:
Chapter 1, Introduction, provides introductory information about Orbital Virtual
Terminal, an overview of the software, and descriptions of the main features with links
to where they are documented in the guide.
Chapter 2, Getting Started, provides information and procedures for starting up and
shutting down the software, basic use of the interface, and using the online help.
Chapter 3, Working with New Orders, provides information on how to process various
transactions using different methods of payment.
Chapter 4, Working with the Open Batch, provides information on how to view unsettled
transactions on-screen or via reports.
Chapter 5, Reviewing Post-Settlement Data, provides information on how to view settled
transactions on-screen or via reports.
Chapter 6, Administering the Virtual Terminal, outlines the various administrative
functions that can be performed via the Virtual Terminal, based on user privileges.
Chapter 7, Working with Reports, describes all the reports that are available to
merchants and how to configure scheduled reports or generate on-demand reports.
Chapter 8, Working With Profiles, provides information on how to create, edit, and use
profiles for transaction processing.
Chapter 9, Managed Billing, provides information on how to set up Managed Billing at
the merchant or profile level.
Chapter 10, Working with Purchasing Cards, provides instructions on how to process
transactions containing Purchasing Card Level II and III information.
Chapter 11, Working with Gift Cards, describes all Gift Card related transactions that can
be processed via the Virtual Terminal along with how to view and generate Gift Card
reports.
Chapter 12, Importing a File, provides instructions on how to import a CSV file for
processing of transactions.

Related Documentation
The following Chase Paymentech documentation contains information to which you may
need to refer:

Page 11 of 214
Orbital Virtual Terminal How to Use this Guide
Version 4.2 What's New in this Release

Orbital Credit Card Processing 101 Guide

Managed Billing Supplemental Guide [Includes Profile Management information]
Orbital Virtual Terminal Quick Reference Guide
These documents are available from the Orbital Integration Library.
You may also need to refer to the Certification Documentation for the platform (Salem or
Tampa) your Merchant account uses. For Tampa merchants, this document is available from
the Orbital Integration Library. Salem merchants should contact your Certification Analyst.

What's New in this Release

Release 4.2 of Orbital Virtual Terminal provides the following new or modified features:

New Features
Several new features have been added to this guide, including Account Updater and Partial
Authorization functionality. For more information on these features, please see the
individual chapters.

New Reports
New reports may have been added in this release. As always, you only have access to the
reports related to features enabled for your Merchant ID. For a description of each individual
report, see the help topics available on the Reporting Admin page.

Using the PDF Version of this Guide

This guide is designed to be viewed in electronic form as a Portable Document Format (PDF)
file. When you use Adobe® Reader® to view this file electronically, you can make use of the
following features of this document:
Open the Bookmarks panel on the left side of the Adobe Reader window to view an
expandable/collapsible outline of the document and click on a bookmark to jump to a
topic.
Click on a hyperlink (indicated by blue underlined text, such as the Adobe Reader link
above) to navigate to a Web page related to the text. All hyperlinks to Internet pages
are defined to open a new browser window.
Click on a cross-reference (indicated by light blue italic text) to jump to the indicated
location in this document.
The items in the Table of Contents, Table of Figures, and Table of Tables at the
beginning of this guide are also clickable hyperlinks to locations in this document.
This PDF file is enabled for commenting in Adobe Reader. If you download the PDF file to
your computer, you can use the Adobe Reader commands available under Tools >
Comment & Markup to add electronic post-it notes, highlights, circles and arrows, and
other such elements wherever you want and save them with the file.

Conventions Used in this Guide

To help you find important information, this guide uses the following conventions:

This convention Indicates

Page 12 of 214
Orbital Virtual Terminal How to Use this Guide
Version 4.2 Conventions Used in this Guide

This convention Indicates

Bold The names of elements of the user interface, such as menus, buttons, and
options.
Monospaced Code, file names, directory paths, and on-screen computer output.
bold monospaced Text you should type exactly as shown, such as:
Type xyz in the Order ID box.

Italics Book titles, new words or terms, or words to be emphasized.

Bold Italic Terms defined in the Glossary.

NOTE Notes that contain additional explanation.

TIP Tips that contain shortcuts or special information.

CAUTION Cautions that contain information to avoid errors.

WARNING Warnings that contain information about potentially damaging actions. Read
them carefully.

SEE ALSO Cross-references that tell you where you can find additional information about a
topic. These references may also occur in the main body of the text. You can
click on the blue text to jump to the referenced section.

Page 13 of 214
Orbital Virtual Terminal Chapter 1 Introduction
Version 4.2 Features and Benefits

Chapter 1 Introduction
The Orbital Virtual Terminal is an Internet-based point of sale terminal for key entered
transactions. It includes a full suite of features to authorize and settle Card-Not-Present
(CNP) transactions. All transaction data and applications are hosted securely on Chase
Paymentech servers.
Chase Paymentech has two locations, Tampa and Salem, each configured as a different
platform. Virtual Terminal merchants are configured on either the Tampa platform or the
Salem platform. Both platforms are significantly similar; however, the Salem platform has a
few additional features that are not supported on the Tampa platform. This guide will define
the differences. If you are unsure which platform you have been assigned, please contact
your account representative or the Gateway Support Center.
All you need to access the Orbital Virtual Terminal is an Internet connection and a Web
browser that supports 128-bit encryption. No additional hardware, telephone lines, or other
technical integration is required. Using the online terminal, you enter order information to
initiate authorizations, settlements, refunds, and other transactions. The Orbital Virtual
Terminal allows different security levels among users, as well as multi-user access.
Additionally, all credit card data is masked unless you specify that the full credit card
number be visible.

Features and Benefits

The Orbital Virtual Terminal serves as a direct interface to Chase Paymentech, allowing
authorizations, captures, credits, voids, voice-authorization captures, and end-of-day
settlement. The Virtual Terminal (VT) also provides tools such as Merchant-Selectable
Response (MSR), Customer Profile Management, Managed Billing, and Authorization
Recycling. These additional tools are explained in later sections.

Payment Methods and Tools

The Orbital Virtual Terminal supports the full range of payment methods offered by Chase
Paymentech, including:
American Express MasterCard PINless Debit*
Bill Me Later* Visa UK Maestro*/Solo*
Discover Card Gift Card (formerly Electronic Check transactions*
FlexCache)
JCB European Direct Debit (EUDD)*

The Orbital Virtual Terminal also supports:

Purchasing Card Level II and Level III data input (including American Express Level II
data for Salem merchants)
All Chase Paymentech-supported international currencies*
Soft Descriptors*

* Not available to all merchants; only supported on Salem host.

Page 14 of 214
Orbital Virtual Terminal Chapter 1 Introduction
Version 4.2 Features and Benefits

The Orbital Virtual Terminal includes support for the following fraud protection components:
Address Verification Service (AVS) (US only)
American Express Card Identification Number (CID) (US and International)
Visa Card Verification Value 2 (CVV2) (US and International)
MasterCard Card Validation Code 2 (CVC2)
Account Verification
Salem Fraud Filters (Not offered directly through the Virtual Terminal. Please refer to
your Account Executive for more details.)
Currently, the Orbital Virtual Terminal does NOT support: Private Label or Chase
Paymentech’s Flexible Payment Options. Some or all of the unsupported features may be
included in future product upgrades.

Auto-Settle Feature
Captured transactions may be settled manually or through the Auto-Settle Feature. This
feature permits the selection of a specific time for captured transactions to be settled.
Merchants select the auto-settle time and time zone during the setup process. Settlement
times are available in convenient 15-minute intervals. If Auto-Settle is not selected during
the initial setup process, it may be implemented at a later date by contacting the Gateway
Support Center or configuring it via the Virtual Terminal ADMIN menu tab.

Duplicate Checking
As a precaution, the VT checks for duplicate transactions. If a possible duplicate order is
detected, the VT will notify you and force you to choose to continue with the transaction or
to cancel the transaction. The account number, amount, and order ID are used to determine
if the transaction may be a duplicate.

Security Features

Authorized Contact Security

This level of security addresses permissions regarding the establishment and change of User
IDs and Passwords. Chase Paymentech stores a merchant’s authorized contact list in the
system. It is used to verify the identity of a caller requesting a change and to ensure the
caller has the “rights” to make such a change. Additionally, e-mail addresses are filed for
those who want to receive e-mail alerts regarding upcoming maintenance and/or releases.

Advanced Transaction Security

Only an Authorized Contact may establish or approve a new User and the associated
transaction processing authority. The following VT User roles are available:
Everything Allowed
Authorize
Mark for Capture
Split
Void
Credit or Reversal

Page 15 of 214
Orbital Virtual Terminal Chapter 1 Introduction
Version 4.2 Features and Benefits

Settle
Read Only

Functional Access Security

Additional permissions or limitations to various functionalities are assigned on a per User
basis through the Orbital Gateway Support Center at the direction of an Authorized Contact.
Examples include Reporting Administration, Profile Management, and Reporting Access.

Application Security
The Virtual Terminal provides four separate ways of protecting access to your transaction
data:
Two-tiered logon process. All Users must enter their user name and password.
Access rescinded after five incorrect logon attempts. After five login attempts
with an invalid User/Password combination, the login is suspended. You may call the
Orbital Gateway Support Center to have the login reset but must be able to authenticate
yourself.
Multiple levels of User access. The primary contact receives a user name and
password by separate e-mails. For security reasons, these are normally sent several
hours apart. The primary contact person can contact Orbital Gateway Support Center to
add, delete, or change Users and assign multiple levels of access.
Masking of Credit Card Number. User assigned rights determine which Users can
view the full credit card number and which are restricted to a truncated view of the card
number. Those with a truncated view only see the last 4 numbers of the credit card
number. Masking is the default setting.

Transaction Security
All your data is protected with the industry standard Secure Socket Layer (SSL)
communication protocol. All data transmissions are encrypted at 128 bits. Our production
network is protected with a series of firewalls to prevent any unauthorized access to our
servers.

Profiles and Managed Billing

The Orbital Gateway includes functionality called Customer Profile Management, which
allows cardholder data to be stored with the Orbital Gateway. You can use the VT to create
and manage Profiles. When using the VT to process a transaction, you can use the Profile ID
to populate some of the information in the transaction. You can override any of this stored
information, as needed, and fill in any additional information not stored in the Profile for the
individual transaction.
Released in March of 2008, Managed Billing extends the capabilities of Profiles to include
Recurring, Installment, and Deferred billing. Using this feature, merchants can configure
future payments that the Orbital Gateway will initiate on the desired date.

Benefits
There are a number of potential benefits when using the Profiles feature:
It simplifies transaction processing. When making a transaction request, one simply
finds the Profile ID (sometimes called the Customer Reference Number) and fills in any
of the missing information.

Page 16 of 214
Orbital Virtual Terminal Chapter 1 Introduction
Version 4.2 Features and Benefits

It eliminates risk. Since it eliminates the need to store sensitive information about a
merchant’s customer on their database, merchants can focus on their business, and
Chase Paymentech can focus on securely processing their transactions.
It can eliminate data entry errors. By retrieving a pre-existing Profile and validating the
data, the risk of keying the wrong customer information, such as credit card number, is
eliminated.

Setup Information
For an Orbital Gateway Merchant ID to support Profiles, it must be configured on the Orbital
System to do so. There are several different configuration parameters that must be set up.
Merchants also wishing to use Managed Billing to support recurring, installment, or deferred
charges must have the Managed Billing feature enabled for their account. A Merchant
Contract Addendum is required to enable the Managed Billing feature, so interested
merchants should contact their Sales Representative or Account Executive.
SEE ALSO For more information on creating and using Profiles, see Working With Profiles.

Merchant Selectable Response (MSR)

Merchant Selectable Response protects merchants from fraud while providing them with the
ability to control their risk exposure. With Merchant Selectable Response, merchants can
configure the Orbital system to decline transactions based on predefined rules for AVS
(Address Verification Service) and CVD (Card Verification Data).

Authorization Recycling
Authorization Recycling provides automated reauthorization attempts for transactions that
receive declines, specifically soft declines, from issuing banks.

Reporting

Financial Reporting
Orbital Virtual Terminal transactions appear on the standard Chase Paymentech financial
reports. Transaction-level detail can be viewed via the Virtual Terminal and online reporting
tools, such as Paymentech Online and Resource Online. Please contact Orbital Gateway
Support Center or your Chase Paymentech Account Executive for additional information on
reporting.

Transaction Reporting
Transaction level reporting based on activity processed through the Virtual Terminal is also
available to merchants. Reporting can be retrieved based on an assortment of parameters
including open, unsettled transactions to closed, settled transactions.

Scheduled Reporting
For merchants using features such as Profile Management, enhanced reporting is available.
These reports can be scheduled at a daily, weekly, or monthly frequency and can be e-
mailed, sent via SFTP, or retrieved via the Virtual Terminal interface.

Page 17 of 214
Orbital Virtual Terminal Chapter 1 Introduction
Version 4.2 24-Hour Technical Support

On Demand Reporting
Many of the scheduled reports are also available on a per demand basis. Merchants may
select date range parameters and the report of their choice which can be retrieved via the
Virtual Terminal.

Data Storage
At any time, users can view transactions in either a pending status, known as Open Batch,
or processed status, found under the REVIEW menu tab. Additionally, reports with up to 11
months of history can be run by querying selected data parameters. Most are available in
PDF formats, CSV files, or viewed on screen.

24-Hour Technical Support

Around-the-clock application support is available for VT users via telephone or e-mail.
Please call or e-mail if you have a question. Our support associates are always available to
assist you.
Table 1 Orbital Gateway Support Center contact details

Phone 1-866-645-1314

E-mail [email protected]

Merchant Requirements
Technical: The Orbital Virtual Terminal runs on computers with browsers that support
128-bit encryption. A User may connect via any type of Internet access (dial-
up, DSL, cable, T1, and so on).
Minimum browser and operating system requirements are:
Windows NT, 2000, 98 and XP: Internet Explorer 6.0 and/or Netscape 6.2
Windows NT, 2000 and 98: Internet Explorer 5.5 and/or Netscape 4.79
Macintosh OS X: Internet Explorer 5.0
Other: New merchants must complete a Chase Paymentech merchant application and
receive processing approval.

Setup Process
For details regarding the setup process, please contact your Chase Paymentech Account
Executive or Sales Representative.

Page 18 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Initial Account Setup

Chapter 2 Getting Started

The Orbital Virtual Terminal provides many features and allows you to enable or disable
those that best meet your business needs. Value-added functions are enabled or not, based
on the various choices made at the time the merchant account is set up and by the
permissions/authorities granted to each user.
To simplify learning about the VT and processing transactions, only the enabled functions
are visible to users. For example, if the merchant is set up for Gift Card (formerly
FlexCache) transaction processing, the associated subject tab and related pages will appear.
If the merchant is not enabled for processing Gift Card transactions, this tab and associated
pages will not be visible to users. Consequently the manner in which the merchant account
is established, the administrative functions selected, and user permissions assigned will
influence which pages are presented as well as the information and choices available.
NOTE This guide describes all of the features available in the VT, using a merchant account with all of the
features enabled (and, therefore, visible). Because your merchant account may not have all features
enabled, you may not see all of the menus/commands/pages described and illustrated in this guide.

Initial Account Setup

In order to begin using the Virtual Terminal, you must get set up with a Merchant account.
Upon successful setup, you will be issued a User ID and Password for logging into the
Virtual Terminal. Please contact your Account Representative or Sales Representative for
more information on getting set up for Virtual Terminal.

About User IDs and Passwords

Prior to accessing the Virtual Terminal, the merchant setup process with Chase Paymentech
Solutions and the Orbital Virtual Terminal must be completed. As part of that process,
selections are made as to the payment methods and the tools to be used. Additionally,
various security decisions regarding users are registered.

Authorized Contact Security

The merchant must provide an authorized contact list to Chase Paymentech. It is used to
verify the identity of a caller requesting a change to the Virtual Terminal and to ensure the
caller has the correct privileges to make such a change. E-mail addresses are registered for
those individuals designated to receive e-mail alerts regarding upcoming maintenance
and/or releases. The following authority options, also known as Admin Rights, are available
for users. Minimally one user must be given the highest level of permissions, to Add
/Delete/Reset all User IDs:
Add/Delete/Reset all User IDs and:
 Specify which Contacts receive e-mail notifications
 Authorize enablement of various Orbital Gateway functionalities
 Determine display structure of customer account number
Reset passwords for all Users
Reset password for only this User
No right or permission

Page 19 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 About User IDs and Passwords

Functional Access Security

An individual User may be assigned additional permissions or limitations by the Orbital
Gateway Help Desk at the direction of the merchant’s Authorized Contact. Please note that
for those identified with an ‘ * ’, the functionality must first be enabled at the merchant
level. Your Account Representative can assist with this.
Mask Account Numbers
Reporting Admin
General Admin
Profile Management
 No Roles – User will not see any Customer Profiles or any reference to Customer
Profiles.
 User Role – User may only use and view customer profiles.
 Administrator Role – User can create, update, view, use and delete Customer
Profiles.
MSR (Merchant Selectable Response) Admin*
Gift Card [also known as FlexCache]*
Soft Descriptor*
VT File Import*
Purchase Level III Administration*
Reporting Access
Receipt Admin*
Managed Billing Admin*
Auth Recycling Admin*
Auto E-mail Service Admin*
PINless Debit Admin*
Account Updater Admin*
NOTE User rights may be changed by contacting our helpdesk. An Authorized Contact must request the
change.

Login and Password Delivery

A User is sent two e-mails, one containing the temporary password and one with the User
ID, after being set-up by Chase Paymentech Solutions. With this information, the User may
login to the Virtual Terminal. Once you have entered your User ID and temporary password,
you will be prompted to reset your password.

Page 20 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 About User IDs and Passwords

Password Guidelines
The new password must be a minimum of 8 characters with at least one alpha and one
numeric character.
The number may not be in the first position.
The new password must be different from your previous password(s).
No special characters may be used.
Remember that the password is case-sensitive.
After three login attempts with an invalid User/Password combination, the login will be
revoked. To reset the login, an Authorized Contact must call or e-mail the Gateway Support
Center and provide the following information:
Merchant Number/Division Number
User Name
Company Name
Phone Number
Primary Address

Forgotten Password
In the event the password is forgotten, you can click on the Forgot Your Password hyperlink
where you’ll be prompted for your User ID and e-mail address. Upon successful entry of this
information, a temporary password will be e-mailed to you. Once you have entered your
User ID and temporary password, you will be prompted to reset your password again.

Page 21 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Accessing the Virtual Terminal

Accessing the Virtual Terminal

Since Orbital Virtual Terminal is a Web application, you can access it via a Web browser.

To log on to the Virtual Terminal

1 Open a browser window and navigate to https://secure.paymentech.com/login.
TIP If you are viewing this guide electronically, you can simply click on the hyperlink above to open
a new browser window to the Chase Paymentech Login Page.

Page 22 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Accessing the Virtual Terminal

Figure 1 Logging on to Virtual Terminal

NOTE For security reasons, VT will automatically log you out after 20 minutes of inactivity, as
indicated on this page.

2 Enter your UserID and Password, and then click on Login.

3 If your password has expired, you are prompted to define a new password.
VT passwords expire every 90 days. See About User IDs and Passwords for information
on password rules.
4 If your user ID is associated with multiple merchant accounts, you are prompted to
select the Merchant ID you want to work with in VT.
A Merchant ID can be associated with only one currency, so, if you process transactions
in multiple currencies, you will have one Merchant ID for each currency. Select the
Merchant ID for the currency you want to work in – you can switch to another without
logging out of VT.

Page 23 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

Figure 2 Choosing a Merchant ID

5 Select the desired Merchant ID.

The application opens to the New Order - Auth page.

Overview of VT Usage
As a Web application, the Virtual Terminal displays each function on a separate page (for
example, Figure 3 shows the page you use to submit a new purchase transaction for
authorization or authorization and capture). Each page presents a set of similar features, as
illustrated and described below.

Page 24 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

The User Interface

Figure 3 Parts of the VT user interface

VT session links
At the top of each page, there are links you can click on to affect your VT session.
Figure 4 VT session links

A User can be associated with multiple Merchant IDs. If so enabled, you can switch to
another Merchant ID without logging out of VT.

Page 25 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

Menu to access VT Functions

The VT menu bar is available at the top of each page. You can select items in the menu to
access the functions you perform in VT.
NOTE Because your merchant account may not have all features enabled, you may not see all of the
menus/commands/pages described and illustrated in this guide.

Figure 5 VT menu bar

Information about Merchant ID

When you log on to VT, you are either:
Immediately set to use the only Merchant ID associated with your User ID.
Prompted to select which of the Merchant IDs associated with your User ID you want to
use.
Information about the Merchant ID you are using is displayed on each page in VT.
Figure 6 Information about Merchant ID

Note that this area displays the currency associated with the Merchant ID you are using.
The Orbital Gateway will consider all monetary amounts you enter on any of the VT pages to
be of this currency.

Pages with tabs

Several of the pages accessed from the NEW ORDER menu contain tabs to include
additional information related to the transaction, in particular, optional and Purchasing Card
data.

Page 26 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

Figure 7 Tabs on page

To enter optional or Purchasing Card data related to the transaction you are processing,
simply click on the tab and fill in the fields.

Command buttons
At the bottom of each page, there are command buttons you can use to act on the data you
have entered or selected on the page. For example, you can use various command buttons
to submit a transaction for processing, run a search, retrieve a report, save configuration
changes, or clear any changes you have entered.
Figure 8 Command buttons on a page

Symbols used on different pages

Required field. You must specify a value for this field.

Conditionally required field. Generally, this field is required if you specify a value for
another (related) field.

Note applies to this field. Look on the right side of the page for an explanation.

Online Help available. See Using the Online Help below for more information.

Field related to the Customer Profile Management feature. If your merchant

account is not configured for this feature, these fields are not visible.

Searching
On pages accessed via the OPEN BATCH, REVIEW, REPORTING, and IMPORT FILE
menus, you can search for a transaction, batch, report, or imported file.

Page 27 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

Figure 9 Searching in the Open Batch

The search functionality works the same in each case:

1. Select or enter values for certain fields to specify your criteria for the search.
 For some fields, you can enter a partial value (as indicated by )—one or more
characters that the item begins with. For example, you could search for transactions
where the Order # begins with 82.
 The more criteria you enter, the fewer results you will need to sift through to find
what you are looking for. For example, searching for only Void transactions where
the Order # begins with 82 and the transaction amount is between $100 and $200
will probably return fewer results than just searching for transactions where the
Order # begins with 82.
2. Then click on Search to get the results that match your criteria.
If there are no matches, you will see:

3. Then use the command buttons displayed with the results to perform other actions.

Page 28 of 214
Orbital Virtual Terminal Chapter 2 Getting Started
Version 4.2 Overview of VT Usage

Using the Online Help

Certain fields or entire pages have related online help. These are identified with the icon.
You can click on this icon to open a separate window containing extra text. This text may
expand on information provided in this guide or include information that is updated more
often than this guide.
Figure 10 Sample Online Help window

There is a Close button at the bottom of the help text to close the window when you are
done.

About Batches
Each time you submit a transaction with one of the features available from the NEW
ORDER menu, the transaction is added to the Open Batch. There is only one such batch
open at a time, and you can interact with these transactions using the features available
from the OPEN BATCH menu tab until the batch is submitted for settlement (see Working
with the Open Batch).
When the Open Batch is submitted (automatically or manually) for settlement, the batch is
closed, and a new batch is opened for subsequent transactions. You can interact with closed
batches using the features available from the REVIEW menu tab (see Reviewing Post-
Settlement Data).
NOTE Transactions that cannot be settled remain in the Open Batch.

Page 29 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Purchase (Authorization and Capture)

Chapter 3 Working with New Orders

You can use the options on the NEW ORDER menu to process a variety of transactions,
with the exception of Gift Card. The procedures for using each option are included in this
chapter, in the order that they appear:

Authorize Processing a Credit Card Purchase (Authorization and Capture)

Credit Processing a Credit Card Refund

Force Processing a Prior Authorization

Account Verification Processing Account Verification

Electronic Check Processing an Electronic Check Transaction

UK Maestro-Solo Processing a UK Maestro/Solo Transaction

European Direct Debit Processing European Direct Debit

BML Authorize Processing a Bill Me Later Purchase

BML Credit Processing a Bill Me Later Refund

PINless Debit Processing a PINless Debit Transaction

NOTE Only the methods of payment enabled for your merchant are visible.

For credit card and Bill Me Later transactions, different options (and thus different
application pages) are used for debit/payment and for credit/refund transactions.
For Electronic Check, UK Maestro/Solo, and PINless Debit transactions, you use the
corresponding option to access a single page from which you can submit both payment and
credit transactions.
CAUTION You may have internal standards for limitations on data (the maximum transaction amount is
$5000.00, or we only ship orders to Florida, Georgia, or Alabama) or procedures (enter a customer
phone number on all credit card purchases, or always enter a card verification number) that
supplement or override the procedures in this guide.

NOTE If configured for your merchant, you can create Profiles storing cardholder information and use a
Profile to fill in many of the fields for a transaction. You can always override any of these values for
the individual transaction. See Working With Profiles, for more information.

Processing a Credit Card Purchase (Authorization and Capture)

You can use the NEW ORDER > Authorize option to open the New Order - Auth page,
where you enter information for a credit card purchase transaction and perform an
Authorize and Capture or just an Authorization.
Action Description

Auth Requests an authorization for the transaction. Use this option if the
items in the transaction will be billed at a later date, at the time of
shipment for example.

Auth and Capture Requests an authorization for the transaction and, after receipt of
the authorization, marks the transaction for capture. The
transaction is included in the next settlement cut.

Page 30 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Purchase (Authorization and Capture)

The New Order - Auth page has four tabs:

RECOMMENDED DATA Required for all credit card purchases
OPTIONAL DATA Optional for all credit card purchases
PURCHASING CARD DATA II Optional; for Purchasing Card purchases
PURCHASING CARD DATA III Optional; for Purchasing Card purchases
NOTE If you are not configured to process Purchasing Card transactions, the Purchasing Card tabs are not
visible. Information related to Purchasing Card data is contained in Working with Purchasing Cards.

To process a basic credit card purchase

1 If necessary, select NEW ORDER > Authorize to open the New Order - Auth page.
The RECOMMENDED DATA tab is displayed.
Figure 11 Entering purchase data

The Credit Card Types Accepted list contains the methods of payment configured for
your merchant account that may be processed on this page. The list is for informational
purposes only.

Page 31 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Purchase (Authorization and Capture)

NOTE The Card Number, Expiration Date, Amount, and Order ID # fields are required.
The customer address information (particularly Postal Code) may be required based on your
merchant settings.

TIP While not all fields on the RECOMMENDED DATA tab are required, it is considered a best
business practice to submit them with every transaction. To avoid higher Interchange fees on
Visa transactions, merchants should, at a minimum, submit the 5-digit postal code for AVS
transactions. Submitting a Card Verification code can offer additional chargeback protection.

2 In the Card Number box, enter the credit card number.

Do not include spaces.
NOTE If so configured, when you enter a number that the system recognizes as a Purchasing Card
(based on the card association's published BIN ranges) and you do not enter information on the
Purchasing Card Data tabs, the VT prompts you to enter Purchasing Card data when you submit
the transaction. See Entering Purchasing Card Data for a Purchase for more information.

3 In the boxes next to Expiration Date, select the month and year the card expires.
4 Enter the total Amount of the transaction.
The Amount must include all taxes and fees (shipping and handling) for the purchase.
The maximum amounts allowed by the Orbital Gateway vary based on card type and
platform (Salem or Tampa) and may be further limited for your merchant account. Refer
to your internal processes for the minimum and maximum amounts you can enter.
5 Enter the Card Verification #.
 Visa/MasterCard/Discover: 3 digits found on the signature panel on the reverse side
of the credit card.
 American Express: 4 digits printed, not embossed, on the front of all cards. On the
American Express card it appears on the right border of the card. On Optima cards,
however, it appears on the left border of the card.
NOTE American Express CID only works if your American Express account is activated for this
program by American Express. Contact American Express directly for more information.
When American Express CID is used, it behaves differently than MasterCard and Visa
CVC2/CVV2. If you do not have a matching CID value, American Express declines the
transaction. If your CID does match, then the transaction is approved assuming all other
criteria are met. There are no response values specific to CID usage.

6 In the Order ID # box, enter an order number, following your internal guidelines. This
should be a unique number.
7 Enter the customer address information.
If entering a non-U.S. address, click on the Non US Address check box. The State field
is set to Non-US, a Country Code field is added for you to select the country from a
list, and the Postal Code field changes to a single box to accommodate non-U.S. postal
code formats.
8 Enter the Customer Name and Customer Phone number.
9 Enter an Order Description.
10 If desired, select the OPTIONAL DATA tab.

Page 32 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Purchase (Authorization and Capture)

Figure 12 Entering optional data for a credit card purchase

a Enter the customer Email Address.

b The Tracking ID box is available for your internal tracking needs.
11 If you want to enter Purchasing Card data for the purchase, skip to To enter Purchasing
Card data for a purchase or force.
12 Click on Auth to request an authorization or Auth and Capture to request an
authorization and, upon receipt, mark the transaction for capture.
The transaction is moved to the Open Batch queue.
A response page indicating if the transaction was approved or declined is displayed along
with the Transaction Reference Number.
Figure 13 Response: purchase transaction approved

Page 33 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Refund

Responses for approved transactions include an Approval Code and generally have a
Response Code of 00 Approved. For Salem merchants who are set up for Fraud Filters,
the Country Fraud Filter values may be returned on transactions. Possible values
include Accepted, Blocked, or Suspect. Please refer to your Account Executive for more
information on Salem Fraud Filters.
NOTE To view a sample response page for partially approved transactions, see Appendix A Partial
Authorizations.

Figure 14 Response: purchase transaction declined

For declined transactions, the Response Code indicates the reason for the decline.
13 If desired, use the buttons on the right side of the page to print the merchant and
customer receipts.
The receipts indicate if the transaction was approved or declined.
14 Click on Close to return to the initial New Order - Auth page.

Processing a Credit Card Refund

You can use the NEW ORDER > Credit option to open the New Order - Credit page, where
you enter a credit card refund transaction. This type of transaction requires you to enter the
credit card information and the Order ID of the original transaction.
NOTE If you do not have the card information or Order ID, you can find the original transaction in a closed
batch and initiate the refund from it, as described in Chapter 5, Reviewing Post-Settlement Data.

Page 34 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Credit Card Refund

To process a credit card refund

1 Select NEW ORDER > Credit to open the New Order - Credit page.
The RECOMMENDED DATA tab is displayed.
Figure 15 Entering refund information

The Credit Card Types Accepted list contains the methods of payment configured for
your merchant account that can be processed on this page.
NOTE The Card Number, Expiration Date, Amount, and Order ID # fields are required.

2 In the Card Number box, enter the credit card number used in the purchase.
Do not include spaces.
3 In the boxes next to Expiration Date, select the month and year the card expires.
4 Enter the Amount to be credited to the credit card.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter an Order Description.
7 If you want to enter Purchasing Card data, skip to Entering Purchasing Card Data for a
Purchase Card Credit/Refund.
8 Click on Credit to submit the transaction.
The transaction is moved to the Open Batch queue.
A response page indicating if the transaction was credited or not is displayed.

Page 35 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Prior Authorization

Figure 16 Response: credit transaction approved

NOTE The Card Number is generally masked in the response.

9 If desired, use the buttons on the right side of the page to print the merchant and
customer receipts.
The receipts indicate if the transaction was declined.
10 Click on Close to return to the initial New Order - Credit page.

Processing a Prior Authorization

You can use the NEW ORDER > Force option to open the New Order - Force page, where
you force an Authorization or Authorization and Capture transaction for a purchase that was
previously authorized manually or over the phone.
This type of transaction is very similar to a credit card purchase, but allows you to enter the
approval code from the manual or voice Authorization.
NOTE Because the prior authorization in these transactions was performed outside of the Orbital Gateway
system, the Orbital Gateway cannot verify the accuracy of the Prior Auth Approval Code you supply.
Although the Orbital Gateway does not require you to enter the Prior Auth Approval Code, the card
company may require it for settlement of the transaction.

Action Description

Force Submits a force transaction without marking for capture. Use this
option if the items in the transaction will be billed at a later date,
at the time of shipment for example.

Force and Capture Submits a force transaction and marks the transaction for
capture.

To process a prior authorization capture

1 Select NEW ORDER > Force to open the New Order - Force page.

Page 36 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Prior Authorization

The RECOMMENDED DATA tab is displayed.

Figure 17 Entering information for a Prior Authorization

The Credit Card Types Accepted list contains the methods of payment configured for
your merchant account that can be processed on this page.
NOTE The Card Number, Expiration Date, Amount, and Order ID # fields are required.
The customer address information (particularly Postal Code) may be required based on your
merchant settings.

TIP While not all fields on the RECOMMENDED DATA tab are required, it is considered a best
business practice to submit them with every transaction. To avoid higher Interchange fees,
merchants should, at a minimum, submit the 5-digit postal code for AVS transactions.
Submitting a Card Verification code can offer additional chargeback protection.

2 In the Card Number box, enter the credit card number.

Do not include spaces.

Page 37 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Prior Authorization

NOTE If you enter a number that the system recognizes as a Purchasing Card (based on the card
association's published BIN ranges) and you do not enter information on the Purchasing Card
Data tabs, the VT will prompt you to enter Purchasing Card data when you submit the
transaction. See Entering Purchasing Card Data for a Purchase for more information.

3 In the boxes next to Expiration Date, select the month and year the card expires.
4 Enter the total Amount of the transaction.
The Amount must include all taxes and fees (shipping and handling) for the purchase.
The maximum amounts allowed by the Orbital Gateway vary based on card type and
platform (Salem or Tampa) and may be further limited for your merchant account. Refer
to your internal processes for the minimum and maximum amounts you can enter.
5 Enter the Card Verification #.
 Visa/MasterCard/Discover: 3 digits found on the signature panel on the reverse side
of the credit card.
 American Express: 4 digits printed, not embossed, on the front of all cards. On the
American Express card it appears on the right side of the card. On Optima cards,
however, it appears on the left side of the card.
NOTE American Express CID only works if your American Express account is activated for this
program by American Express. Contact American Express directly for more information.
When American Express CID is used, it behaves differently than MasterCard and Visa
CVC2/CVV2. If you do not have a matching CID value, American Express declines the
transaction. If your CID does match, then the transaction is approved assuming all other
criteria are met. There are no response values specific to CID usage.

6 In the Order ID # box, enter an order number, following your internal guidelines.
7 Enter the customer address information.
If entering a non-U.S. address, click on the Non US Address check box. The State field
is set to Non-US, a Country Code field is added for you to select the country from a
list, and the Postal Code field changes to a single box to accommodate non-U.S. postal
code formats.
8 Enter the Customer Name and Customer Phone number.
9 In the Prior Auth Approval Code box, enter the approval code from the prior
authorization.
The card company may require the Prior Auth Approval Code for settlement.
10 If desired, select the OPTIONAL DATA tab.
a Enter the customer Email Address.
b In the Tracking ID box, enter the unique tracking number to send to the Issuer
Authentication/Service in the Authentication Request message.
11 If you want to enter Purchasing Card data, skip to To enter Purchasing Card data for a
purchase or force.
12 Click on Force or Force and Capture.
The transaction is moved to the Open Batch queue.
13 If desired, use the buttons on the right side of the response page to print the merchant
and customer receipts.

Page 38 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing Account Verification

The receipts indicate if the transaction was declined.

14 Click on Close to return to the initial New Order - Force page.

Processing Account Verification

The Account Verification feature allows you to verify accounts (i.e. valid account number,
currently open account) without financially impacting the accountholder’s open-to-buy. For
example, you might verify an account before you set up recurring payments on it.

To verify an account
1 Select NEW ORDER > Account Verification to open the New Order - Account
Verification page.
Figure 18 Entering information to verify an account

The Amount field is automatically set to 0 and cannot be modified.

NOTE The Card Number, Expiration Date, Order ID #, and Postal Code fields are required.
The Postal Code allows AVS verification. Include the Card Verification # to also verify this data
for the account.

Page 39 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing Account Verification

2 In the Card Number box, enter the credit card number.

Do not include spaces.
3 In the boxes next to Expiration Date, select the month and year the card expires.
4 Enter the Card Verification # to also verify this data for the account.
For Visa and MasterCard, this is a 3-digit number found on the signature panel on the
reverse side of the credit card. There is no card verification number for Diner's Club
accounts.
5 In the Order ID # box, enter an order number, following your internal guidelines.
6 Enter the customer address information.
If entering a non-U.S. address, click on the Non US Address check box. The State field
is set to Non-US, a Country Code field is added for you to select the country from a
list, and the Postal Code field changes to a single box to accommodate non-U.S. postal
code formats.
7 Click on Verify to submit the transaction.
A response page indicating if the transaction was approved or declined is displayed.
Figure 19 Response: account verified

NOTE The Card Number and Card Verification # are generally masked in the response.

8 If desired, use the buttons on the right side of the response page to print the merchant
and customer receipts.

Page 40 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing an Electronic Check Transaction

The receipts indicate if the transaction was declined.

9 Click on Close to return to the initial New Order - Account Verification page.

Processing an Electronic Check Transaction

You can use the NEW ORDER > Electronic Check option to open the New Order -
Electronic Check page to process electronic check verification, validation, purchase, and
refund transactions.
NOTE The Electronic Check function is available only to merchants processing on the Salem platform.

Verification is the means by which Chase Paymentech determines whether the ECP
transaction being presented can be processed through the Federal Reserve System or
Canadian Payments Association. Verification includes three checks:
1. Checks the Chase Paymentech internal negative database to determine if the account is
listed as bad.
2. Checks the Notification of Change (NOC) file to see if Chase Paymentech has been
alerted that there is new account information about this transaction.
3. Checks the Thompson File to verify that the ABA Routing is valid.
NOTE Verification does NOT determine if the funds are available in the account.

US checking accounts undergo an additional verification that compares the Routing Number
and Account Number information in the Electronic Check Processing (ECP) transaction to an
external negative file database. This file resides on the Chase Paymentech system and is
updated daily.
NOTE The external negative file check can only be performed for ECP transactions involving a U.S. bank
account.

The external negative file check fails if the account:

Has unpaid checks outstanding.
Has been closed for cause by the customer's financial institution.
Transactions that fail the external negative file check are returned with the Response Code
519 On Negative File, which means that the account appears on the external negative
file.
Verification is performed at the time you submit a transaction by using the Validate or
Validate and Capture button.
Validation, which is different than Validate or Validate and Capture, includes the three
checks performed in Verification minus the external negative file check.
Validation is performed on every ECP transaction at the time of settlement. If validation
fails at this point, the transaction is logged as a rejected item and can be located using the
options available from the REVIEW menu tab.

Page 41 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing an Electronic Check Transaction

For ECP transactions, you can perform the following operations:

Action Description

Validate U.S. check:

Runs the verification process including the external
negative file database.
Canadian check:
Runs the verification checks to determine if the ECP
transaction being presented can be processed through the
Canadian Payments Association.
If a Capture is not performed, the transaction is not funded.

Validate and Capture U.S. check:

Runs the verification process including the external
negative file database.
At time of settlement, runs the validation check. If
successful, the funds are withdrawn from the account.
Canadian check:
Runs the verification checks to determine if the ECP
transaction being presented can be processed through the
Canadian Payments Association. If successful, the funds are
withdrawn from the account upon settlement.
If there is a time lag between the verification and
settlement, the validation check is performed again before
the funds are withdrawn.

Capture Only At the time of settlement, performs the validation check and, if
successful, withdraws the funds from the account.
NO verification is performed.

Credit Runs the verification checks immediately. If successful, returns

funds to the consumer’s account at settlement.

To process an Electronic Check transaction

1 Select NEW ORDER > Electronic Check to open the New Order - Electronic Check
page.

Page 42 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing an Electronic Check Transaction

Figure 20 Entering information for an Electronic Check transaction

NOTE The Deposit Account #, Bank Routing #, Amount, Order ID #, and Check Holder Name fields
are required.
The Account Type may be required based on your internal guidelines.

2 Enter the Deposit Account #.

The account number can contain up to 17 characters.
3 Enter the Bank Routing #.
All US Bank Routing Numbers contain 9 digits.
All Canadian Bank Routing Numbers contain 8 digits only—no spaces or dashes. The
proper formatting for a Canadian Bank Routing Number is:
FFFBBBBB
where
FFF refers to the Financial Institution
BBBBB refers to the Branch Number
NOTE This is the opposite order of how this information is presented on a paper Canadian check.

4 Enter the total Amount of the transaction.

The Amount must include all taxes and fees (shipping and handling) for the purchase.
The maximum amount allowed for check transactions may be limited for your merchant
account. Refer to your internal processes for the minimum and maximum amounts you
can enter.

Page 43 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a UK Maestro/Solo Transaction

5 In the Order ID # box, enter an order number, following your internal guidelines.
6 In the Check Holder Name box, enter the name of the account holder.
7 In the Account Type list, select the type of account.
The choices include:
Consumer Check Consumer checking account
Consumer Saving Consumer savings account
Commercial Check Business checking account
8 Enter the Postal Code of the account holder.
The Postal Code is used when you create a Profile for the information you enter for the
transaction.
9 If desired, select the OPTIONAL DATA tab.
a Enter the Customer Phone number.
b Enter the customer Email Address.
c In the Tracking ID box, enter the unique tracking number.
10 Click on the command button for the action you want to take.
If you click on Validate or Validate and Capture, you are notified immediately of
whether the account passes or fails the verification checks.
Figure 21 Response: ECP passed validation

Processing a UK Maestro/Solo Transaction

You can use the NEW ORDER > UK Maestro-Solo option to open the New Order - UK
Maestro-Solo page to process purchase and refund transactions for Great Britain’s UK
Maestro and Solo debit cards.
NOTE The UK Maestro-Solo function is available only to merchants processing on the Salem platform that
are configured for this service. Please contact your Chase Paymentech account representative if you
wish to accept UK Maestro and Solo.

Page 44 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a UK Maestro/Solo Transaction

For UK Maestro-Solo transactions, you can perform the following operations:

Action Description

Auth Requests an authorization for the transaction. Use this option if the
items in the transaction will be billed at a later date, at the time of
shipment for example.

Auth and Capture Requests an authorization for the transaction and, after receipt of
the authorization, marks the transaction for capture.

Credit Returns funds to a consumer’s account.

To process a UK Maestro-Solo transaction

1 Select NEW ORDER > UK Maestro-Solo to open the New Order - UK Maestro-Solo
page.

Page 45 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a UK Maestro/Solo Transaction

Figure 22 Entering information for a UK Maestro-Solo transaction

NOTE The Card Number, Expiration Date, Amount, and Order ID # fields are required.
Either the Issue Number or Start Date is required—if both are available, submit both.
The customer address information (particularly Postal Code) may be required based on your
merchant settings.

TIP While not all fields on the RECOMMENDED DATA tab are required, it is considered a best
business practice to submit them with every transaction.

2 Enter the Name as shown on Card.

3 In the Card Number box, enter the large number across the card.
The card number contains 16–19 digits. Do not include the smaller numbers at the
bottom center of the card.
4 In the boxes next to Expiration Date, select the month and year the card expires.

Page 46 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a UK Maestro/Solo Transaction

5 Enter the Card Verification #.

6 In the Issue Number box, enter the entire Issue Number as it reads on the card,
including any leading zeros.
If the card does not have an Issue Number, you must enter the Start Date.
7 In the boxes next to Start Date, select the month and year specified on the card.
If both an Issue Number and Start Date are available, enter them both.
8 Enter the total Amount of the transaction.
The Amount must include all taxes and fees (shipping and handling) for the purchase.
Refer to your internal processes for the minimum and maximum amounts you can enter.
9 In the Order ID # box, enter an order number, following your internal guidelines.
10 Enter the customer address information.
The Country Code is automatically set to Great Britain and cannot be changed.
11 Enter the Customer Name and Customer Phone Number.
12 Enter an Order Description.
13 If desired, select the OPTIONAL DATA tab.
a In the Tracking ID box, enter the unique tracking number to send to the Issuer
Authentication/Service in the Authentication Request message.
b Enter the customer Email Address.
14 Click on the command button for the action you want to take.

Page 47 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing European Direct Debit

Figure 23 Response: UK Maestro transaction approved

Processing European Direct Debit

You can use the NEW ORDER > European Direct Debit option to open the New Order –
European Direct Debit page to process EU DD validation, capture, and credit transactions.
NOTE The European Direct Debit function is available only to merchants processing on the Salem platform.

EU DD is conceptually the same as accepting ACH payments in the United States or Canada.
However, there are major operational and rule differences in Europe. Each country in
Europe:
operates its own direct debit payment system
has its own rules that govern the process
has its own technical and banking requirements
As a result of these local variations, merchants wanting to accept direct debit payments in
Europe face the challenge of establishing processing interfaces and relationships with every
European country in which they do business. Chase Paymentech Solutions has “normalized”
the country variations enabling merchants to have a single technical interface, funding
source and processing relationship. Currently Chase Paymentech Solutions supports direct
debit in six European countries and two currencies:
Pounds Sterling (GBP) – United Kingdom
Euro - Austria, Germany, France, Belgium, and Netherlands
For EU DD transactions, you can perform the following operations:

Page 48 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing European Direct Debit

Action Description

Validate Validation is performed by an external vendor.

Validate and Capture Validates and withdraws funds from the designated Deposit
Account upon settlement.

Capture Only Withdraws funds from the designated Deposit Account without
validating first. Validation is performed at settlement.

Credit Returns funds to a consumer’s Deposit Account.

To process a European Direct Debit transaction

1 Select NEW ORDER > European Direct Debit to open the New Order – European
Direct Debit page.

NOTE For Euro currency:

 The Deposit Account #, Amount, Order ID #, Account Holder’s Name, and
Country Code of Bank fields are required.
 The Bank Sort Code is required for all countries except Belgium or the
Netherlands.
 The RB Code is required for France only.
For Great Britain Pound currency:
 The Deposit Account #, Amount, Order ID #, and Account Holder’s Name
fields are required.
 The Bank Sort Code is conditionally required.

2 Enter the Deposit Account #.

The account number can contain up to 16 characters.
3 Enter the total Amount of the transaction.
4 In the Order ID # box, enter an order number, following your internal guidelines.

Page 49 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Bill Me Later Purchase

5 In the Account Holder’s Name box, enter the name of the account holder.
6 Select the Country Code of Bank if required.
7 Enter the Bank Sort Code if required.
 For Germany 8 digits
 For Austria 5 digits
 For France 2-10 digits
 For UK 6 digits
8 Enter the RIB Code for France only.
 2 digits
9 If desired, select the OPTIONAL DATA tab.
a Enter the Customer Phone number.
b Enter the customer Email Address.
c In the Tracking ID box, enter the unique tracking number.
10 Click on the command button for the action you want to take.
Figure 24 Response: EU DD approval

Processing a Bill Me Later Purchase

You can use the NEW ORDER > BML Authorize option to open the Bill Me Later -
Authorize page to process Bill Me Later purchase transactions, which are handled in a way
similar to credit card purchases.
Action Description

Auth Requests an authorization for the transaction. Use this option if the
items in the transaction will be billed at a later date, at the time of
shipment for example.

Auth and Capture Requests an authorization for the transaction and, after receipt of
the authorization, marks the transaction for capture.

To process a Bill Me Later purchase transaction

1 Select NEW ORDER > BML Authorize to open the Bill Me Later - Authorize page.

Page 50 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Bill Me Later Purchase

Figure 25 Entering information for a Bill Me Later purchase transaction

2 In the Bill Me Later Card Number Present, select Yes or No. If Yes, enter the card
number in Card Number box
3 Enter the total Amount of the transaction
4 In the Order ID # box, enter an order number, following your internal guidelines. This
should be a unique number.

Page 51 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Bill Me Later Purchase

5 Enter the Shipping Cost.

6 Select the Delivery Type.
7 Enter the four digit Item Category number (assigned by BillMeLater).
8 Enter the Bill to Address information.
9 If the Ship to Address is the same as the Bill to Address, click on the Same as Bill
To checkbox else provide the Ship to Address information.
10 Enter the Customer Birth Date.
11 Enter the date the customer registered in Customer Registration Date (defaulted to
today’s date).
12 Enter the Terms and Conditions Version number that is agreed to by the customer.
13 Enter the Customer Social Security number.
14 Enter the Customer IP Address.
15 Enter an Order Description.
16 Enter the Customer Email Address.
17 Re-enter the customer e-mail address in Confirm Customer Email Address.
18 Enter the Merchant Promotion Code.
19 Enter Annual Income.
20 Enter the Pre-Approval Invitation #. This number indicates whether or not the
customer has been pre-approved. Pre-approval from the credit bureau should include
the 16 digit pre-approval number. This allows the pre-approval to be matched with the
first customer order. Internal pre-approvals should include the leftmost digit as a 1. Pre-
approvals should not be all zeros.
21 Select the Customer Residence Status.
22 Select Yes or No for Checking Account.
23 Select Yes or No for Savings Account.
24 Click on Auth to request an authorization or Auth and Capture to request an
authorization and, upon receipt, mark the transaction for capture.
The transaction is moved to the Open Batch queue.
A response page indicating if the transaction was approved or declined is displayed.

Page 52 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a Bill Me Later Refund

Figure 26 Response: Bill Me Later transaction approved

Processing a Bill Me Later Refund

You can use the NEW ORDER > BML Credit option to open the Bill Me Later - Credit page
to process Bill Me Later refund transactions, which are handled in a way similar to credit
card refunds and requires you to enter the Bill Me Later account number and the Order ID of
the purchase transaction.
NOTE If you do not have the account information or Order ID, you can find the original transaction in a
closed batch and initiate the refund from it, as described in Chapter 5, Reviewing Post-Settlement
Data.

To process a Bill Me Later refund transaction

1 Select NEW ORDER > BML Credit to open the Bill Me Later - Credit page.

Page 53 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a PINless Debit Transaction

Figure 27 Entering information for a Bill Me Later refund transaction

2 In the Card Number box, enter the Bill Me Later account number from the purchase
transaction.
3 Enter the Amount to be credited to the account.
4 Enter the Order ID # from the purchase transaction.
5 If desired or required by your internal processes, enter an Order Description.
6 Click on Credit to submit the transaction.
The transaction is moved to the Open Batch queue.
A response page indicating if the transaction was credited or declined is displayed.

Processing a PINless Debit Transaction

You can use the NEW ORDER > PINless Debit option to open the New Order - PINless
Debit page to process purchase and refund transactions for PINless debit cards.
For PINless Debit transactions, you can perform the following operations:
Action Description

Auth and Capture Requests an authorization for the transaction and, after receipt of
the authorization, marks the transaction for capture.

Credit Returns funds to a consumer’s account.

To process a PINless Debit transaction

1 Select NEW ORDER > PINless Debit to open the New Order - PINless Debit page.

Page 54 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Processing a PINless Debit Transaction

Figure 28 Entering information for a PINless Debit transaction

NOTE The Card Number, Biller Reference Number, Amount, and Order ID # fields are required.
The customer address information (particularly Postal Code) may be required based on your
merchant settings.

2 In the Card Number box, enter the debit card number.

Do not include spaces.
3 In the boxes next to Expiration Date, select the month and year, if any, the card
expires.
4 Enter a Biller Reference Number, following your internal guidelines.
5 Enter the total Amount of the transaction.
Refer to your internal processes for the minimum and maximum amounts you can enter.
6 In the Order ID # box, enter an order number, following your internal guidelines.
7 Enter the customer address information.

Page 55 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Advanced Features for Transaction Processing

If entering a non-U.S. address, click on the Non US Address check box. The State field
is set to Non-US, a Country Code field is added for you to select the country from a
list, and the Postal Code field changes to a single box to accommodate non-U.S. postal
code formats.
8 Enter the Customer Name and Customer Phone number.
9 Enter an Order Description.
10 If desired, select the OPTIONAL DATA tab.
d Enter the customer Email Address.
e Enter the Tracking ID.
11 Click on the command button for the action you want to take.

Advanced Features for Transaction Processing

Additional features on the New Order screens can be used for quickly processing
transactions or creating profiles. These features are only visible if the merchant account is
enabled for Profile Management, Managed Billing, or Soft Descriptors.

Page 56 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Advanced Features for Transaction Processing

Figure 29 Additional Features of the VT user interface

Use Profiles
To quickly access profile data for processing a new transaction, click on one of the options in
this section.

Search Profiles  Search for a specific profile by automatically navigating to the

Profile Management screen. Once the profile is found, select the
profile by clicking on the radio button and then clicking on Use
Profile button.

Page 57 of 214
Orbital Virtual Terminal Chapter 3 Working with New Orders
Version 4.2 Advanced Features for Transaction Processing

Reuse Last Profile  By selecting this option, the profile data from the profile that was
last used will be reused in the current transaction. This option is
only visible once a profile has been referenced to process a
transaction.

Profile Auto Suggest  This feature displays matching profiles based on keystrokes being
entered. Select the profile from the list once it is displayed in order
to populate all the fields.

Add Profiles
Use this feature to create a profile based on the information being entered on the order
screen. Select one of the options for generating the unique Profile ID. For any of the options
selected, enter the customer name in the Profile Customer Name field, if needed.

Blank Field  Enter a Profile ID of your choice.

Use Next Available Profile ID  Use this option to automatically generate the next
available Profile ID number.

Use Order Number as Profile ID  Use this option to use the Order ID as the Profile ID.

Use Order Description as Profile ID  Use this option to use the Order Description as the
Profile ID.

Add Managed Billing

This feature is only available if Managed Billing is enabled for Profile Management. Click on
the Add Managed Billing checkbox if a billing schedule is required for the profile being set
up. If Managed Billing default settings have been set up and should be applied to this
profile, leave as is. If no defaults are set up or a different schedule needs to be applied,
click on the Override Defaults checkbox and create the desired schedule.

Selecting Soft Descriptors

If a default soft descriptor has been designated via the Soft Descriptor Admin page, it will
be displayed in the dropdown else NONE will be displayed. Either leave the default descriptor
as is or select another descriptor from the dropdown menu.

Page 58 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Searching for a Transaction in the Open Batch

Chapter 4 Working with the Open Batch

All transactions submitted in the VT are placed into a queue called Open Batch pending
completion. While the transactions are in this state, you can:
Mark/unmark a transaction for settlement
Void a transaction
Settle all marked transactions
Split a transaction for multiple shipments
View the history of a transaction
Create a profile from a transaction
NOTE Gift Card transactions are not viewable from the Open Batch. They can only be viewed from the
FLEXCACHE menu tab.

Searching for a Transaction in the Open Batch

1 To view the Open Batch – Search page, click on the OPEN BATCH menu tab.
Figure 30 Open Batch Search page

2 To search for transactions in a specific status, select an option from the Transaction
Status dropdown menu:
 All (default)
 Voids Only

Page 59 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Searching for a Transaction in the Open Batch

 Declines and Errors Only

 Account Verifications Only
3 To search for transactions by account number, enter the full or partial account number
in the Account # box or just the last four digits in the Last 4 box.
4 To search by Account Type, select Non ECP or ECP.
5 To search by full or partial Order ID number, enter the value in the Order # box.
6 To search by full or partial Order Description, enter the value in the Order Description
box.
7 To search by a specific card brand, select an option in the Card Type dropdown box.
8 To search for transactions within an amount range, enter the minimum and/or maximum
value of the amount(s) in the Amount Range boxes. It is not necessary to supply both
values.
9 To search by approval code, enter the full value in the Approval Code box.
10 To search by Transaction Reference number, enter the full value in the Transaction
Reference box.
11 To search by a specific Profile ID, enter the full or partial Profile ID in the Profile ID
box. This field is only visible if the merchant and User ID are set up for Profile
Management.
12 To search by a specific VT User ID, select a user from the User Logon dropdown box or
enter the full User ID in the entry box. Searches can be performed on both active and
inactive/terminated User IDs.
13 In addition to any of the search parameters mentioned above, a date range can be
utilized to further narrow a search request. By default, the date range is set to the
current day. Change the From and To dates as needed. If no date range is needed,
uncheck the Date Range checkbox.

Results Output
Once the search criteria have been selected, there are several methods for generating the
results. Choose one of the following options in the Query Type dropdown box to complete
the search.
Detailed Transactions (Default) Search results are outputted to the screen for
immediate viewing. Individual transactions are
displayed in groups of 10. It is from this screen that
additional functionality can be accessed such as Void,
Settle, and Ship Partial. See Figure 31 Open Batch
– Search Results page (Detailed Transactions view)

Summary Query Search results are summarized on the screen.

Transaction counts by various transaction types are
provided. Examples include Sale counts, Return
counts, and Decline/Error counts. See Figure 32
Open Batch – Search Results (Summary Query
view)

Page 60 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Searching for a Transaction in the Open Batch

Generate Detail Report Search results are provided in PDF format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Generate Detail File Search results are provided in CSV format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Figure 31 Open Batch – Search Results page (Detailed Transactions view)

The Trans Status - Type column denotes the current status of the transaction.
Authorization Success Successful authorization. Transaction does not settle
until “Marked for Capture”.

Marked for Capture Successful authorization and marked for capture.

Transaction is submitted the next time settlement is
initiated.

Credited Refund transaction. Transaction is submitted the

next time settlement is initiated.

Marked for Capture – Split Partial shipment. The portion of the transaction
submitted the next time settlement is initiated.

Declined Declined authorization. Transaction is removed from

the open batch after the next settlement is
performed.

Page 61 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Viewing Transaction Details

Voided Voided transaction. Transaction is removed from the

open batch after the next settlement is performed.

Split Open (un-captured) portion of a partial shipment

transaction.

Figure 32 Open Batch – Search Results (Summary Query view)

Viewing Transaction Details

After generating search results using the Detailed Transactions query type, details for
each individual transaction in the Open Batch can be viewed.
1 Click on the radio button by the transaction that is to be viewed.
2 Click on View Order button.

Page 62 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Viewing Transaction Details

Figure 33 Selecting and viewing a transaction

Details of the transaction can now be viewed. By default, two tabs are displayed:
Recommended Data and Response Data. Depending on the New Order request,
Optional Data and Purchasing Card Data II are displayed. If Purchasing Card III data is
provided in the transaction request, a fifth tab called Purchasing Card Data III is
displayed.
Other than the Response Data tab, all other tabs simply mirror the information that was
submitted for processing the transaction with the exception of the Recommended Data
page which contains additional transaction specific information.
Transaction Date Date the transaction was originally created.

Transaction Reference Number Unique identifier assigned to each

transaction; also known as the Orbital
Gateway Reference Number.

Transaction Reference Index Referenced for internal Orbital Gateway use.

Transaction Creation User ID User ID or system which created this

transaction.

Transaction Last Modification User ID User ID or system which last modified this
transaction.

Page 63 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Viewing Transaction Details

Original Order Reference Number The Transaction Reference Number

(TxRefNum) associated with the original authorization of a
split transaction.
Figure 34 Open Batch – View Order

The Response Data page displays response information provided by the card issuing bank.
The response data returned is dependent on the transaction data provided at the time of
authorization.
Approval Code Provided when the transaction has been approved by
the card issuing bank.

Response Code Orbital Gateway response code indicating the status of

the transaction. A 00 indicates the transaction was
successful and approved. Any number greater than 00
generally indicates a decline or error. A text message
will indicate the exact error message associated with
the response code. See Response Codes for list of
response codes.

AVS Response Code Provided by participating card issuing banks when

address information is submitted in the New Order
request. See AVS Response Codes for list of AVS
response codes.

Card Verification Number Provided by participating card issuing banks when a

Response Code card verification number is submitted in the New Order
request. See CVV2/CVC2/CID Response Codes for list of
CVD response codes.

Page 64 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Viewing Transaction Details

Figure 35 Response Data tab

NOTE To view a sample Response Data page for partially approved transactions, see Appendix A Partial
Authorizations.

Adding a Profile
The Orbital Virtual Terminal will allow a profile to be created from within the transaction
detail pages in the Open Batch. The merchant and User ID must be enabled for Profile
Management in order to have access to this functionality.
1 From the Open Batch – Search Results page, click on the transaction for which a
profile needs to be created from.
2 Click on View Order button.
3 Click on Add Profile button.
4 The Admin – Profile Management page is opened with fields for a new profile already
populated. Complete the fields, including Profile ID, based on your internal guidelines.
5 Click on Add button.
6 Message for successful addition of profile is displayed. For more information on creating
profiles, see Working With Profiles.

Page 65 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Viewing Transaction Details

Figure 36 Add Profile from Open Batch

Viewing the Order History (Audit Trail)

History details of an order may be viewed by clicking on the Order History button.
1 From the Open Batch – Search Results page, click on the transaction for which the
history needs to be viewed from.
2 Click on View Order button.
3 Click on Order History button.
The Request Type column displays the different requests that were performed on the
order. The Transaction Origination column displays the system where the request
originated from. The Username column displays the VT User ID that originated the request
if the Transaction Origination is “VT”.

Page 66 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Marking a Successful Authorization for Capture

Figure 37 Order History

NOTE To view a sample Order History page for partially approved transactions, see Appendix A Partial
Authorizations.

Marking a Successful Authorization for Capture

The Mark/Unmark column allows the User to easily Mark or Unmark transactions for
settlement.
Clicking on the term Mark in this column changes the status from Auth Success to Marked
for Capture. The transaction is submitted the next time a settlement is initiated.
NOTE For information regarding Mark/Unmark for Purchase Card Data, see Adjusting Purchasing Card
Data.

Figure 38 Marking a transaction for capture

Unmarking a Captured Transaction

Clicking on the term Unmark in this column changes the status from Marked for Capture
to Auth Success. The item will not be included in the next settlement. It will remain in the
open batch until its Transaction Status is changed.

Page 67 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Adjusting Purchasing Card Data

Figure 39 Unmarking a transaction

Adjusting Purchasing Card Data

When authorizations are performed on Purchasing Cards, a special column on the Open
Batch – Search Results page is displayed. The Adjust Purchase Card & Mark column
allows you to adjust the original Purchasing Card Level II and III data then mark the
transaction for capture in the event of a ship partial.
Figure 40 Adjust Purchase Card & Mark column

1 From the Open Batch – Search Results page, click on the Pcard&Mark link by the
Purchasing Card transaction that is to be split.
2 The Purchasing Card Data III tab is displayed. Remove and/or edit the line items as
desired. As a reminder, Tampa Users are forced to ensure the variance is zero before
continuing. This is the same requirement discussed in Entering Purchasing Card Data for
a Purchase. Also important to note that Level III data only remains attached to the
transaction currently being settled. It is no longer attached to the remaining un-captured
portion of the transaction. In other words, if Level III data is still needed at the time of
Capture for the remaining un-captured portion, it will need to be re-entered.

Page 68 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Voiding a Transaction

Figure 41 Adjusting Purchase Card data

Voiding a Transaction
The Void button is used to cancel a transaction. It removes a transaction from an active
status and prevents its future settlement.
1 From the Open Batch – Search Results page, click on the transaction that needs to be
voided.
2 Click on the Void button.

Page 69 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Voiding a Transaction

Figure 42 Voiding a transaction

Upon using the Void button, the status is changed to Voided. Once voided, the status can
no longer be changed. To settle a voided authorization, the data must be re-entered on the
New Order > Force page and clicking on the Force and Capture button.
NOTE A void, in and of itself, does not reverse the original authorization for any card type other than
Gift Card and PINless Debit. In order to free up the hold on the accountholder’s open-to-buy
(line-of-credit), which was reserved by the original authorization, an authorization reversal must
be performed.
Authorization reversals can be automatically attempted with every Void by enabling this
functionality via the ADMIN > General Admin menu. For more information on how to enable this
feature, please see Setting General Preferences.

Page 70 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Settling All Marked for Capture, Credit, and Force Transactions

Figure 43 Voided transaction

Settling All Marked for Capture, Credit, and Force Transactions

The Settle action instructs the Orbital Virtual Terminal to immediately settle all transactions
with a status of Marked for Capture, Force, or Credit. After the Settle function is performed,
all Voided and Declined transactions are purged from the Open Batch view. They, along with
errors, can be located by specifically searching for Voids Only or Declines and Errors
Only in the Transaction Status dropdown box of the Open Batch – Search page. The
only transactions that remain in Open Batch after settlement are Authorizations that were
not Marked for Capture.
Figure 44 Settling an open batch

Once the Settle button is selected, a summary page appears displaying summary totals.

Page 71 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Splitting a Transaction into Separate Shipments

Figure 45 Settlement summary report

Splitting a Transaction into Separate Shipments

Ship Partial, also known as Split Shipment, is a function that allows you to split one
transaction into multiple transactions. Bankcard regulations prohibit charging a consumer
for goods prior to shipment. If a consumer purchases several items and multiple shipments
occur on different days (back orders, etc.), then the order must be charged to the consumer
in multiple increments. For a process flow diagram, please see Split Shipment Process Flow.
Only Unmarked transactions can be selected for Ship Partial. If you attempt to split a
transaction that is already Marked for Capture, an alert appears advising you to unmark
the transaction.
1 From the Open Batch – Search Results page, select the Authorization Success
transaction that needs to be split.
2 Click on Ship Partial button. The Ship Partial page appears. This page contains all the
transaction information previously recorded plus a field to enter the portion of the total
amount to capture

Page 72 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Splitting a Transaction into Separate Shipments

Figure 46 Splitting a transaction

3 Enter the amount that needs to be captured. Amount can be equal to or less than the
authorized amount. After entering the amount, click on one of the standard action
buttons:
Mark for Capture
Clear Amount
Return to Results List

Page 73 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Splitting a Transaction into Separate Shipments

Figure 47 Entering ship partial amount

4 Click on Mark for Capture button. The results are displayed on the Open Batch –
Search Results page indicating the amount captured. The page reflects both the
transaction that was split and the portion of the transaction that was Marked for
Capture. Once a specific amount of a Split Shipment has been Marked for Capture, it
cannot be unmarked, but it can be voided. In the example below, an original transaction
of $25.00 has been split twice, once for $5.00 and again for $6.00.
Figure 48 Ship partial results

To see the historical detail of the split transaction click on the View Order button on the
Open Batch – Search Results page, then on the Order History button. The following
page appears with the history.

Page 74 of 214
Orbital Virtual Terminal Chapter 4 Working with the Open Batch
Version 4.2 Splitting a Transaction into Separate Shipments

Figure 49 Ship Partial order history

The TxRefNum is a unique identifier assigned to each transaction. Although each split of the
transaction is assigned a new TxRefNum, you can search for all split transactions by the
Original TxRefNum. The reference to the Original TxRefNum is kept internally with each
subsequent split transaction.
The remaining balance of the authorization (uncaptured portion) is displayed in the Amount
section of the Order History page
NOTE For information on splitting Purchasing Card II and III transactions, see Adjusting Purchasing
Card Data.

Page 75 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Chapter 5 Reviewing Post-Settlement Data

The REVIEW menu tab allows you to view post-settlement data at the batch or transaction
level. The screens provide the ability to view closed, pending or rejected batches or
transactions. Post-settlement data is retained for six months plus current month. The Batch
Search is used for locating batch information and subsequently drilling down to individual
transaction information. The Transactions Search is employed to immediately locate a
specific transaction. To begin the search of post-settlement data, click on REVIEW > Batch
Search or REVIEW > Transaction Search.
NOTE Gift Card transactions are not viewable from the REVIEW menu tab. They can only be viewed
from the FLEXCACHE menu tab.

Searching for Batches

1 To view the Review – Batch Search page, click on REVIEW > Batch Search option.
2 To search by Batch Number range, enter the beginning and ending batch numbers in the
From and To boxes. Both boxes must be populated in order to perform this search.
 Tampa batch numbers increase numerically beginning with 001 (i.e. 001,002,003,
etc.)
 For batches that are greater than 2400 transactions, the Orbital Gateway will
split the batch prior to sending to the host system at the time of settlement. The
first batch sent to the host will contain 2400 transactions, the second will contain
2399, the third will contain 2398, etc. Each subsequent batch will be
decremented by 1 transaction.
 Each batch that is split will be assigned the next incremental batch number.
 Salem batch numbers are assigned by the Salem host system and resemble the
following: 20906.4195f.
 Salem batches are not split up prior to being sent to the host.
3 To search by Date range, select the beginning and ending date ranges in the From and
To dropdown boxes. The default is set to the current date.

Results Output
Once the batch number range or date range has been selected, there are several methods
for generating results. Choose one of the following options in the Query Type dropdown
box to complete the search.
Detailed Transactions (Default) Search results are outputted to the screen for
immediate viewing. Individual batches are displayed
in groups of 10. Users can drill down to the
transaction level from this page. See Figure 50
Review – Batch Search Results (Detailed
Transactions view)

Page 76 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Summary Query Search results are summarized on the screen.

Transaction counts by various transaction types
across batches within the search parameters are
provided. Examples include Sale counts and Return
counts. See Figure 51 Review – Batch Search
Results (Summary Query view). Payment types may
differ from screenshot provided. To print Summary
page, click on Print button and change printer options
to landscape mode.

Generate Detail Report Search results are provided in PDF format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Generate Detail File Search results are provided in CSV format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Generate Detail Report – Search results for transactions in pending status are
Pending provided in PDF format. The report is obtained from
the REPORTING menu tab. The VT User ID must be
enabled for Reporting in order to retrieve this report.
See Working with Reports for more information on
retrieving reports.

Generate Detail File – Pending Search results for transactions in pending status are
provided in CSV format. The report is obtained from
the REPORTING menu tab. The VT User ID must be
enabled for Reporting in order to retrieve this report.
See Working with Reports for more information on
retrieving reports.

Generate Detail Report – Search results for rejected transactions are provided
Rejected in PDF format. The report is obtained from the
REPORTING menu tab. The VT User ID must be
enabled for Reporting in order to retrieve this report.
See Working with Reports for more information on
retrieving reports.

Generate Detail File - Rejected Search results for rejected transactions are provided
in CSV format. The report is obtained from the
REPORTING menu tab. The VT User ID must be
enabled for Reporting in order to retrieve this report.
See Working with Reports for more information on
retrieving reports.

Page 77 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Figure 50 Review – Batch Search Results (Detailed Transactions view)

The Batch Status column denotes the status of the batch.

Closed Successfully processed batch.

Pending Batch is waiting to be processed. This status may last anywhere from
one to six hours.

Rejected All or some of the transactions were rejected. Transactions in this

state can be resettled after fixing the cause for rejection

Figure 51 Review – Batch Search Results (Summary Query view)

Page 78 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Reviewing a Closed or Pending Batch

After generating search results using the Detailed Transactions query type from the
REVIEW > Batch Search page, batch details for Closed or Pending batches can be viewed
on the Review – Batch Search Results page. Click on the radio button next to the batch
(closed or pending) you wish to view then click on the Batch Details button.
For closed batches, in addition to the batch details, a summary of the batch is displayed
below the transactions. The summary information includes the total number of
records/transactions, total Sales, total Credit, and net Amount of the file.
Figure 52 Review - Batch Details (Closed Batch)

For pending batches, the Trans Status – Type column will display a Capture in Progress
status.

Page 79 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Figure 53 Review – Batch Details (Pending Batch)

Reviewing a Rejected Batch

Transactions may get rejected by the host processing system at the time of settlement.
Examples for rejects include invalid card numbers or ECP validation errors.
Rejected transactions can be viewed in the Rejected Batch on the Review – Batch Search
Results page after generating search results using the Detailed Transactions query type
from the REVIEW > Batch Search page. Click on the radio button next to the rejected
batch then click on the Batch Details button. Within the Rejected Batch, the Trans Status
– Type column will display the status of each transaction. Users have the option to:
View the transaction
Mark and Re-settle the transaction
Void the transaction
Upon determining that a transaction cannot be marked/resettled from the Rejected Batch,
users can opt to resubmit the transaction as a Force transaction after voiding in the
Rejected Batch. If assistance is needed to research rejected transactions, please contact the
Orbital Gateway Support helpdesk.

Page 80 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

Figure 54 Review – Batch Details (Rejected Transactions)

Voiding a Transaction in a Rejected Batch

If no further action needs to be taken on a rejected transaction, users can void it to remove
it from the Rejected Batch.
1 From the rejected transactions page, click on the transaction that is to be voided.
2 Click on the Void button. Trans Status – Type column will display Voided status.
Figure 55 Voiding a rejected transaction

Resettling a Rejected Transaction

Any transaction within the Rejected Batch can attempt to be settled again.
1 From the rejected transactions page, click on the Mark hyperlink by the transaction that
is to be re-settled. The Trans Status – Type column will display Tran Reject –
(Marked) status.

Page 81 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Batches

2 Click on the Re-settle button. A settlement summary will be displayed of all rejected
transactions that were marked for settlement on the Review – Settle page.

Viewing a Transaction in a Closed, Pending, or Rejected Batch

Individual transactions can be viewed from within any Closed or Pending Batch and/or the
Rejected Batch.
1 From within the batch, click on the radio button by the transaction that is to be viewed.
2 Click on the View Order button. Details of the transaction can now be viewed.
NOTE For more information on what is displayed, Adding a Profile, performing a Quick Credit, and
viewing Order History, see Viewing Transaction Details.

Figure 56 Viewing transactions from Closed, Pending, or Rejected batches

Page 82 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Transactions

Searching for Transactions

1 To view the Review – Transaction Search page, click on the REVIEW > Transaction
Search option.
Figure 57 Closed Batch Transaction Search page

2 To search for transactions in a specific status, select an option from the Transaction
Status dropdown menu:
 Settled All (default)
 Pending Transactions
 Settled Sales
 Settled Returns
 Rejected Items
3 To search for transactions by account number, enter the full or partial account number
in the Account # box or just the last four digits in the Last 4 box.
4 To search by Account Type, select Non ECP or ECP.
5 To search by full or partial Order ID number, enter the value in the Order # box.
6 To search by full or partial Order Description, enter the value in the Order Description
box.
7 To search by a specific card brand, select an option in the Card Type dropdown box.

Page 83 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Transactions

8 To search for transactions within an amount range, enter the minimum and/or maximum
value of the amount(s) in the Amount Range boxes. It is not necessary to supply both
values.
9 To search by approval code, enter the full value in the Approval Code box.
10 To search by Transaction Reference number, enter the full value in the Transaction
Reference box.
11 To search by a specific Profile ID, enter the full or partial Profile ID in the Profile ID
box. This field is only visible if the merchant and User ID are set up for Profile
Management.
12 To search by a specific VT User ID, select a user from the User Logon dropdown box or
enter the full User ID in the entry box. Searches can be performed on both active and
inactive/terminated User IDs.
13 In addition to any of the search parameters mentioned above, a date range can be
utilized to further narrow a search request. By default, the date range is set to the
current day. Change the From and To dates as needed. If no date range is needed,
uncheck the Date Range checkbox.

Results Output
Once the search criteria have been selected, there are several methods for generating the
results. Choose one of the following options in the Query Type dropdown box to complete
the search.
Detailed Transactions (Default) Search results are outputted to the screen for
immediate viewing. Individual transactions are
displayed in groups of 10. It is from this screen that
additional functionality can be accessed such as Add
Profile and Credit. See Figure 58 Review –
Transaction Search Results page (Detailed
Transactions view)

Summary Query Search results are summarized on the screen.

Transaction counts by various transaction types are
provided. Examples include Sale counts and Return
counts. See Figure 59 Review – Transaction
Search Results (Summary Query view). Payment
types may differ from screenshot provided. To print
Summary page, click on Print button and change
printer options to landscape mode.

Generate Detail Report Search results are provided in PDF format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Generate Detail File Search results are provided in CSV format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Page 84 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Searching for Transactions

Figure 58 Review – Transaction Search Results page (Detailed Transactions view)

Figure 59 Review – Transaction Search Results (Summary Query view)

Page 85 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Viewing Transaction Details

After generating search results using the Detailed Transactions query type, details for each
individual transaction on the Review page can be viewed.
1 Click on the radio button by the transaction that is to be viewed.
2 Click on View Order button.
Figure 60 Selecting and viewing a settled transaction

Details of the transaction can now be viewed. By default, two tabs are displayed:
Recommended Data and Response Data. Depending on the New Order request,
Optional Data and Purchasing Card Data II are displayed. If Purchasing Card III data is
provided in the transaction request, a fifth tab called Purchasing Card Data III is
displayed.
Other than the Response Data tab, all other tabs simply mirror the information that was
submitted for processing the transaction with the exception of the Recommended Data
page which contains additional transaction specific information.
Transaction Date Date the transaction was originally created.

Transaction Reference Number Unique identifier assigned to each

transaction; also known as the Orbital
Gateway Reference Number.

Transaction Reference Index Referenced for internal Orbital Gateway use.

Transaction Creation User ID User ID or system which created this

transaction.

Transaction Last Modification User ID User ID or system which last modified this
transaction.

Page 86 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Original Order Reference Number The Transaction Reference Number

(TxRefNum) associated with the original authorization of a
split transaction.

Figure 61 Review – View Order

The Response Data page displays response information provided by the card issuing bank.
The response data returned is dependent on the transaction data provided at the time of
authorization.
Approval Code Provided when the transaction has been approved by
the card issuing bank.

Response Code Orbital Gateway response code indicating the status of

the transaction. A 00 indicates the transaction was
successful and approved. Any number greater than 00
generally indicates a decline or error. A text message
will indicate the exact error message associated with
the response code. See Response Codes for list of
response codes.

AVS Response Code Provided by participating card issuing banks when

address information is submitted in the New Order
request. See AVS Response Codes for list of AVS
response codes.

Page 87 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Card Verification Number Provided by participating card issuing banks when a

Response Code card verification number is submitted in the New Order
request. See CVV2/CVC2/CID Response Codes for list of
CVD response codes.

Figure 62 Review – Response Data tab

Adding a Profile
The Orbital Virtual Terminal will allow a profile to be created from within the transaction
detail pages in the Review section. The merchant and User ID must be enabled for Profile
Management in order to have access to this functionality.
1 From the Review – Transaction Search Results page, click on the transaction for
which a profile needs to be created from.
2 Click on View Order button.
3 Click on Add Profile button.
4 The Admin – Profile Management page is opened with fields for a new profile already
populated. Complete the fields, including Profile ID, based on your internal guidelines.
5 Click on Add button.
6 Message for successful addition of profile is displayed. For more information on creating
profiles, see Working With Profiles.

Page 88 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Figure 63 Add Profile from Review – Transaction Search Results

Initiating a Credit from an Order (Quick Credit)

From the Review – View Order page, a previous Sale can be quickly turned into a refund.
By clicking on the Credit button, a New Order - Credit is automatically created. The fields
are pre-populated using the data from the original transaction in the View Order page.
However, you can override any data as needed. If the User’s role only allows viewing of
masked account numbers, then only the masked card number is presented. Please note that
purchase card data is not carried over from an original transaction.
NOTE The Quick Credit feature is only available for transactions no older than four months plus the
current month. Users will have to manually enter the transaction information on the New Order
– Credit page for transactions older than that.

Page 89 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Figure 64 Quick Credit

Viewing the Order History (Audit Trail)

History details of an order may be viewed by clicking on the Order History button.
1 From the Review – Transaction Search Results page, click on the transaction for
which history needs to be viewed from.
2 Click on View Order button.
3 Click on Order History button.
The Request Type column displays the different requests that were performed on the
order. The Transaction Origination column displays the system where the request
originated from. The Username column displays the VT User ID that originated the request
if the Transaction Origination is “VT”.

Page 90 of 214
Orbital Virtual Terminal Chapter 5 Reviewing Post-Settlement Data
Version 4.2 Viewing Transaction Details

Figure 65 Review – Order History

Page 91 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Profile Management

Chapter 6 Administering the Virtual Terminal

The Admin functionalities are optional and only appear if the merchant is enabled and the
User has the appropriate Admin rights. There are 12 administrative categories for which to
be set up for. Each provides the ability to self-administer various functionalities. After
clicking on the ADMIN menu tab, only the options for which you are enabled will appear.
Profile Management
Profile > Account Updater
Profile > Auto Email Service
Profile > Managed Billing
Profile > PINless Debit
Auth Recycling
FlexCache (Salem Only)
General Admin
Purchase Card III Admin
Receipt Admin
Reporting Admin
Selectable Response
Soft Descriptors

Profile Management
The Orbital Virtual Terminal includes functionality called Customer Profile Management,
which allows Cardholder data to be stored within the Orbital Gateway and subsequently
used for transaction processing. The screens associated with this menu choice are used to
create, search, edit, delete, or use Customer Profiles. Please see Working With Profiles for
more information on using Customer Profiles.

Configuring Account Updater

Fully managed Account Updater for profiles is available to Salem merchants using customer
profiles. The functionality is specifically designed to update Merchant or Chain level profiles
housed on the Gateway utilizing the Salem Account Updater process. As a prerequisite, Visa
and MasterCard approval is required for participation. Please contact your Account Executive
for further details. You may also review the Account Updater Supplemental Reference
guide for more details on Account Updater and the Orbital Gateway.
Once enabled, requests for update are automatically submitted to Visa and MasterCard
according to a merchant selected schedule. Visa and MasterCard typically respond to
requests within three days, inclusive of the submission day. Responses may contain
information regarding new card account numbers, expiration dates, account closures, etc.
Based upon the information returned, the Orbital Gateway automatically updates customer
profiles. A scheduled report which lists profiles that were updated is available.

Page 92 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Account Updater

NOTE If the card account number is invalid or the card account is closed, the associated profile is
automatically suspended, preventing unsuccessful future authorization or capture attempts.
As with any suspended profile, the status can easily be changed to active as new
information becomes available.

In addition to updating profiles via the Account Updater process, merchants have the option
to initiate a one-off update request for a specific profile, outside of the preset schedule. The
request is included in the next Account Updater submission.
The one-off request can be initiated via the VT in two ways:
From a Profile Query results page, find the desired profile and click on the corresponding
Yes in the Send Account Updater Request column.
Navigate to the desired profile via the ADMIN > Profile Management page. Click on
the Send button in the box referencing the Account Updater request.

Page 93 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Account Updater

Figure 66 Account Updater one-off request

WARNING A change of account number via the Account Updater process is suppressed if the merchant
initiates a change to the account number after the Account Updater request is initiated and
prior to the update.

Page 94 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Account Updater

To configure the Account Updater settings, navigate to the ADMIN > Profile > Account
Updater dropdown menu. The page will vary depending on whether your account is set up
for Chain Level or Merchant Level Profile Management.
On the Profile Account Updater Admin page, select whether to:
Include suspended profiles in the Account Updater request along with all active profiles
or the default, which is to include all active profiles only.
Apply updates to all profiles that have the same card account number (inclusive of
suspended profiles) or the default, which is to update the initial profile that triggers an
update request.

Schedule of AU Requests
This refers to when the request for updated information is sent. Counting the request day as
Day 1, the corresponding Visa and/or MasterCard response is normally received on Day 3.
Typically, updates are posted to profiles on Day 3, the same day as receipt. For invalid
cards, the update is posted the same day as the request.
The start date, unless otherwise requested or set, is the day after setup on the Orbital
Gateway. It is the day that the system starts looking to see if an update request should be
sent. For example, if the Start Date is January 28th and the schedule is Day 01 of every 1
Month, the first update request will be sent on the 1st of February.
A basic schedule is required; however the parameters of the schedule are flexible. The
default schedule is the day following enablement of the functionality in the Orbital Gateway
and every six months thereafter.
You may select any day of the month with an interim of any time between 1 and 6 months.
The day can be a specific day, such as the 23rd or may be a day of the week, such as the
Second Thursday. The month selection may range from every month (X of every 01 month)
to a maximum interval of 6 months (X of every 06 months). For example, one might choose
the 16th day of every 04 months.
Best Practice Recommendation
 Once per month on a day that is 6 days prior to the day most billings occur.

Optional Schedules
Expiring Cards This optional schedule will send an update request five days prior to the
end of month in which the card account expires and for those that have
already expired.
Best Practice Recommendation
 Select if Basic Schedule update interval is longer than one
month or if updates occur at the beginning of the month.

Managed Billing Available only to merchant level profiles, update requests are sent five
days prior to the next scheduled managed billing event.
Best Practice Recommendation
 Depending on the number of Managed Billing profiles and
the shortness of the billing interval, i.e. weekly, this may
be a helpful option.

Page 95 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Account Updater

AU Default Merchant Number

This is only applicable to Chain Level Profiles.
Since Chain Level profiles are shared across multiple Merchant IDs, one default merchant
number is used to submit the updated requests. As you select the one merchant number to
be used, keep in mind it must be approved by Visa and/or MasterCard as well as be setup
for Account Updater in both Salem and the Orbital Gateway. It is also the merchant number
that Account Updater fees accrue. The second screen shot shows the field for entry of the
AU Default merchant number.
Figure 67 Account Updater Options – Merchant Level Profiles

Page 96 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Automatic E-mail Messages to Cardholders

Figure 68 Account Updater Options – Chain Level Profiles

Configuring Automatic E-mail Messages to Cardholders

The Orbital Virtual Terminal provides an optional service of automated cardholder e-mails. It
is offered in conjunction with Managed Billing and/or the Account Updater functionality and
must be enabled at the Merchant Level. Profiles securely house information, which includes
cardholders’ e-mail addresses if provided by the merchant. If the service is elected, the
Orbital Gateway uses these addresses to send automated customer notifications.
Select ADMIN > Profile > Auto Email Service to access the Admin – Auto E-mail
Service page.

Page 97 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Automatic E-mail Messages to Cardholders

Figure 69 Auto E-mail Service page

The Auto E-mail Service page reflects the current e-mail choices and provides the
opportunity to enable or disable each category of e-mails. Simply click on the dropdown box
to make your selection. The merchant may choose any combination of the following.
Expiring Card E-mail notification that the card account on-file will soon
expire and to contact the merchant with updated
information.
(Sent seven days prior to the month of expiration)

Declined Transaction E-mail notification that the card account has been
declined and to contact the merchant. If Authorization
Recycle is used, the e-mail is not triggered until the cycle
is exhausted or a hard decline is received. See Setting
Preferences for Authorization Recycling for more
information on Authorization Recycling.
(Sent same day)

Successful Billing E-mail notification to the customer that the account on

record was successfully billed.
(Sent same day)

Page 98 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Automatic E-mail Messages to Cardholders

Upcoming Billing E-mail notification informing the cardholder that the

account on record is about to be charged.
(Sent day before billing)

Ineligible PINless Debit E-mail notification informing the cardholder of an invalid

ATM (PINless Debit) card.

Account Close E-mail notification of a closed credit card account is sent

to the respective cardholder.

New Account Number and/or E-mail notification is sent to the respective cardholder
Expiration Date that a new card account number and/or expiration date
was received from a credit card association.
This screen also allows changes to additional fields related to the e-mail.
From E-mail Address E-mails are sent on behalf of the merchant from an e-
mail address which cannot receive replies. The domain
name portion, “billing-notification.com”, follows the “@”.
It cannot be changed or edited. The local part of the
address, that which proceeds the “@”, defaults to the
merchant’s legal name. In the absence of a legal name,
the Doing Business As (DBA) name is used. However, the
local address can be changed and saved according to the
merchant’s wishes. Simply key the desired name in front
of the “@” and click on the Save button.

Merchant Notification E-mail If the Cardholder Auto E-mail Service is chosen, the
Address merchant must populate this field so a Non-notification
alert can be sent. It is a notification that a cardholder e-
mail was not sent due to the absence of a cardholder e-
mail address in the Profile. After populating the field, click
on the Save button.

Merchant’s Customer Service In the text of the e-mail sent to the cardholder, the
Phone Number Merchant Legal Name followed by the DBA name is
included. If the Customer Service phone number field is
populated and saved, this information is also included.
The choice to send cardholder e-mails is made at the merchant level. Assuming the flag is
enabled for any of the e-mails described previously, one of following results can occur.
These can be used to fine tune the e-mails sent.
1. Cardholder e-mail address is present in Profile.
 An e-mail is sent to the cardholder.
2. Cardholder e-mail address field for Profile is empty.
 A non-distributed cardholder e-mail notification is sent to the merchant using the
merchant’s notification e-mail address discussed above. For example, the merchant
has a high profile customer to whom an e-mail should not be sent. See Auto E-mail
Cardholder Text for example of the non-distributed cardholder e-mail notification.
3. Cardholder e-mail address field for Profile is populated with ‘NO E-MAIL’.
 An e-mail is not sent to the cardholder or to the merchant.

Page 99 of 214
Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Automatic E-mail Messages to Cardholders

NOTE No action is taken on bounced e-mails nor is the merchant notified of the non-delivery.

The default e-mail text for the e-mails is found in Auto E-mail Cardholder Text. The
merchant can customize the text per their internal guidelines or restore the default text.
WARNING The merchant has the ability to change the content of these e-mails without approval or
review by Chase Paymentech. The merchant has sole responsibility for any changes and for
restricting those authorized to make e-mail content changes, as well as enforcing related
internal policies. For VT users, this can be supported in part by the permissions granted to
users
It is important that text changes are carefully considered and reviewed prior to saving.
Please remember that the e-mail has the potential to be sent to all of your customers. To
enhance customer relations, make sure that the text professionally represents your
business.

1 To view or edit the text of the Cardholder e-mail, click on the corresponding View/Edit
Text link by each e-mail template. The current text is displayed.
2 To change the text, enter the desired changes and click on the Save button. Once the
text is saved, it will be used in the next cardholder e-mail distribution.
The text has a limit of 2000 characters. The “Please do not reply” and “This Message is
Confidential” messages comprise 520 characters of the total of 2000.
3 The original default text can be restored by using the Restore Defaults button. After
clicking on the button, the original text will be made visible. To apply and save this
verbiage, click on the Save button.
Figure 70 Editing e-mail text

Page 100 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Managed Billing

Setting Preferences for Managed Billing

Managed Billing is an extension of the Customer Profile Management. It is designed to meet
merchants’ recurring and deferred billing needs. In accordance with a merchant’s predefined
set of business rules, the Orbital Gateway generates an Authorization-Capture transaction
for the merchant. The Managed Billing service can be utilized recurring, installment, or
billing transactions.
Recurring Cardholder agrees to a regular on-going billing of a
designated amount at a specified time interval.

Installment Cardholder agrees to set number of payments over a

specified time for the purchase of an item.

Deferred transaction A single billing that is triggered at a predefined future date.

The screens associated with this menu choice are used to designate the type of billing and
billing schedule. Please see Managed Billing for more information on this functionality.

Setting Preferences for PINless Debit

PINless Debit card ranges may become ineligible for processing. At times, cards falling into
this category can also be used as Visa or MasterCard Debit Cards. The PINless Debit Admin
page allows merchants to automatically update PINless Debit profiles to Visa or MasterCard
methods of payment should the card account number no longer be eligible as a PINless
Debit card.
To access the PINless Debit Admin page, select ADMIN > Profile > PINLess Debit. Click
on Yes to have the profiles automatically updated to Visa or MasterCard.
Figure 71 Admin – PINless Debit Admin

Page 101 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Authorization Recycling

Setting Preferences for Authorization Recycling

This optional service is enabled at the Merchant level. It automates re-authorization
attempts for transactions which have received soft declines from the issuing bank. A soft
decline is a decline that has the potential to be approved at a later date, such as an Over
Limit Decline. The merchant selects the soft declines to recycle as well as the frequency,
number of authorization attempts, and the interval between authorization attempts. The
Authorization Recycling process continues until an approval is obtained, a hard decline is
received, or the number of designated attempts is exhausted.
The process is only applicable to Authorization-Capture transactions for the following card
types:
American Express
Discover Card
JCB
MasterCard
Visa
Maestro – UK Domestic (Only Salem Platform)
From the ADMIN > Auth Recycling menu, you can view and administer the current
parameters.
1 Enter Days Between Attempts
 You may choose from 1-16. It is recommended that you follow the normalized
association guidelines of a maximum of 4 attempts over 16 days.
2 Enter Maximum Number of Attempts
 You may choose from 1-4 reauthorization attempts. It is recommended that you
follow the normalized association guidelines of a maximum of 4 attempts over 16
days.
3 Select the Authorization Recycle Exhaust Action
 Defines the action taken when Authorization Recycle is exhausted or a hard decline is
received
None No action is taken when Authorization Recycle is exhausted.
This is the default value.

Auto-Suspend For all profiles, Standard and Managed Billing, the Profile
Status is changed to auto-suspended.

4 Check the boxes of the Soft Decline Response Codes to be recycled

 The soft declines eligible for the reauthorization process are displayed in the list.
Only the Enabled (i.e. checked) soft decline response codes trigger the Auth Recycle
process.
5 Click on the Save button

Page 102 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences Related to Gift Card Redemptions

Figure 72 Admin – Auth Recycling

Setting Preferences Related to Gift Card Redemptions

From the ADMIN > FlexCache menu, you can administer two options for your Gift Card
processing.

Partial Redemption Auto Authorization

When partially redeeming an authorization, the hold on the funds that are not captured is
released. Enabling this option results in an auto-authorization attempt so that the funds are
held for another 7 days.

Remaining Balance Capture Setting

If you process Gift Card transactions in a two-step environment (Auth followed by a
Redemption), you can elect to have the Redemption Request capture the remaining balance
on the card if it is less than that of the amount originally Authorized. The only time the
remaining balance on the card is less than the authorized amount is when the original
Authorization has expired (over 7 days without the Redemption Request). The Response
page displays the amount requested as well as the amount actually captured.
NOTE Admin - FlexCache is only available for Salem merchants.

Page 103 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting General Preferences

Figure 73 Admin - FlexCache

Setting General Preferences

The ADMIN > General Admin page provides the User the ability to alter various VT
behaviors including Purchase Cards, Address Verification Service (AVS), Settlement,
Authorization Reversals, and Partial Authorizations. Simply choose the desired behaviors by
radio buttons or the dropdown menu, then click on Save.

Page 104 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting General Preferences

Figure 74 Admin – General Admin – Tampa Merchants

Page 105 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting General Preferences

For Salem merchants, the Partial Authorization section of the General Admin page offers a
slightly differently functionality.
Figure 75 Admin – General Admin – Salem Merchant

Purchase Card Prompt on Mark For Capture

If YES is selected, the Adjust Purchase Card and Mark column is added to the Open
Batch page. The hyperlink Pcard&Mark in the column indicates that the Auth transaction
falls within the Visa or MasterCard Purchase Card bin ranges. To add or edit purchase card
data prior to settling, click on the Pcard&Mark link. This will direct you to another page to
enter or edit the data. See Adjusting Purchasing Card Data for more information on how to
edit the Purchasing Card data.

Page 106 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting General Preferences

Figure 76 Pcard&Mark column

View/Enter Card Number

This option determines if the credit card number box is displayed as either four separate
boxes or one box.

Remove Auth or Auth/Capture Button

This determines which command buttons are displayed on the Recommended Data tab of
the NEW ORDER pages: Auth, Auth/Capture, or both.

Mandatory AVS
This option is used to enforce whether AVS and/or CVD is mandatory or not. The following
options can be enabled:
Require AVS Zip to be mandatory
Require Street Address to be mandatory
Require Card Verification Data (CVD) to be mandatory

Two Step Settlement Process

This feature, when selected, inserts an intermediary confirmation page into the settlement
process. The User must view a pre-settlement summary total and then click on the Confirm
button before completing the Settlement/End-of-Day process.

Auto Settle
This option is used to establish an auto-settle time and time zone.

Page 107 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting General Preferences

Attempt Authorization Reversal When Voiding

Selecting this option triggers the automatic attempt of Authorization Reversals when voids
are processed. An Authorization Reversal attempts to cancel an outstanding authorization
that is not stale and has not yet settled. A successful Authorization Reversal releases the
hold on a cardholder's funds related to the original authorization transaction. If the
authorization is stale, meaning it is greater than 72 hours old, only the Void request will be
attempted.

Partial Authorization
A Partial Authorization occurs when the cardholder’s issuing bank returns an approval for an
amount less than the original requested amount. This is most common with customers who
use pre-paid credit cards, but may happen under other circumstances as well. The partially
approved amount is the amount that will be settled during the end of day process. It is
important to note that you must request that a partial be returned if a full authorization is
not available.
Partial Authorizations are not supported for the following functionality:
Authorization Recycling
Managed Billing
Mark for Capture transactions (2-n)
An authorization can be marked for capture multiple times causing the original
transaction to be split into several transactions. When a partial authorization is returned
on the authorization, the initial Mark for Capture request amount will be subtracted from
the partially approved amount rather than the originally requested amount.
For subsequent Mark for Capture requests of an authorization after the initial Mark for
Capture, the Orbital Gateway attempts to obtain a new authorization. For these
authorization requests, partial authorizations will not be supported.
NOTE A Declined: Partial Auth not Supported error is returned when a merchant is not set up to
support Partial Authorizations but a partial authorization was returned from the host
system.

Tampa merchants
Selecting Yes will allow approval for a portion of the original amount.
Selecting No will prevent partial authorizations.

Salem merchants
Three options are available: Yes, No, or Salem Merchant Default Setting. The Yes and
No options will override the Salem merchant default settings.
NOTE American Express, neither the Yes or No Partial Authorization override is supported.

Selecting Yes will allow approval for a portion of the original amount. Partial
authorizations are only supported for:
 Visa
 MasterCard
 MasterCard Diners
 Discover

Page 108 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Selecting Purchasing Card 3 Units of Measure

 Discover Diners
Selecting No will prevent partial authorizations.
Selecting Salem Merchant Default Setting will support the settings that are
configured on the Salem host system.

Selecting Purchasing Card 3 Units of Measure

The ADMIN > Purchase Card III Admin page extends the Unit of Measure options for
Level III processing. By default, the only Unit of Measure displayed is NMB, or Number. All
possible Unit of Measure options are listed in the top window and can be added to (or
removed from) the bottom window using the Add Unit of Measure or Remove Unit of
Measure buttons.
Figure 77 Admin – Purchase Card III Admin

Specifying Information to Appear on Receipts

Through the ADMIN > Receipt Configuration page, merchants are able to partially edit
the header and footer of Virtual Terminal receipts. Key receipt elements such as the
disclaimer and transaction details cannot be edited. There are three main elements to the
screen.
Receipt Header
Six lines are available for editing (40 characters per line). Since the Orbital system does
not automatically print the merchant name, address, and phone number, merchants are
required to provide this information.
Receipt Footer
Four lines of text with 40 characters per line are available.
Optional Receipt Data

Page 109 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Specifying Information to Appear on Receipts

The following fields can be displayed on the receipt when enabled.

 Customer Name
 Order Description
 VT User Name
 Signature Line
After editing the receipt information, click on the Save button.
Figure 78 Admin – Receipt Configuration

Page 110 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Scheduled Reports

Figure 79 Receipt Examples

Configuring Scheduled Reports

The ADMIN > Reporting Admin page allows self administration of two aspects of
reporting, card account truncation on reports and scheduled reports. Additionally, specific
On-Demand reports may be ordered. For a high level review of data columns for the various
reports, see Appendix H Reporting.

Card Account Truncation

Truncation or masking of card account numbers replaces all but the last four digits of the
account number with ‘X’s. Card numbers are truncated as a default. If you wish for the full
account number to be visible on reports, go to ADMIN > Reporting Admin menu, click on
No and the Save button. To restrict certain Users from seeing the full account number, call
the Gateway Support Help Desk to adjust the Users’ permissions.
WARNING This feature is currently not available. Cardholder account numbers on all reporting is
masked.

Scheduled Reports
Scheduled reports are automatically created and delivered according to the merchant
selected parameters. These include the format, frequency, and delivery mechanism. The
subgroup of event driven reports are triggered by a specific event. For example, the Closed
Batch Detail Report is created shortly after a batch is closed.

Report Description
Settlement Related Scheduled Reports
Closed Batch Detail Displays information about transactions in a batch when
closed.

Page 111 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Scheduled Reports

Closed Batch Summary Displays summary information regarding transactions in a

Report batch when closed. For Tampa merchants settling batches
that exceed 2400 transactions, the batches will be split up
into smaller batches prior to sending to the host system.
These batches will be individually displayed in the Virtual
Terminal as separate batches but the Closed Batch Summary
report will include the combined information for all the split
batches of that settlement.
NOTE This report is only available in CSV format.

Rejected Batch Detail Displays information regarding rejected transactions.

Additional Scheduled Reports
Account Updater Report Provides information regarding changes automatically made
to any given Profile ID via the Account Updater process.

Authorization Recycle Provides information regarding the status (Approved, Final

Declines, and in Recycle Process) for Authorization Recycle
transactions. It is available to merchants enabled for
Authorization Recycling.

Expiring Card Displays the associated Profile ID, Name, and e-mail address
for each card that has expired or will soon expire. This
information can assist in efforts to obtain updated customer
information necessary for future submissions. This report is
only offered on a monthly basis.

Managed Billing Provides information regarding the authorization status

(Approved, Final Declines, and in Recycle Process) for
Managed Billing transactions. It is only available to
merchants using Managed Billing.

PINless Debit Status Displays a list of Profiles for which the Profile Status was
Change modified due to ineligibility of the PINless debit account
number. Only available to merchants enabled for PINless
Debit.

Scheduled Profile Activity Displays the scheduled authorization dates for up to 24

future receivables per Profile. It contains both customer and
transactional information. It is only offered to merchants
using Managed Billing.

Suspended Profile Displays all Profiles that have been placed in a suspended
state. It includes both Auto-Suspended and Manually-
Suspended Profiles. It is only offered to merchants using
Managed Billing or Authorization Recycling.

Formats Available
PDF report document
CSV comma-delimited file
NOTE Reports generated but not retrieved for 6 consecutive months are discontinued.

Page 112 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Scheduled Reports

Frequency
The Expiring Card Report which is produced once monthly. All others may be scheduled
daily, weekly, or monthly.

File Delivery Options

Virtual Terminal The report is available for pick-up in the VT. The VT also houses a
copy of the report regardless of delivery method.

E-mail The report is sent to the e-mail recipients as populated in the

identified column.
NOTE Reports sent via e-mail ALWAYS mask the expiration date and all
but the last four digits of the card number.

SFTP Pick-up The report is placed in an SFTP directory for pick-up, just like an
Orbital Batch response file. The User ID must be set-up in advance by
Chase Paymentech listed in the dropdown Batch User menu.
Outbound file encryption choice:
From the following, the merchant may choose the encryption method
for unsolicited, outbound files such as the auto-generated SFTP
report.
Zip (default choice)
PGP
GPG
ASC
NOTE The choices of PGP, GPG, and ASC require loading an accompanying
certificate through the batch tool. The new Outbound-Only setting
will not override the existing echo encryption methodology used for
inbound files, (i.e. this will not impact the resultant response files
of any inbound files).

Page 113 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Scheduled Reports

Figure 80 Admin – Reporting Admin

To administer the options described, choose ADMIN > Reporting Admin menu. Enable or
disable reports by clicking in the Enable checkbox. If enabling, make the corresponding
selections and click on the Save button.

On Demand Reports
To request on Demand Reports for this group, click on the On Demand Reports button.

Page 114 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Configuring Scheduled Reports

Figure 81 Admin – Reporting Admin – On Demand Reports

Make your search criteria and Report Type selections, and then click on the Search button.
The page will refresh with the instructions to check Reporting. Click on the REPORTING
menu tab to view the report. For more information on retrieving reports, see Working with
Reports.

Chain Level Reports

Merchants who are enabled for Chain Level Profile Management will have access to Profile
related reports at the Chain Level. These reports can be easily identified in the VT by the
chain link icon to the left of the report name.
The following reports are available for Chain Level Profile Management:
Account Updater
PINless Debit Status Change
Expiring Card
Suspended Profile

Page 115 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Selecting Response Codes to Automatically Decline

Figure 82 Chain Level Reporting

Selecting Response Codes to Automatically Decline

The Merchant Selectable Response solution not only helps protect you from fraud but it also
gives you flexible control over your risk exposure. Merchant Selectable Response (MSR)
allows you to configure the Orbital Processing System to return an override decline based
on predefined options. You select the Address Verification Service (AVS) or Card Verification
Data (CVD) response codes that you want auto-declined. For example, if you choose to auto
decline all approvals receiving the AVS Code indicating Zip-No Match, an automatic
merchant override decline is returned for those transactions. It is displayed as an M1
Override decline.
This feature must be enabled at the Merchant Level and the User level. To enable MSR
response codes, go to ADMIN > Selectable Response.

Page 116 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Selecting Response Codes to Automatically Decline

Figure 83 Admin – Selectable Response

From the available options in the top window, simply choose the AVS or CVD response
codes and then add to your list of declines by clicking on the Add Decline button. Only the
eligible codes for your merchant account appear in the menu list. A complete list of all
possible codes is found in Appendix C Merchant Selectable Response Codes. You may also
deselect a response code by choosing the code in the bottom window and clicking on the
Remove Decline button.
The list of Decline Codes in the bottom window will trigger an auto decline on transactions
that receive those codes in the response. The declined transaction will appear as Merchant
Override Decline.

Page 117 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

Figure 84 Merchant Override Decline

Setting Preferences for Soft Descriptors

Certain merchants may have a need to include merchant identifying information with each
transaction rather than using defaults that are stored at the Chase Paymentech system.
These merchants may take advantage of Soft Descriptors in order to submit information
such as merchant name, street address, city, state, and zip. The soft data is passed to the
card association along with the transaction and posted on the accountholder’s statement, if
applicable.
The Soft Descriptor Records are used to define the merchant name/product description that
will appear on the consumer’s statement. It allows the merchant greater flexibility in
describing the consumer’s purchase. Soft Descriptors are supported for Visa, MasterCard,
MasterCard Diners, and ECP.
It is subject to issuer discretion whether this descriptor will be displayed on the
accountholder statement.

Salem (BIN 000001)

The Orbital Gateway supports Soft Descriptors into the Salem Host. However:
Prior Risk Department approval is required.
The Merchant ID and User ID must be enabled for Soft Descriptors on the Orbital
Gateway.

PNS (BIN 000002)

The Orbital Gateway supports Soft Descriptors into the PNS Host. However:

Page 118 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

It is only supported for Chase Paymentech Canada customers.

The Merchant ID and User ID must be enabled for Soft Descriptors on the Orbital
Gateway.

Salem Support

Rules and Guidelines—Credit Card

Chase Paymentech will not generate or segregate reports by the Soft Descriptor. If the
merchant wishes to see Salem reports segregated by product, the merchant must set up
specific reporting divisions and deposit those transactions under that division number.
For those merchants who need to roll up several merchant names under one corporation,
please contact your Chase Paymentech Representative for details on the use and regulation
of the Soft Descriptors.
The description in the Merchant Name field should be what is most recognizable to the
cardholder. It should consist of the company name and/or trade name combined with some
type of description of the product or service that was purchased.
The Merchant Name can be one of 3 different lengths. In addition, the Product
Description can be appended based on the length of the Merchant Name, such that they
are a combined length of 21 bytes. In other words, the options are:
Merchant Name Product Description

3 bytes 18 bytes

7 bytes 14 bytes

12 bytes 9 bytes

Additional notes:
The Customer Service Phone Number and Merchant URL fields provide the
cardholder with a Customer Service Phone Number or URL. This is a requirement to
qualify for Visa’s lowest Direct Marketing interchange rate.
If the merchant submits a backslash (\) in the soft descriptor, it is converted to a
hyphen (-) on the cardholder statement. If the merchant submits a question mark (?) in
the merchant descriptor, it is converted to a space on the cardholder statement.
There are certain American Express card types/programs that ignore the descriptors
sent using Soft Descriptors. The Optima card is one of these types. The merchant should
contact their American Express representative for more details.
Non-eCommerce transactions sent with a URL do not qualify for the best interchange.
For MasterCard MOTO and Recurring Industry Types, if the City/Phone field at the
division level is not a Customer Service Phone Number, then a Customer Service Phone
Number must be populated in the Customer Service Phone Number field, or the
transaction will error with Response Reason Code BP: Customer Service Phone reqd.
for MOTO and Recurring. MC Only.
The Orbital Gateway will apply the asterisks (*) in the necessary locations. Please do not
add these in any of the fields.

Page 119 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

Rules and Guidelines—ECP

The Automated Clearing House (ACH) uses two fields to describe the transaction to the
consumer. The Merchant Name will always appear on the consumer’s statement, and the
Product Description will appear on the consumer’s statement a majority of the time. Both
are required fields.
Chase Paymentech recommends using the Doing Business As (DBA) description/value in the
Merchant Name field and the product information in the Product Description field.
When utilizing the Soft Descriptor for ECP transactions, both the Merchant Name and the
Product Description are mandatory.

PNS/Tampa Support

Rules and Guidelines

Again, the support for Soft Descriptors via the PNS Host is only for customers processing
through Chase Paymentech Canada.
Unlike Salem, the only value passed on to the cardholder statement is the Merchant Name
field, which, for these customers, is a maximum of 25 bytes of data.
All other Soft Descriptor fields can optionally be sent, but will not be submitted to the
settlement host and will not display on the cardholder statement.

Setting Descriptors
To access the Soft Descriptors menu, the Merchant ID and the User ID must both be
enabled for Soft Descriptors.
1 Select ADMIN > Soft Descriptors menu.
2 To create a soft descriptors, press the New Descriptor button from the Admin – Soft
Descriptors page.

Page 120 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

Figure 85 New Descriptor

3 Click on Credit Card or Electronic Check radio button.

4 If selecting Credit Card:
a Enter text for Merchant Name and Product Description combination.
b Enter Customer Service Phone Number, Merchant URL, or Merchant E-mail Address.
c Press Add Descriptor or Add & Set as Default (soft descriptor will be set as the
default option) button.

Page 121 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

Figure 86 New Credit Card soft descriptor

5 If clicking on Electronic Check radio button:

d Enter text for Merchant Name and Product Description.
e Press Add Descriptor or Add & Set as Default (soft descriptor will be set as the
default option) button.
Figure 87 New ECP soft descriptor

6 To search for existing soft descriptors, enter the search parameters in any of the
provided fields and press the Search button.

Page 122 of 214

Orbital Virtual Terminal Chapter 6 Administering the Virtual Terminal
Version 4.2 Setting Preferences for Soft Descriptors

Figure 88 Admin – Soft Descriptors

7 A list of descriptors will be displayed.

Figure 89 Soft Descriptors search results

8 To edit an existing descriptor, click on the radio button by the descriptor and click on the
Edit button. Make modifications as necessary and click on Update Descriptor or
Update & Set as Default button. The default button will set the descriptor as the
default descriptor on the New Order page.
9 To set an inactive descriptor to active status or an active descriptor to inactive status,
click on the radio button by the descriptor and click on the Active/Inactive button.
10 To set a specific descriptor as the default descriptor, click on the radio button by the
descriptor and click on the Set Default button.

Page 123 of 214

Orbital Virtual Terminal Chapter 7 Working with Reports
Version 4.2 About Reports

Chapter 7 Working with Reports

About Reports
The Virtual Terminal enables Users to generate and retrieve reports. The previous chapter
included a discussion of creating reports by the On Demand Reports through the Admin >
Reporting Admin> On Demand Reports. Reports can also be created through the
following search queries by the selecting Detail Report or Detail File from the Query
Type dropdown menu.
Open Batch
Closed Batch
Profile
Once created the reports are easily located and retrieved from the REPORTING menu tab.

Locating Reports

To locate a generated report

1 Click on REPORTING on the VT menu bar. The Retrieve Report page is displayed along
with the current day’s reports.
2 To adjust the search parameter by Report Status, select the appropriate option from
the dropdown menu.
3 To adjust the search parameter by Submitter, select the appropriate User name of the
person who ordered the report from the dropdown menu.
4 To adjust the search parameter by Report Type, select Report [PDF] or File [CSV] from
the dropdown menu.
5 To adjust the search parameter by the Reporting Options, select the appropriate
report type from the dropdown menu.
6 To adjust the search parameter by the report submission date, uncheck the box beside
Filter by Submit Date and change the From and To dates as needed.
7 Click on the Search button. The screen will refresh with a list of reports meeting the
search criteria.

Page 124 of 214

Orbital Virtual Terminal Chapter 7 Working with Reports
Version 4.2 About Reports

Figure 90 Reporting – Retrieve Reports

Retrieving and Saving Reports

To Retrieve and Save Reports

1 Click on the radio button next to the report.
2 Click on Retrieve Report button.
If selecting a report, the report opens automatically as a PDF in Adobe Acrobat reader. You
may save a copy of the report from within Adobe. With a CSV file format, a pop up asks
whether to ‘Save’ or ‘Open’ the file. You may choose either. At this point you need to choose
which 3rd party software you wish to use to view the file.
NOTE As a reporting default, card account numbers are truncated, i.e. masked. This means that you will
only see the last 4 numbers of the card account. All preceding numbers of the account are
replaced with ‘Xs’.

Excel Quick Tip for Unmasked Account Numbers:

Excel automatically displays the Account Number field as a numeric field. In Excel
the numeric field length defaults to 15 digits. Account numbers that are longer than
15 digits are not presented properly. To avoid this issue first save the file. Then open
Excel and import the file while changing the Account Number field to a text field.

Page 125 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 About Profiles and Managed Billing

Chapter 8 Working With Profiles

The Orbital Virtual Terminal includes functionality called Customer Profile Management, i.e.
tokenization, which allows Cardholder data to be stored within the Orbital Gateway. A
merchant can process transactions by simply passing a token value representing a
cardholder. Using the Customer Profile ID, i.e. the token, simplifies transaction processing
and mitigates data entry errors. Additionally it eliminates the need to store sensitive
information in-house so you can focus on growing the business as Chase Paymentech
Solutions focuses on securely processing the transactions.

About Profiles and Managed Billing

Profile Management provides the flexibility of single transaction processing, recurring billing,
or deferred billing. The Orbital Gateway can store relevant information for processing for all
three options.
For the standard Customer Profile you initiate each transaction request.
For recurring and installment billing, you establish a recurrent billing schedule. The
Orbital Gateway then processes transactions according to the pre-set schedule. Please
see the Managed Billing section for additional information.
For a deferred billing, you set the future one-time billing date. The Orbital Gateway kicks
off the authorization and capture process on the designated date. Please see the
Managed Billing section for additional information.

Creating a Profile
To utilized Profile Management your merchant account must be enabled for the
functionality. Please contact your account representative if you are not already set up the
program. Once enabled the next step is to create customer profiles. This can be done in two
ways.
Create a Profile as a distinct action.
Create a Profile as a part of a transaction request.
Once a Profile exists, it can be used to process a new transaction. The information stored in
the profile is used to populate the transaction data elements. You always have the option to
override any part of the Profile for a subsequent transaction. Finally, the Profile can be
updated [or even deleted] at any point.

Creating a Profile as a Distinct Action

To create a profile as a discrete action the User must have Profile Administration Rights.
With this right, also known as a permission, the Admin – Profile Management page is
accessed to create a Profile. There are two convenient ways to navigate to the Profile Admin
page:
Using the VT menu bar select ADMIN > Profile Management.

From the NEW ORDER page simply click on .

To create a profile
1 Click on New Profile button to open the Profile Configuration tab.

Page 126 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Creating a Profile

Figure 91 New Profile button

2 The Profile Configuration page is displayed. Using the available options, enter the
cardholder-related data that you want the Orbital system to store.
NOTE A unique Profile ID and Card Number are minimally required. Additional information may be
required as noted by the required field symbol. Example: Expiration Date for a credit card.

Page 127 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Creating a Profile

Figure 92 New Profile cardholder data

3 Create unique Profile ID by one of the following methods.

Manually
 In the Profile ID box, enter a unique identification number and unselect the Use
Next Available Profile ID check box. The guidelines for creating the Profile ID
follow.
 Length
Range of 1 to 22 characters
 Valid Characters
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-
,$@& and a space character
WARNING A space character cannot be a leading character.
Alpha characters are stored as uppercase characters. Profile ID 12aaa is stored as Profile ID
12AAA. Since Profile IDs cannot be duplicated, the system will not allow the creation of a
second profile with the ID of 12AAA.

NOTE A unique Profile ID and Card Number are minimally required. Additional information may be
required as noted by the required field symbol. Example: Expiration Date for a credit card.

Page 128 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Creating a Profile

Systemically
 Leave the Use Next Available Profile ID box checked. The Orbital Gateway will
create a Profile ID on your behalf.
4 In the box next to Profile Status, select Active.
5 If desired or required by your internal processes enter the following optional data in the
respective boxes.
f Enter Customer Name
g Enter Customer Address information.
h Enter E-mail Address
i Enter Phone Number
j Enter Order Description
6 Check Use Profile Number as Order Number if you want to create an Order ID with
the same name as the profile. The Order ID appears in PTI reporting offered to Global
Platform merchants.
7 Check Use Profile ID as Order Description if you want the Order Description to
reflect the same name as the profile. The Order Description appears as Customer
Defined Data in ROL reporting offered to North American platform
8 In the box next to Payment Method, choose one of the options from the dropdown
menu.
9 Enter the information for the Method of Payment. Each Method of Payment will have
required fields and may have additional optional fields. For example, a credit card has
the following options:
k Enter Card Number
l Enter Expiration Date
10 If desire or required by your internal processes, enter an Amount. It is used to populate
the Amount field when the New Order is created using a Profile. It may be overridden
on the New Order page.
11 Click on Add to store the Profile data. The page refreshes, displaying the Profile Add
message that indicates the information was successfully saved and stored. The Profile
may now be used for subsequent transactions.

Creating a Profile When Processing a Transaction

A Profile may be created along with a New Order transaction. The User must have the
Profile Administration permission referenced above. The information in the following New
Order fields can be included as part of the profile.
Card Number City
Expiration Date State
Amount Postal Code
Country code E-mail Address [Found on Optional
Data tab]
Order Description
Customer Phone
Customer Name
Street

Page 129 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2

Figure 93 Profile Management fields from New Order page

1 Check the Add to Profile Management box. The screen refreshes, displaying Customer
Profile data fields.
2 Click on a radio button beside the option you want to use to create a Profile ID.
m Click on the blank box and enter a Profile ID to manually create the Profile ID.
n Click on Use Next Available Profile ID to have the Orbital Gateway systemically
create a Profile ID.
o Click on Use Order Number as Profile ID to create a profile with the Order ID as
the name.
p Click on Use Order Description as Profile ID to create a profile with the Order
Description as the name.
3 If desired or required by your internal processes, enter a customer name in the Profile
Customer Name box.
4 Click on Auth or Auth and Capture to process the transaction and create a profile.

Page 130 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Locating an Existing Profile

When adding the Profile as a part of processing a New Order transaction, a Profile Response
Code is displayed on the response page. It indicates the profile was successfully created or
that there was a problem or error in creating the profile. The Profile Response Codes are
listed in Appendix D Profile Response Codes.
Figure 94 New Order – Auth response with Profile Data

Locating an Existing Profile

After a Profile is created and stored, it can be used at a later date to process transactions.
A profile can be located a couple of ways. The approaches begin with proceeding to either
ADMIN or NEW ORDER pages.

Search by ADMIN > Profile Management

Select ADMIN >Profile Management to open the Admin-Profile Management page. To
search for a Profile ID use any one or a combination of the following search criteria.
1 To search by Profile ID, enter a part or the full Profile ID in the box.
2 To search by Account #, enter the full or partial account number in the box; or just the
last four digits in the Last 4 box.
3 To search by Customer Name, enter the full or partial name in the box.
4 To search by Postal Code, enter the full or partial code in the box.
5 To search by a Payment Method, select one of the available options.
6 To search by Status of Profile, select one of the available options.

Page 131 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Locating an Existing Profile

7 In addition to the search parameters mentioned above, a date range can be utilized to
further narrow a search request. Check the box next to Date Range and change the
From and To dates as needed. If no date range is needed, leave the Date Range box
unchecked.
8 For Query Type, leave the default Display on Screen.
9 Click on the Search button. A new page appears displaying the search results.
10 Click on the radio button next to the Profile ID to select it.
11 Click on the command button for the action you want to take.
If you click on Use Profile, you are taken to the New Order page. The stored profile
information is used to populate various fields. Clicking on Edit/View Profile takes you
to the Profile Configuration page that displays the profile information.
Figure 95 Use or Edit/View profiles

Search by NEW ORDER

Two Profile icons are displayed on the New Order page. One takes you to the Admin Profile
Management screen, the second displays matching profiles based on matching keystrokes.

Search Profiles Icon

1 Click on the Search Profiles icon.
Various search parameters are displayed on the Admin - Profile Management page.
Please see Search by ADMIN > Profile Management section above for more information
on how to search for profiles.

Page 132 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Using a Profile in a Transaction

2 Once the profile has been found, click on the radio button by the profile. Click on the
command button for the action you wish to take.

Profile Auto-Suggest feature

If you know the Profile ID and want to quickly pull it up, use the Profile Auto Suggest text
box.
1 Begin entering the Profile ID number.
The tool will find Profile IDs that match your entry and dynamically display them in a
drop-down box.
2 Choose the profile displayed in the drop-down box using either your mouse or the Enter
key. The data from the selected profile populates the New Order page.
Figure 96 Profile Auto Suggest feature

Using a Profile in a Transaction

Once a Profile has been created, it can be used to process subsequent transactions. Locate
the profile by one to the methods explained in the Locating an Existing Profile section
above.
ADMIN>Profile Management Search
NEW ORDER Search Profiles
NEW ORDER Profile Auto-Suggest

Page 133 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Editing a Profile

To Process a Transaction
1 Click on the radio button beside the profile and click on Use Profile if you are on the
Admin-Profile Management Search page. Or, select the profile using the Auto Suggest
icon on the New Order page. Data from the selected profile populates New Order
fields.
2 Edit the information in the fields as necessary.
3 Add additional information as necessary or in accordance with your internal processes.
4 Click on the command button for the action you want to take.

Editing a Profile
Profile data elements can be easily modified or changed. The only exception is the Profile
ID. It can only be used once and it must be a unique value. Even if a profile is deleted, the
Profile ID may not be reused.
To edit a profile first locate it by either clicking on the Search Profiles icon on the New
Order page or by selecting ADMIN > Profile Management from the VT menu bar. Follow
the steps previously discussed in Search by ADMIN > Profile Management section.

To edit a profile
1 From the list of displayed profiles, click on the radio button next to the Profile ID that is
to be viewed.
2 Click on the Edit/View Profile button.
3 Edit the profile by entering new information in the respective boxes or choosing another
option from the dropdown menus.
NOTE The Profile ID is the only data element that cannot be changed.

4 Click on Update to save the edit changes. A message is displayed at the top of the page
indicating the successful update.
NOTE Only Users with a Profile Management Role of Administrator can update profiles.

Page 134 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Profile Status

Figure 97 Update Profile

Profile Status
Although there are several statuses that may be applied to a profile, only one may be
applied at any given moment. A profile status may be viewed or changed on the Admin
Profile Management page, the Profile Configuration tab. The following are the statuses that
can be displayed.
Active Active profile which can be used for transaction processing.

Active-MB A profile that is enabled for either a recurring or deferred billing

schedule. A Managed Billing Profile can also be used to process
one-off transactions.

Manual-Suspend Profile use for sale transactions was suspended by the merchant.
It may still be used to process Credits/Returns.

Auto-Suspend Profile use was systemically suspended based on pre-selected

rules set by the Merchant.

Inactive Profile was inactivated by the merchant. Neither Sale nor Credit/
Refund transactions can be processed with the profile.

Page 135 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Profile Status

NOTE Because your merchant account may not have all the features enabled, you may not see all of the
status listed above.

To change a profile status

1 Locate the profile and navigate to the Profile Configuration screen.
2 Click on the down arrow in the box beside Profile Status.
3 Click on the Profile Status to be applied.
4 Click on Update. A message is displayed at the top of the page indicating the profile
was updated.

To delete a profile
1 Locate the profile and navigate to the Profile Configuration screen.
2 Click on the Delete button. A message is displayed at the top of the page indicating the
profile has been successfully deleted.
WARNING Once a Profile is deleted all access is permanently removed. The Profile cannot be located,
viewed, or modified and it will not appear on reports. Although no longer accessible, the
Profile ID cannot be reused.

Page 136 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Change Log

Figure 98 Profile status change or delete

Change Log
Information regarding the changes made to Managed Billing Profiles is tracked via the
Change Log. This log is available for viewing at the Profile level and displays the changes
that were made, along with the User that made the changes.

To view the history of profile changes

1 Locate the specific profile and navigate to the Profile Configuration page.
2 Click on the Change Log tab.

Page 137 of 214

Orbital Virtual Terminal Chapter 8 Working With Profiles
Version 4.2 Change Log

Figure 99 Profile Change Log

3 Click on the radio button beside the change you wish to view in greater detail.
4 Click on View Details.
5 Review the two columns of information to identify the changes made.
NOTE A Change of Profile action is recorded if the Update command button is clicked on the Profile
Configuration page regardless of whether new information was entered. If there is no difference
found in the Change Log detail columns, the Update command button was clicked without new
information being entered for the profile.

Page 138 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Chapter 9 Managed Billing

The Managed Billing Service takes Profile Management to the next step. Once invoked, this
convenient service manages the processing of authorization-capture transactions according
to a merchant’s pre-defined rules. This automation simplifies the billing process of recurring
transactions. Additionally the risk and cost of issues relating to human error are mitigated.
It is an effective service for recurring, installment and deferred billings.
Recurring Cardholder agrees to a regular on-going billing of a
designated amount at a specified time interval.

Installment Cardholder agrees to set number of payments over a

specified time for the purchase of an item.

Deferred transaction A single billing that is triggered at a predefined future date.

Managed Billing supports the following card types:
American Express
Discover Card
JCB
MasterCard
Visa
Maestro – UK Domestic*
Electronic Check *
*Supported only on Salem Platform
Managed Billing first requires that Customer Profile Management be set at the Merchant
(MID) level. Next one of two Managed Billing options is selected, either Recurring, which
also supports installment billing, or Deferred. The following additional functions can be
established at the merchant level [applicable to all profiles] or at the individual profile:
Billing Schedule:
Order Number Generation
Automated Cardholder notifications via e-mail

Billing Schedule
Whether enabled for recurring or deferred, a billing schedule must be established. It may be
established at the merchant level or at the profile level or both. An individual profile setting
will override the merchant level setting for that specific profile. Profile billing schedules or
parameters (dates, number of occurrences, card information, etc.) can be edited or
modified at any time. However to ensure the next billing occurs as desired, changes should
be made at least 24 hour in advance of the billing.

Recurring/Installment Parameters – Merchant Level

To create a merchant level billing schedule, click on ADMIN > Profile > Managed Billing
to open the Admin – Profile Managed Billing Admin page. On this page you may choose
to create a recurrent billing pattern to be applied to all Managed Billing profiles.
NOTE Individual Profile parameters selected at the individual profile level always supersede the
merchant level parameters.

Page 139 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Figure 100 Admin – Profile Managed Billing Admin (Recurring Billing)

To establish a Merchant Level recurring billing pattern

1 Select one Recurrence Pattern. This defines the frequency of payment transaction
processing.
Not Specified No recurrent pattern.
Choose this option if not specifying a recurrent pattern at the Merchant level.

Weekly Number of week(s) and day of the week.

 Click on the Weekly radio button,
 Enter the number of weeks between billings; and,
 Select the day of the week on which the billings are to occur.

Monthly Day of Month(s) or weekday of month(s).

 Click on the Monthly radio button, then follow on of the following:
 Click on radio button before Day, enter the specific day of the month, and
the number of months between billings; or,
 Click on radio button before The, select the order, select the Day, and
enter the number of months between billings.

Yearly Month and day or weekday of month.

 Click on the Yearly radio button, then select one of the following:
 Click on radio button before Recur every, select the Month, and enter the
specific day of the month; or,
 Click on radio button before The, select the order, select the Day, and
select the Month.

Page 140 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

NOTE If 31st day of a month is selected, for months with less than 31 days, the billing will occur on
the last day of the month.

2 Select the Range of Recurrence. This defines how long the cardholder is billed. Choose
one of the following:
Not Specified No recurrent pattern.
 Choose this option if not specifying a recurrent pattern at
the Merchant level.

Start  User defined future start date for the billings. This date
must be at least one day after the information is being
entered.
 Select the Month
 Select the day of the Month
 Select the Year

NOTE If the billing schedule is changed or modified, typically a

new Start Date is required.

Click on one of the following billing range options:

No End date  Click on the radio button before No End Date for on-going
billing. The billings will continue according to the designated
billing pattern until action is taken to end the billing.

End after [blank] billings  To choose a specific number of billings, click on the radio
button before End after and enter the number of billings.

End by  To choose a date by which the billings are to end, click on

the radio button before End by, select the month, select
the day, and select the year.

3 Select one of the two methods to generate the Order Number. The Order Number/Order
ID is used to populate the Order ID/Order Number in Managed Billing payment
transactions.
Profile ID  Select Use Profile ID to use the Profile ID, also known as the Customer
Reference Number, for Order ID/Order Number.

Dynamic  Select Dynamic to use a systemically created computed number combining

up to 16 bytes of the Profile ID and incrementing integers.

4 Click on Save button to save the settings.

Recurring/Installment Parameters – Profile Level

The billing pattern may be established or changed at the individual Profile level. The
decisions are the same as those described above at the Merchant level. To locate and access
a Profile, use the same procedures discussed in the Working With Profiles section.

To establish a Merchant Level recurring billing pattern

1 Click Add Managed Billing – Recurring found close to the bottom of the Profile
Management page. As soon as it is checked, the page refreshes with override default
options.
2 To apply the defaults as displayed, click on Update.

Page 141 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

3 To change the defaults, click on Override defaults.

4 Make your selections.
5 Click on the Update button. The updated parameters are immediately applied. The
authorization-capture request is initiated in accordance with the billing schedule.
Figure 101 Managed Billing Schedule options

Page 142 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Deferred Billing Parameters – Merchant Level

To set the deferred billing parameter at the merchant level, use the ADMIN > Profile >
Managed Billing option to open Admin-Profile Managed Billing Admin page. On this page
you may choose and save the method for creating the Order Number for all Deferred Billing
transactions. The same two choices are available as for Recurring or Installment billing:

To establish the Order Number parameter

1 Select one of the two methods to generate the Order Number. The Order Number/Order
ID is used to populate the Order ID/Order Number in Managed Billing payment
transactions.
Profile ID  Select Use Profile ID to use the Profile ID, also known as the Customer
Reference Number, for Order ID/Order Number.

Dynamic  Select Dynamic to use a systemically created computed number combining

up to 16 bytes of the Profile ID and incrementing integers.

2 Click on Save button to save the settings.

Figure 102 Admin – Profile Managed Billing Admin (Deferred Billing)

Deferred Billing Parameters – Profile Level

Deferred Billing is used to establish a future date to process a transaction. The date is set at
the Profile level. Only one future payment can be defined per Profile at a time.
Navigate to the Profile Configuration tab on the Admin – Profile Management page either
by creating a new profile or locating an existing profile.

To add Deferred Managed Billing to a profile

1 Check the box next to Add Managed Billing – Deferred found at the end of the profile
settings. Once checked, the screen refreshes displaying two additional fields.

Page 143 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Figure 103 Deferred Billing options

2 Select one of the two methods to generate the Order Number. The Order Number/Order
ID is used to populate the Order ID/Order Number in the Managed Billing payment
transactions.
Profile ID  Select Use Profile ID to use the Profile ID, also known as the Customer
Reference Number, for Order ID/Order Number.

Dynamic  Select Dynamic to use a systemically created computed number combining

up to 16 bytes of the Profile ID and incrementing integers.

3 Select the Deferred Billing Date: the Month, Day and Year. This is date the deferred
transaction will be processed, authorized and settled if approved.
4 Click on Add for new profiles or Update for existing profiles. A message indicated a
successful Add or Update is displayed.

Page 144 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Scheduled Billings
A list of future billings and the associated billing schedule is available. A maximum of 20
future billings is displayed on the Admin – View Managed Billing page. Navigate to the
page by using the Admin - Profile Management page and selecting the Scheduled
Billing tab. The following page appears. The top portion of the screen displays profile
information including Billing Schedule information. The bottom section provides the future
billings dates, cardholder account number, dollar amount, and the status.
Figure 104 View Managed Billings – Scheduled Billings

Skip Billing
The option to skip a billing is provided. Click on the radio button beside the billing date that
is to be skipped and then click on the Skip Billing button. This suspends the billing for the
date designated. A confirmation message appears at the top of the screen and the Status is
change to Billing Skipped. Billing will resume on the next scheduled date.
NOTE If the profile has been established with a set number of scheduled billings, the Skip functionality
moves the skipped billing to the end of the scheduled billings. It does not eliminate the billing.

Page 145 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Figure 105 Skipped Billing

A skipped billing can be restored prior to its billing date by clicking on the radio button next
to the skipped billing date and the Restored Billing button. A message indicating it has
been restored appears and the status is changed to Billing Pending. To ensure success,
the Restore Billing action should be completed at least 24 hours in advance of the billing
date.

Page 146 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Figure 106 Restored Billing

Cancelled Billing
The Managed Billing functionality can be turned off at the profile level or the merchant level.
This cancels all future billings.

To remove Managed Billing at the Profile level

1 Locate the profile.
2 Uncheck the box next to Add Managed Billing.
3 Click on Update button. An Update message is displayed.
NOTE If Managed Billing is resumed by checking the Add Managed Billing box, the Merchant level
recurring billing settings are applied unless they are overridden by a manual reset at the profile
level.

To remove Managed Billing at the Merchant level

To deactivate the Managed Billing functionality at the merchant level, Gateway Support
must be contacted. Once turned off at the Merchant level, all future billings for every
Managed Billing profile is frozen, but not removed. Should the functionality be restored, the
billing pattern resumes at the point it was interrupted.

Page 147 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

Completed Billings
A six month history of processed Manage Billing transactions can be viewed in the Virtual
Terminal. It is accessed through the Completed Billings tab on the Admin - Profile
Management page. The top portion of the page displays basic Profile information including
the billing schedule. The bottom section contains the following:
Billing Date
Order ID
Card Holder Number
Amount of the Transaction
Status
Figure 107 View Managed Billings – Completed Billings

To view the details of the transactions, click on the associated radio button and then View
Order. The Review – View Order screen is displayed. It is the same page as discussed in
the Viewing Transaction Details section.

Change Log
Information regarding the changes made to Managed Billing Profiles is tracked. A log is
available that tracks the changes and the User that made the changes.

To view the history of profile changes

1 Locate the specific profile and navigate to the Profile Configuration page.

Page 148 of 214

Orbital Virtual Terminal Chapter 9 Managed Billing
Version 4.2 Change Log

2 Click on the Change Log tab.

Figure 108 Profile Change Log

3 Click on the radio button beside the change you wish to view in greater detail.
4 Click on View Details.
5 Review the two columns of information to identify the change made.
NOTE A Change of Profile action is recorded if the Update command button is clicked on the Profile
Configuration page regardless of whether new information was entered. If there is no
difference found in the Change Log detail columns, the Update command button was clicked
without new information entered for the profile.

Page 149 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase

Chapter 10 Working with Purchasing Cards

The Orbital Gateway supports the processing of procurement cards or Purchasing Card by
fully supporting the enhanced data required by Visa and MasterCard for both Level 2 and
Level 3 data. Additionally, for American Express, the Orbital Gateway for Salem customers
supports Level 2 and enhanced Transaction Advice Addenda (TAA).
Purchasing Cards with Level 3 data are typically used in a business-to-business environment
that provides and collects funds for outstanding invoices. Merchants have the ability to
collect their funds in conjunction with the settlement of their credit card transactions and
still provide their customer with the necessary line item detail, providing a cleaner process
for both the merchant and their customer.

Entering Purchasing Card Data for a Purchase

There are three levels of Purchasing Card data that can be collected:
Level I The data normally required for any credit card transaction (described in
Processing a Credit Card Purchase (Authorization and Capture)).
Level II A few additional fields, most notably Purchase Order Number and Sales Tax
Amount.
Level III Detailed line-item data pertaining to each item found in a transaction. A
merchant must be configured for this feature, which currently supports only
U.S. Dollar currency transactions.
Special Interchange rates can apply when the Level II or III data is included with a
transaction. Contact your Sales or Account representative for more information.
You can enter Purchasing Card Level II and III data as part of an Authorization and Capture
or Force transaction. The fields on the Purchasing Card tabs are identical for both types of
transactions; the procedure below uses the New Order - Auth page to illustrate these
tabs.

To enter Purchasing Card data for a purchase or force

1 If you want to enter Purchasing Card Level II data for the purchase, select the
PURCHASING CARD DATA II tab.
NOTE The Card Number and Amount fields on the RECOMMENDED DATA tab must be completed in
order to process information entered on either of the Purchasing Card tabs.

Page 150 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase

Figure 109 Entering Purchasing Card Level II data

The Purchase Order #, Sales Tax Amount, and Destination Zip Code fields are
conditionally required—if you enter a value for one, you must enter a value for all these
fields. As illustrated above and in the next figure, the Destination Zip Code field is
moved to the Level III tab if enabled for this level of Purchase Card data.
The Transaction Advice Addendum Records and Ship To Information fields apply
only to AMEX Purchasing Card transactions. These fields are only visible for merchants
on the Salem platform.
2 Enter the Purchase Order # from the customer and the Sales Tax Amount for the
entire transaction.
3 In the fields in the Transaction Advice Addendum Records section, enter specific
details about the transaction that can be displayed on the cardholder's statement for
purchase identification and tracking purposes.
TAAs should be as concise as possible, while still providing adequate information. For
example, a TAA of Merchandise would not be acceptable.
4 Enter the shipping address information.
5 If only entering Purchase Card Level II data for the purchase, click on the command
button for the action you want to take.
6 If you want to enter Purchasing Card Level III data for the purchase, select the
PURCHASING CARD DATA III tab.

Page 151 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase

Figure 110 Entering Purchasing Card Level III details (Salem merchant, MasterCard)

The PURCHASING CARD DATA III tab contains two sections: the Enter Order Level
Detail Below section at the top, in which you enter information pertaining to the entire
transaction, and an Enter Line Item section at the bottom where you enter information
for each item in the transaction.
NOTE Different fields are displayed on this tab for Tampa merchants than for Salem merchants. Also,
different fields are displayed and/or required for Visa Purchasing Cards than MasterCard.

This tab also contains the Variance Calculator—a floating window (circled in Figure
110) that actively calculates the sum of the completed line item entries
[(Unit Cost * Quantity) - Discount Amount] and compares it to the overall
transaction amount. The Variance Calculator also contains the buttons to submit the
transaction; the button on the main portion of the tab allows you to save each line item.
CAUTION For Tampa merchants, the variance must be zero before submitting the transaction. The
transaction will not be accepted if the line item total is greater than the transaction total.

7 In the Enter Order Level Detail Below section, complete the fields with information
that applies to the entire transaction.

Field Tampa Salem Description

Freight Amount   Total freight or shipping and handling
charges. Enter numeric values in a format
with two decimal places (##.##).

Destination Country Code   Select the two-character code of the country

to which the goods are shipped.

Page 152 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase

Field Tampa Salem Description

Destination Zip Code   The zip/postal code of the location to which
the goods are shipped. Required for best
interchange rate.

Ship From Zip   The zip/postal code of the location from which
the goods are shipped. Required for best
interchange rate.

Duty Amount  Total charges for any import and/or export

duties included in this transaction.

Discount Amount  Visa only; should not be sent for MasterCard.

The total amount of discount applied to the
transaction by the merchant.

VAT Tax Amount  Visa only; should not be sent for MasterCard.
The total amount of VAT or other tax included
in this transaction.

VAT Tax Rate  Visa only; should not be sent for MasterCard.
The total amount of VAT or other tax included
(expressed in percentage terms) for this
transaction.

8 In the Enter Line Item section, complete the fields for the first line item in the
purchase.
NOTE All fields, except Tax Type Applied and Discount Amount, are required for each line item. If
the correct value for a field (Commodity Code, Product Code) is not known, you must still
enter a value.

Field Tampa Salem Description

Item Type   Select Sale or Return to identify the type of
line item entry.

Product Code   Product code of the item purchased.

Description   Text description of the item purchased.

Unit Cost   Unit cost of the item purchased.

Quantity   Number of units of the item purchased.

Unit of Measure   Select the unit of measure used for this line
item. All units of measure configured for your
merchant account are included in the list.

Tax Rate   The tax rate applied for this item.

Tax Amount   The tax amount applied for this item.

Commodity Code   Visa only.

The commodity code used to classify the item
purchased.
Discount Amount   Amount of the discount applied to the line
item. [Optional]
As you enter values, the Line Item Total is calculated using the following formula:

Page 153 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase

Line Item Total = (Unit Cost * Quantity) - Discount Amount

NOTE Note that the Line Item Total does not include tax.

9 Click on Save Line Item.

Figure 111 Purchasing Card Level III Data with Line Item defined

The fields in the Enter Line Item section are cleared, and the line item number is
incremented.
A Line Items section is added at the bottom of the tab. This section lists information
about each line item. You can click on the edit option to edit any of the information for
the line item or the remove option for a line item to remove it from the transaction.
CAUTION Be aware that you are not prompted to confirm the removal of the line item from the
transaction.

The Variance Calculator is updated to reflect the Line Item Total value of all line
items defined. The Variance value represents the remaining purchase amount that
needs to be accounted for in additional line items. If the Variance value is displayed in
red, there is a negative balance remaining—the amounts calculated in the line items
surpasses the Amount indicated on the RECOMMENDED DATA tab.
CAUTION For Tampa merchants, the Variance must equal zero to submit the transaction.

10 Repeat steps 8–9 for each line item in the purchase.

Page 154 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase Card Credit/Refund

11 Click on Auth and Capture or Auth on the Variance Calculator.

Entering Purchasing Card Data for a Purchase Card

Credit/Refund
There are two levels of Purchasing Card data that can be collected:
Level I The data normally required for any credit card transaction (described in
Processing a Credit Card Purchase (Authorization and Capture)).
Level II A few additional fields, most notably Purchase Order Number, Sales Tax
Amount, Destination Postal Code.
1 If you want to enter Purchasing Card Level II data for a credit/refund, select the
PURCHASING CARD DATA II tab.
NOTE The Card Number and Amount fields on the RECOMMENDED DATA tab must be completed in
order to process information entered on either of the Purchasing Card tabs.

Figure 112 Entering Purchase Card Level II data for a credit

The Purchase Order #, Sales Tax Amount, and Destination Zip Code fields are
conditionally required—if you enter a value for one, you must enter a value for all these
fields.
The Tax Indicator field is visible only for a Master Card transaction.
The Transaction Advice Addendum Records and Ship To Information fields apply
only to AMEX Purchasing Card transactions. These fields are only visible for merchants
on the Salem platform.

Page 155 of 214

Orbital Virtual Terminal Chapter 10 Working with Purchasing Cards
Version 4.2 Entering Purchasing Card Data for a Purchase Card Credit/Refund

2 Enter the Purchase Order # from the customer, the Sales Tax Amount for the entire
transaction, and the Destination Zip Code.
3 In the fields in the Transaction Advice Addendum Records section, enter specific
details about the transaction that can be displayed on the cardholder's statement for
purchase identification and tracking purposes.
TAAs should be as concise as possible, while still providing adequate information. For
example, a TAA of Merchandise would not be acceptable.
4 Enter the shipping address information.
5 Click on Credit.

Page 156 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Processing a New Gift Card Transaction

Chapter 11 Working with Gift Cards

The Orbital Virtual Terminal supports Chase Paymentech Solutions’ proprietary Stored Value
Card product called Gift Card (formerly known as FlexCache). This functionality is available
for both Salem and Tampa merchants.

Merchant Account Set up

If you are interested in processing Gift Card, please contact your Chase Paymentech
Solutions Account Representative to begin the set up process.
Once set up for Gift Card, you will see the FLEXCACHE tab in the VT menu bar. From within
this menu you can choose to process any Gift Card transaction type or access current and
historical transactions.
Options within this menu are:
New Transaction
Balance Inquiry
Activation
Current Transactions
Historical Transactions

Processing a New Gift Card Transaction

From the FLEXCACHE > New Transaction menu, several transaction options are
presented:
Authorization Only This is only supported for Salem merchant and allows you to
do an “authorization only” which puts a hold on the funds for
7 days. You must “Capture” the transaction within the 7
days. After the 7 days you must perform a new
authorization. Capturing a transaction is done from the Open
Batch section.

Redemption This allows you to process a redemption transaction. This is

the equivalent to a sale transaction in the credit card
environment.

Prior Redemption This is only supported for Tampa merchants and is only used
when a voice authorization is obtained.

Add Value This allows you to add value to a customer’s card.

Prior Add Value This is only supported for Tampa merchants and is only used
when a voice authorization is obtained.

Refund This places value back on a customer’s FlexCache card.

NOTE The following section only displays the transaction order page. To view the response page, see
Figure 117 Gift Card response page .

Page 157 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Processing a New Gift Card Transaction

Figure 113 Gift Card New Transaction page

Performing a Gift Card Authorization

Almost all Gift Card transactions immediately affect the card balance, meaning they add or
reduce the funds based on the result. In some circumstances, there might be a desire to
perform a sale wherein an authorization is performed, and the funds are not actually
moved. One reason for this, for example, might be a deferred shipment of goods.
The Auth transaction does exactly that. It reduces the Available to Buy amount without
reducing the actual funds.
Once the item has been shipped, performing a Redemption can complete the transaction.
There are two different optional behaviors when managing Redemptions: Partial Redemption
and Redemption Completion. For more information on these two options, see Performing a
Gift Card Sale (Redemption).
Generally speaking, an authorization holds the requested funds for seven days, after which
the funds will be available again.
NOTE This functionality is only available to merchants processing through the Salem Platform.

To perform a Gift Card Authorization:

1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Auth radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount of the sale in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.

Page 158 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Processing a New Gift Card Transaction

8 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.
9 Click on the Auth button.

Performing a Gift Card Sale (Redemption)

A Redemption is the mechanism to perform an immediate redemption. Once completed,
Redemptions can be reversed or partially redeemed. By partially redeeming a redemption,
the original redemption is released and a new redemption is performed for the new amount.
See Viewing Transaction Details for more information on how to perform a partial
redemption.
For security reasons, most Gift Card programs require the four-digit CVD (CardSecVal)
printed on the front of the card to be included with the redemption request.
1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Redemption radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount of the sale in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.
9 Click on the Redemption button.

Performing a Prior Redemption

Merchants processing to the PNS Host can process Prior Redemption transactions by
additionally providing the correct prior approval code. If the valid Prior Approval code is not
passed, it is treated as a new Redemption request.
Prior Redemption transactions are not supported on the Salem system; therefore, Salem
merchants attempting to process a Prior Redemption will receive an error response.
1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Prior Redemption radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount of the sale in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.

Page 159 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Processing a New Gift Card Transaction

8 Enter the Prior Auth Approval Code that was obtained via voice authorization.
9 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.
10 Click on the Prior Redemption button.

Adding Funds to a Gift Card Balance

This transaction adds value to an active card. If an Add Value is performed on an inactive
card, it both activates the card and performs the add value action.
1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Add Value radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount to be added to the card in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.
9 Click on the Add Value button.

Performing a Prior Add Value

Merchants processing to the PNS Host can process Prior Add Value Transactions by
additionally passing the correct prior approval code. If the valid Prior Approval code is not
passed, it is treated as a new Add Value request.
Prior Add Value transactions are not supported on the Salem system; therefore, Salem
merchants attempting to process a Prior Add Value will receive an error response.
1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Prior Add Value radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount to be added to the card in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Enter the Prior Auth Approval Code that was obtained via voice authorization.
9 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.

Page 160 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Viewing the Balance Available on a Gift Card

10 Click on the Prior Add Value button.

Refunding a Purchase Value to a Gift Card

This transaction is for initiating refunds to a Gift Card. It is essentially the same as an Add
Value transaction.
1 Select FLEXCACHE > New Transaction to open the FlexCache – New Transaction
page.
2 Click on Refund radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount to be added to the card in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Enter the Card Verification Data 2 number. This is an extra security feature. This
option is up to you, you may choose to use this extra feature or not. Please notify your
Account Executive of your decision at time of set up.
9 Click on the Refund button.

Viewing the Balance Available on a Gift Card

This option allows you to inquire as to the current balance of a card, without adding or
subtracting any value.
1 Select FLEXCACHE > Balance Inquiry.
2 Enter the Card Number.
3 Enter the Card Verification Data 2 value. For security reasons, most Gift Card
programs require the four-digit CVD (CardSecVal) printed on the front of the card to be
included).
4 Click on the Submit Inquiry button.
Figure 114 Gift Card Balance Inquiry page

Page 161 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Gift Card Activation

The response displays the customer’s current balance.

Figure 115 Gift Card Balance Inquiry response page

Gift Card Activation

From the FLEXCACHE > Activation menu, a user can process the following types of
activations.
Single Activation You must first activate a card before you can perform any
other transaction. This transaction activates only one card at
a time.
NOTE The Orbital Gateway supports $0 activation transactions
for PNS (BIN 000002).

Block Activation Block activation will activate up to 10,000 cards at one time.

Reactivation If a card has been deactivated you may choose to reactivate

it by using this transaction request.

Deactivation You may deactivate a card with this transaction type.

Prior Activation This is only supported for Tampa merchants. This transaction
type is used when a voice authorization is obtained.

Activating a Single Gift Card

You must first activate a card before you can perform any other transaction. This
transaction activates only one card at a time.
1 Select FLEXCACHE > Activation menu to open the FlexCache – Activation page.
2 Click on Single Activation radio button.

Page 162 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Gift Card Activation

3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount that needs to be activated in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Click on the Single Activate button.
Figure 116 Gift Card Single Activation page

The response page is displayed with either an approval or a decline.

Figure 117 Gift Card response page

Page 163 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Gift Card Activation

Activating a Block of Gift Cards

A Block Activation provides for the ability to activate more than one card at a time. A
maximum of 10,000 cards can be activated at one time. If a Block Activation fails, none of
the cards in the block are activated.
1 Select FLEXCACHE > Activation menu to open the FlexCache – Activation page.
2 Click on Block Activation radio button.
3 In the Card Number box, enter the Gift Card number. This is the card number on the
first card in the series. Do not include spaces.
4 In the Additional Cards field, enter the total number of cards that need to be activated
LESS the card entered in the Card Number box. The card number in the Card Number
field counts as the first card. The number entered in the Additional Cards field is the
balance of the number of cards you wish to activate. For example: If you wish to
activate 500 cards, enter the first card number in the Card Number field then specify
499 cards in the Additional Cards field.
5 Enter the Amount that needs to be activated on each card.
6 Enter the Order ID # from the purchase transaction.
7 If desired or required by your internal processes, enter the Employee ID.
8 If desired or required by your internal processes, enter an Order Description.
9 Click on the Activate button.
Figure 118 Block Activation page

After clicking on the Activate button, you are directed to an intermediate page that informs
you that your activation request is being processed. This is due to the high number of cards
potentially being activated. From this page you have the option to Return to Block
Activation page or linking to the Block Activation Results page.

Page 164 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Gift Card Activation

Figure 119 Block Activation processing page

By clicking on the Block Activation Results button, the status of the block activations is
displayed. The page displays information so that you may determine if the block activation
was successful or failed. Please note that while you may submit up to 10,000 cards for a
block activation, the process is broken into blocks of 100. This means that any block of 100
may fail. If one block fails the entire block activation stops processing. To view an updated
status of the block activation, click on the Refresh Results button to refresh the Results
and # Activated columns.
Figure 120 Block Activation status results

You may further drill down into a particular block by clicking on the radio button and clicking
on the View Block Details button. The View Block page displays all card numbers within
the chosen block and their individual status. In this example, the Block Activate failed. To
view individual cards within the block, click on the radio button by the transaction and click
on the View Order button.

Page 165 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Gift Card Activation

Figure 121 Block Activate Details page

Reactivating a Gift Card

If a card has been deactivated, you may choose to reactivate it by using this transaction
request.
1 Select FLEXCACHE > Activation menu to open the FlexCache – Activation page.
2 Click on Reactivation radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount that needs to be reactivated in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Click on the Reactivate button.
NOTE The Reactivation page is similar to the Single Activation page. See Activating a Single Gift Card for
examples of the entry page and the response page.

Deactivating a Gift Card

You may deactivate a live card by performing a deactivation. Please note that once a card is
deactivated, you cannot choose to Activate again. You must Reactivate.

1 Select FLEXCACHE > Activation menu to open the FlexCache – Activation page.
2 Click on Deactivation radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the Order ID # from the purchase transaction.

Page 166 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

5 If desired or required by your internal processes, enter the Employee ID.

6 If desired or required by your internal processes, enter an Order Description.
7 Click on the Deactivate button.
NOTE The Deactivation page is similar to the Single Activation page. See Activating a Single Gift Card for
examples of the entry page and the response page.

Prior Activation of a Gift Card

A Prior Activation is similar to a Single Activation. It is only performed if a manual Voice
Approval has been obtained for the transaction. An additional Prior Auth Approval Code field
is required to be populated with the manually obtained Voice Approval code in order to
complete the transaction. Prior activations are only supported for Tampa merchants.
1 Select FLEXCACHE > Activation menu to open the FlexCache – Activation page.
2 Click on Prior Activation radio button.
3 In the Card Number box, enter the Gift Card number. Do not include spaces.
4 Enter the amount of the sale in the Amount box.
5 Enter the Order ID # from the purchase transaction.
6 If desired or required by your internal processes, enter the Employee ID.
7 If desired or required by your internal processes, enter an Order Description.
8 Enter the Prior Auth Approval Code that was obtained via voice authorization.
9 Click on the Prior Activate button.
NOTE The Prior Activation page is similar to the Single Activation page. See Activating a Single Gift Card
for examples of the entry page and the response page.

Working with Gift Card Batches

Since transactions affect the balance of a card in real time, Gift Card transactions are not
affected by the End of Day process options as other methods of payments are (i.e. Credit
cards). Instead, transactions automatically fall into one of two buckets when viewed through
the Virtual Terminal:
Current Transactions (this includes all un-settled activity)
 Authorizations that have not been redeemed (Redemption Completion)
 Declined transactions
 Errors
Historical Transactions (all redeemed items)
These items are grouped on a daily basis on the same timing that the Chase
Paymentech Gift Card System reports activity, which is 5A.M.–5A.M.
NOTE All true Gift Card reporting is available from the Gift Card system, including Resource Online. Any
questions about the available reports should be directed to your Account Manager. The Virtual
Terminal should not be used for Gift Card reconciliation.

Page 167 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Viewing Current Transactions (Open Batch)

To view, manage and generate reports on all Gift Card transactions that have not yet
settled, select FLEXCACHE > Current Transactions. In addition to performing numerous
actions, you may also choose to view transaction details or a summary of the transactions.
1 Select FLEXCACHE > Current Transactions to view the FlexCache – Current
Transactions page.
2 To search only for Block Activations, click on Search only Block Activations checkbox.
Choosing this option refreshes the screen and allows you to choose the date range.
3 To search by Transaction Type, select an option from the dropdown menu:
Auth Auth Reversal

Redemption Redemption Reversal

Add Value Add Value Reversal

Refund Refund Reversal

Single Activation Single Activation Reversal

Block Activation Block Activation Reversal

Deactivation Deactivation Reversal

Reactivation Reactivation Reversal

Balance Inquiries Declines and Errors

4 To search by a specific Gift Card number, enter the value in the Card Number box.
5 To search by Order ID number, enter the value in the Order # box.
6 To search by the FlexCache Host Reference Number, enter the value that was
returned in the transaction response.
7 To search by the Transaction Reference Number [TxRefNum], enter the value that
was returned in the transaction response.
8 In addition to any of the search parameters mentioned above, a date range can be
utilized to further narrow a search request. By default, the date range is set to the
current day. Change the From and To dates as needed. If no date range is needed,
uncheck the Date Range checkbox.

Page 168 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Figure 122 Current Transactions search page

Results Output
Once the search criteria have been selected, there are several methods for generating the
results. Choose one of the following options in the Query Type dropdown box to complete
the search.
Detailed Transactions (Default) Search results are outputted to the screen for
immediate viewing. Individual transactions are
displayed in groups of 10. It is from this screen that
additional functionality can be accessed such as
Redeem, Redeem Partial, and Reverse Order. See
Viewing Transaction Details.

Summary Query Search results are summarized on the screen.

Transaction counts by various transaction types are
provided. Examples include Sale counts and Return
counts. See Summary Query. Transaction Types may
differ from screenshot provided. To print Summary
page, click on Print button and change printer options
to landscape mode.

Generate Detail Report Search results are provided in PDF format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Page 169 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Generate Detail File Search results are provided in CSV format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Viewing Transaction Details

The Detailed Transactions query allows you to manage the Gift Card transactions in your
current batch. Click on the radio button by the transaction that is to be viewed and click on
the desired button to perform an action.
Figure 123 Gift Card – Current Transactions search results

View Order button

Displays the response data from the original transaction.
Approval Code Provided when the transaction has been approved by
the Stored Value Host System.

Response Code Orbital Gateway response code indicating the status of

the transaction. A 00 indicates the transaction was
successful and approved. Any number greater than 00
generally indicates a decline or error. A text message
will indicate the exact error message associated with
the response code. See Response Codes for list of
response codes.

Card Verification Data Provided by the Stored Value Host System when a card
Response Code verification number is submitted in the New Order
request. See CVV2/CVC2/CID Response Codes for list of
CVD response codes.

Page 170 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Previous Balance The balance on the Gift Card prior to the current
transaction.

Transaction Amount The amount of the current transaction.

Current Balance The balance on the Gift Card after the current
transaction has been processed.

Card Number The Gift Card number provided in the original

transaction.

Order ID # The order number for the transaction.

FlexCache Host Reference The reference number returned from the Stored Value
Number Host System.

Transaction Date Date the transaction was originally created.

Transaction Reference Unique identifier assigned to each transaction; also

Number known as the Orbital Gateway Reference Number.

Transaction Last User ID or system which last modified this transaction.

Modification User ID
Figure 124 Current Transactions – transaction details page

Redeem button
For Salem merchants only. Redeems a Gift Card authorization transaction for the full
amount of the authorization. If the Remaining Balance Capture Setting is enabled on the
FlexCache Admin page, the redemption amount can be less than the authorized amount.
See Remaining Balance Capture Setting for more information on how this setting works.
Redeem Partial button

Page 171 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

For Salem merchants only. Allows you to redeem an amount less than the authorized
amount. Choosing this option directs you to another page to specify the redemption
amount. Please note that this releases the hold on the remaining balance of the original
authorization.
Figure 125 Redeem Partial order page

Reverse Order button

All transaction, excluding Balance Inquiries, can be reversed, thus returning a
transaction to the state it was in prior to the action being reversed. You may not
perform a reversal if subsequent transactions are run on that card which negates the
affect of the initial transaction. For example: You may not reverse an activation that has
a subsequent transaction. The card can only be deactivated.
There are two restrictions as it relates to processing Reversals:
 For Salem customers, the reversal must be performed within seven days of the
original transaction.
 For PNS-based customers, the reversal must be performed before the next batch
close. Closing of Gift Cad batches are usually performed automatically by the Tampa
host system at 5:00A.M. EST, regardless of what the Auto-Settle time is on the
Gateway.
NOTE Gift Card transactions cannot be manually settled. The transactions in Current Transactions (open
batch) are settled daily at approximately 5:00 AM, at which point they are moved to Historical
Transactions (closed batch). The only exceptions are Auth Only transactions. These remain in Open
Batch until the transaction type is changed.

Summary Query
The Summary Query displays a summary of Gift Card-related activity based on the search
filters. The summary information includes totals by Gift Card transaction type.

Page 172 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Figure 126 Current Transactions – Summary Query

Viewing Historical Transactions (Closed Batches)

To search for historical Gift Card transactions, select FLEXCACHE > Historical
Transactions. Historical transactions are the transactions that have been previously
settled. You may view transactions details or reverse transactions from this page.
1 Select FLEXCACHE > Historical Transactions to view the FlexCache – Historical
Transactions page.
2 To search only for Block Activations, click on Search only Block Activations checkbox.
Choosing this option refreshes the screen and allows you to choose the date range.
3 To search by Transaction Type, select an option from the dropdown menu:
Auth Auth Reversal

Redemption Redemption Reversal

Add Value Add Value Reversal

Refund Refund Reversal

Single Activation Single Activation Reversal

Block Activation Block Activation Reversal

Deactivation Deactivation Reversal

Reactivation Reactivation Reversal

Balance Inquiries Declines and Errors

4 To search by a specific Gift Card number, enter the value in the Card Number box.

Page 173 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

5 To search by Order ID number, enter the value in the Order # box.

6 To search by the FlexCache Host Reference Number, enter the value that was
returned in the transaction response.
7 To search by the Transaction Reference Number [TxRefNum], enter the value that
was returned in the transaction response.
8 In addition to any of the search parameters mentioned above, a date range can be
utilized to further narrow a search request. By default, the date range is set to the
current day. Change the From and To dates as needed. If no date range is needed,
uncheck the Date Range checkbox.
Figure 127 Historical Transactions search page

Results Output
Once the search criteria have been selected, there are several methods for generating the
results. Choose one of the following options in the Query Type dropdown box to complete
the search.
Detailed Transactions (Default) Search results are outputted to the screen for
immediate viewing. Individual transactions are
displayed in groups of 10. It is from this screen that
additional functionality can be accessed such as
Reverse Order. See Viewing Historical Transaction
Details.

Page 174 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Summary Query Search results are summarized on the screen.

Transaction counts by various transaction types are
provided. Examples include Sale counts and Return
counts. See Historical Summary Query. Transaction
Types may differ from screenshot provided. To print
Summary page, click on Print button and change
printer options to landscape mode.

Generate Detail Report Search results are provided in PDF format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Generate Detail File Search results are provided in CSV format. The report
is obtained from the REPORTING menu tab. The VT
User ID must be enabled for Reporting in order to
retrieve this report. See Working with Reports for
more information on retrieving reports.

Viewing Historical Transaction Details

The Detailed Transactions query allows you to view and reverse the Gift Card transactions in
your historical (closed) batch. Click on the radio button by the transaction that is to be
viewed and click on the desired button to perform an action.
Figure 128 Gift Card – Historical Transactions search results

View Order button

Displays the response data from the original transaction.
Approval Code Provided when the transaction has been approved by
the Stored Value Host System.

Page 175 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Response Code Orbital Gateway response code indicating the status of

the transaction. A 00 indicates the transaction was
successful and approved. Any number greater than 00
generally indicates a decline or error. A text message
will indicate the exact error message associated with
the response code. See Response Codes for list of
response codes.

Card Verification Data Provided by the Stored Value Host System when a card
Response Code verification number is submitted in the New Order
request. See CVV2/CVC2/CID Response Codes for list of
CVD response codes.

Previous Balance The balance on the Gift Card prior to the current
transaction.

Transaction Amount The amount of the current transaction.

Current Balance The balance on the Gift Card after the current
transaction has been processed.

Card Number The Gift Card number provided in the original

transaction.

Order ID # The order number for the transaction.

FlexCache Host Reference The reference number returned from the Stored Value
Number Host System.

Transaction Date Date the transaction was originally created.

Transaction Reference Unique identifier assigned to each transaction; also

Number known as the Orbital Gateway Reference Number.

Transaction Last User ID or system which last modified this transaction.

Modification User ID

Page 176 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Figure 129 Historical Transactions – transaction details page

Reverse Order button

All transaction, excluding Balance Inquiries, can be reversed, thus returning a
transaction to the state it was in prior to the action being reversed. You may not
perform a reversal if subsequent transactions are run on that card which negates the
affect of the initial transaction. For example: You may not reverse an activation that has
a subsequent transaction. The card can only be deactivated.
There are two restrictions as it relates to processing Reversals:
 For Salem customers, the reversal must be performed within seven days of the
original transaction.
 For PNS-based customers, the reversal must be performed before the next batch
close. Closing of Gift Card batches are usually performed automatically by the Tampa
host system at 5:00A.M. EST, regardless of what the Auto-Settle time is on the
Gateway.
NOTE Gift Card transactions cannot be manually settled. The transactions in Current Transactions (open
batch) are settled daily at approximately 5:00 AM, at which point they are moved to Historical
Transactions (closed batch). The only exceptions are Auth Only transactions. These remain in Open
Batch until the transaction type is changed.

Historical Summary Query

The Summary Query displays a summary of Gift Card-related activity based on the search
filters. The summary information includes totals by Gift Card transaction type.

Page 177 of 214

Orbital Virtual Terminal Chapter 11 Working with Gift Cards
Version 4.2 Working with Gift Card Batches

Figure 130 Historical Transactions – Summary Query

Page 178 of 214

Orbital Virtual Terminal Chapter 12 Importing a File
Version 4.2 Working with Gift Card Batches

Chapter 12 Importing a File

The CSV File Import feature is designed to provide a simplified, streamlined Batch
Processing service to the average merchant needing to process small to medium-sized
batches. Merchants needing a more robust, fully-featured Batch solution are advised to
investigate Chase Paymentech’s Orbital Batch product.
NOTE Additional information is available at http://download.chasepaymentech.com.

In line with the design, the Orbital Virtual Terminal can accept batch file submissions in the
form of CSV files (comma-delimited files with a .csv extension). Users who are configured
for this feature can see the IMPORT FILE tab in the VT menu bar to the right of the
ADMIN tab. If you wish to take advantage of this functionality and it is not a currently
available option on the VT, please contact your Account Executive or Sales Representative
for further direction

Creating a CSV File

Our CSV file format is documented in the Orbital Gateway CSV Interface Specification.
Please contact your Account Executive or Certification Analyst for more information
regarding this specification.
Files must have a .csv extension and be properly formatted using our proprietary CSV
format in order to process transactions via the Import File feature. Consequently, Users
need to successfully process CSV test files through the Chase Paymentech test environment
prior to being configured for the Import File feature in the Production environment.

Importing a CSV file

Once a file has been created, use the IMPORT FILE tab in the VT menu bar to get to the
Import File page.
Figure 131 Import File

Page 179 of 214

Orbital Virtual Terminal Chapter 12 Importing a File
Version 4.2 Working with Gift Card Batches

1 Click on the Browse button to search your computer for the CSV file that you wish to
import.
2 Once the file is found, click on the Import File button to upload it to the Virtual
Terminal. The screen quickly updates to show the new file.

Checking the Status of a CSV file

As soon as a file is imported, it appears on the Import File page with an assigned status.
Users are shown the current Status of the file, Submit Date, Completion Date, File Name,
Record Count, and Submitter (the VT username of the person who uploaded the file).
All files cycle through a number of Status categories while processing; which include
Received, Processing, and Completed. Files can also be in an Error state. To see an error
description, hover over the word Error with your mouse. To refresh the Status results at
any time, click on the Refresh Results button.
Once transactions have successfully processed, they can be viewed individually on either the
Open Batch or Review pages, just like transactions entered manually into the VT.

CSV-generated Reporting
When a CSV file is successfully processed (with a Status of Completed), a CSV results file is
automatically generated and can be located on the REPORTING menu tab. The format of
this response file is found in the Orbital Gateway CSV Interface Specification. Of course,
Users can still generate any ad hoc reporting that is needed via the standard method
provided in the Open Batch or Review pages.

Limitations of the File Import feature

Only Single MID capable
Imported CSV files may only contain transactions for a single merchant number that the
User is logged into at the time of the file upload. In other words, a User with 15 merchant
numbers needs to submit 15 different CSV files, one each while logged in to each respective
merchant account on the VT. Batch merchants needing a Multi-MID capable product should
use Chase Paymentech’s Orbital Batch product.
Only Supports Purchase Card Level I & II
The CSV file format supports Level I and II data, but not Level III. Batch merchants needing
a Level III solution should use Chase Paymentech’s Orbital Batch product.

Page 180 of 214

Orbital Virtual Terminal Appendix A Partial Authorizations
Version 4.2 Working with Gift Card Batches

Appendix A Partial Authorizations

Merchant have the option to support partial authorization via the Virtual Terminal. Once
enabled, transactions can be approved for a portion of the original, requested amount.
These amounts, both approved and requested, are displayed on various pages within the
Virtual Terminal.
The following is an example of a response page for a partial authorization. A user has the
option to void out the entire transaction by clicking on the Void Partial Auth button, for
example, in the event that additional form of payment for the remaining balance cannot be
obtained.
Figure 132 New Order – Partial Authorization Response

Within the OPEN BATCH menu tab, details regarding partial authorizations can be viewed
via the Recommended Data and Response Data tabs. By clicking on the Order History
button on the Recommended Data tab, detailed information about the history of the
partial authorization is displayed, including the Original Amount Requested.

Page 181 of 214

Orbital Virtual Terminal Appendix A Partial Authorizations
Version 4.2 Working with Gift Card Batches

Figure 133 Open Batch – View Order – Order History for Partial Authorization

Partial authorization information can be viewed on the Response Data tab of a transaction.
Figure 134 Open Batch – Response Data tab

Page 182 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

Appendix B Codes Reference

The following section describes the various types of response codes that are returned in
Virtual Terminal response pages. Typical responses include the host, AVS, and CVD codes.

Response Codes
The Response Code table describes all the various codes that can be returned from the
issuer or host.

Table 2 Response code values

Code Definition Status Action*

00 Approved Approved None

01 Call Voice Center Decline Voice

02 Refer to Card Issuer's Special Conditions Decline Voice

03 Invalid Merchant Number Error Fix

04 Pickup Decline Cust.

05 Do Not Honor Decline Cust.

06 Other Error Decline Cust.

07 Stop Deposit Order Decline Cust.

08 Approved Authorization, Honor with Identification Approved None

09 Revocation of Authorization Decline Cust.

10 Default Call Decline Voice

11 Approved Authorization, VIP Approval Approved None

12 Invalid Transaction Type Decline Cust.

13 Bad Amount Decline Fix

14 Invalid Credit Card Number Decline Fix

15 Default Call Low Fraud Decline Voice

16 Default Call Medium Fraud Decline Voice

17 Default Call High Fraud Decline Voice

18 Default Call Unavailable Fraud Decline Voice

19 Re-enter Transaction Error Resend

20 Floor Low Fraud Decline Cust.

21 Floor Medium Fraud Decline Cust.

22 Floor High fraud Decline Cust.

23 Floor Unavailable Fraud Decline Cust.

24 Validated Approved None

Page 183 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

26 Pre-noted Approved None

27 No Reason to Decline Decline Cust.

28 Received and Stored Approved None

29 Provided Authorization Approved None

30 Invalid Value in Message Error Fix

31 Request Received Approved None

32 BIN Alert Approved None

33 Card is Expired Decline Cust.

34 Approved for Partial Approved None

35 Zero Amount Error Fix

36 Bad Total Authorization Amount Error Fix

37 Invalid VbV or MC Secure Payment Data Error Fix

38 Merchant not MC SecureCode Enabled Decline Call

39 Previously Processed Transaction Error Fix

40 Requested Function not Supported Error Call or Fix

41 Lost/Stolen Decline Cust.

42 Account Not Active Decline Cust.

43 Lost/Stolen Card Decline Cust.

44 Account Not Active Error Fix

45 Duplicate Transaction Decline Cust.

46 Blanks not Passed in Reserved Field Decline Fix

50 Positive ID Decline Cust.

52 Processor Decline Decline Cust.

56 Restraint Decline Cust.

58 Transaction not Permitted to Terminal Error Call

59 Soft AVS Decline Cust.

60 Do Not Honor Low Fraud Decline Cust.

61 Do Not Honor Medium Fraud Decline Cust.

62 Do Not Honor High fraud Decline Cust.

63 Do Not Honor Unavailable Fraud Decline Cust.

64 CVV2/CVC2 Failure Decline Cust.

65 Invalid Amex CID Decline Cust.

Page 184 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

66 Other Error Error Fix

68 Invalid CC Number Error Fix

69 Does not Match MOP Error Fix

71 No Account Decline Fix

72 Invalid Institution Code Decline Fix

73 Method of Payment is Invalid for Merchant Error Fix

74 Invalid Expiration Date Decline Cust.

75 Bad Amount Error Fix

77 Invalid Amount Decline Fix

78 Missing Companion Data Error Fix

79 Invalid Merchant Error Fix

80 Invalid MOP for Division Error Fix

81 Call Low Fraud Decline Call

82 Call Medium Fraud Decline Call

83 Call High Fraud Decline Call

84 Call Unavailable Fraud Decline Call

85 Duplicated Order # Error Fix

86 Auth Recycle Host down Error Wait

87 Invalid Currency Error Fix

88 Invalid Purch. Level 3 Error Fix

89 Credit Floor Decline Cust.

91 Approved Low Fraud Approved None

92 Approved Medium Fraud Approved None

93 Approved High Fraud Approved None

94 Approved Fraud Service Unavailable Approved None

95 Invalid Data Type Error Fix

96 Invalid Record Sequence Error Fix

97 Percents Not Total 100 Error Fix

98 Issuer Unavailable Decline Resend

99 No Answer/Unable to send Error Resend

A1 Payments Not Total Order Error Fix

A2 Bad Order Number Error Fix

Page 185 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

A3 FPO Locked Error Wait

A4 FPO Not Allowed Error Call

A5 Auth Amount Wrong Error Fix

A6 Illegal Action Error Fix

A8 Invalid Start Date Error Fix

A9 Invalid Issue Number Error Fix

B1 Invalid Transaction Type Error Fix

B2 Account Previously Activated Decline Cust

B3 Unable to Void Transaction Error Fix

B5 Not on File Decline Fix

B7 Security Violation/No Match CID Decline Cust.

B8 Bad Debt Decline Cust.

B9 On Negative File Decline Cust.

BA Date of Birth Indicates Customer is Less Than 18 Decline Cust.

BB Customer Reported Possible Compromise and Blocked Account Decline Cust.

BC Bill To Address Not Equal To Ship To Address Decline Cust.

BD Pre-Approval Number not Recognized Decline Cust.

BE E-mail Address Failed Standard Validation Rules Decline Cust.

BF Pre-approval Number no Longer Valid Decline Cust.

BG Billing System Account Status Decline Cust.

BH Billing Address Could Not be Verified Decline Cust.

BI Need More Information. Request Full Social Security Number. Decline Cust.

BJ Previously Declined Decline Cust.

BK Closed Account, New Account Issued Decline Cust.

BL Re-Authorization Request Declined. Original Authorization not Decline Cust.

Found.

BM Re-Authorization Request Declined. Account, MID, or Amount Decline Cust.

not Matching Original Auth

BN Re-Authorization Request Declined. Amount Exceed Original Decline Cust.

Request Amount.

BO Declined Auth Using Stand-In Rules. Auth May be Obtained Decline Cust.
When Systems Available.

BP Customer Service Phone Number required on Transaction Types Error Fix

1 (MO/TO) and 2 (Recurring). MC Only

BQ Issuer has Flagged Account as Suspected Fraud. (Discover Only) Decline Cust.

Page 186 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

BR Invalid MCC Sent Error Fix

BS New Card Issued Decline Cust.

C1 Invalid Issuer Decline Cust.

C2 Invalid Response Code Decline Fix

C3 Excessive PIN Try Decline Cust.

C4 Over Limit Decline Cust.

C5 Over Freq Limit Decline Cust.

C6 Over Sav Limit Decline Cust.

C7 Over Sav Freq Decline Cust.

C8 Over Credit Limit Decline Cust.

C9 Over Credit Freq Decline Cust.

D1 Invalid For Credit Decline Fix

D2 Invalid For Debit Decline Fix

D3 Rev Exceed Withdrawal Decline Cust.

D4 One Purchasing Limit Decline Cust.

D5 On Negative File Decline Cust.

D6 Changed Field Decline Fix

D7 Insufficient Funds Decline Cust.

D8 Encrypted Data Bad Decline Fix

D9 Altered Data Decline Fix

E3 Invalid Prefix Decline Fix

E4 Invalid Institution Decline Fix

E5 Invalid Cardholder Decline Fix

E6 BIN Block Decline Fix

E7 Stored Approved None

E8 Invalid Transit Routing Number Error Fix

E9 Unknown Transit Routing Number Error Fix

F1 Missing Name Error Fix

F2 Invalid Account Type Error Fix

F3 Account Closed Error Cust.

F4 No Account/Unable To Locate Error Fix

F5 Account Holder Deceased Error Cust.

Page 187 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

F6 Beneficiary Deceased Error Cust.

F7 Account Frozen Error Cust.

F8 Customer Opt Out Error Cust.

F9 ACH Non-Participant Error Cust.

G1 No Pre-note Error Fix

G2 No Address Error Fix

G3 Invalid Account Number Error Fix

G4 Authorization Revoked by Consumer Error Cust.

G5 Customer Advises Not Authorized Error Cust.

G6 Invalid CECP Action Code Error Fix

G7 Invalid Account Format Error Fix

G8 Bad Account Number Data Error Fix

G9 No Capture Decline N/A

H1 No Credit Function Decline N/A

H2 No Debit Function Decline N/A

H3 Rev Exceed Withdrawal Decline Cust.

H4 Changed Field Decline N/A

H5 Terminal Not Owned Decline N/A

H6 Invalid Time Decline Fix

H7 Invalid Date Decline Fix

H8 Invalid Terminal Number Decline Fix

H9 Invalid PIN Decline Cust.

I1 Block Activation Failed – Card Range Not Set Up for MOD 10 Error Fix

I2 Block Activation Failed – E-mail or Fulfillment Flags were set to Y Error Fix

I3 Declined – Issuance Does Not Meet Minimum Amount Declined Cust

I4 Declined – No Original Auth Found Decline Cust

I5 Declined – Outstanding Auth, Funds On Hold Decline Cust

I6 Activation Amount Incorrect Decline Fix

I7 Block Activation Failed – Account Not Correct Or Block Size Not Decline Fix
Correct

I8 Mag Stripe CVD Value Failed Decline Fix

I9 Max Redemption Limit Met Decline Fix

J1 No Manual Key Decline Fix

Page 188 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 Response Codes

J2 Not Signed In Decline Fix

J3 Excessive PIN Try Decline Cust.

J4 No DDA Decline Fix

J5 No SAV Decline Fix

J6 Excess DDA Decline Cust.

J7 Excess DDA FREQ Decline Cust.

J8 Excess SAV Decline Cust.

J9 Excess SAV FREQ Decline Cust.

K1 Excess Card Decline Cust.

K2 Excess Card Freq Decline Cust.

K3 Reserved Future Decline N/A

K4 Reserved Closing Decline N/A

K5 Dormant Decline Cust.

K6 NSF Decline Cust.

K7 Future RD Six Decline N/A

K8 Future RD Seven Decline N/A

K9 Transaction Code Conflict Decline Fix

L1 In Progress Decline Wait

L2 Process Unavailable Error Resend

L3 Invalid Expiration Error Fix

L4 Invalid Effective Error Fix

L5 Invalid Issuer Decline Fix

L6 Transaction Not Allowed For Cardholder Decline Cust.

L7 Unable to Determine Network Routing Error Call

L8 System Error Error Call

L9 Database Error Error Call

M1 Merchant Override Decline Decline Cust.

M2 Partial Approval Not Allowed Decline N/A

PA Partial Approval Approved N/A

PB Revocation of all Authorization Decline Cust.

PC Country On Fraud Filter List Decline Cust.

PP No Match for Debit Authorization based on Trace, Account, and Error Fix
Division Number

Page 189 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 AVS Response Codes

PQ Unable to Validate Debit Auth Record Based on Amount, Action Error Fix
Code, and MOP

PR Refund Not Allowed – Refund Requested on a Star only BIN or Error Fix
BIN not Found

R1 Blocked Card Number Prefix Decline Cust.

R2 Blocked Card Number Decline Cust.

R3 Blocked Issuing Country Decline Cust.

R4 Ceiling Limit Decline Cust.

AVS Response Codes

The AVS Response Codes table describes all the various AVS codes that can be returned
from participating card issuing banks if AVS data is provided in the order transaction.

Table 3 AVS response code values

Code AVS Message

1 No address supplied

2 Bill-to address did not pass Auth Host edit checks

3 AVS not performed

4 or R Issuer does not participate in AVS

5 Edit-error - AVS data is invalid

6 System unavailable or time-out

7 Address information unavailable

8 Transaction Ineligible for AVS

9 Zip Match/Zip4 Match/Locale match

A Zip Match/Zip 4 Match/Locale no match

B Zip Match/Zip 4 no Match/Locale match

C Zip Match/Zip 4 no Match/Locale no match

D Zip No Match/Zip 4 Match/Locale match

E Zip No Match/Zip 4 Match/Locale no match

F Zip No Match/Zip 4 No Match/Locale match

G No match at all

H Zip Match/Locale match

J Issuer does not participate in Global AVS

JA International street address and postal match

JB International street address match. Postal code not verified.

Page 190 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 CVV2/CVC2/CID Response Codes

JC International street address and postal code not verified.

JD International postal code match. Street address not verified.

M1 Merchant Override Decline

M2 Cardholder name, billing address, and postal code matches

M3 Cardholder name and billing code matches

M4 Cardholder name and billing address match

M5 Cardholder name incorrect, billing address and postal code match

M6 Cardholder name incorrect, billing address matches

M7 Cardholder name incorrect, billing address matches

M8 Cardholder name, billing address and postal code are all incorrect

N3 Address matches, ZIP not verified

N4 Address and ZIP code not verified due to incompatible formats

N5 Address and ZIP code match (International only)

N6 Address not verified (International only)

N7 ZIP matches, address not verified

N8 Address and ZIP code match (International only)

N9 Address and ZIP code match (UK only)

R Issuer does not participate in AVS

UK Unknown

X Zip Match/Zip 4 Match/Address Match

Z Zip Match/Locale no match

blank Not applicable (non-Visa)

CVV2/CVC2/CID Response Codes

The CVD Response Codes table describes the various CVD codes that can be returned by
participating card issuing banks if the code was provided in the order transaction.

Table 4 CVV request response code values

Code Description
M CVV Match

N CVV No match

P Not processed

S Should have been present

U Unsupported by issuer/Issuer unable to process request

Page 191 of 214

Orbital Virtual Terminal Appendix B Codes Reference
Version 4.2 CVV2/CVC2/CID Response Codes

I Invalid

Y Invalid

blank Not applicable (non-Visa)

Page 192 of 214

Orbital Virtual Terminal Appendix C Merchant Selectable Response Codes
Version 4.2 CVV2/CVC2/CID Response Codes

Appendix C Merchant Selectable Response Codes

The following codes can be selected within the Merchant Selectable Response Admin page
and will generate a decline if the code is returned from the issuing back in an approved
transaction.

AVS Response Codes

Table 5 AVS Response Codes for MSR

Response Description Salem Tampa

Code
Not applicable (non-Visa) 

1 No address supplied 

2 Bill-to address did not pass Auth Host edit 

checks

3 AVS not performed 

4 Issuer does not participate in AVS 

5 Edit-error - AVS data is invalid 

6 System unavailable or time-out  

7 Address information unavailable  

8 Transaction Ineligible for AVS 

9 Zip Match / Zip4 Match / Locale match 

A Zip Match / Zip 4 Match / Locale no match  

B Zip Match / Zip4 No Match / Locale match 

C Zip Match / Zip4 No Match / Locale No match 

D Zip No Match / Zip4 Match / Locale match 

E Zip No Match / Zip4 Match / Locale no match 

F Zip No Match / Zip4 No Match / Locale match  

G No match at all  

H Zip Match / Locale match 

J Issuer does not participate in Global AVS 

JA International street address and postal match 

JB International street address match. Postal 

code not verified.

Page 193 of 214

Orbital Virtual Terminal Appendix C Merchant Selectable Response Codes
Version 4.2 CVV2/CVC2/CID Response Codes

JC International street address and postal code 

not verified.

JD International postal code match. Street 

address not verified.

M2 Cardholder name, billing address, and postal 

code matches

M3 Cardholder name and billing code matches 

M4 Cardholder name and billing address match 

M5 Cardholder name incorrect, billing address and 

postal code match

M6 Cardholder name incorrect, billing address 

matches

M7 Cardholder name incorrect, billing address 

matches

M8 Cardholder name, billing address and postal 

code are all incorrect

M9 Cardholder name matches 

N3 Address matches, ZIP not verified 

N4 Address and ZIP code not verified due to 

incompatible formats

N5 Address and ZIP code match (International 

only)

N6 Address not verified (International only) 

N7 ZIP matches, address not verified 

N8 Address and ZIP code match (International 

only)

N9 Address and ZIP code match (UK only) 

R Issuer does not participate in AVS  

X Zip Match / Zip 4 Match / Address Match 

Z Zip Match / Locale no match 

Verification Response Codes

Table 6 Verification Response Codes for MSR

Response Description Salem Tampa

Code
Not applicable (non-Visa)  

I Invalid  

Page 194 of 214

Orbital Virtual Terminal Appendix C Merchant Selectable Response Codes
Version 4.2 CVV2/CVC2/CID Response Codes

M Match  

N No match  

P Not processed  

S Should have been present  

U Unsupported by issuer  

Page 195 of 214

Orbital Virtual Terminal Appendix D Profile Response Codes
Version 4.2 CVV2/CVC2/CID Response Codes

Appendix D Profile Response Codes

The following is a list of possible response codes associated with profiles.
Table 7 Profile Response Codes

Profile Errors
9550 Invalid Customer Reference Number From Order Indicator Fix

9551 Invalid Customer Reference Number Fix

9552 System Failure. Unable To Perform Customer Profile Request at This Time. Call

9553 Invalid Action Indicator Fix

9555 Invalid BIN Fix

9556 Invalid Merchant ID Fix

9557 Invalid Name Fix

9558 Invalid Address Fix

9559 Invalid Address 2 Fix

9560 Invalid City Fix

9561 Invalid State Fix

9562 Invalid ZIP Fix

9563 Invalid E-mail Fix

9564 Invalid Phone Fix

9565 Invalid Order Description Fix

9566 Invalid Amount Fix

9567 Invalid Account Type Indicator Fix

9568 Invalid Account Number Fix

9569 Invalid Account Expire Date Fix

9570 Invalid ECP Account DDA Fix

9571 Invalid ECP Account Type Indicator Fix

9572 Invalid ECP Account Route Fix

9573 Invalid ECP Bank Payment Delivery Method Fix

9574 Invalid Switch Solo Start Date Fix

9575 Invalid Switch Solo Issue Number Fix

9576 Unable to Perform Profile Transaction. The Associated Transaction Failed. Call

9577 Invalid Order Override Indicator Fix

9578 Merchant-Bin combination is not allowed to perform profile transactions. Call

Page 196 of 214

Orbital Virtual Terminal Appendix D Profile Response Codes
Version 4.2 CVV2/CVC2/CID Response Codes

9579 Merchant-Bin is not active. Call

9580 Cannot process profile for Cust Ref Num and MID combination. A database error has Call
occurred

9581 Cannot process profile. Profile does not exist for Cust Ref Num and MID. Fix

9582 Cannot process profile. Profile already exists for Cust Ref Num and MID. Fix

9583 Missing Switch Solo Account Information. Either start date or issue number is Fix
required.

9584 Missing Electronic Check Account Information. Fix

9585 Missing Credit Card Account Information. Fix

9587 Auto-Gen Cust Ref Num Error. Call

9588 Unable to Determine Profile Action from Auth Request Fix

9589 Cannot Create Profile: A Customer Profile Name is Required Fix

9592 Invalid Profile Status Requested Fix

9594 The Profile’s status prohibits the type of transaction being attempted. Fix

9595 The Profile’s Account Updater Scheduled Date is invalid Fix

9596 The Profile’s Account Updater Scheduled Date is not a future date Fix

Page 197 of 214

Orbital Virtual Terminal Appendix E Overview of Credit Card Processing
Version 4.2 What are Credit Cards?

Appendix E Overview of Credit Card Processing

Credit Card Transactions- Millions of people throughout the world use credit cards as a form
of payment. Cardholders consider the use of credit cards a simple easy method in which to
pay for goods and services. Merchants benefit from these transactions because it simplifies
the process in which they receive funds for purchased goods.

What are Credit Cards?

Credit Cards provide customers with a convenient way to purchase goods and services
without having to use cash. Credit cards are issued with a personal line of credit against
which the customer makes purchases and/or obtains cash advances. Payments are made to
the issuer monthly either in full or on a revolving basis with a minimum payment
requirement each month.
As credit card transactions occur, the retailers and financial institutions must submit these
transactions to their designated acquirer for processing and payment. The various credit
card types include:
Visa
MasterCard
American Express
Discover
Diners Club/Carte Blanche
JCB
Private Label
Debit Cards or Check Cards, are perceived the same, the major difference is there is not a
credit line involved, the funds are taken from a checking or savings account.

What is Payment Processing?

Payment processing is the method by which credit card and merchant data activity is
collected. In many cases, the merchant uses a terminal to enter cardholder and transaction
data. As the credit card is swiped through the reader, the terminal verifies its validity,
contacts the credit card company to make sure funds are available and, finally, stores the
sale transaction along with all the others the merchant has processed that day. At the end
of each sales day, the terminal “calls” Chase Paymentech (or a Chase Paymentech certified
submitter) one last time to report total sales for the day. This starts the process of
reimbursing the merchant for cardholder purchases.
The Virtual Terminal provides a way of completing this process using key-entered data and
an internet connection to Chase Paymentech.

Credit Card Transaction Flow

Each credit card transaction has two parts: the Authorization and the Deposit. Below are
flow charts of each.

Page 198 of 214

Orbital Virtual Terminal Appendix E Overview of Credit Card Processing
Version 4.2 Credit Card Transaction Flow

Figure 135 Authorization process flow

Figure 136 Settlement process flow

Page 199 of 214

Orbital Virtual Terminal Appendix F Split Shipment Process Flow
Version 4.2 Credit Card Transaction Flow

Appendix F Split Shipment Process Flow

A shipment can be split into two or more transactions. The Orbital Virtual Terminal
automatically obtains an authorization for each portion of the transaction that is Marked for
Capture. The flow chart below explains the steps that occur in a transaction that is split
several times. Transactions can be split as many times as needed.

Figure 137 Sample split shipment process flow

Page 200 of 214

Orbital Virtual Terminal Appendix G Auto E-mail Cardholder Text
Version 4.2 CARDHOLDER E-MAILS

Appendix G Auto E-mail Cardholder Text

CARDHOLDER E-MAILS
EXPIRING CARD

Subject Line: [DBA Name] – Updates to Your Account Required

Dear Customer,
Our records indicate that the credit card we have on file will expire next month. To ensure
uninterrupted service, please contact us immediately to update your information. For your
security, please do not send your card information to us via e-mail. We request you contact
us directly by phone or through the mail with your updated account information.
Thank you for your prompt attention to this matter and your continued business.
[MERCHANT Legal NAME] doing business as [DBA Name]
[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field does not
appear.)

TRANSACTION DECLINED

Subject Line: [DBA Name] - Updated Account Information Needed

Dear Customer,
We recently attempted to charge the account on record in accordance with the terms of our
agreement. Unfortunately, we were unable to obtain an approval for the transaction.
Please contact us immediately to update your account information or provide an alternative
payment method.
Thank you for your prompt attention to this matter. We thank you for your business.
[MERCHANT Legal NAME] doing business as [DBA Name]
[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field does not
appear.)

SUCCESSFUL BILLING

Subject Line: [DBA Name] - Your Payment Has Been Successfully Completed
Dear Customer,
Your account has successfully been charged in accordance with the terms of our agreement.
The charge should appear on your next billing statement. Thank you for your business.
Please do not hesitate to contact us if you have any questions.

Page 201 of 214

Orbital Virtual Terminal Appendix G Auto E-mail Cardholder Text
Version 4.2 CARDHOLDER E-MAILS

[MERCHANT Legal NAME] doing business as [DBA Name]

[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field will not
appear.)

AMOUNT TO BE CHARGED

Subject Line: [DBA Name] - Notice of Upcoming Billing

Dear Customer,
As you may recall, you chose a recurring billing option with our company. This e-mail
serves as notification that the account we have on record will soon be charged in
accordance with your wishes. Once the transaction has been processed, you will receive
notification of the transaction’s success. Similarly, if there is an error in processing your
transaction, we will notify you promptly. The successful transaction will be reflected on your
next account statement.
Thank you for your continued business. Please contact us if you have any questions.
[MERCHANT Legal NAME] doing business as [DBA Name]
[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field does not
appear.)

ACCOUNT CLOSED

Subject Line: [DBA Name] – Updated Information

Dear Customer,
We recently received notification that the card account we have on file has been closed.
Please contact us to update your account information or provide an alternative payment
method to ensure uninterrupted service.
To ensure your security, please do not send your card information to us via e-mail. Instead,
please contact us directly by phone, through the mail, or through our website.
Thank you for your prompt attention to this matter. We thank you for your business.
[MERCHANT Legal NAME] doing business as [DBA Name]
[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field does not
appear.)

NEW ACCOUNT NUMBER/EXP DATE

Subject Line: [DBA Name] – Updated Information Requested

Page 202 of 214

Orbital Virtual Terminal Appendix G Auto E-mail Cardholder Text
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Dear Customer,
As a convenience to you, your customer information was recently updated with a new card
account number and/or expiration date. In these busy times this is one less task to
complete. Should you have additional updates, please do not hesitate to contact us. Thank
you for your business.
[MERCHANT Legal NAME] doing business as [DBA Name]
[MERCHANT CUSTOMER SERVICE PHONE NUMBER] (If found under Auto E-mail Service text
box on Profiles /Management Tab. If we do not have this number, this field does not
appear.)
Please do not reply to this message. This is an automatically generated e-mail which cannot
receive replies.

MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED

CARDHOLDER E-MAIL
EXPIRING CARD

Subject Line: Notice of non-distributed e-mail: Expired Card

RE: [Profile ID]
In reference to: Cardholder Expiring Card E-mail
Dear Merchant,
As part of the Orbital Managed Billing Service, you elected to have Chase Paymentech send
automated e-mails to cardholders when the account on record was about to expire. This e-
mail was not sent to the cardholder associated with the above referenced Profile ID because
a corresponding e-mail address was not available in the Profile. To add an e-mail address to
the Profile, please enter that information via the Orbital Virtual Terminal.
Sincerely,
Chase Paymentech

TRANSACTION DECLINED

Subject Line: Notice of non-distributed e-mail: Declined Transaction

RE: [Profile ID]
In reference to: Cardholder Declined Transaction E-mail
Dear Merchant,

Page 203 of 214

Orbital Virtual Terminal Appendix G Auto E-mail Cardholder Text
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

As part of the Orbital Managed Billing Service, you elected to have Chase Paymentech send
automated e-mails to cardholders requesting updated information when an approval code
was not provided. We received a decline on the account associated with the above
reference Profile ID. However, since a corresponding e-mail address was not available in
the Profile we were unable to send a cardholder notification. To add an e-mail address to
the Profile, please enter that information via the Orbital Virtual Terminal.
Sincerely,
Chase Paymentech

SUCCESSFUL BILLING

Subject Line: Notice of non-distributed e-mail: Successful Billing

RE: [Profile ID]
In reference to: Cardholder Successful Billing E-mail
Dear Merchant,
As part of the Orbital Managed Billing Service, you elected to have Chase Paymentech send
automated e-mails to cardholders when the account on record was successfully billed. We
were unable to send this e-mail to the cardholder associated with the above reference
Profile ID since a corresponding e-mail address was not available in the Profile. To add an e-
mail address to the Profile, please enter that information via the Orbital Virtual Terminal.
Sincerely,
Chase Paymentech

AMOUNT TO BE CHARGED

Subject Line: Notice of non-distributed e-mail: Pre-notification of Billing

RE: [Profile ID]
In reference to: Cardholder Notice of Upcoming Billing
Dear Merchant,
As part of the Orbital Managed Billing Service, you elected to have Chase Paymentech send
automated pre-notification e-mails to cardholders when the account on record was about to
be billed. We were unable to send this e-mail to the cardholder associated with the above
reference Profile ID since a corresponding e-mail address was not available in the Profile. To
add an e-mail address to the Profile, please enter that information via the Orbital Virtual
Terminal.
Sincerely,
Chase Paymentech

Page 204 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Appendix H Reporting
The tables below reflect the data fields contained within the various reports that may be
retrieved from the REPORTING menu tab. Please note that most reports are offered in
both PDF [Report] or CSV [File] format.

OPEN BATCH REPORTS

Open Batch Open Batch

Detail Report [PDF] Detail File [CSV]

Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

AVS Response AVS Response

CVV Response CVV Response

Date Date

Order ID Order ID

Order Description order Description

Entry Source Entry Source

Customer Profile Customer Profile

REVIEW BATCH REPORTS

Review Review

Detail Report [PDF] Detail File [CSV]

Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

Date/Time Date/Time

Order Number Order Number

Order Description Order Description

Batch ID Batch ID

Entry Source Entry Source

Customer Profile Customer Profile

Page 205 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Review – Pending Review – Pending

Detail Report [PDF] Detail File [CSV]

Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

AVS Response AVS Response

CVV Response CVV Response

Date Date

Order ID Order ID

Order Description Order Description

Entry Source Entry Source

Customer Profile Customer Profile

Review – Rejected Review – Rejected

Detail Report [PDF] Detail File [CSV]

Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

AVS Response AVS Response

CVV Response CVV Response

Date Date

Order ID Order ID

Order Description Order Description

Entry Source Entry Source

Customer Profile Customer Profile

Page 206 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

PROFILE QUERIES
The profile queries are only available in a CSV format or as an on-screen display.
Profile Queries:

All Profiles, Active Profiles,

Inactive Profiles, Active
Standard, Active MB, MB in
Active Billing Cycle

Profile ID

Status

Card Number

Name

Address

Next MB Billing

Scheduled MB Amount

Last Change Date

Suspend Queries:

All Suspended, Auto

Suspended: Account Updater,
Auto Suspended: Auth Recycle,
Auto Suspended: PINless
Debit, Manual Suspend

Profile ID

Status

Card Number

Name

Expiration Date

Suspend Date

MB Profile

Next MB Billing

Scheduled MB Amount

Converted PINless Debit

Profile ID

Card Number

Page 207 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Converted PINless Debit

Name

Conversion Date

Conversion Method

Suspended?

Status

MB Profile

Next MB Billing

Scheduled MB Amount

EVENT DRIVEN REPORTS

Closed Batch Summary Report

[Available only in CSV format]

Card Type

Sale Count

Sale Amount

Return Count

Return Amount

Decline and Error Count

Total Count

Net Amount

Closed Batch Detail Report Closed Batch Detail Report

[PDF] [CSV]
Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

Trans Date/Time Trans Date/Time

Settle Date/Time Settle Date/Time

Order Number Order Number

Order Description Order Description

Page 208 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Closed Batch Detail Report Closed Batch Detail Report

[PDF] [CSV]
Batch ID Batch ID

Entry Source Entry Source

Customer Profile Customer Profile

Rejected Batch Detail Report Rejected Batch Detail Report

[PDF] [CSV]
Card Type Card Type

Card Number Card Number

Trans Type Trans Type

Amount Amount

Response Code Response Code

Reject Response Reject Response

Trans Date/Time Trans Date/Time

Reject Date/Time Reject Date/Time

Order Number Order Number

Order Description Order Description

Batch ID Batch ID

Entry Source Entry Source

Customer Profile Customer Profile

SCHEDULED REPORTS – MERCHANT LEVEL

Auth Recycling Auth Recycling

[PDF] [CSV]
Profile ID Profile ID

Order ID Order ID

Order Description Order Description

Card Number Card Number

Account Type Account Type

Amount Amount

Original Auth Date Original Auth Date

Last Reauth Attempted Last Reauth Attempted

Page 209 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Auth Recycling Auth Recycling

[PDF] [CSV]
Number Reauths Attempted Number Reauths Attempted

Number Reauths Left Number Reauths Left

Last Response Code Last Response Code

Response Description Response Description

Expiring Card Expiring Card

[PDF] [CSV]
Profile ID Profile ID

Card Number Card Number

Expiration Date Expiration Date

Next MB Billing Next MB Billing

Name Name

E-mail Address E-mail Address

Amount Amount

Active Profile Status Active Profile Status

Suspended Profile Suspended Profile

[PDF] [CSV]
Profile ID Profile ID

Biller Reference Number Biller Reference Number

Card Number Card Number

Expiration Date Expiration Date

Suspend Date Suspend Date

Name Name

E-mail Address E-mail Address

Amount Amount

Profile Status Profile Status

Response Code Response Code

Response Description Response Description

Page 210 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Account Updater Account Updater

[PDF] [CSV]
Profile ID Profile ID

Current Card Number Current Card Number

Prior Card Number Prior Card Number

Name Name

Date of Update Date of Update

Action Action

Reason Reason

New Expiration Date New Expiration Date

New Card Brand New Card Brand

MB Profile MB Profile

Next MB Billing Next MB Billing

Scheduled MB Amount Scheduled MB Amount

PINless Debit Status Change PINless Debit Status Change

[PDF] [CSV]
Profile ID Profile ID

Biller Reference Number Biller Reference Number

Card Number Card Number

Name Name

Status Change Status Change

Date of Change Date of Change

MB Profile MB Profile

Next MB Billing Next MB Billing

Scheduled MB Amount Scheduled MB Amount

Page 211 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

SCHEDULED REPORTS – MERCHANT LEVEL – MANAGED BILLING

MB Activity MB Activity

[PDF] [CSV]
Profile ID Profile ID

Order ID Order ID

Order Description Order Description

Card Number Card Number

Card Type Card Type

Amount Amount

Original Auth Date Original Date

Final Auth Date Final Date

Number Reauths Attempted Number Reauths Attempted

Number Reauths Left Number Reauths Left

Response Code Response Code

Response Description Response Description

Scheduled Profile Activity Scheduled Profile Activity

[PDF] [CSV]
Profile ID Profile ID

Order ID Order ID

Order Description Order Description

Card Number Card Number

Card Type Card Type

Amount Amount

Scheduled Date Scheduled Date

SCHEDULED REPORTS – CHAIN LEVEL

Expiring Card Expiring Card

[PDF] [CSV]
Profile ID Profile ID

Card Number Card Number

Expiration Date Expiration Date

Name Name

Page 212 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

Expiring Card Expiring Card

[PDF] [CSV]
E-mail Address E-mail Address

Active Profile Status Active Profile Status

Suspended Profile Suspended Profile

[PDF] [CSV]
Profile ID Profile ID

Biller # Biller #

Card Number Card Number

Expiration Date Expiration Date

Suspend Date Suspend Date

Name Name

E-mail Address E-mail Address

Suspend Status Suspend Status

Response Code Response Code

Response Description Response Description

Account Updater Account Updater

[PDF] [CSV]
Profile ID Profile ID

Current Card Number Current Card Number

Prior Card Number Prior Card Number

Name Name

Date of Update Date of Update

Action Action

Reason Reason

New Expiration Date New Expiration Date

New Card Brand New Card Brand

PINless Debit Status Change PINless Debit Status Change

[PDF] [CSV]

Page 213 of 214

Orbital Virtual Terminal Appendix H Reporting
Version 4.2 MERCHANT E-MAILS: NOTIFICATION OF NON-DISTRIBUTED CARDHOLDER E-MAIL

PINless Debit Status Change PINless Debit Status Change

[PDF] [CSV]
Profile ID Profile ID

Biller Reference Number Biller Reference Number

Card Number Card Number

Name Name

Status Change Status Change

Date of Change Date of Change

Page 214 of 214