Business Rules and Guidelines Global Canada HC BCP

Business Rules and
Guidelines
Global Payments Canada BCP HC Adaptor
Contents
Overview.................................................................................................................................................................. 3
Adjustment Processing.............................................................................................................................................4
Alternate Transaction Routing (ATR)........................................................................................................................5
Contactless Payments..............................................................................................................................................5
CVV2, CVC2, CID, CSC Processing.............................................................................................................................6
Duplicate Transaction Checking...............................................................................................................................6
Interac......................................................................................................................................................................7
Message Authentication Code (MAC)...................................................................................................................7
RequestKey()........................................................................................................................................................8
Partial Approval (Partial Authorization)................................................................................................................8
Refunds................................................................................................................................................................8
Cashback..............................................................................................................................................................8
Fees and Surcharges.............................................................................................................................................8
Interac Online.......................................................................................................................................................9
Interac Flash.........................................................................................................................................................9
International Card Processing..................................................................................................................................9
Merchant Identifier (MID/TID).................................................................................................................................9
Mobile POS Terminals (mPOS)...............................................................................................................................10
Partial Approvals (Partial Authorization)................................................................................................................10
Prepaid Credit Cards...............................................................................................................................................11
Purchase Card - Level 2..........................................................................................................................................11
Recurring Bill Payments..........................................................................................................................................12
Resubmit for “008” Response................................................................................................................................12
Soft Descriptor (Dynamic Descriptor).....................................................................................................................12
Verify().................................................................................................................................................................... 13
3-D Secure Processing............................................................................................................................................13
Verified By Visa (VbV/VPAS)...............................................................................................................................13
MasterCard Secure Code (MCSC/UCAF).............................................................................................................13
End of Day..............................................................................................................................................................14
Making Payments a Snap* for Developers | Proprietary & Confidential 1

EMV Processing......................................................................................................................................................14
Tip Adjustments.................................................................................................................................................15
Supported AIDs...................................................................................................................................................15
EMV Receipt Requirements................................................................................................................................15
Fallback Approval Receipt..............................................................................................................................17

Signature CVM – Online Approval Receipt.....................................................................................................18
Authorized Online Approval Using PIN Receipt..............................................................................................19
Authorized Online Declined Receipt...............................................................................................................20
Fallback Declined Receipt...............................................................................................................................21
Fallback Declined Receipt...............................................................................................................................22
Fallback Refund Receipt.................................................................................................................................23
Online Void Sale Receipt.................................................................................................................................24
Fallback Void Sale Receipt..............................................................................................................................25
Retail/Restaurant Tip Amount Online Funds Approved Using PIN Receipt....................................................26
Retail/Restaurant Tip Amount Online Funds Approved Using Chip and Signature Receipt............................27
Retail/Restaurant Tip Amount Fallback Approved Receipt.............................................................................28
Interac Debit Card (Online Approved – PIN)...................................................................................................29
Response Codes.....................................................................................................................................................30

Overview
MOTO Ecomm Retail Restaurant
Transactions - CREDIT
AVSONLY (Verify) ***Verify must be keyed*** X X X N/A
AUTHONLY (Authorize) X X X X
AUTH Standard Purchase (AuthorizeAndCapture) X X X X
AUTH PreAuth Completion (Capture) X X X X
AUTH Force Post (AuthorizeAndCapture) X X X X
INCAUTH (Adjust +) N/A N/A N/A N/A
REVAUTH (Adjust -) N/A N/A N/A N/A
VOID (Undo) X X X X
RETURN (ReturnUnlinked) X X X X
RETURN (ReturnById) X X X X
BALINQ (QueryAccount)** N/A N/A X X
REGISTER (called by TPS) N/A N/A N/A N/A
Features - CREDIT
AVS X X X X
CVV2, CVC2, CID X X X X
3-D Secure N/A X N/A N/A
Adjustment Support N/A N/A N/A N/A
Bill Payment - Deferred N/A N/A N/A N/A
Bill Payment - Installment N/A N/A N/A N/A
Bill Payment - Single N/A N/A N/A N/A
Bill Payment - Recurring X X N/A N/A
Purchase Card - Level 2 X X X N/A
Purchase Card - Extended Level 2 N/A N/A N/A N/A
Purchase Card - Level 3 N/A N/A N/A N/A
Purchase Card - Extended Level 3 N/A N/A N/A N/A
Soft Descriptors (Alternate Merchant Data) X X N/A N/A
Convenience Fees N/A N/A N/A N/A
IIAS – Healthcare Amounts N/A N/A N/A N/A
Amex Enhanced AVS N/A N/A N/A N/A
Provider Tokenization N/A N/A N/A N/A
Secure MSR N/A N/A N/A N/A
Contactless Cards N/A N/A X X
Cash Back N/A N/A N/A N/A
Partial Approvals X X X X
Cardholder Activated Transactions (CAT) N/A N/A N/A N/A
Private Label Cards N/A N/A N/A N/A
Quasi-Cash N/A N/A N/A N/A
Host Capture Manual Batch Close N/A N/A N/A N/A
EMV Support N/A N/A X X
PIN-less Debit N/A N/A N/A N/A
Credentials Required N/A N/A N/A N/A
Transactions - PINDEBIT
AUTH (AuthorizeAndCapture) N/A N/A X X

MOTO Ecomm Retail Restaurant
REVERSAL (Undo) N/A N/A X X
RETURN (ReturnUnlinked) N/A N/A X X
RETURN (ReturnById) N/A N/A X X
BALINQ (QueryAccount) N/A N/A N/A N/A
REGISTER (called by TPS) N/A N/A N/A N/A
CONF (called by adaptor) N/A N/A N/A N/A
Features - PINDEBIT
Cash Back N/A N/A X X
Partial Approvals N/A N/A N/A N/A
Scrip Devices N/A N/A N/A N/A
Provider Tokenization N/A N/A N/A N/A
Secure MSR N/A N/A N/A N/A
Quasi-Cash N/A N/A N/A N/A
Contactless Cards N/A N/A X X
EMV Support ***EMV Required*** N/A N/A X X
Credentials Required N/A N/A N/A N/A
Visa, MasterCard, Amex, Discover, JCB, Diner's Club,

Supported Card Types
Interac
**BALINQ (QueryAccount) is supported for Prepaid Credit Cards only and for Retail and
Restaurant industry types only.
The Global Payments Canada BCP adaptor supports card present and card not present processing for Canadian
merchants, including EMV processing with offline PIN. Global Canada only supports offline PIN processing,
therefore no PIN or KSN information is ever sent to them in any financial transaction.
Offline EMV processing is not supported for this service and must not be implemented. Terminals must be
configured with a zero floor limit.
Card Not Present processing (MOTO and Ecommerce) will be supported in Phase I and Card Present Processing
including Interac will be supported in Phase II.
This service supports Track 2 or keyed data only. Card present credit transactions should be chip read as fallback
is a temporary practice that will only be allowed for a limited time. If fallback processing is used,
BankcardTenderData/CardData/FallbackReason must be set to explain the reason for the fallback processing.
Interac transactions must be chip read as fallback is never allowed. If the Interac chip cannot be read, another
form of payment must be requested.
Merchants will be required to set BankcardTenderDataPro/TenderType for all transactions.
This service is Managed processing with time-initiated settlement at 1:00 am Eastern Time.
Adjustment Processing
Adjust() is not supported for this service. Capture() may be for an amount less than, equal to, or greater than
the Authorize() amount. The allowable excess limit for amounts greater than the authorized amount is
determined by the card associations.

Prepaid cards are not covered under brand tolerance rules. All authorizations on prepaid cards must be equal to
or less than the available balance at the time of the authorization or the merchant may be subject to charge
backs. Merchants who allow the addition of tips or other offline adjustments should be especially aware of this
fact.
Alternate Transaction Routing (ATR)

ATR Processing refers to the ability of the POS to obtain approvals for specified transaction types when the
Global Payments East host is unable to receive online approvals from the card issuer due to temporary
communication issues. This is a true alternate host and all approvals are valid authorizations from the card
associations. These are not “stand in” responses. When the host is in ATR mode, the host will return
responses/approval codes for supported transaction types/dollar amounts depending on the merchant’s host
configuration. The primary difference between a normal East host response and an ATR response will be the
lack of certain data on the ATR response. Since the ATR host will not have a running total of transactions from
the East host, the ATR host will not be able to return item numbers and batch numbers
(BankcardTransactionResponse/BatchId) in sequence with the East host. Therefore, all item and batch
numbers returned from the ATR host will always be 9999. All other fields will remain the same.
ATR transaction processing is primarily beneficial to Host-based merchants as all transactions approved during
ATR will be applied to the current open batch when the East host becomes available.
Contactless Payments
A contactless payment can originate from a variety of payment vehicles such as a payment card with contactless
capability, a non-payment card form factor (such as key fob, sticker, etc) or mobile phone.
Contactless Payment Cards are similar to traditional credit/debit cards except that they have a contactless chip
and radio frequency (RF) antenna configuration embedded within the plastic. After you tap or wave your
contactless payment card at a merchant terminal equipped with an RFID (Radio Frequency Identification)
reader, the card wirelessly transmits Track 2 and/or Track 1 payment details to the terminal.
These transactions typically do not do not require any PIN or signature for certain dollar amounts which makes
them ideal for fast low value payments.
ApplicationData/ReadCapability must be set to ContactlessMSR or ContactlessChip.
BankcardTransactionDataDefaults/EntryMode must be set to ContactlessStripe, MSRTrack2DataFromRFID,
ContactlessMChipOrSmartCard or ChipTrack2DataFromRFID. Track 2 Data must be populated for all contactless
payments.
RFID is also referred to as a contactless transaction, which can be processed as contactless chips and contactless
magnetic stripes.
The following contactless programs are supported on the Global Payments Canada East host:
 Interac Flash - No contactless Mag Stripe. Only contactless EMV available. (see requirements below)
 Visa payWave qVSDC - Contactless Mag Stripe and Contactless EMV available.
o If Visa payWave is supported, both the MSD (dCVV and CVN17) and qVSDC protocols must be
supported. qVSDC is a quicker version of EMV for contactless.

o The required VCPS version is 2.1.1 or higher. The required EMV Contactless Communication
Protocol Specification (CCPS) version is 1.x or higher.
o Voice Authorized Transactions or Forced Transactions are not supported for payWave.
o A contactless reader must be certified by Visa and listed as a “Visa Approved IRWIN Compliant
Reader” or a “Visa Approved Chip Card Device Supporting Visa Contactless Payments”.
o Visa does not permit a maximum contactless amount. Any amount is permissible for Visa
contactless transactions.
o The POS or contactless reader MUST display the transaction type and the final transaction
amount including any additional charges (e.g. Tip) prior to card presentment.
o Failed contactless transactions that revert to contact processing are not considered fallback.
 MasterCard MChip PayPass - Contactless Mag Stripe and Contactless EMV available.
o If MasterCard PayPass is supported, both the MSD and MChip protocols must be supported.
o Maestro PayPass and Voice Authorized Transactions or Forced Transactions are not supported.
o A contactless reader must be certified by MasterCard and must obtain a “MasterCard PayPass
Vendor Product Letter of Approval”.
o The required PayPass MChip version is 3.x or higher.
 American Express Expresspay - Contactless Mag Stripe only.
o If AMEX ExpressPay 3.0 is supported, both the MSD mode and EMV mode protocols must be
supported.
o Voice Authorized Transactions or Forced Transactions are not supported.
o A contactless reader must be certified by AMEX and obtain an AMEX Level 2 approved letter
from AMEX.
o The required ExpressPay version is 3.0 and higher.
o Any amount is permissible for an ExpressPay contactless transaction as long as a matching CVM
is supported above the CVM Required Limit.
CVV2, CVC2, CID, CSC Processing

This is the secure number imprinted on credit cards that helps merchants verify that the customer possesses a
legitimate card. The merchant asks the customer for the code and then sends it to the card issuer as part of the
authorization request.
In order to comply with American Express CID, the merchant must first register with American Express.
There is no CVV2 result code value for JCB. JCB transactions switched to an interface other than JCB for
authorization may return values associated with that interface.

Duplicate Transaction Checking
Global East performs duplicate transaction checking based on:
 Transaction amount (BankcardTransaction/TransactionData/Amount)
 PAN (BankcardTransaction/TenderData/CardData/PAN)
 Transaction Type (Authorize, Capture, AuthorizeAndCapture, ReturnById/ReturnUnlinked, Undo)
Duplicate transactions will be declined with an error message:
 BankcardTransactionResponse/StatusCode will contain “094”
 BankcardTransactionResponse/StatusMessage will contain “AP DUPE”.
In order to authorize identical transactions in a single batch, resubmit the declined transaction by setting
BankcardTransaction/TransactionData/TransactionCode to “Override”. The only transactions that allow
duplicate processing are AuthorizeAndCapture (including Force Post), ReturnById or ReturnUnlinked, and
Capture.
Interac
Interac is the association responsible for the development of Canada’s network of two shared electronic
financial services; Shared Cash Dispensing (ABM) and Interac Direct Payment (debit at point of sale). Interac
Debit is like using cash, only more secure. Transactions are approved online and in real time as money is
exchanged electronically between the financial institution and the merchant.
For Interac Direct Payment processing, the cardholder must be present and the cash-point must have a PIN pad
attached. The cardholder must complete an Interac prompting sequence on the PIN pad, and the PIN must be
encrypted using the PIN pad before the debit transaction can be sent to the host for authorization.
The Interac prompting sequence includes:
 Approving the Transaction Type and Amount
 Selecting an account (Chequing or Savings)
 Entering a PIN and pressing OK
Message Authentication Code (MAC)

The Message Authentication Code (MAC) is a value determined by a cryptographic process used to ensure debit
messages are received intact and unaltered. It is calculated by the PIN pad or the host and verified at each end
point.
In request messages, the cash-point uses the PIN pad to calculate the MAC value. When the host receives the
message it will verify the MAC value received. If the MAC values don’t match, the host will send a response
message with the bank response code field set to ‘898’.
In response messages, the MAC value (BankcardTransactionResponse/MessageAuthenticationCode) MUST be
verified by the PIN pad when a bank response code (BankcardTransactionResponse/BankResponseCode) is
returned. This includes declined host responses that contain a bank response code. If MAC verification on the
host response fails, an Undo() must be submitted with BankcardTransaction/TransactionData/PINDebitReason
set to “MACFailure”, even if the transaction was declined. A new set of keys will be returned in the next
response, or the POS may send a RequestKey() to re-synch with Global’s host.

On a response message, the PIN pad will use NEW keys that are returned in the response message (if present) to
verify the MAC value. Working keys are returned in the following fields:
 BankcardTransactionResponse/InitialEncryptionKeys/MACInitialKey/KeyValue
 BankcardTransactionResponse/InitialEncryptionKeys/PINInitialKey/KeyValue
 BankcardTransactionResponse/InitialEncryptionKeys/FieldInitialKey/KeyValue
If the financial transaction response does not contain a value in
BankcardTransactionResponse/BankResponseCode (meaning the transaction was stopped by the Global host
i.e. Invalid Merch ID, AP Dupe, DB Unavail), DO NOT verify the MAC value, even if present. Complete the
transaction at the POS treating the transactions as “Transaction Not Completed”.
RequestKey()
Each PIN pad associated with a Terminal ID has a unique set of Security Keys that must be synchronized with the
host for all unique Debit Terminal ID’s. If the keys are not synchronized, it will not be possible to perform Debit
card host transactions.
The Key Change transaction is required when:
 A new PIN pad is attached to a cash-point.
 PIN pad security keys are ‘out of step’ with the host.
If RequestKey() returns an error response, retry the transaction until an approved response and new working
keys are received. If several attempts to request keys fails this could mean there is an issue with the PIN Pad
and the merchant must contact their PIN Pad support team.
For an Interac transaction where the Global Host response message containing new Security Working Keys is
reversed, the new keys should be discarded by the POS. The next transaction should be processed using the old
keys until new keys are received from Host. If the next transaction will not process, RequestKey() can be used to
retrieve new keys.
The MAC value is not sent in RequestKey() request but it is included in the RequestKey() response.
Partial Approval (Partial Authorization)

Partial Approvals are not supported for Interac. Since Interac Debit is an online, real-time service, the debit is
immediate. This means that the required funds must be available in the cardholder’s account at the time of
purchase.
Refunds
Like purchases made with any other payment method, refunds and exchanges using Interac Debit are a matter
of merchant policy. In order for a refund to be processed through the Point-of-Sale service, the cardholder who
made the purchase must be present to authorize the transaction.
Cashback
Merchants who offer Interac Debit as a payment option can also offer "cashback". It allows customers to request
additional cash to be debited from their account, on top of the purchase.
Fees and Surcharges

Interac Association does not set or collect fees from cardholders. However, financial institutions may charge a
transaction fee.

Merchants may choose to apply a surcharge (additional fee) for transactions made using Interac services. This
fee is not passed on to Interac Association.
Interac Online
Interac Online is not supported by Global.
Interac Flash
Interac Flash is Canada’s first contactless debit solution and is supported for purchases under $100. It allows
cardholders to pay for everyday purchases quickly, securely and conveniently by simply holding their Interac
Flash-enabled bank card in front of the reader at checkout.
Mobile Interac Flash brings Interac Flash, the contactless enhancement of Interac Debit, to the mobile form
factor. This means that Canadians, regardless of their mobile network, will be able to choose to use Interac
Flash on their mobile devices as long as their financial institution supports mobile Interac Flash, their device
hardware (e.g., NFC) supports it, and the mobile payment wallet application supports mobile Interac Flash.
Requirements:
 A PIN is not required for these transactions.
 The PINpad must NOT request account selection for an Interac Flash transaction.
BankcardTransaction/TransactionData/AccountType must be set to “NotSpecified”.
 The POS or contactless reader MUST display the transaction type and the final transaction amount
including any additional charges (e.g. Tip) prior to card presentment.
 A contactless reader must be certified by an Interac approved testing facility and listed as an Interac
approved “Dual Interface Certified Reader” and must be certified by EMVCo as a Level 1 Contactless
Approved Proximity Coupling Device.
 A device that accepts Flash must also accept Interac contact chip and PIN.
 Cashback is NOT permitted for an Interac Flash transaction.
 Flash transactions must be in Canadian currency.
 Interac Flash limits MUST NOT be defined by the Terminal Reader (e.g. Contactless Transaction Limit,
CVM required limit) as per Interac requirement. Interac Flash Issuer is responsible for indicating a Flash
Per transaction limit as per the configuration of the Flash card.
 Since there is no card present when the host response is received, if chip data is received in the host
response for an Interac Flash transaction, the terminal shall ignore it.
 Failed contactless transactions that revert to contact processing are not considered fallback.
International Card Processing

Diners Club transactions are processed through the Discover Network.
JCB transactions in the United States, Puerto Rico, the US Virgin Islands, Guam, Palau, and the Northern Mariana
Islands are processed through an agreement with the Discover Network.
JCB transactions in Canada are processed through an agreement with American Express.

Merchant Identifier (MID/TID)
The Merchant Identifier (MerchantProfileMerchantData/MerchantId) submitted in the request message must
match exactly the MID for the terminal as configured in the Customer Master File on the Global Payments host.
Please do not pad/fill the MID field with leading spaces or zeros. Applications that fill the MID field with leading
spaces or zeros will not pass the message certification process.
Terminals must be uniquely identified when a merchant location has multiple terminals, i.e. in a merchant
location with multiple lanes each lane has to be assigned its own unique terminal ID.
Mobile POS Terminals (mPOS)

Mobile point of Sale (mPOS) acceptance solutions allow merchants to use mobile devices as point-of-sale
terminals. Mobile POS acceptance solutions typically make use of a “mobile POS card reader accessory” that can
either be plugged into the audio jack or USB port or connected via Bluetooth to read payment cards. “Mobile
devices” refer to computer oriented multi-purpose mobile computing platforms including feature phones,
smartphones, tablets and PDA’s.
Mobile POS solutions support different forms of terminals:
 Chip Only mPOS: without magnetic stripe reading capability
 Chip-capable mPOS; with both magnetic stripe and chip reading capability but without PIN capability
 Hybrid mPOS
ApplicationData/HardwareType must be set to "MPOS".
Partial Approvals (Partial

Authorization)
A partial authorization transaction enables a merchant to receive approval for a credit card's balance if that
balance is less than the transaction request amount.
All credit transactions should have BankcardTransactionData/PartialApprovalCapable set to either “true” or
“false”. The flag will default to “false” if not present. “True” means the merchant is capable of accepting partial
approvals and handling the resulting split tender transaction. A split tender transaction occurs when a partial
authorization of the total purchase amount is returned to the device in the transaction response. The device
must then prompt for payment of the remaining balance due on the sale. The cardholder uses a different form
of payment, such as another payment card, cash, or a check.
If the card's balance is less than the purchase amount and the card issuer supports partial approvals, the portion
of the transaction request amount equal to the credit card's balance will be approved.
BankcardTransactionResponse/StatusCode will contain “010” and BankcardTransactionResponse/Amount will
contain the approved amount. The POS device must prompt for the remaining purchase amount.
If the customer is not capable of completing the transaction, the partial approval must be reversed (Undo). If
the reversal is declined, a return can be used to remove the transaction from the cardholder’s account.
Merchant’s American Express accounts must be enabled by American Express to allow partial approvals.

Card Associations require that the merchants who are partial authorization capable must support reversal of
authorization.
Partial approvals are not supported for PIN Debit.
Prepaid Credit Cards

Prepaid cards are fixed value cards branded with a payment brand logo—such as American Express, Discover,
MasterCard, or Visa. Although prepaid cards are sometimes called “gift cards”, they should not be confused
with proprietary, closed loop gift cards purchased by merchants and issued to customers for use only at the
merchant’s locations. Brand issued prepaid “gift cards” are meant to be accepted anywhere the brand is
accepted and not limited to a particular merchant. The transactions flow through the normal authorization
systems at the various endpoints and are sent to the issuer, just like non-prepaid credit cards. Prepaid cards can
be labeled by the Issuer as Credit or Debit cards. Prepaid cards can be processed in any industry.
If the card issuer returns the card's remaining balance and the purchase amount does not exceed the card's
balance, the remaining balance after the purchase will be returned in
BankcardTransactionResponse/FinalBalance. A negative balance will be returned as zero.
Displaying balances on a terminal screen or printing them on the customer receipt are optional for all brands
except MasterCard. MasterCard requires that balances, when available, are either displayed on a screen or
printed on the customer’s receipt. Providing the opportunity for the customer to view the account balance on a
customer-facing terminal screen or on a printed receipt can provide a more positive customer experience.
Discover returns the balance on prepaid cards as the approval code in the authorization response.
Purchase Card - Level 2

For detailed information about Purchase/Commercial Card Processing, refer to the EVO Snap* Support
Knowledge Base. Global East supports Level 2 processing using the fields listed below. All fields should be
submitted in order to achieve the best interchange rates.
Canadian merchants using Level 2 Data must use Itemized Taxes,
BankcardTransactionPro/TransactionData/Level2Data/Tax/ItemizedTaxes/ItemizedTax/Amount and
BankcardTransactionPro/TransactionData/Level2Data/Tax/ItemizedTaxes/ItemizedTax/Type.
ItemizedTax/Type for National Tax (GST) is GoodsServicesTax; ItemizedTax/Type for Local Tax (PST) is
StateProvincialTax or (QST) QuebecSalesTax. The total of all ItemizedTax/Amount values must equal the
amount submitted in BankcardTransactionPro/TransactionData/Level2Data/Tax/Amount. ItemizedTax/Type
HarmonizedTax (HST) may be used in place of GST, PST and QST tax values but itemized taxes must still be used
to show type. If itemized taxes are not sent, the tax amount may not be reported.
BankcardTransactionPro/TransactionData/Level2Data/CustomerCode – a customer code or purchase order
number supplied by the customer for this invoice.
BankcardTransactionPro/TransactionData/Level2Data/ShipFromPostalCode – optional postal code from which
goods are shipped.
BankcardTransactionPro/TransactionData/Level2Data/DestinationPostal– optional postal code to which goods
are shipped.

BankcardTransactionPro/TransactionData/Level2Data/DestinationCntryCode– optional country code to which
goods are shipped.
BankcardTransactionPro/TransactionData/Level2Data/Description– used for American Express only to provide
up to 160 characters of additional charge description information.
BankcardTransactionPro/TransactionData/Level2Data/TaxExempt/IsTaxExempt – the tax exempt indicator for
this invoice.
 If the customer is tax exempt, set the indicator to “Exempt”.
 If the customer is not tax exempt and the tax amount is not included in the transaction, set the indicator
to “NotExemptTaxInfoNotProvided”.
 If the customer is not tax exempt and the tax amount is included in the transaction, set the indicator to
“NotExemptTaxInfoProvided”.
Recurring Bill Payments

A recurring transaction is a transaction for which a cardholder provides written permission to a merchant to
periodically charge his/her account number for recurring goods or services. These may include payment of
charges such as insurance premiums, subscriptions, membership fees, tuition or utility charges. The recurring
transaction indicator must be present in the authorization. Address verification must be obtained with the initial
authorization request and is not required in the subsequent recurring transactions that contain the recurring
indicator. Address verification is required to be obtained yearly.
Recurring Bill Payments are supported in the MOTO and Ecommerce industry types.
BankcardTransactionPro/InterchangeData/BillPayment must be set to “Recurring”.

BankcardTransaction/TransactionData/CustomerPresent must be set to “BillPayment”.
BankcardTransactionPro/InterchangeData/ExistingDebt must be set to “NotExistingDebt”.
BankcardTransactionPro/InterchangeData/CurrentInstallmentNumber must be set to “1” for the first
transaction of a recurring payment series. Subsequent payments must be set to any value greater than 1.
BankcardTransaction/TransactionData/OrderNumber cannot be blank or all zeroes.
Resubmit for “008” Response

The value “008” in BankcardTransactionResponse/StatusCode and the
BankcardTransactionResponse/StatusMessage “AP WITH ID” will be returned as a failed transaction. This
response usually results from a person using a card for the first time. The merchant should verify the identity of
the cardholder and may then accept or reject the transaction.
 If the merchant rejects the transaction, no action is necessary.
 If the merchant accepts the transaction, they must call Resubmit() in order to force this transaction into
their open batch.

Soft Descriptor (Dynamic Descriptor)
Global supports dynamic descriptors for MOTO and Ecommerce only.
This data may be used to provide more descriptive information in the merchant name field on settled
transactions. Data is limited to 25 characters and requires Global Merchant Master File set up.
The following field may be submitted:
BankcardTransaction/TransactionData/AlternativeMerchantData/Name
Verify()
Some merchants may wish to verify credit card information in order to determine whether to accept a
transaction. This transaction allows the merchant to submit a request for AVS information and/or
CVV2/CVC2/CID information without requesting transaction authorization.
Verify() is not supported for the Restaurant industry. Global expects Authorize() followed by either Capture()
or Undo(), depending on whether the merchant wants to complete the transaction or reverse it.
Verify() transactions MUST be keyed transactions, even in the Retail industry type. Swiped verification is not
supported by Global Canada.
Verify() transactions may include BankcardTransaction/TenderData/CardSecurityData/AVSData/PostalCode,
BankcardTransaction/TenderData/CardSecurityData/AVSData/Street and
BankcardTransaction/TenderData/CardSecurityData/CVData.
Discover requires ZIP Code and address information if AVS data is submitted. American Express does not verify
CID on non-monetary transactions.
3-D Secure Processing

Verified By Visa (VbV/VPAS)
If a token is obtained:
BankcardTransaction/TenderData/EcommerceSecurityData/TokenData is required and contains the
token provided by the service.
BankcardTransaction/TenderData/EcommerceSecurityData/TokenIndicator is required and must be
set to “VPAS”.
BankcardTransaction/TenderData/EcommerceSecurityData/XID is optional and may contain the Visa
XID value.
If VbV is supported but the token could not be obtained:
BankcardTransaction/TenderData/EcommerceSecurityData/TokenData will not be populated.
set to “AttemptedCardUnsupported” or “AttemptedServiceUnavailable”.

MasterCard Secure Code (MCSC/UCAF)
NOTE: As of 13 November 2016, all MasterCard SecureCode transactions must include an Accountholder
Authentication Value (AAV) value (TokenData). Transactions without the AAV will be automatically downgraded
to a regular eCommerce transaction and will not benefit from the liability shift and other advantages of an
attempted SecureCode transaction.
If a token is obtained:
BankcardTransaction/TenderData/EcommerceSecurityData/TokenData is required and contains the
token provided by the service.
set to “UCAFWithData”.
If MCSC is supported but the token could not be obtained or will not be sent with the transaction:
BankcardTransaction/TenderData/EcommerceSecurityData/TokenData will not be populated.
set to “AttemptedCardUnsupported”, “AttemptedServiceUnavailable”, or “UCAFWithoutData”.
End of Day
Host-based settlements are limited to a total of 5120 units (a unit is part of the detail record) per batch.
Acquirer Reference Data (1 unit), Market Data (1 unit), and the remainder of the Detail Record (1 unit) are each
considered single units of data. A single detail item can contain one, two, or three units. Since the host can
accept a maximum of 5120 units in a single batch, the maximum number of detail items in the batch is
dependent upon the number of units in each detail item. When the limit is reached a new batch is automatically
begun. Therefore, it is possible for a merchant to have more than one batch per day if their transaction
volume is high.
Global Payments automatically closes the merchant's batch of transactions on its host computer at 1:00 a.m.
Eastern Time, without the merchant’s intervention, guaranteeing at least one daily balance and settlement for
the merchant. This function does not require the merchant to balance the paper sales slips to the electronic
batch.
If a transaction response contains data in the BankcardTransactionResponse/ServiceTransactionId field, that
value may be used to tie the authorization to the settlement report for reconciliation purposes. However, there
is no guarantee that data will be present in this field.
EMV Processing
All EMV Data must be translated from binary and submitted in HEX format.
Track 2 Data is required with EMV Data.
ApplicationData/ReadCapability must be set to “MSRKeyICC”, “MSREMVICC”, “Chip”, “EMVICC”, or
“ContactlessChip”.
BankcardTransactionDataDefaults/EntryMode must be set to “ChipReliable”, “ContactlessMChipOrSmartCard”,
“ChipTrack2DataFromRFID” or “ChipUnreliable”.
BankcardTransaction/TransactionData/CardholderAuthenticationEntity may be set to “ICC” or “PIN”.

ApplicationData/EMVTerminalData/CardDataOutputCapability may be set to “ICC”.
Offline EMV processing is not supported for this service and must not be implemented. Terminals must be
configured with zero EMV floor limit.
Global Canada only supports offline PIN processing, therefore no PIN or KSN information is ever sent to them in
any financial transaction.
An Undo transaction must be sent if the chip declines a transaction that was approved by the host.
BankcardTransaction/TransactionData/UndoReason or
BankcardTransaction/TransactionData/PINDebitReason must be set to “SuspectMalfunction” for these
reversals.
Tip Adjustments
Historically for credit card purchases that may have a tip added (e.g. Restaurant); the Pre-Authorization and
Completion transactions have been used. Because EMV POS Applications will always have a PIN pad present,
Global Payments recommends that EMV credit card tip transactions be processed using the EMV Purchase
transaction rather than the Pre-Authorization and Completion transactions.
The credit EMV Purchase (with tip) transaction flow should be:
1. Display transaction amount on the PIN pad for cardholder approval.
2. Prompt cardholder to add a tip amount.
3. Confirm total (Transaction + Tip).
4. Begin the standard EMV Purchase transaction flow using the new total.
Supported AIDs
Application Identifiers (AID)
Application Partial AID (RID + PIX) RID PIX
Selection
Visa Credit and Debit Yes A0000000031010 A000000003 1010
Visa Electron Yes A0000000032010 A000000003 2010
MasterCard Credit Yes A0000000041010 A000000004 1010
Interac Yes A0000002771010 A000000277 1010
American Express Yes A00000002501 A000000025 01
JCB Yes A0000000651010 A000000065 1010
Discover Yes A0000001523010 A000000152 3010
EMV Receipt Requirements

All General Receipt Requirements must be followed. In addition, EMV processed transaction receipts must
follow these guidelines:
• All EMV transaction receipts must display the Application Identifier (AID) number of the chip card
plan being processed (BankcardTransactionPro/TenderData/EMVData/ApplicationId). The AID shall
be printed as hexadecimal characters.
• All EMV transaction receipts must display the Terminal Verification Results (TVR) hexadecimal value
on the transaction receipt (BankcardTransactionPro/TenderData/EMVData/TerminalVerifyResult).
This value can help in troubleshooting errors caused by the financial application for an EMV
transaction processed. However, TVR and TSI are optional on refund receipts and are not applicable
on void receipts.
• If the transaction is performed with offline PIN for Cardholder Verification Method (CVM), then no
signature line is printed on the receipt but the following information is printed:

“By entering a verified PIN, cardholder agrees to pay issuer such total in accordance with
issuer’s agreement with cardholder”.
• When the applicable CVM is signature the terminal shall print a receipt with a line for cardholder
signature.
• It is a mandatory requirement that the receipt does not indicate whether a transaction was
processed online or offline.
• If the authorization is declined, the application should print a transaction receipt with the reason for
decline clearly stated.
• If a mobile devices battery is too low to print a receipt, the application should display a message
about the receipt printing issue, informing the user about recharging the battery in order to print
the transaction receipt.
• All receipts should include the Total Authorization Amount and the Tip Amount and/or Cash Back
Amount if included in the transaction.

Fallback Approval Receipt
Required fields:
1. Entry Method (Chip/Mag)
2. Approved message with authorization code

Signature CVM – Online Approval Receipt
Required fields:
1. Entry Method (Chip)
3. Preferred mnemonic associated with AID
4. Application Identifier (AID) used to process the transaction
5. Terminal Verification Results of transaction processed (TVR)
6. Transaction Status Information performed on the terminal (TSI)

Authorized Online Approval Using PIN Receipt
Required fields:
3. Disclaimer message to indicate transaction was verified by PIN

Authorized Online Declined Receipt
Required fields:
2. Declined message

Fallback Declined Receipt
Required fields:
2. Declined message

Fallback Declined Receipt
Required fields:

Fallback Refund Receipt
Required fields:

Online Void Sale Receipt
Required fields:
1. Entry Method (retains original transaction information)
2. Online Approved

Fallback Void Sale Receipt
Required fields:
1. Entry Method (retains original transaction information)

Retail/Restaurant Tip Amount Online Funds Approved Using PIN Receipt
Required fields:
2. Approved message for online funds with authorization code
3. Disclaimer message to indicate transaction was verified by PIN

Retail/Restaurant Tip Amount Online Funds Approved Using Chip and
Signature Receipt
Required fields:
2. Approval message for online funds with authorization code

Retail/Restaurant Tip Amount Fallback Approved Receipt
Required fields:

Interac Debit Card (Online Approved – PIN)
Required fields:
1. Entry Method (‘C’ - Chip)
2. Approval message for online funds with authorization code
3. Preferred mnemonic associated with AID (Interac)
Notes:
1. The currency indicator has been included on the “Total” line.
2. A signature line has not been printed because the CVM was “PIN”.
3. Card Swipe Indicator is “C” because Track 2 Data was read from the EMV chip.
4. Depending what is programmed on the Chip Card Application Preferred Name, Application Label or Card
Label based on PAN’s Bin should be printed.

Response Codes
From the “Greenhouse South Spec 2015.001_0520.pdf”, version 2015.001, release May 2015 and “Global
Payments East Host EMV Specifications Ver 1.32.pdf”, version 1.32, release February 2016.
See the Resubmit for “008” Response section for instructions on dealing with the “AP WITH ID” response.
Action Code <StatusCode> Sandbox Trigger Values

To simulate a host
approved/chip declined
transaction, send EMV data in
the request with *.06 trigger
value.
Global East
Global East Verbiage Global East Description
Code
Credit Response Codes
Any cent value not listed here
AP Approved or Completed Successfully
000 will return this response for
AP NEW INFO Approved. Updated cardholder data available
CREDIT transactions
Refer to American Express
CALL AE
Refer to Discover
CALL DISCOVER
001 Call your Visa/MasterCard Voice Authorization *.03
CALL CENTER
Center
CALL XXXXXXXXXX
Call indicated number
CALL AE
CALL DISCOVER
002 Touchtone capture, won’t roll to an operator *.04
CALL CENTER
CALL XXXXXXXXXX
003 INVLD MERCH ID Invalid Merchant ID *.05
004 PIC UP Authorization Declined *.07
DECLINE Authorization Declined *.08|*.27|*.32|*.33|*.41|
DECLINE NEW INFO Update cardholder data and retry the transaction *.42|*.43|*.44|*.45|*.46|
005 DECLINE TRY LATER Try again in 3 days *.47|*.48|*.49|*.50|*.51|
DO NOT TRY AGAIN Stop payment of a specific recurring payment *.52|*.53|*.54|*.55|*.56|
STOP PAY ORDERED Stop all future recurring payments *.57
All Undo() (VOID/REVERSAL)
transactions will return this
006 REVERSED Requested transaction reversal was successful
response for successfully
voided transactions.
007 DECLINE-CV2 FAIL Response for CVV2 failure. Declined. (Visa) *.09
Approved with positive ID. Host does not capture
008 AP WITH ID *.10
this transaction
*.59
The approved response
010 PARTIAL AP Only part of the requested amount was approved amount will be $1.59, so the
request value should be at
least $2.59.

To simulate a host
value.
Global East
Code
Processing code entered is incorrect. Please refer to
012 INVLD TRAN CODE *.11
valid processing code.
013 INVLD AMOUNT Amount entered is invalid *.12
Account number or track data does not pass edit
014 INVLD ACCT *.13
checks
019 PLEASE RETRY Retry the transaction. *.14
020 INVLD INSTALLMNT Reserved. Global Payments internal use. *.15
021 INVLD CURRENCY Reserved. Global Payments internal use. *.16
Required data for processing chip transactions was
025 INVLD ICC DATA missing from the authorization request or data could *.17
not be parsed.
Reserved. The transaction is not allowed because
030 NA CAPT TXN *.18
the original item is in the current open batch.
Reserved. The transaction could not be processed
031 FAX REQUIRED *.19
on-line so the fax process must be used.
Reserved. The transaction is not allowed because
032 NA SETL TXN *.20
the original item is in a closed batch.
054 INVLD EXP DATE Expiration date entered is incorrect *.21
INVLD PIN Incorrect PIN entered
055 *.22
ENCRYPTION ERROR Encryption error
The transaction is not being allowed to the
057 TRAN NOT ALLOWED *.23
cardholder.
Customer, merchant or terminal set up incorrectly
058 UNAUTH TRANS for transaction used or the transaction is not being *.24
allowed to the merchant.
075 MAX PIN RETRIES Maximum PIN entry attempts exceeded *.25
Global Payments cannot contact issuing bank for
091 ISSUER UNAVAIL *.26
authorization
*.01
To override duplicate
checking, resubmit the
094 AP DUPE Transaction entered is a duplicate declined transaction by setting
BankcardTransaction/Transac
tionData/TransactionCode to
“Override”
0C1 SYSTEM UNAVAILABLE Global Payments Check System unavailable *.28
Terminal has not been balanced within time
0N5 MUST BALANCE NOW specified in the Global Payments Merchant Master *.29
File for this merchant.
0N8 INVALID DATA Format of the transaction is incorrect. *.30

To simulate a host
value.
Global East
Code
Transaction is attempted on a transaction that is not
0NA NO TRANS FOUND *.31
in the open batch on the host.
Approved but not captured (applies only to credit
0NC AP NOT CAPTURED N/A
card transactions)- stand in
Approved but this EDC merchant is not set up to
0NE AP AUTH-ONLY capture this card type (applies only to credit card N/A
transactions)
0P1 APPROVED Approved debit card transaction N/A
Global Payments GATEWAY is experiencing a
0P2 DB UNAVAILABLE *.35
problem.
Merchant is not set up for debit on Global Payments
0P5 UNAUTH USER *.36
Merchant Master File.
0P6 INVALID CARD Invalid card number *.37
0T1 EDC UNAVAILABLE EDC application down, try later *.38
121 EXCEEDS MAX AMT Exceeds withdrawal amount limit *.39
122 INVLD CID American Express CID failure. *.40
Only part of the requested amount was approved,
1NE PART AP AUTH-ONLY but this EDC merchant is not set up to capture this N/A
card type (applies only to credit card transactions)
Debit Response Codes
Any cent value not listed here
000 – 049 N/A Approved response. will return the "000" response
for DEBIT transactions
*.23|*.24|*.25|*.26|*.27|
*.28|*.29|*.30|*.31|*.32|
*.33|*.35|*.36|*.37|*.38|
050 – 099 N/A Declined response. *.39|*.40|*.41|*.42|*.43|
*.44|*.45|*.46|*.47|*.48|
*.49|*.50|*.51|*.52|*.53|
*.54|*.55|*.56|*.57
052 N/A PIN try limit exceeded *.03
Restricted Card Status (Interac Fallback Decline
059 N/A *.04
Response)
060 N/A Selected bank account not set-up on debit card. *.05
Track II information sent in the request is invalid
064 N/A *.07
or bad.
Unable to authorize (issuing FI is not available to
074 N/A *.08
authorize)
076 N/A Insufficient Funds *.09

To simulate a host
value.
Global East
Code
*.01
To override duplicate
Duplicate transaction. Host received a request checking, resubmit the
078 N/A with a duplicate Transmission Number for the declined transaction by setting
Terminal ID. BankcardTransaction/Transac
tionData/TransactionCode to
“Override”
100 – 149 N/A Referral response. *.10
Card used in the request is not a card accepted by
105 N/A *.11
the merchant.
150 N/A Setup error. *.12
200 – 821 N/A Transaction error response. *.13
201 N/A Incorrect PIN entered. *.14
204 N/A Enter Lesser Amount *.15
206 N/A Card not Setup *.16
210 or 877 N/A PIN Key error. *.17
An error was encountered with one or more of the
800 N/A *.18
data fields sent in the request.
Time-out. Host did not receive a response from a
810 N/A *.19
card authoriser.
898 N/A MAC error in the Request message. *.20
899 N/A Sequence number error *.21
Declined. (POS Capture Code problems and
900 – 987 N/A *.22
miscellaneous Administrative reasons)

Business Rules and Guidelines Global Canada HC BCP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Rules and Guidelines Global Canada HC BCP

Uploaded by

Copyright:

Available Formats

Business Rules and

Making Payments a Snap* for Developers | Proprietary & Confidential 1

Fallback Approval Receipt..............................................................................................................................17

Making Payments a Snap* for Developers | Proprietary & Confidential 2

Making Payments a Snap* for Developers | Proprietary & Confidential 3

Visa, MasterCard, Amex, Discover, JCB, Diner's Club,

Making Payments a Snap* for Developers | Proprietary & Confidential 4

Alternate Transaction Routing (ATR)

Making Payments a Snap* for Developers | Proprietary & Confidential 5

CVV2, CVC2, CID, CSC Processing

Making Payments a Snap* for Developers | Proprietary & Confidential 6

Message Authentication Code (MAC)

Making Payments a Snap* for Developers | Proprietary & Confidential 7

Partial Approval (Partial Authorization)

Fees and Surcharges

Making Payments a Snap* for Developers | Proprietary & Confidential 8

International Card Processing

Making Payments a Snap* for Developers | Proprietary & Confidential 9

Mobile POS Terminals (mPOS)

Partial Approvals (Partial

Making Payments a Snap* for Developers | Proprietary & Confidential 10

Prepaid Credit Cards

Purchase Card - Level 2

Making Payments a Snap* for Developers | Proprietary & Confidential 11

Recurring Bill Payments

BankcardTransactionPro/InterchangeData/BillPayment must be set to “Recurring”.

Resubmit for “008” Response

Making Payments a Snap* for Developers | Proprietary & Confidential 12

3-D Secure Processing

Making Payments a Snap* for Developers | Proprietary & Confidential 13

Making Payments a Snap* for Developers | Proprietary & Confidential 14

EMV Receipt Requirements

Making Payments a Snap* for Developers | Proprietary & Confidential 15

Making Payments a Snap* for Developers | Proprietary & Confidential 16

Making Payments a Snap* for Developers | Proprietary & Confidential 17

Making Payments a Snap* for Developers | Proprietary & Confidential 18

Making Payments a Snap* for Developers | Proprietary & Confidential 19

Making Payments a Snap* for Developers | Proprietary & Confidential 21

Making Payments a Snap* for Developers | Proprietary & Confidential 22

Making Payments a Snap* for Developers | Proprietary & Confidential 23

Making Payments a Snap* for Developers | Proprietary & Confidential 24

Making Payments a Snap* for Developers | Proprietary & Confidential 25

Making Payments a Snap* for Developers | Proprietary & Confidential 26

Making Payments a Snap* for Developers | Proprietary & Confidential 27

Making Payments a Snap* for Developers | Proprietary & Confidential 28

Making Payments a Snap* for Developers | Proprietary & Confidential 30

Making Payments a Snap* for Developers | Proprietary & Confidential 31

Action Code <StatusCode> Sandbox Trigger Values

Making Payments a Snap* for Developers | Proprietary & Confidential 32

Making Payments a Snap* for Developers | Proprietary & Confidential 33

Making Payments a Snap* for Developers | Proprietary & Confidential 34

Making Payments a Snap* for Developers | Proprietary & Confidential 35

You might also like