Online Authorisation System Version 3.7 R02 Processing Reference Guide

ONLINE
Authorisation System
Version 3.7 R02
Processing Reference
Guide
Prepared by
Card Tech Ltd
114A Cromwell Road, London SW7 4ES
© Card Tech Limited 2003-2006. All rights reserved
Copyright in the whole and every part of this document belongs to Card Tech Limited, with the
exception of proprietary material and the brand or product names of other parties for which the
rights in such material or trademarks remain with their respective owners. Names and data used
in examples herein are fictitious unless otherwise noted.
This document and the Card Tech software it describes are furnished by Card Tech Limited
under a Software Licensing Agreement or Confidentiality Agreement, and may be used or
copied only in accordance with the terms of such Agreement. Neither this document nor the
Card Tech software it describes may be used, sold, transferred, copied, translated, reproduced or
transmitted in any form or by any means, electronic or mechanical, for any purpose, in whole or
in part, other than in accordance with the terms of such Agreement, or otherwise without prior
written consent of Card Tech Limited.
This document describes a generic product and should be read in conjunction with other
documents relevant to the configuration of any specific system. The licensee of Card Tech
software is responsible for ensuring that the product described herein meets its own
requirements. The information contained in this document is subject to change without notice
and should not be taken as a commitment by Card Tech Limited. Card Tech Limited assumes no
responsibility for any errors that may appear in this document.
ONLINE Version 3.7 R02 Processing Reference Guide
Publication: P1665 — Release: 001
Additional copies of this guide may be purchased separately: for further information
please apply to Card Tech Limited at www.ctl.com.
Contents
Contents
How to use this manual … … … … … … … … vi
Authorisation processing … … … … … … … 7
Authorisation process … … … … … … … … 7
Chip cards … … … … … … … … … … 8
Traditional VISA … … … … … … … … … 12
Traditional MasterCard … … … … … … … … 16
MasterCard Corporate Fleet Card … … … … … … 20
Instalments … … … … … … … … … … 21
Traditional Europay … … … … … … … … 22
Traditional HOST … … … … … … … … … 26
COPAC cards … … … … … … … … … 30
Balance inquiry response … … … … … … … 33
Merchant Profiles … … … … … … … … … 34
Currency conversion … … … … … … … … 35
Transaction currency … … … … … … … … 35
Issuer currency … … … … … … … … … 35
Center currency … … … … … … … … … 35
Card currency … … … … … … … … … 35
Group currency … … … … … … … … … 35
Fraud weight … … … … … … … … … … 36
Groups … … … … … … … … … … … 38
Group OTB checking … … … … … … … … 38
Group cash OTB checking … … … … … … … 38
Group number of cash transactions checking … … … … 38
MCC Profiles … … … … … … … … … … 40
MCC Product Velocity Checks … … … … … … 41

Authorisation logic for a Velocity Check … … … … … 41
PIN verification during authorisation … … … … … 43

PIN previous block checking … … … … … … … 43
© Card Tech Limited 2003-2006. All rights reserved ONLINE AUTHORISATION SYSTEM Version 3.7 R02
Revised: 05 July 2006 iii PROCESSING REFERENCE GUIDE (P1665-001)
Contents
PIN verification - VISA, MasterCard and Host … … … … 44

PIN verification - Europay … … … … … … … 44
Reconciliation processing … … … … … … … 45
Interface file transaction matching … … … … … 45
Matching on MCCs … … … … … … … … … 46
Daily Reports … … … … … … … … … … 47
Acquirer Log … … … … … … … … … … 48
Acquirer Log (MDS) … … … … … … … … 49
Acquirer Log (SMS) … … … … … … … … 50
All pending chargebacks … … … … … … … … 51
Authorisations Exceeding the Center Limit … … … … … 52
Authorisations Exceeding High Count … … … … … 53
Card Bonus Change … … … … … … … … 54
Card Bonuses Approved … … … … … … … … 55
Card Bonuses Used … … … … … … … … 56
Card Cash Bonuses Approved … … … … … … … 57
Card Cash Bonuses Used … … … … … … … 58
Card Listing … … … … … … … … … … 59
Card Listing (Short) … … … … … … … … 60
Cards Near Credit Limit … … … … … … … … 61
Cards with High Authorisation Amount … … … … … 62
Cards with High Authorisation Amount in Center Currency … … 63
Cards with High Number of Authorisations for EOD … … … 64
Chargeback reversals … … … … … … … … 65
Dropped Authorisations … … … … … … … … 66
Exception Management … … … … … … … … 67
Exception Management Delete Failures … … … … … 68
Exception Management Update Failures … … … … … 69
Fee Collection & Funds disbursement … … … … … 70
Group Bonus Change … … … … … … … … 71
Group Bonuses Approved … … … … … … … 72
Group Bonuses Used … … … … … … … … 73
Group Cash Bonuses Approved … … … … … … 74
Group Cash Bonuses Used … … … … … … … 75
Group Listing … … … … … … … … … 76
Group Listing (Short) … … … … … … … … 77
ONLINE AUTHORISATION SYSTEM Version 3.7 R02 © Card Tech Limited 2003-2006. All rights reserved
PROCESSING REFERENCE GUIDE (P1665-001) iv Revised: 05 July 2006
Contents
Issuer Log … … … … … … … … … … 78
Issuer Log (Declines) … … … … … … … … 79
Manual Advices Approved … … … … … … … 80
Manual Advices Used … … … … … … … … 81
Manual Card Status Change … … … … … … … 82
New Chargebacks received … … … … … … … 83
Outstanding Authorisations … … … … … … … 84
Reconciliations … … … … … … … … … 85
Representments … … … … … … … … … 86
STIP Authorisations … … … … … … … … 87
Transactions … … … … … … … … … … 88
Unauthorised Transactions … … … … … … … 89
Appendix … … … … … … … … … … … … 91
ISO 8583 messages … … … … … … … … 91
ISO Response codes … … … … … … … … 93
Issuer Response Reason Codes… … … … … … 95
Acquirer Response Reason codes … … … … … 110
Visa Reason Codes … … … … … … … … 112
MasterCard Reason Codes … … … … … … … 117
Routing Product List … … … … … … … … 119
Region coding for exception files … … … … … 121
Index … … … … … … … … … … … … … 123
© Card Tech Limited 2003-2006. All rights reserved ONLINE AUTHORISATION SYSTEM Version 3.7 R02
Revised: 05 July 2006 v PROCESSING REFERENCE GUIDE (P1665-001)
- How to use this manual - Revisions
un 2000
How to use this manual

15 Jun
Revisions
This manual describes various system processing operations and includes a catalogue of
the system’s reports. It also includes parameter files and an appendix of messages and
codes used in ONLINE. Users who are familiar with previous versions of the system can
find information on the differences between this and previous versions in the release notes
issued with the system.
Documentation conventions
The following conventions apply throughout this manual: 15 Jun
– Every stage of each function is illustrated with a snapshot of the screen. When only a
portion of the screen is relevant to the description, only that portion is printed.
– Instructions that you need to enter or select, such as command buttons or menu options,
are printed in boldface as in: “press Enter”, “click OK”, or “select Merchant”.
– File and directory names are printed in sans serif text thus: /usr/tmp/.
Important notes are printed in a box.
VISA/MasterCard/Europay/American Express
This manual assumes that your authorising centre has a VAP/MIP/EM/Globe connection 15 Jun
to VISA (BASE I/II, SMS), MasterCard, Europay and American Express. If you have
only one connection, please disregard any reference to the payment system to which your
centre is not connected.
Please note, however, that any request for a card of the non-connected payment system
will not be rejected by ONLINE. It will be sent to the connected payment system, which
will route it to the other payment system.
The payment system will charge fees for this routing service.

Revised: 05 July 2006 vi ONLINE AUTHORISATION SYSTEM Version 3.7 R02
PROCESSING REFERENCE GUIDE (P1665-001)
Authorisation processing
Authorisation process - -
ONLINE AuthorisATION SYSTEM Version 3.7 R02
Authorisation processing 15 Jun
Authorisation process
15 Jun
When an authorisation request (message 0100) is received, the engine performs the
following checks to determine whether the request should be approved or declined.
Authorisations may be requested for Visa, MasterCard, American Express, Europay or
Host formats. Host is used to designate a link other than Visa, MasterCard, American
Express, or Europay.
In the following descriptions of the process, any decision that results in an approval or
decline is followed by the ISO response code (shown in italic) and the response reason
code. The response code may be shown in one of the following ways:
– a fixed numeric response code
– the name of a parameter in the engine section of the center parameter file, which
evaluates to a numeric response code
– the card status code, which evaluates to a numeric response code
A list of ISO response codes is shown on p. 110.
The engine processes requests for each payment system separately.

Revised: 05 July 2006 7 ONLINE AUTHORISATION SYSTEM Version 3.7 R02
Authorisation process - Chip cards -
Chip cards
When the engine determines that the card is a chip card, it performs the following checks:
15 Jun
Is the card in the database?
Yes: Proceed
No: Is there a banking system host connection and is the card a debit card?
Yes: Forward to banking system
No: Decline, respnotfound, 2
Is the authorisation request cryptogram (ARQC) correct?
Yes: Proceed
No: Decline, respchiparqcfl, 251
Was ATC verification successful?
Yes: Proceed
No: Decline, respchipcntseq, 252
Do the TVRs match the values in [engine]checkstvr?
Yes: Proceed
No: Decline, reschipcrespchiptvrfl, 253
Does the CVR match the values in [engine]checkscvr?
Yes: Proceed
No: Decline, respchippcvrfl, 254
Is fallback option activated?
Yes: Decline, respchipfallbk,255
No: Proceed
Is CVV data unreliable?
Yes: Decline, respchipcvvunr,256
No: Proceed
Is card status code any of the following: 01, 04, 05, 07, 41, 43.
Yes: Decline, card status code, 3
No: Proceed
Perform PIN previous block checking. See p. 43 for details.
Has the card expired?
Yes: Decline, respickexpired, 4
No: Proceed
Is card pending activation?
(If [engine]messexpirydate is set to 4 or 5)
No: No activation check
Yes: Is authorisation PIN-based?
Yes: Proceed with card activation
No: Does the authorisation contain a PIN prevalidation from VISA?
ONLINE AUTHORISATION SYSTEM Version 3.7 R02

PROCESSING REFERENCE GUIDE (P1665-001) 8 © Card Tech Limited 2003-2006. All rights reserved
Revised: 05 July 2006

No: No activation check.
Activation check
No: Proceed (activation check completed)
Yes: Is automatic activation allowed at system level ([engine]cardactivationmethod greater than 0)?
No: Decline, respexpnotpermitted (card check completed)
Yes: Does authorisation request info match the values contained in card?
Yes: Proceed
[engine]cardactivate:1 activate card if authorisation request is approved
[engine]cardactivate:2 activate card directly
Is the card local only and is the country of the merchant different from the country of the cardholder?
Yes: Decline, resplocalonly, 5
No: Proceed
Is the card ATM only and is the merchant category code different from 6011?
Yes: Decline, respnoatms, 6
No: Proceed
Are the first 2 positions of field 22 equal to 90 and is CVV/CVC checking enabled for the BIN?
Yes: Attempt to verify the CVV/CVC.
| Did an error occur during verification?
| Yes: Is respnoverifcvv = 00?
| | Yes: Proceed
| | No: Decline, respnoverifcvv, 9
| No: Is the CVV/CVC correct?
| Yes: Proceed
| No: Decline, respwrongcvv, 10
No: Proceed
| Yes: Is respnvcvvisa = 00?
| | Yes: Proceed
| | No: Decline, respnvcvvvisa, 9
| Yes: Proceed
| No: Decline, respwgcvvvisa, 10
No: Proceed
Perform PIN verification. See p. 44 for details.
Is there a telecode in the message and does it match the card’s telecode in the database?
Yes: Proceed
No: Decline, respwrongtelecode, 11

Is there an address in the message and does it match the card’s address in the database?
Yes: Proceed
No: Decline, respwrongaddress, 12
Perform MCC checking. See p. 40 for details
Is the request an account verification only or telecode verification only?
Yes: Approve, 85, 14
No: Proceed
Is there a banking system host connection and is the card a debit card?
No: Proceed
Is the request a balance inquiry only?
Yes: Is balance inquiry supported
| Yes: Is there an amount available for this card?
| | Yes: Approve, 00,30
| | No: Decline, 57,32?
| No: Proceed
No: Proceed
Can the requested amount be converted to both the card currency and the center currency?
Yes: Proceed
No: Decline, respnoexrate, 15
Perform fraud weight checking. See p. 36 for details.
Is the card status code = 11?
Yes: Approve, respapprove, 16
No: Proceed
Is the requested amount larger than the card’s OTB?
Yes: Is financial checking enabled?
| Yes: Does the card have a VIP bonus?
| | Yes: Is the requested amount larger than the card’s OTB + VIP bonus?
| | | Yes: Is the request from a T&E merchant and does the card have a T&E bonus?
| | | | Yes: Is the requested amount larger than the card’s OTB + VIP bonus + T&E bonus?
| | | | | Yes: Is the card flagged for referrals instead of declines?
| | | | | | Yes: Decline, 01, 17
| | | | | | No: Decline, resplowotb, 17
| | | | | No: Proceed
| | | | No: Is the card flagged for referrals instead of declines?
| | | | Yes: Decline, 01, 17
| | | | No: Decline, resplowotb, 17
| | | No: Proceed
| | No: Is the request from a T&E merchant and does the card have a T&E bonus?
| | Yes: Is the requested amount larger than the card’s OTB + T&E bonus?
| | | Yes: Is the card flagged for referrals instead of declines?
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | No: Is the card flagged for referrals instead of declines?
| | Yes: Decline, 01, 1
| | No: Decline, resplowotb, 17

| No: Proceed
No: Is at least one limiting group enabled?
Yes: Proceed
No: Decline, resplowotb, 80
Perform group OTB checking. See p. 38 for details.
Is the request for cash and are cash limits enabled for the card and is the requested amount larger than the card’s cash
OTB?
Yes: Is the card flagged for referrals instead of declines?
| Yes: Decline, 01, 18
| No: Decline, resplowcashotb, 18
No: Proceed
Perform group cash OTB checking. See p. 38 for details.
Is the request for cash and are cash limits enabled for the card and has the card exceeded its allowed number of cash
transactions for the current period?
| No: Decline, respnocashtxn, 19
No: Proceed
Perform group number of cash transactions checking. See p. 38 for details.
Is the requested amount larger than the maximum single transaction amount for the card?
Yes: Decline, respabove1trxnlimit, 20
No: Proceed
Is the request for a purchase and the requested amount larger than the center purchase ceiling?
Yes: Decline, respabovepurchceil, 21
No: Proceed
Is the request for cash and the requested amount larger than the center cash ceiling?
Yes: Decline, respabovecashceil, 22
No: Proceed
Is the request for T&E and the requested amount larger than the center T&E ceiling?
Yes: Decline, respaboveteceil, 23
No: Proceed
Is the request for mail order and the requested amount larger than the center mail order ceiling?
Yes: Decline, respabovemailceil, 23
No: Approve, respapproval, 07

Authorisation process - Traditional VISA -
Traditional VISA
When the engine determines that the card is a traditional (non-chip) Visa card, it performs
the following checks.
15 Jun
Yes: Proceed
No: Proceed
No: Proceed
Activation check
Yes: Proceed
No: Proceed

No: Proceed
| | Yes: Proceed
| Yes: Proceed
No: Proceed
| Yes: Is respnvcvvisa = 00?
| | Yes: Proceed
| | No: Decline, respnvcvvvisa, 9
| Yes: Proceed
| No: Decline, respwgcvvvisa, 10
No: Proceed
Yes: Proceed
Yes: Proceed
No: Proceed
No: Proceed
| | No: Decline, 57,32?
| No: Proceed
No: Proceed

Yes: Proceed
No: Proceed
| | | | | | Yes: Decline, 01, 17
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| No: Proceed
Yes: Proceed
OTB?
No: Proceed
No: Proceed

No: Proceed
No: Proceed
No: Proceed
No: Proceed

Authorisation process - Traditional MasterCard -
Traditional MasterCard
15 Jun
When the engine determines that the card is a traditional (non-chip) MasterCard card, it
performs the following checks:
Yes: Proceed
No: Proceed
No: Proceed
Activation check
Yes: Proceed
No: Proceed

No: Proceed
| | Yes: Proceed
| Yes: Proceed
No: Proceed
| Yes: Is respnvcvvmast = 00?
| | Yes: Proceed
| | No: Decline, respnvcvvmast, 9
| Yes: Proceed
| No: Decline, respwgcvvmast, 10
No: Proceed
Yes: Proceed
Yes: Proceed
No: Proceed
No: Proceed
| | No: Decline, 57,32?
| No: Proceed
No: Proceed

Yes: Proceed
No: Proceed
| | | | | | Yes: Decline, 01, 17
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| No: Proceed
Yes: Proceed
OTB?
No: Proceed
No: Proceed

No: Proceed
No: Proceed
No: Proceed
No: Proceed

Authorisation process - MasterCard Corporate Fleet Card -
MasterCard Corporate Fleet Card

When the engine receives an authorisation request (message 0100), it performs the
following checks, to determine whether the request should be declined or continued for
further checking*:
Is the card MC Product Type 1 to 3?
No: Skip the next checks and proceed with the remaining verifications
Yes: Does the resource field in the message have a correct length?
No: Decline, respwrongresrc , 260
Yes: Does the card have a valid resource profile?
| | No: Decline, respwrongresrc, 261
| | Yes: Is the resource found in the resource profile?
| | No: Decline via the respwrongresrc, 262
| | Yes: Skip the next checks and proceed with the rest verifications
Is either Driver/ID/Vehicle number found at field 48?
Yes: Proceed with the remaining verifications
No: Decline, respwrongresrc, 263
*(For further details, refer to ‘MasterCard - Corporate Products Payment
Solutions Implementation - Guidelines and Strategies’.)

Authorisation process - Instalments -
Instalments
When the engine receives an instalment authorisation request, it performs the following
checks:
Is the parameter ‘instalments’ under the [engine] section equal to ‘1’?
No: Skip the following checks.
Yes: Is the card linked to a group with account type set to ‘70’?
No: Decline, respnoloan, 51
Yes: Is the loan period within the Maximum Loan Period?
| | No: Decline, respnoloan, 51
| | Yes: Is the instalment amount less or equal to the maximum loan amount?
| | Yes: Is the instalment amount less or equal to the OTB in the group?
| | Yes: Continue with the rest of the checking.

Authorisation process - Traditional Europay -
Traditional Europay
15 Jun
When the engine determines that the card is a traditional (non-chip) Europay card, it
performs the following checks.
Are amounts and currencies numeric
Yes: Proceed
No: Decline, 20,180
Is the STAN unique?
Yes: Proceed
No: Decline, respduplicatestr, 28
Yes: Proceed
Is card status code any of the following: 01, 05, 41, 43.
No: Proceed
Is the card status code 04 or 07?
Yes: Has the card expired?
| Yes: Decline, resppickexpired, 3
| No: Decline, 04, 3
No: Proceed
Is there track 3 information
Yes: Decline, 12, 35
No: Proceed
No: Proceed
Activation check


Yes: Proceed
No: Proceed
No: Proceed
| | Yes: Proceed
| Yes: Proceed
No: Proceed
| Yes: Is respnvcvveuro = 00?
| | Yes: Proceed
| | No: Decline, respnvcvveuro, 9
| Yes: Proceed
| No: Decline, respwgcvveuro, 10
No: Proceed
Is the card number and expiry date correct as per fields 2 and 14?
Yes: Proceed
No: Decline, respreqwrongtrack
No: Proceed


| | No: Decline, 57,32?
| No: Proceed
No: Proceed
No: Proceed
Can the requested amount be converted to both the card currency and the centre currency?
Yes: Proceed
No: Proceed
| | | | | | Yes: Decline, 01, 17
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| No: Proceed
Yes: Proceed
OTB?

No: Proceed
No: Proceed
No: Proceed
No: Proceed
No: Proceed
No: Proceed
No: Is this a Europay card?
Yes: Is card status 08?
| Yes: Approve, 08, 0
| No: Approve, respapproval, 0

Authorisation process - Traditional HOST -
Traditional HOST
15 Jun
When the engine determines that the card is a traditional (non-chip) Host card, it performs
the following checks.
Yes: Proceed
No: Proceed
No: Proceed
Activation check
Yes: Proceed
No: Proceed

No: Proceed
| | Yes: Proceed
| Yes: Proceed
No: Proceed
| Yes: Is respnvcvvhost = 00?
| | Yes: Proceed
| | No: Decline, respnvcvvhost, 9
| Yes: Proceed
| No: Decline, respwgcvvhost, 10
No: Proceed
Yes: Proceed
Yes: Proceed
No: Proceed
No: Proceed
| | No: Decline, 57,32?
| No: Proceed
No: Proceed

Yes: Proceed
No: Proceed
| | | | | | Yes: Decline, 01, 17
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| No: Proceed
Yes: Proceed
OTB?
No: Proceed
No: Proceed

No: Proceed
No: Proceed
No: Proceed
No: Proceed Is the request for mail order and the requested amount larger than the center mail order ceiling?
No:Approve, respapproval, 0

Authorisation process - COPAC cards -
COPAC cards
15 Jun
When the engine determines that the card is a COPAC card, it performs the following
checks:
Is the card in database?
Yes: Proceed
No: Is the preauthorisation cryptogram (ARQC) correct?
Yes: Decline, respnotfound, 2
No: Decline, respwrongarqc, 205
Is the preauthorisation cryptogram (ARQC) correct?
Yes: Proceed
No: Decline, respwrongarqc, 202
Is the card’s preauthorisation message trace the same as the system’s count?
Yes: Proceed
No: Is the card’s preauthorisation trace one less than the system’s count?
Yes: Cancel the previous pre-authorisation and proceed
No: Decline, respwrongtrace, 201
Is the card message cryptogram trace number lower or equal to the system’s count?
Yes: Decline, respwrongtrace, 207
No: Proceed
No: Proceed
No: Proceed
Activation check

Yes: Proceed
No: Proceed
No: Proceed
Perform MCC checking. See p.40 for details
No: Proceed
Can the requested amount be converted to both the card currency and the centre currency?
Yes: Proceed
Perform fraud weight checking. See p.36 for details.
No: Proceed
| | | | Yes: Is the requested amount larger than the card’s OTB + VIP bonus + T&E
| | | | | bonus?
| | | | | | Yes: Decline, 01, 17
| | | | Yes: Decline, 01, 17
| | | No: Proceed
| | | | Yes: Decline, 01, 17
| | | No: Proceed

| No: Proceed
Yes: Proceed
Perform group OTB checking. See p.38 for details.
OTB?
No: Proceed
Perform group cash OTB checking. See p.38 for details.
Is the request for cash and are cash limits enabled for the card and has the card exceeded it’s allowed number of cash
No: Proceed
Perform group number of cash transactions checking. See p.38 for details.

Balance inquiry response - COPAC cards -
Balance inquiry response

15 Jun
The system can respond to a balance inquiry request from an ATM by returning two
amounts, total OTB and cash OTB (only if cash OTB is enabled for that card).
*[engine]balance The system searches the specified card/groups to obtain the lowest balance.* The cash
inqinclude OTB must be enabled for the card/group to be included in this search.
The following center parameter file values affect the balances returned in a balance
inquiry request:
[engine]balance – [engine]balanceinqtotalotb. The default is to return the total OTB in a balance
inqtotalotb inquiry request.
[engine]balance – [engine]balanceinqcashotb. The default is to not return the cash OTB in a balance
inqcashotb inquiry request.
[engine]balance – [engine]balanceinqinclude. This is a string of 11 characters(0 or 1), the first
inqinclude character represents the card and the remaining ten characters represent group0-9
respectively. Each character is set to include/exclude the card/group it relates to in the
search for the lowest OTB to report. For cash OTB the card/group cash OTB must be
enabled to be included in the search. An example:
11100000000 searches the card, group0 and group1 for the lowest OTB to report.

Merchant Profiles - COPAC cards -
Merchant Profiles
A merchant profile is a list of individual merchants collected under a title, such as
“stationary/computer disposables” or “petrol stations”. A card may be associated to only
one merchant profile. Therefore the usage of this card is restricted to the merchants
specified in the merchant profile, for example, the purchase of petrol from a specific petrol
company.
The number of the merchant profiles and the merchants allocated to them is defined
during the licencing of the module.
The following centre parameter relates to the authorisation process:
[engine]respmccbloc – [engine]respmccblock. Response code generated by the engine when the merchant
k category code in the request is not present in any of the profiles to which the card is
associated. This response is always associated with response reason code 13.
The system performs the MCC checking in the authorisation process as follows:
Is Merchant Profile blocking enabled for the card?
Yes: Is the request’s Merchant Number and Acquirer ID in the profile linked to the card?
| Yes: Proceed
| No: Decline, respmccblock, 13
No: Proceed

Currency conversion - Transaction currency -
Currency conversion
15 Jun
The system uses separate currencies for different parts of the authorisation process:
Transaction currency
This is the currency used by the merchant and may be any currency in the world. In a 15 Jun
MasterCard transaction the transaction currency is expressed in US dollars.
Issuer currency
This is the currency that the issuer of a card has declared to the payment systems as its 15 Jun
authorisation currency. It may be any currency. For Visa issuers participating in on-line
currency conversions, Visa/Europay converts from the transaction currency to the issuer
currency before forwarding the message to the issuer.
Center currency
This is the currency in which the authorisation system maintains centre-wide limits. The 15 Jun
center currency is used for reporting, e.g. for reports that serve to control authorisation
limits (see p.63 and p. 52)
Card currency
This is the currency in which a card’s OTB is maintained. 15 Jun
Group currency
This is the currency in which a group’s OTB is maintained. 15 Jun

Fraud weight - Group currency -
Fraud weight
15 Jun
*[fraud weight] Fraud weight is used to highlight a potentially fraudulent transaction based on a
rangeNweight combination of fraud weights assigned to various elements present in the transaction. The
fraud weight of the transaction is calculated as follows:
country code fraud weight + mcc fraud weight + fraud weight of transaction amount*
unless you have defined a transaction fraud weight in the onlini.ini file of your system,
when it calculated as follows:
country code fraud weight + mcc fraud weight + fraud weight of transaction amount +
transaction fraud weight
*[fraud weight] If the country code record is not found in the database, the default value defined in the
defaultcountryweight center parameter file is used.*
*[fraud weight] If the MCC record is not found in the database, the default value defined in the center
defaultmccweight parameter file is used.*
*[fraud weight] The fraud weight of transaction amount* is used to assign a fraud weight to a transaction
rangeNweight amount range. This allows you to give higher transaction amounts a higher fraud weight.
*[fraud weight] The fraud weight is used to assign a fraud weight to a specific transaction type in a specific
ptttmmmsss=NN transaction mode for a specific payment system. The system allows you up to thirty such
combinations.
*[engine]fraud- The accumulated fraud weight is compared to the centre fraud ceiling* and card fraud
weightceiling ceiling. If during the interface file load a card record does not contain a fraud ceiling value
†[fraud weight] a default value is loaded.†
defaultcardvalue
*[engine]respabove- If the accumulated fraud weight exceeds the centre ceiling response reason code 170 is
frdceil logged.*
†[engine]respabove- If the accumulated fraud weight exceeds the card ceiling response reason code 171 is
cardfrd logged.*
The system performs the fraud weight checking in the authorisation process as follows:
Is card fraud weight enabled or
Is centre fraud weight enabled?
Yes: Is MCC fraud weight found in MCC record?
| Yes: Use MCC fraud weight to begin fraud weight accumulation.
| No: Use CPF [fraud weight]defaultmccweight to begin fraud weight accumulation.
| Is country fraud weight found in country record?
| Yes: Add country fraud weight to fraud weight accumulation.
| No: Add CPF [fraud weight]defaultcountryweight to fraud weight accumulation.
| Is a matching range weight (CPF [fraud weight]rangeNweight) found?
| Yes: Add CPF [fraud weight]rangeNweight to fraud weight accumulation.
| No: Proceed.
| Is ptttmmmss (transaction fraud weight) found for this transaction?
| Yes: Add CPF[fraud weight]ptttmmmsss to fraud weight accumulation.

Fraud weight - Group currency -
| No: Proceed
| Is center ceiling enabled?
| Yes: Is the fraud weight above the center ceiling?
| | Yes: Decline, respabovefrdceil, 170
| | No: Proceed
| No: Proceed
| Is card ceiling enabled?
| Yes: Is the fraud weight above the card ceiling?
| | Yes: Decline, respabovefrdceil, 170
| | No: Proceed
No: Fraud weight not being utilized, proceed

Groups - Group OTB checking -
Groups
If a card is not related to any group, only its own limits are considered when a request is
received for the card. If a card is related to one or more groups, the system looks at the
card’s limits, as well as the limits of all the groups to which it is related. If any of the
group’s limits warrants a decline, the request is declined. If the request is approved, the
limits of the card, as well as the limits of all the groups to which it is related, are updated in
the same way.
The system performs the following checks in the authorisation process.
Group OTB checking

For all the groups to which the card is related:
Is the requested amount larger than the group’s OTB?
Yes: Is the request from a T&E merchant and does the group have a T&E bonus?
| Yes: Is the requested amount larger than the group’s OTB + T&E bonus?
| | Yes: Is the card flagged for referrals instead of declines?
| | | Yes: Decline, 01, 50...59 (depending on the group)
| | | No: Decline, resplowotb, 50...59 (depending on the group)
| | No: Proceed
| No: Is the card flagged for referrals instead of declines?
| Yes: Decline, 01, 50...59 (depending on the group)
| No: Decline, resplowotb, 50...59 (depending on the group)
No: Proceed
Group cash OTB checking

Is the request for cash and are cash limits enabled for the group and is the requested amount
larger than the group’s cash OTB?
| No: Decline, resplowcashotb, 60...69 (depending on the group)
No: Proceed
Group number of cash transactions checking

Is the request for cash and are cash limits enabled for the group and has the group exceeded its
allowed number of cash transactions for the current period?

Groups - Group number of cash transactions checking -
| No: Decline, respnocashtxn, 70...79 (depending on the group)

No: Proceed

MCC Profiles - Group number of cash transactions checking -
MCC Profiles
15 Jun
All merchants are assigned a merchant category code (MCC). An MCC profile is a list of
individual MCC’s collected together under a title, such as “airlines” or “restaurants”.
A card can be associated with up to 60 MCC profiles. If a card is associated with one or
more MCC profiles, the system will only authorise transactions originating from
merchants included in those MCC profiles.
The following center file parameters relate to the authorisation process:
[engine]mcc- – [engine]mccnotpresent. Determines the behaviour of the engine if a card has MCC
notpresent checking enabled and the request message does not contain an MCC. The default is to
decline the request with response code [engine]respmccblock.
[engine]respmcc- – [engine]respmccblock. Response code generated by the engine when the merchant
block category code in the request is not present in any of the profiles to which the card is
associated. This response is always associated with response reason code 13.
The system performs the MCC checking in the authorisation process as follows:
Is MCC blocking enabled for the card?
Yes: Is the request’s MCC in any of the profiles linked to the cards?
| Yes: Proceed
| No: Decline, respmccblock, 13
No: Proceed

MCC Product Velocity Checks - Authorisation logic for a Velocity Check -
MCC Product Velocity Checks

15 Jun
The MCC Product Velocity Check is a feature that lets you restrict card spending per
product and Merchant Category Code, (MCC). You do this by setting limits (velocity
limits) on the number of transactions and declines and on the total authorised or declined
amounts, that a card is allowed for a specific MCC and product combination, within a
specific period of time. This period is also referred to as the velocity period.
See the section about MCC Product Velocity in the Parameters Reference Guide manual,
for more information about setting limits for MCC product velocity checks.
ONLINE checks MCC product velocity limits for the length of the velocity period. The
velocity period can be defined in hours or days. For example, if you want to check the
limits for the entire day, you can set the velocity type to ‘H’ (hours) and the velocity period
to ‘24’; or, you can set the velocity type to ‘D’ (days) and the velocity period to ‘1’.
The authorisation logic for the MCC Product Velocity Check is described in the following
section.
Authorisation logic for a Velocity Check

When ONLINE receives an authorisation request, it checks the online[engine]
mccvelocitylimit parameter. If the parameter is set to ‘1’, ONLINE calls a function to
verify the MCC velocity limits.
Note that for every one-hour block, ONLINE creates a new record of the sum of amounts
and counts in the ‘CARDMCCSTATS’ table, when the first authorisation request is
honoured in that hour. Thereafter, ONLINE updates this record for each new request
arriving within the same hour.
The authorisation logic for a velocity check is shown below.

MCC Product Velocity Checks - Authorisation logic for a Velocity Check - MCC Product Velocity authorisation process
MCC Product Velocity authorisation process
NOTE: The issuer reason codes referred to in the authorisation logic

are defined in the Issuer Reason Codes parameter. (See the related
section in the ONLINE Parameter Reference Guide for details.
Is the parameter [engine]mccvelocitylimit equal to ‘1’?

No: Exit this check.
Yes: Proceed. Use field 018 from the authorisation message as the MCC.
Is the authorisation amount in the centre currency between the maximum and minimum single transaction
amounts?
No: Decline with a response code that maps to the issuer reason code 20 and exit this check.
Yes: Proceed.
Check all transactions in the current and previous velocity period.
Is the sum of all amounts and counts in the authorised or declined transactions less or equal to the
corresponding limits taken from the ‘MCCPRODUCTVEL’ table?
No: Decline with a valid response code that maps to the issuer reason codes between 981 and 994
inclusive, and exit this check.
Yes: Proceed.
Is there a record in the ‘cardmccstats’ table that refers to the current hour?
Yes: Update the record with the new sum amount and sum count fields.
No: Insert a new record with the sum amount and sum count fields.
Continue with the next authorisation check.

PIN verification during authorisation - PIN previous block checking - MCC
PIN verification during authorisation

15 Jun
When the PIN retries have been exceeded for a card the system places a “block” on the
card. The “block” prevents any further authorisation approvals. The system will prompt
you in the card status update screen to change the status of a “blocked” card.
A new message allows ONLINE to take into account PIN changes. This message is part of
the authorisation update from a back-office system to ONLINE.
The following center parameter file values affect PIN processing:
[engine]pinretries – [engine]pinretries. Number of incorrect PIN retries after which the card number is
blocked. The default is 0 (disabled). This response is always associated with response
reason code 25.
[engine]resp – [engine]respwrongpin. Response code generated by the engine when the PIN
wrongpin contained in the request message is not correct (wrong PIN). This response is always
associated with response reason code 8.
[engine]respno – [engine]respnoverifpin. Response code generated by the engine when it encounters
verifpin an error while verifying the PIN contained in a request message. This response is
always associated with response reason code 7.
[engine]respno – [engine]respnoverifpineuro. Response code generated by the engine when it
verifpineuro encounters an error while verifying the PIN contained in a Europay request message.
This response is always associated with response reason code 7.
[engine]respexc – [engine]respexcpinretryat. Response code generated by the engine when PIN retries
pinretryat [engine]pinretries (response reason code 25) has already been received for this card
and it is now being used at an attended terminal. This response is always associated
with response reason codes 26.
[engine]respexc – [engine]respexcpinretryut. Response code generated by the engine when PIN retries
pinretryut [engine]pinretries (response reason code 25) has already been received for this card
and it is now being used at an unattended terminal. This response is always associated
with response reason codes 27.
The system performs the following checks in the authorisation process.
PIN previous block checking

An ATM will normally keep a card if the PIN retries are exceeded. This check covers the
possibility that the card was returned to the cardholder in error.
Have PIN retries previously been exceeded?
Yes: Is this an attended terminal?
| Yes: Decline, respexcpinretryat, 26
| No: Decline, respexcpinretryut, 27
No: Proceed
REFERENCE GUIDE (P1665-001)
PIN verification during authorisation - PIN verification - VISA, MasterCard and Host - MCC Product Velocity authorisation process
PIN verification - VISA, MasterCard and Host

Is there a PIN in the message?
Yes: Attempt to verify it.
| Yes: Decline, respnoverifpin, 7
| No: Is the PIN correct?
| Yes: Proceed
| No: Have PIN retries been exceeded in this session?
| Yes: Decline, respexcpinretryut, 25
| No: Decline, respwrongpin, 8
No: Proceed
PIN verification - Europay

Is there a PIN in the message?
Yes: Is the PIN prevalidated?
| Yes: Get results for PIN Block
| No: Attempt to verify the PIN
| Yes: Decline, respnoverifeuro, 7
| No: Is the PIN correct?
| Yes: Proceed
| No: Have PIN retries been exceeded in this session?
| Yes: Decline, respexcpineuroat, 25
| No: Decline, respwrongpin, 8
No: Proceed

REFERENCE GUIDE (P1665-001) 44 © Card Tech Limited 2003-2006. All rights reserved
Reconciliation processing
Interface file transaction matching - -
Reconciliation processing 15 Jun
The system must reconcile transactions against authorisations in order to restore OTB
balances, unless automatic replenishment is enabled.
Interface file transaction matching

15 Jun
Reconciliation takes place for transactions with transaction code equal to 05 or 07 and
DB/CR flag equal to “D” (for Debit). The following fields are used:
– Card Number
*[reconciliation]trxnr – Billing amount (+/- percentage set in center parameter file.)*
econcilpercent
*[reconciliation]matc – Billing currency / transaction currency

hbyauthcur (Billing or transaction, according to the [reconciliation]matchbyauthcur parameter).
*[reconciliation] use – MCC if present and if the system is set to use MCC.*
merchantcategory
– Authorisation code if present
– Merchant ID if present in both transaction and authorisation
Authorisation code and Merchant ID are optional. If they exist in the interface file the
system will use them for matching otherwise it will use the first four fields. If any one of
the above fields does not match, the authorisation will not be dropped.

Reconciliation processing
Matching on MCCs - -
Matching on MCCs
15 Jun
[reconciliation]use Matching on Merchant Category Codes (MCCs) is controlled by a center file parameter*
merchantcategory because many POS terminals cannot send the proper MCC in the authorisation message.
Therefore the authorisation message from different acquirers may contain a default MCC
and the transaction contains the real MCC.
The following center file parameter relates to MCC reconciliation.
[reconciliation]use – [reconciliation]usemerchantcategory. Determines if the system uses MCC when
merchantcategory matching outstanding authorisations and transactions. The default is to never use MCC
in matching.

Daily Reports
- -
Daily Reports
Technical note The system produces all reports in an 80-column format for printing on standard 8½ by 11
inch paper at six lines per inch and 66 lines per page. The reports are formatted without
form feed characters.
Reports may also be viewed on the screen.
Production The parameter values referenced in this section are found in the reports parameter file,
reports.ini. For information on generating and printing these reports, see the description
of the Batch menu, in particular the Report options screen.
Category Each report description includes a category name indicating the business function it
serves.
Sample reports Page numbers are printed at the bottom of each report page: they are not shown in the
following samples in order to save space.
All parameter values referenced in this section are found in the

reports parameter file, reports.ini.

Daily Reports
- Acquirer Log -
Acquirer Log
15 Jun
Overview This report lists all authorisation activity for an acquirer centre since the last End-of-Day
reporting point, together with the responses received.
Category Control report
Sorted by Acquirer ID

Daily Reports
- Acquirer Log (MDS) -
Acquirer Log (MDS)

Overview This report lists all MasterCard Debit Switch activity for an acquirer centre since the last
End-of-Day reporting point, together with the responses received.

Daily Reports
- Acquirer Log (SMS) -
Acquirer Log (SMS)

Overview This report lists all SingleConnect message activity for an acquirer centre since the last
End-of-Day reporting point, together with the responses received.

Daily Reports
- All pending chargebacks -
All pending chargebacks

Overview This report lists all pending chargebacks (SingleConnect) since the last End-of-Day
reporting point. The acquirer needs to review the chargebacks to decide whether to accept
or dispute them.
Category Operational
Sorted by Card Number

Daily Reports
- Authorisations Exceeding the Center Limit -
Authorisations Exceeding the Center Limit

15 Jun
Overview This report lists all authorisations whose value exceeds the limit in centre currency, fixed
*[authorizations] in the system’s parameters*, since the last EOD reporting point. Using a card for such high
centerlimit transaction amounts may be an indication of fraud, and this report highlights potential
cases for further investigation.
The limit has no connection with any authorisation limits placed on individual cards. The
default limit is 5000.
Category Fraud detection

Daily Reports
- Authorisations Exceeding High Count -
Authorisations Exceeding High Count

15 Jun
Overview This report lists all authorisations of cards whose total number of authorisations since the
*[authorizations] last EOD reporting point exceed the high authorisation count in the system’s parameters*.
highauthcount Intensive use of a card may be an indication of fraud, and this report highlights potential
cases for further investigation.
The high authorisation count limit has no connection with any authorisation limits placed
on individual cards. The default limit is 3 but may be changed to reflect the requirements
of your centre.

Daily Reports
- Card Bonus Change -
Card Bonus Change

15 Jun
Overview This report lists all card bonus changes since the last End-of-Day reporting point. Card
bonus changes may be an indication of fraud, and this report highlights potential cases for
further investigation. The report lists all bonus changes, including those with and without
security codes. It includes both total bonus changes and cash bonus changes.
Bonuses may be added via the Card or Card Cash Bonus screens on ONLINE or may be
introduced to the system via an external file, e.g. the Prime Interface file.
To help trace changes, the report includes the name of the user who introduced the bonus
change to the system.
Category Internal fraud

Daily Reports
- Card Bonuses Approved -
Card Bonuses Approved

Overview This report lists all card bonuses for which a security code was created since the last
End-of-Day reporting point. The report shows the name of the user who generated the
security authorisation code and lists the card number, the date and time of approval and
the security code.
*[bonus screen] Bonuses require a security code if they exceed the maximum security card bonus amount*
seccardtotamt optionally defined in the parameters of your system.

Daily Reports
- Card Bonuses Used -
Card Bonuses Used

Overview This report lists all card bonus security codes used by system operators to add bonuses
since the last End-of-Day reporting point. It is possible that not all security codes created
are used. The report shows the name of the user who generated the security authorisation
code and the name of the operator who used it to create the bonus. The report lists the card
number, the date and time the bonus was approved through the creation of a security code,
the date and time the code was used to add the bonus and the security code.

Daily Reports
- Card Cash Bonuses Approved -
Card Cash Bonuses Approved

Overview This report lists all card cash bonuses for which a security code was created since the last
security authorisation code for the cash bonus and lists the card number, the date and time
of approval and the security code.
*[bonus screen] Cash bonuses require a security code if they exceed the maximum security card cash
seccardcashamt bonus amount *optionally defined in the parameters of your system.

Daily Reports
- Card Cash Bonuses Used -
Card Cash Bonuses Used

Overview This report lists all card cash bonus security codes used by system operators to add
bonuses since the last End-of-Day reporting point. It is possible that not all security codes
created are used. The report shows the name of the user who generated the security
authorisation code and the name of the operator who used it to create a cash bonus. The
report lists the card number, the date and time the cash bonus was approved through the
creation of a security code, the date and time the code was used to add the bonus and the
security code.

Daily Reports
- Card Listing -
Card Listing
15 Jun
Overview This report lists the current financial status of all cards in the local authorisation database.
The report is printed for monitoring purposes.
NOTE: The brackets [ ] around line 4 in the report header, indicate

the bonus information is printed only if it is not zero. This is done to
reduce report size.

Daily Reports
- Card Listing (Short) -
Card Listing (Short)

15 Jun
Overview This report lists the current OTB, cash OTB and number of cash transactions for all cards
in the local authorisation database.
In a typical system situation, this report is suppressed.

Daily Reports
- Cards Near Credit Limit -
Cards Near Credit Limit

15 Jun
Overview This report lists all cards whose expenditure is near or beyond their credit limit.* The
*[cards]nearpercent report is based on OTB balances, not card balances. This advance warning of cardholders
who are about to exceed their credit limit enables you to take early action. You may wish
to send a reminder to the cardholder, or increase the cardholder’s credit limit.
If this report includes an exceptionally large number of cards near the credit limit, you
should look at in conjunction with the Outstanding Authorisations (see p. 84) and
Reconciliations (see p. 85) reports to detect possible failures in the matching process (see
p. 45).
The default percentage threshold for the report is 10%, indicating that the OTB of a card is
10% or less of the card’s total credit limit. You can change this parameter to suit the
requirements of your system.
Category Risk control/Customer services

reduce report size.

Daily Reports
- Cards with High Authorisation Amount -
Cards with High Authorisation Amount

15 Jun
Overview This report lists all cards whose total authorisation requests since the last EOD reporting
*reports.ini point (whether approved or declined) exceed the amount* defined in the system’s report
[card]highauthamount parameter file (reports.ini). Intensive use of a card may be an indication of fraud, and this
report highlights potential cases for further investigation.
default limit is 1000, denominated in the card’s billing currency. You can change this
parameter to suit the requirements of your system.

reduce report size.

Daily Reports
- Cards with High Authorisation Amount in Center Currency -
Cards with High Authorisation Amount in

Center Currency
15 Jun
Overview This report lists all cards whose total authorisation requests since the last EOD reporting
*reports.ini point (whether approved or declined) exceed the amount*, in centre currency, defined in
[cards]highcentamount the system’s report parameter file (report.ini). Intensive use of a card may be an indication
of fraud and this report highlights potential cases for further investigation.
default limit is 1000, denominated in the card’s center currency. You can change this
parameter to suit the requirements of your system.

reduce report size.

Daily Reports
- Cards with High Number of Authorisations for EOD -
Cards with High Number of Authorisations for

EOD
15 Jun
Overview This report lists all cards whose requests since the last EOD reporting point (whether
*[card]highauthcount approved or declined) exceed a certain count.* Intensive use of a card may be an
indication of fraud, and this report highlights potential cases for further investigation.
default limit is 3. You can change this parameter to suit the requirements of your system.

reduce report size.

Daily Reports
- Chargeback reversals -
Chargeback reversals
Overview This report lists all Visa SingleConnect chargeback reversals received by the acquirer
since the last End-of-Day reporting point.

Daily Reports
- Dropped Authorisations -
Dropped Authorisations
15 Jun
Overview This report lists all of the authorisations manually or automatically cancelled since the last
End-of-Day reporting point.

Daily Reports
- Exception Management -
Exception Management
15 Jun
Overview This report lists all cards sent to the exception file of the payment system for processing.
For more information on which card status changes the system will update the exception
file at the relevant payment system. The report includes status changes made by ONLINE
operators and changes triggered by the loading of a card from the card interface file.

Daily Reports
- Exception Management Delete Failures -
Exception Management Delete Failures

Overview This report lists all cards whose exception status code the system was unable to delete.

Daily Reports
- Exception Management Update Failures -
Exception Management Update Failures

Overview This report lists all cards whose status code the system was unable to update. Update
failures may be the result of trying to update cards outside the range registered with VISA.

Daily Reports
- Fee Collection & Funds disbursement -
Fee Collection & Funds disbursement

Overview This report lists all fees collected and all funds disbursed by the acquiring centre from
issuing centres since the last End-of-Day reporting point. The fee transactions, which only
apply to Visa PLUS transactions, take place online through the Visa SingleConnect
system.
Category Control report/Operational
Sorted by Card Name

Daily Reports
- Group Bonus Change -
Group Bonus Change

15 Jun
Overview This report lists all group bonus changes since the last End-of-Day reporting point. Group
bonus changes may be an indication of fraud, and this report highlights potential cases for
further investigation. The report lists all group bonus changes, including those with and
without security codes. It includes both total group bonus changes and group cash bonus
changes.
Bonuses may be added via the Group total OTB or Group Cash Bonus Screen on ONLINE
or may be introduced to the system via an external file, e.g. the Prime Interface file.
To help trace changes, the report includes the name of the user who made the group bonus
change.
Sorted by Group Name

Daily Reports
- Group Bonuses Approved -
Group Bonuses Approved

Overview This report lists all group bonuses for which a security code was created since the last
security code and lists the group name, the date and time of approval and the security code.
*[bonus screen] Group bonuses require a security code if they exceed the maximum security group bonus
secgrptotamt amount *optionally defined in the parameters of your system.

Daily Reports
- Group Bonuses Used -
Group Bonuses Used

Overview This report lists all group cash bonus security codes used by system operators to add group
bonuses since the last End-of-Day reporting point. It is possible that not all security codes
created are used. The report shows the name of the user who generated the security
authorisation code for the group bonus and the name of the operator who used it to create
the bonus. The report lists the group name, the date and time the bonus was approved
through the creation of a security code, the date and time the code was used to add the
bonus and the security code.

Daily Reports
- Group Cash Bonuses Approved -
Group Cash Bonuses Approved

Overview This report lists all group cash bonuses for which a security code was created since the last
security authorisation code for the group cash bonus and lists the group name, the date and
time of approval and the security code.
*[bonus screen] Group cash bonuses require a security code if they exceed the maximum security group
secgrpcashamt cash bonus amount * optionally defined in the parameters of your system.

Daily Reports
- Group Cash Bonuses Used -
Group Cash Bonuses Used

Overview This report lists all group cash bonus security codes used by system operators to add group
cash bonuses since the last End-of-Day reporting point. It is possible that not all security
codes created are used. The report shows the name of the user who generated the security
authorisation code for the group cash bonus and the name of the operator who used it to
create the bonus. The report lists the group name, the date and time the cash bonus was
approved through the creation of a security code, the date and time the code was used to
add the cash bonus and the security code.

Daily Reports
- Group Listing -
Group Listing
15 Jun
Overview This report lists the current financial status of all groups in the local authorisation
database. The report is printed for monitoring purposes.

reduce report size.

Daily Reports
- Group Listing (Short) -
Group Listing (Short)

15 Jun
Overview This report lists the current OTB, cash OTB and number of cash transactions of all groups
in the local authorisation database.
In a typical system situation, this report is suppressed.

Daily Reports
- Issuer Log -
Issuer Log
15 Jun
Overview This report lists all authorisation activity carried out by an issuer center since the last
End-of-Day reporting point (i.e. 0110, 0120 and 0410 messages).

Daily Reports
- Issuer Log (Declines) -
Issuer Log (Declines)

15 Jun
Overview This report lists all requests that were declined (i.e. 0110 and 0120 messages) since the last
End-of-Day reporting point because of an unfavourable exception code or insufficient
funds.

Daily Reports
- Manual Advices Approved -
Manual Advices Approved

Overview This report lists all manual advices for which a security code was created since the last
security authorisation code and lists the card number, the date and time of approval, the
approved sum and the security code. Creating security codes for manual authorisations
only applies to on-us cards.
*[manual advice Manual advices require a security code if they exceed the maximum security manual
screen] advice amount * optionally defined in the parameters of your system.
secadvamt


Daily Reports
- Manual Advices Used -
Manual Advices Used

Overview This report lists all manual advice security codes used by system operators since the last
End-of-Day reporting point. It is possible that not all security codes created are used. The
report shows the name of the user who generated the security authorisation code for the
manual advice and the name of the operator who used it. The report lists the card number,
the date and time the manual advice was approved through the creation of a security code,
the date and time the code was used to advise the system of the authorisation and the
security code.
Manual authorisations only apply to on-us cards.

Daily Reports
- Manual Card Status Change -
Manual Card Status Change

Overview This report lists all cards whose status has been changed manually since the last
End-of-Day reporting point.

Daily Reports
- New Chargebacks received -
New Chargebacks received

Overview This report lists all new chargebacks received by the acquirer system through Visa
SingleConnect since the last End-of-Day reporting point.

Daily Reports
- Outstanding Authorisations -
Outstanding Authorisations
15 Jun
Overview This report lists all authorisations (including advices) that have not yet been matched. You
may use this report to try to match outstanding authorisations against any transactions that
appear to be unauthorised.
Category Control report/Customer services

Daily Reports
- Reconciliations -
Reconciliations
Overview This report lists all SingleConnect reconciliations received from the payment system
since the last EOD reporting point. You may use this report to check the reconciliation
information sent from the payment systems against the corresponding data kept by the
ONLINE system.

Daily Reports
- Representments -
Representments
Overview This report lists all SingleConnect transaction representments made by the acquirer
following the rejection of an issuer chargeback since the last EOD reporting point.
Category Control report/Operational

Daily Reports
- STIP Authorisations -
STIP Authorisations
15 Jun
Overview This report is based on the advice messages provided by the payment systems. This
includes all authorisations provided by the Stand-In processors since the last End-of-Day
reporting point, including declines. Authorisations may be provided by the Stand-In
Processors for the following reasons:
1 your centre is in suppress enquiry mode
2 your centre is signed off
Too may STIP authorisations may be indication of a bad VisaNet connection.
Category Risk control

Daily Reports
- Transactions -
Transactions
15 Jun
Overview This report lists all card transactions loaded from the card management system since the
last End-of-Day reporting point. The report is run to verify the loading file.

Daily Reports
- Unauthorised Transactions -
Unauthorised Transactions
15 Jun
Overview This report lists all of the transactions loaded from the card management system since the
last End-of-Day reporting point which did not match an outstanding authorisation.
Examples of transactions included in the report are: transactions created by an offline
POS machine, transactions below the floor limit and transactions that have not been
matched with an authorisation request.

Daily Reports
- Unauthorised Transactions -

Appendix
ISO 8583 messages - -
Appendix
ISO 8583 messages
ONLINE sends and receives the following internationally standard messages.
Code Description VISA BASE I/II VISA SMS MasterCard EuroPay
0100 Authorisation request Yes Yes Yes Yes
0101 Repeat authorisation request Yes Yes No No
0102 ATM confirmation Yes - no response. No No No
Received as an is-
suer. Sends only if
ATM module is
present.
0110 Authorisation response Yes Yes Yes Yes
0120 Authorisation advice Yes - no response. Yes Yes Yes
0130 Authorisation advice response No Yes Yes Yes
0200 Financial Transaction Request No Yes No No
0210 Financial Transaction Response No Yes No No
0220 Financial Transaction Advice No Yes No No
0230 Financial Transaction Advice No Yes No No
Response
0302 Issuer file update Yes Yes Yes No
0312 Issuer file update response Yes Yes Yes No
0400 Reversal request Yes Yes No No
0401 Repeat reversal request Yes No No No
0410 Reversal request response Yes Yes No No
0420 Reversal advice No Yes Yes - Supports
On-Us acquir-
ing.
0422 Chargeback reversals No Yes No No
0430 Reversal advice response No Yes Yes Yes
0432 Chargeback reversal response No Yes No No
0500 Advices of reconciliation totals No Yes No No
0510 Response to confirm receipt of No Yes No No
reconciliation totals
0520 Automatic advices of reconcili- No Yes No No
ation totals sent by VISA
0530 Confirmation of receipt of rec- No No No No
onciliation totals

Appendix
ISO 8583 messages - -
Code Description VISA BASE I/II VISA SMS MasterCard EuroPay

0600 Administrative messages Yes Yes No No
0610 Response to administrative No Yes No No
messages
0630 Administrative advice response No Yes No No
0800 Network management request Yes Yes Yes Yes
0810 Network management response Yes Yes Yes Yes
9620 Fraud notification No Yes No No
9630 Fraud notification response No Yes No No

Appendix
ISO Response codes - -
ISO Response codes

ONLINE supports the following ISO response codes:
Code Description
00 Approved
01 Refer to issuer
02 Refer to issuer (special)
03 Invalid merchant
04 Pick up card
05 Do not honor
06 Error
07 Pick up card (special)
08 Honour with identification/approve
11 VIP Approval
12 Invalid transaction
13 Invalid amount
14 Card number does not exist
15 No such issuer
19 Re-enter transaction
21 No action taken (no match)
25 Unable to locate record
28 File temporarily unavailable
41 Pick up card (lost card)
43 Pick up card (stolen card)
51 Not sufficient funds
52 No checking account
53 No savings account
54 Expired card
55 Incorrect PIN
57 Trxn not permitted to card
58 Trxn not permitted to card
61 Exceeds withdrawal limit
62 Restricted card
63 Security violation
65 Activity count exceeded
75 Too many wrong PIN tries
76 Previous message not found
77 Data does not match original

Appendix
ISO Response codes - -
Code Description
78 No cash transactions left in period in group 8
80 Invalid date
81 Cryptographic error in PIN
82 Incorrect CVV
83 Unable to verify PIN
85 No reason to decline
91 Issuer or switch inoperative
92 No routing path
93 Violation of law
94 Duplicate transmission
96 System malfunction
XA Forward to issuer
XD Forward to issuer

Appendix
Issuer Response Reason Codes - -
Issuer Response Reason Codes

The system uses Issuer Response Reason codes to further define ISO messages.
Code Message Sys. Brief / Full Description Parameter
1 All All Invalid Message Type: respwrongisoformat
Invalid message type or message type not allowed
2 0100/ All Card not in database: respnotfound
0200 Card not in database
3 0100/ E Card Status: respickexpired
0200 Declined because the card status code is set to 04 or 07 (if card Expired) 04
3 0100/ All Card Status: Depends on the card sta-
0200 Declined because the card status is set for the card to be tus code
declined
4 0100/ All Card Expired: resppickexpired
0200 Card has expired
5 0100/ All Local Use Only: resplocalonly
0200 Card is local and merchant is not located in cardholder’s
country
6 0100/ All No ATM Auth Allowed: respnoatms
0200 Card is not allowed in ATMs and request originated from
an ATM
7 0100/ All Format Error: respnoverifpineuro (ap-
0200 Unable to verify PIN (format error in data) plicable to Europay only)
respnoverifpin
8 0100/ All Wrong PIN: respwrongpin
0200 Wrong PIN
9 0100/ All Format Error: respnoverifcvv
0200 Unable to verify CVV (format error in data)
10 0100/ All Wrong CVV: respwrongcvv
0200 Wrong CVV
11 0100/ O,V Wrong Telecode: respwrongtelecode
0200 Wrong Telecode
12 0100/ All Wrong Address: respwrongaddress
0200 Wrong Address
13 0100/ All No MCC Associated: respmccblock
0200 MCC not associated with any of the card MCC profiles
14 0100/ O,M, Approved Account Verification or Moto: No parameter
0200 V Approved non-financial request (account verification only
or telecode verification only)

Appendix

15 0100/ O,M, No Exchange Rate: respnoexrate
0200 V No exchange rate from transaction/billing to card and cen-
tre currencies
16 0100/ All Card Status Code is 11: respapprove
0200 Approved because card status code is 11
17 0100/ All Not Enough Total OTB: resplowotb
0200 Not enough total OTB
18 0100/ All Not Enough Cash OTB: resplowcash
0200 Not enough cash OTB
19 0100/ All No Cash Auths Left For Period: respnocashtxn
0200 No cash transactions left for period
20 0100/ All Amount Larger than Single Transaction Limit For respabove1trxnlimit
0200 Card:
Requested amount larger than single transaction limit for
card
21 0100/ All Purchase Amount Larger Than Centre Ceiling: respabovepurchceil
0200 Purchase requested amount larger than centre purchase
ceiling
22 0100/ All Cash Amount Larger Than Centre Ceiling: respabovecashceil
0200 Cash requested amount larger than centre cash ceiling
23 0100/ All T&E Amount Larger Than Centre Ceiling: respaboveteceil
0200 T&E requested amount larger than centre T&E ceiling
24 0100/ All Mail Order Amount Larger than Centre Ceiling: respabovemailceil
0200 Mail Order requested amount larger than centre mail order
ceiling
25 0100/ All PIN Retry Exceeded: respexcpineurout
0200 PIN retry exceeded. Pickup card (applicable to Europay
only)
respexcpinretryut
26 0100/ All PIN Retry Exceeded: respexcpineuroat
0200 PIN retry exceeded - Attended terminal card pickup (applicable to EuroPay
only)
respexcpinretryat
27 0100/ All PIN Retry Exceeded: respexcpineurout
0200 PIN retry exceeded - Unattended terminal card pickup (applicable to Europay
only)
respexcpinretryut
28 0200 V Card Transfer Amount Is Larger Than The Centre respabovetrnfceil
Ceiling:
COPAC: Card transfer amount is larger than the centre
transfer ceiling

Appendix

29 0100 All Wrong Track Data: resprewrongtrack
0200/ Wrong track data in the message
30 0100/ All Approval of balance inquiry: No parameter
0200 Approval of balance inquiry and balance sent
31 0100/ All Balance Inquiry Not Enabled: No parameter
0200 Balance inquiry not enabled by the system
32 0100/ All Balance Inquiry Not Supported: No parameter
0200 Balance inquiry enabled by the system, but not supported
for this cardholder
33 0100/ E Duplicate Message: respduplicatestr
0120/ A duplication combination of Trace Number + Acquirer Id
0420 + Forwarder Id within a specified period of time received
35 0100 E Track 3 Present: No parameter
Europay - Track 3 present (length not zero). Invalid
transaction
36 0100 E Wrong Format In Field 52: No parameter
EuroPay - prevalidated PIN , wrong format in field 52
37 0100/ All Manual Entry For Electron Card: respnoauth
0200 A non - swipe Electron card is used for a swipe transaction
38 0100/0200 All PIN Change, Sucess: No parameter
PIN change, success
39 0100/0200 All PIN Change, Failed: No parameter
PIN change, failed
40 0100/ V Unable To Verify CVV: respnvcvvvisa
0200 VISA - Unable to verify CVV when field 22 = 02
41 0100/ V Wrong CVV: respwgcvvvisa
0200 VISA - Wrong CVV when field 22 = 02
42 0100 M Unable To Verify CVV: respnvcvvmast
MasterCard : Unable to verify CVV when field 22 = 02
43 0100 M Wrong CVV: respwgcvvmast
MasterCard : Wrong CVV when field 22 = 02
44 0100 O Unable To Verify CVV: respnvcvvhost
Host : when field 22 = 02
45 0100 O Wrong CVV: respwgcvvhost
Host : Wrong CVV when field 22 = 02
46 0100 E Unable To Verify: respnvcvveuro
Europay : Unable to verify CVV when field 22 = 02
47 0100 E Wrong CVV: respwgcvveuro
Europay : Wrong CVV when field 22 = 02

Appendix

48 0100/ All Wrong CVV2: respwrongcvv2
0200 Wrong CVV2
49 0100/ O,V Wrong CVV2: respwrongcvv2
0200 Wrong CVV2
50 0100/ All Not Enough Total OTB In Group 0: resplowotb
0200 Not enough total OTB in group 0
60 0100/ All Not Enough Cash OTB In Group 0: resplowcasheuro
0200 Not enough cash OTB in group 0 (applicable to Europay
only)
resplowcash
only)
resplowcash
only)
resplowcash
only)
resplowcash

Appendix

only)
resplowcash
only)
resplowcash
only)
resplowcash
only)
resplowcash
only)
resplowcash
only)
resplowcash
70 0100/ All No Cash Transactions Left In Period In Group 0: respnocashtxneuro
0200 No cash transactions left in period in group 0 (applicable to Europay
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn

Appendix

0200 No cash transactions left in period in group 4 (applicable to EuroPay
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn
only)
respnocashtxn
80 0100 All Card With No Financial Checks And No Linked resplowotb
Groups:
Card with no financial checks and no linked groups
81 0100/ All Not Enough Total Transaction: respnottotxn
0200 Not enough total transaction
82 0100/ All Not Enough Total Transaction In Group 0: respnottotxn
0200 Not enough total transaction in group 0

Appendix

95 0100/0200 All Request Without PIN Data For Card That Requires A resppinrequired
PIN:
Request without PIN data for a card that requires a PIN
101 0101 O,V Same Response Code As Original Message: Same as original
0201 Same response code as original message (Response to
0101)
102 0101/ O,V Original Message Not Found: resprepnotfound
0201 Original message not found and system not allowed to
authorise repeats (Response to 0101)
103 0100 E Zero Amount: respzeroreqamount
Zero amount authorisation request
103 0101/ V Card Not In Database: respnotfound
0201 Visa Repeat Request, Card not in Database
104 0100 E Unknown Exchange Rate: respeuroreqnoexrate
Europay: Unknown exchange rate
105 0100 E Invalid MCC: respeuroinvmcc
Europay: Invalid MCC in Request
110 0102 O,V Card Not In Database: No parameter
Card not in database
111 0102 O,V No Exchange Rate: No parameter
No exchange rate from transaction/billing to card and cen-
ter currencies
112 0102 O,V Original Message Not Found: No parameter
Original message not found
113 0102 O,V Original Message Approved: No parameter
Original message was not approved
114 0102 O,V Original Message Is Already Reversed: No parameter
Original message is already reversed
115 0102 O,V Replacement Amount Is Larger Than Original No parameter
Amount:
Replacement amount is larger than original amount

Appendix

120 0120/0121/ E,O, Card Not In Database: No parameter
0220 M,V Card not in database
121 0120/0121/ E,O, No Exchange Rate: respnoexrate
0220 M,V No exchange rate from transaction/billing to card and cen-
tre currencies
122 0120/0121/ E,O, Advice Message Was Not An Approval: No parameter
0220 M,V Advice message was not an approval
123 0121 E Original Message Processed: No parameter
Europay only. Original message was received and pro-
cessed.
124 0120/0121 E Zero Amount: respzeroadvamount
Europay: Zero amount in Advice
125 0120/0121 E Wrong MCC: respadvwrongmcc
Europay: Wrong MCC in Advice
126 0120/0121 E Wrong Track 2 Format: respadvwrongtrack
Europay: Wrong Track 2 format in Advice
127 1100/1200 A Ansi Track: Respansiemrgcyu /
Amex: Ansi Track for non-Emergency Card respansiemrgcya
130 0100/0200 V,M Payment Transaction Not Allowed: respnopaymentv
Payment transaction not allowed
131 0100/0200 E Payment Transaction Not Allowed: respnopaymente
Payment transaction not allowed
140 0400 O,V Card Not In Database: respnotfound
141 0400 O,V No Exchange Rate: respnoexrate
ter currencies
142 0400 O,V Original Authorisation Message Not Found: resprevnotfound
Original authorisation message not found
143 0400 O,V Original Authorisation Message Was Not An Ap- resprevnotapproved
proval:
Original authorisation message was not an approval
144 0400 O,V Original Authorisation Message Is Already Reversed: resprevorigreversed
Original authorisation message is already reversed
145 0400 O,V Replacement Amount Is Larger Than Original resprevamttoobig
Amount:
150 0401 O,V Card Not In Database: respnotfound

Appendix

151 0401 O,V No Exchange Rate: respnoexrate
tre currencies
152 0401 O,V Original Authorisation Message Not Found: resprevnotfound
Original authorisation message not found
153 0401 O,V Original Authorisation Message Was Not An resprevnotapproved
Approval :
154 0401 O,V Original Authorisation Message Is Already Reversed: resprevorigreversed
Original authorisation message is already reversed
155 0401 O,V Replacement Amount Is Larger Than Original resprevamttoobig
Amount:
160 0420/ All Card Not In Database: No parameter
421 Card not in database
161 0420/ All No Exchange Rate From Transaction/Billing to Card respnoexrate
0421 And Centre Currencies:
tre currencies
162 0420/ All Original Authorisation Message Not Found: No parameter
0421 Original authorisation message not found
163 0420/ All Original Authorisation Message Was Not An No parameter
0421 Approval:
164 0420/ All Original Authorisation Message Is Already Reversed: No parameter
0421 Original authorisation message is already reversed
165 0420/ All Replacement Amount Larger Than Original Amount: No parameter
0421 Replacement amount is larger than original amount
166 0421 E Message Processed: No parameter
Europay only. Original message was received and pro-
cessed.
167 0420/ E Zero Amount: respzeroadvamount
0421 Europay: Zero Amount in Reversal Advice
170 0100/ All Above Centre Fraud Ceiling: respabovefidceil
0200 Above centre fraud ceiling
171 0100/ All Above Card Fraud Ceiling: respabovecardfrd
0200 Above card fraud ceiling
172 0100 M Wrong Security Level Indicator: respwrngseclvlind
Wrong security level indicator

Appendix

175 0100 V Wrong Authentication Message: No parameter
Authentication message but with wrong transaction
amount, processing code and field 48
176 0100 V Authentication request failed No parameter
177 0100/0200 V Visa Prevalidated Decline: No parameter
Visa prevalidated decline
180 0100/ E Invalid Amount: No parameter
0120/ Invalid Amount - Failure to convert amounts and currency
0121/
0420/
0421
190 All STIP No Approval: No parameter
Original STIP authorisation was not approved
190 All All Forwarded To Debit Interface: No parameter
Message forwarded to debit interface
201 0200 V Incorrect Card’s Preauthorisation Trace: respwrongtrace
COPAC: Card’s preauthorisation trace produced one less
than the system’s count
202 0200 V ARQC Not Correct: respwrongarqc
COPAC: Preauthorisation cryptogram (ARQC) not correct
203 0200 V Key Or HSM Error: No parameter
COPAC Key or HSM error
204 0200 V Error Generating ARQC: No parameter
COPAC: Error Generating ARQC
205 0200 V ARQC Not Correct: respwrongarqc
COPAC: preauthorisation cryptogram (ARQC) not correct
206 0200 V Key Or HSM Error: No parameter
COPAC Key or HSM error
207 0200 V Wrong Card Message Cryptogram Trace Number: respwrongtrace
COPAC: Card message cryptogram trace number lower or
equal to the system’s count
208 0200 V Post Issuance: No parameter
COPAC: Post issuance only
209 0200 V Card’s Spending Power + the Requested Amount is respabovspending
Larger than the Centre Purchase Ceiling:
COPAC: Card’s spending power + the requested amount
is larger than the centre purchase ceiling

Appendix

210 0100 E Wrong Transaction Type for CIRRUS: respreqwrongmcc
The CIRRUS card is authorised for ATM or manual trans-
action types only. An authorisation request was received
by ONLINE for a Withdrawal/Cash Advance but the
transaction was rejected as the MCC is not the correct one
for ATM or manual transaction. Wrong MCC.
211 0100 E Wrong Transaction Type for CIRRUS: respeurocmorig
CIRRUS card only accepts withdrawal / Cash Advance (applicable to Europay
only)
212 0100 E Wrong Merchant Type for MAESTRO: respreqwrongmcc
The MAESTRO card is authorised for ATM or manual
transaction types only. An authorisation request was re-
ceived by ONLINE for a Withdrawal/Cash Advance but
the transaction was rejected as the MCC is not the correct
one for ATM or manual transaction. Wrong MCC.
212 0120/ E Wrong Transaction Type for CIRRUS: respeurocmadv
0121 CIRRUS card does not accept POS transaction or other (applicable to Europay
cash transactions apart from Withdrawal / Cash Advance. only)
Wrong transaction type.
213 0100/ E Wrong Transaction Type for MAESTRO: respeurocmorig
0120/ MAESTRO card does not accept other cash transactions (applicable to Europay
0121 apart from Withdrawal /Cash Advance. Wrong transaction only)
type. respeurocmadv
(applicable to Europay
only)
214 0100 E Wrong MCC for Cash: respreqwrongmcc
Europay: Wrong merchant type for cash transaction
214 0420/ E Wrong Transaction Type for CIRRUS: respeurocmadv
0421 CIRRUS card does not accept POS or other cash transac- (applicable to EuroPay
tions beside Withdrawal / Cash Advance. Wrong transac- only)
tion type.
215 0420/ E Wrong Transaction Type for MAESTRO: respeurocmadv
0421 MAESTRO card does not accept transactions other than (applicable to EuroPay
Withdrawal / Cash Advice. Wrong transaction type. only)
230 0100/ O,M, No Account Selected (To): respnoaccountNO
0220/ V No account selected (To)
0400/
0420/

Appendix

231 0100/ All No Account Selected (From): respnoaccountNO
0102/ No account selected (From)
0120/
0121/
0200/
0220/
0400/
0401/
0420/
0421
232 0100/ All Purchase Amount Less than Centre Minimum Pur- respbelowpurchceil
0200 chase Ceiling:
Purchase requested amount less than centre minimum pur-
chase ceiling
233 0100/ All Cash Amount Less than Centre Minimum Cash Ceil- respbelowcashceil
0200 ing:
Cash requested amount is less than the centre minimum
cash ceiling
234 0200 V Cash Amount Less than Centre Minimum Cash Ceil- respbelowcashceil
ing:
COPAC: Cash requested amount is less than the centre
minimum cash ceiling
235 0100/ All Approved Balance Inquiry: No parameter
Approved balance inquiry
236 0400 O,V Deposit reversal (Log Only) By Debit Interface: No parameter
Deposit reversal sent by Debit Interface for log only
240 0100/ All Invalid Card Usage: respwrongusage
0200 Invalid transaction type for card usage
241 0100/0200 All Invalid Group Usage: respwrongusage
Invalid Group Usage
242 0100/0200 All Wrong transfer to usage: respwrongusage
Wrong transfer to usage
250 0100/0200 M Error in Parsing Chip Data: respchipwrongfield55m
Error in parsing chip data
251 0100 V ARQC Not Correct: respchiparqcfl
Authorisation request cryptogram (ARQC) not correct
252 0100 V ATC Not Correct: respchipcntseq
Attached verification not successful
253 0100 V TVRs do not match: respchiptvrfl
TVRs do not match the values in [engine] checkstvr

Appendix

254 0100 V CVRs do not match: respchipcvrfl
CVR does not match the values in [engine] checkscvr
255 0100 V Fallback Option Activated: respchipfallbk
Fallback option activated
256 0100 V CVV Data Unreliable: respchipcvvunr
CVV data unreliable
257 0100/0200 V Reliability Indicator Set To Decline: respchipauthrelib
Reliability indicator set to decline
260 0100 M Invalid Resource Length: respwrongresrc
Invalid Resource Length Tag for MC Flee Card
261 0100 M No Link to Resource File: respwrongresrc
No Resource Profile Linked to MC Fleetcard
262 0100 M Resource not found: respwrongresrc
Resource not found in resource file linked to MC Fleetcard
263 0100 M Invalid Resource: respwrongresrc
Invalid resource in message for MC Fleetcard
299 0200 V Error Sending Script: No parameter
Error Sending Script
300 0420/ All SAF Message by Debit Interface: No parameter
SAF message as Debit support SAF
301 8420 V Declined: No parameter
Decline for message type 8420
302 0100/0200 A Amex Wrong Processing Code: respinvproccodea
Amex wrong processing code
401 0100/0200 All Enrolled Utility Companies Inquiry, Success: No parameter
Enrolled utility companies inquiry, success
402 0100/0200 All Enrolled Utility Companies Inquiry Failed: No parameter
Enrolled utility companies inquiry failed
403 0100/0200 All Utility Bill Payment Failed: No parameter
Utility bill payment failed
420 0100/0200 All Debit Card Account Inquiry, Success: No parameter
Debit card account inquiry, success
421 0100/0200 All Debit Card Account Inquiry Failed: No parameter
Debit card account inquiry failed
500 0100 All OTB Usage Expired: No parameter
Proxy Card, OTB Usage Expired
502 0100 All No Transactions Left: No parameter
Proxy Card, No Transactions Left
503 0100 All Advice Not Allowed: No parameter
Proxy Card, Advice not allowed

Appendix

505 0100 All Card Expired: No parameter
Proxy Card, Card Expired
506 0100 All Card Status: No parameter
Proxy Card status is set for the card to be declined.
702 9110 All Card Not in Database: No parameter
Card Not in Database
715 9110 All No Exchange Rate: No parameter
tre currencies
729 9110 All Approval of Balance Inquiry: No parameter
Approval of balance inquiry and balance sent
730 9110 All No account selected (To): No parameter
No account selected (To)
731 9110 All No account selected (From): No parameter
No account selected (From)
350 0100/ V More Than Instalment Period of Group 0: resp loan
0200 More Than Instalment Period of Group 0
360 0100/ V More Than Maximum Loan Amnt of Group 0: resp loan
0200 More Than Maximum Loan Amount of Group 0

Appendix

371 0100/ V Less Than Minimum Loan Amnt of Group 0: resp loan
0200 Less Than Minimum Loan Amount of Group 0

Appendix
Acquirer Response Reason codes - -
Acquirer Response Reason codes

The system uses Acquirer Response Reason codes to further define ISO messages.
Communication with ATM terminals needs system-protocol compatibility. Use MapIDs
to ensure this.
Code: Assigned by the system. Maps to description of error/problem.

Brief/Full Description: Error/Problem description
Code Brief/Full Description

101 MessageClass Not defined
102 Out of Memory
103 Invalid Data
104 Terminal Counts Failed
105 Could not send message
106 Unable To Log
107 Merch Term not found
108 Could not Route
109 Could not Update
130 Invalid Terminal
131 Terminal Not Found
132 Merchant Not Found
133 TrxnType Not Found
134 Inquiry Not Allowed
141 Original Not Found
142 Original Reversed
143 Original Not An Approval
150 Unable to create an ISO message based on in-
put data
151 Verify Date Failed
152 Wrong Class
153 Not Valid API
154 ATM deposit not supported
155 Exchange Rate not defined
156 Transaction not supported
157 Zero Amount
158 Pin block verification failed
159 Cannot route balance to Mastercard

Appendix
Acquirer Response Reason codes - -
160 Field 48 exceeded

161 E-commerce without CVV2
162 Pin Change without Pin Block
163 Check hotcards failed
164 Cashback for Europay
165 Utility Pay not set
166 Utility Serial missing

Appendix
Visa Reason Codes - -
Visa Reason Codes

Visa Reason Codes and Visa Plus Reason Codes (shaded area) explain why a reversal,
adjustment, chargeback, chargeback reversal, representment or fee collection/funds
disbursement has been sent. The following table shows all Visa reason codes in the
sequence that they appear on the ONLINE screen. The second and third columns show the
ISO code of the transaction and the processing code respectively. The fourth column is a
description of the reason code (Visa or Plus). A series of restrictions applies in certain
cases, as shown in the Restrictions column.
Restrictions Notes
other (see key following table)

Invalid for CPS (US only)
More than $10 (US only)
Processing code
Code Type Description

International only
Invalid for EPS
Invalid for T&E

More than $25
T&E only
US only
0062 0220 01 Representment of Counterfeit Transaction 1

Chargeback
Chargeback
Chargeback
0062 0422 01 Counterfeit Transaction 1
0074 0220 01 Representment of Late Presentment * *
Chargeback
Chargeback
Chargeback
0074 0422 01 Late Presentment * *
0076 0220 01 Representment of Non-transaction currency * *
Base II Chargeback
Base II Chargeback
Base II Chargeback
0076 0422 01 Non-transaction currency thru Base II * *

Appendix
Restrictions Notes

Processing code
International only
Invalid for EPS
Invalid for T&E

More than $25
T&E only
US only
0090 0220 01 Representment of Non-receipt funds * * *
Chargeback
Chargeback
Chargeback
0090 0422 01 Non-receipt of funds * * *
0100 0220 19 Telex, telephone & cable charges *
0110 0220 19 Auto-telex charges (Acq) *
0110 0220 29 Auto-telex charges (Acq) *
0110 0422 19 Auto-telex charges (Iss) *
0110 0422 29 Auto-telex charges (Iss) *
0130 0220 19 Lost/stolen card report fees (Acq)
0130 0220 29 Lost/stolen card report fees (Acq)
0130 0422 19 Lost/stolen card report fees (Iss)
0130 0422 29 Lost/stolen card report fees (Iss)
0140 0220 19 Merchant service fees (Acq) *
0140 0220 29 Merchant services fees (Acq) *
0140 0422 19 Merchant service fees (Iss) *
0140 0422 29 Merchant service fees (Iss) *
015011 0220 19 Recovered card handling fees/rewards - Acq
0150 0220 29 Recovered card handling fees/rewards - Acq
0150 0422 19 Recovered card handling fees/rewards - Iss
0150 0422 29 Recovered card handling fees/rewards - Iss
0160 0220 19 Invalid CAB chargeback handling fee (Acq) *
0160 0220 29 Invalid CAB chargeback handling fee (Acq) *
0160 0422 19 Invalid CAB chargeback handling fee (Iss) *
0160 0422 29 Invalid CAB chargeback handling fee (Iss) *
0170 0220 19 Recovery of copy/original fee (Acq)

Appendix
Restrictions Notes

Processing code
International only
Invalid for EPS
Invalid for T&E

More than $25
T&E only
US only
0170 0220 29 Recovery of copy/original fee (Acq)
0170 0422 19 Recovery of copy/original fee (Iss)
0170 0422 29 Recovery of copy/original fee (Iss)
0200 0220 19 Emergency replacement card distr. fee - Acq
0200 0220 29 Emergency replacement card distr. fee - Acq
0200 0422 19 Emergency replacement card distr. fee - Iss
0200 0422 29 Emergency replacement card distr. fee - Iss
0210 0220 19 Emergency cash disb, handling fee (Acq)
0210 0220 29 Emergency cash disb, handling fee (Acq)
0210 0422 19 Emergency cash disb, handling fee (Iss)
0210 0422 29 Emergency cash disb, handling fee (Iss)
0220 0220 19 Arbitration./compliance/resolution case de-
cision or request fee (Acq)
cision or request fee (Acq)
cision or request fee (Iss)
cision or request fee (Iss)
0230 0220 19 Incorrect merchant idnt. /txn data handling *
fee (Acq)
0230 0422 19 Incorrect merchant idnt./txn data handling *
fee (Iss)
0230 0422 29 Incorrect merchant idnt./txn data handling *
fee (Iss)
2001 0220 02 Transaction voided by c/h (online) - DB
2001 0220 22 Transaction voided by c/h (online) - CR
2002 0220 02 Wrong amount due to ATM misread (on- online
line) - DB correction
2002 0220 22 Wrong amount due to ATM misread (on- online
line) - CR correction
2004 0220 02 Acquirer back-office correction - DB back-office
correction

Appendix
Restrictions Notes

Processing code
International only
Invalid for EPS
Invalid for T&E

More than $25
T&E only
US only
2004 0220 22 Acquirer back-office correction - CR back-office
correction
2006 0220 02 Reversal of a previous credit adjustment back-office
correction
2006 0220 22 Reversal of a previous credit adjustment back-office
correction
2008 0220 02 Reversal of a previous debit adjustment back-office
correction
2008 0220 22 Reversal of a previous debit adjustment back-office
correction
2020 0220 01 Resp. to C/H Dispute Chargeback (DB)
2020 0220 02 Resp. to C/H Dispute Chargeback (DB)
2020 0220 22 Resp. to C/H Dispute Chargeback (CR)
2022 0220 01 Invalid Chargeback (Debit)
2022 0220 02 Invalid Chargeback (Debit)
2022 0220 22 Invalid Chargeback (Credit)
2102 0220 02 Approved transaction, previously reversed
when no confirmation received from point
of service, completed - DB
of service, completed - CR
of service, completed - DB
of service, completed - CR
2202 0220 02 Partial dispense detected, previously
reversed - DB
2202 0220 22 Partial dispense detected, previously
reversed - CR
2501 0420 01 Transaction voided by c/h

Appendix
Restrictions Notes

Processing code
International only
Invalid for EPS
Invalid for T&E

More than $25
T&E only
US only
2502 0420 01 Transaction has not completed
2503 0420 01 No confirmation from Point of Service
2547 0420 01 Potential duplicate txn. Visa generated
2548 0420 01 Duplicate txn. Visa generated
2602 0220 19 Cardholder dispute, credit to cardholder
2602 0422 29 Cardholder dispute, credit to cardholder
2604 0220 19 Cardholder dispute, debit to cardholder
2604 0422 29 Cardholder dispute, debit to cardholder
2606 0220 19 Reversal of a previous credit chargeback
2606 0422 29 Reversal of a previous credit chargeback
2608 0220 19 Reversal of a previous debit chargeback
2608 0422 29 Reversal of a previous debit chargeback
2620 0220 19 Cardholder dispute (of previous adjust)
2620 0422 29 Cardholder dispute (of previous adjust)
2622 0220 19 Invalid adjustment received
2622 0422 29 Invalid adjustment received
2624 0220 19 Account closed/insuff. fund (prev. adj)
2624 0422 29 Account closed/insuff. fund (prev. adj)
5290 0220 19 Corporate indemnification of Settl. Risk * 2
5290 0422 29 Corporate indemnification of Settl. Risk * 2
white background = Visa Reason Codes
grey (shaded) background = Visa Plus Reason Codes
* = restriction applies
1 = Invalid for a transaction in which the POS entry mode code field of the authorisation request includes the value “90"
2 = Incoming only with the account number field zero-filled; the transaction is initiated by Visa.

Appendix
MasterCard Reason Codes - -
MasterCard Reason Codes

MasterCard Advice Reason Codes are used to indicate the specific purpose of an advice
message. The following table shows all MasterCard reason codes in the sequence that
they appear on the ONLINE screen. The first column shows the advice message type, the
second the advice reason code, the third the advice detail code (if any) and the fourth a
description of the reason code.
Advice Advice Advice
Message Reason Detail Advice Reason Code Description
Type Code Code
0220 200 Network Stand-In: issuer selected option
201 Network Stand-In: IPS signed out
202 Network Stand-In: IPS timed out
203 Network Stand-In: IPS unavailable
250 Network Stand-In: Possible Duplicate
251 0010 APS approved transaction; card returned; partial dispense
251 0010 APS approved transaction; card retained; partial dispense
280 APS approved transaction; Late Acquirer Financial Acknowledgment/0280
290 0000 APS approved transaction; Pre-Authorised by Issuer
291 APS approved transaction; Network time-out
293 APS approved transaction; APS system error
0420 400 0080 Network advice: APS errors; no APS 0180/0280 Acknowledgment
402 0090 Network advice: IPS time-out error
450 0011 Zero Dispense: Card returned; no receipt issued
450 1011 Zero Dispense: Card retained; no receipt issued
450 0018 Zero Dispense: Card returned; ATM failure
450 0018 Zero Dispense: Card retained; ATM failure
450 0019 Zero Dispense: Card returned; ATM time-out
450 0019 Zero Dispense: Card retained; ATM time-out
450 0041 Zero Dispense: Card returned; Cardholder time-out
450 1040 Zero Dispense: Card retained; Cardholder time-out
451 0010 Partial Dispense: Card returned
451 1010 Partial Dispense: Card retained
453 0040 Financial transaction cancellation: Card returned
453 1041 Financial transaction cancellation: Card retained
454 APS unable to deliver response
455 0090 APS time-out: Card returned
455 1090 APS time-out: Card retained
0420 490 Network Advice: Switch-generated Chargeback action

Appendix
MasterCard Reason Codes - -
Advice Advice Advice

Message Reason Detail Advice Reason Code Description
Type Code Code
490 Network Advice: Switch-generated Adjustment action
490 Network Advice: Switch-generated Representment action
0422 489 Network Advice: Switch-generated Chargeback action
489 Network Advice: Switch-generated Adjustment action
489 Network Advice: Switch-generated Representment action
0520 500 Automatic reconciliation/totals complete
501 Reconciliation request response/totals complete
502 Reconciliation request response/totals incomplete
0522 500 Automatic reconciliation/totals complete
501 Reconciliation request response/totals complete
502 Reconciliation request response/totals incomplete
0620 600 Message unreadable/indecipherable/contains invalid data; (Advice Detail Code
field MAY contain but map number of data element where messages scanning was
aborted)
601 Retrieval request
602 Fulfillment notification
0644 690 4 Message not dispatched from remote MIP
690 5 Message not dispatched to remote MIP
690 6 Message not delivered to remote MIP
690 7 Message not delivered from remote MIP

Appendix
Routing Product List - -
Routing Product List

ROUTING PRODUCT LIST 15 Jun
These product types maybe entered in the actions screen of the route subsystem of the
batch menu.
Product
Product Description File Origin
Type
A VISA ATM Visa
B Visa Business Visa
C Visa Classic Visa
E Visa Electron Visa
M MasterCard Visa
P Visa Gold Visa
R Visa Corporate T&E Card Visa
S Visa Purchasing Card Visa
T Visa Travel Voucher Visa
PLUS Visa PLUS Visa
ECMC EuroCard/MasterCard EuroPay
MAST MasterCard EuroPay
ECHA Eurocheque Pictogram EuroPay
CRUS Cirrus EuroPay
ECCR Eurocheque/Cirrus EuroPay
EDC EDC EuroPay
MAES Maestro EuroPay
EDCM EDC/Maestro EuroPay
CBAN Carte Bancaire EuroPay
AMX American Express MasterCard
CBL MasterCard CBL MasterCard
DCC Diners Club Card MasterCard
DSV MasterCard DSV MasterCard
ENR MasterCard ENR MasterCard
JCB JCB MasterCard
MCB MasterCard Business MasterCard
MCC MasterCard Card MasterCard
MCD MasterMoney Card MasterCard
MCG MasterCard Gold MasterCard
MCP MasterCard Premier MasterCard
MCS MasterCard MCS MasterCard

Appendix
Routing Product List - -
Product
Product Description File Origin
Type
PVL MasterCard Private Label MasterCard
VIS VIS MasterCard
DEFA Used for Default Ranges

REFERENCE GUIDE (P1665-001) 120 © Card Tech Limited 2003-2006. All rights reserved
Appendix
Region coding for exception files - -
Region coding for exception files

The following table is a list of region coding which is used by issuers to specify in which
geographical areas a card should be published in a warning bulletin for pickup. The table
shows the coding used by Visa, MasterCard and EuroPay.
Regions VISA MasterCard EuroPay
USA X (1-9) 1 1
All non-USA regions Y no equivalent no equivalent
Central America F B B
Latin America F no equivalent no equivalent
South America F B B
Canada C A A
Caribbean Y B B
Mexico F B B
Europe E D D
Middle East B/E E E
Asia/Pacific A C C
Africa B E E
National D no equivalent no equivalent
All regions Z no equivalent no equivalent
Do not list card on any bulletin 0 no equivalent no equivalent

INDEX
ONLINE
3.7 R02 AUTHORIZATION SYSTEM Version
Index
A authorization process 8 - 11 cards with high number of

Acquirer Currency authorizations 64
report - log 48 conversion 35 cards with high trxn
report - log (SMS) 50 amounts 52
D group bonus changes 71
Authorization
EuroPay 22 - 25 Date
See also purge date G
Host 26 - 29
MasterCard 16 - 19 Group
E cash OTB checking 38
process 7 - 32
report - dropped Europay OTB checking 38
authorizations 66 authorization process 22 - 25 transaction checking 38 - 40
report - exceed center lmt 52 Exception codes Group reports
report - exceed high count 53 report - exception bonus changes 71
report - outstanding 84 management 67 bonuses approved 72
report - STIP 87 report - exception management bonuses used 73
VISA 8 - 15 delete failures 68 cash bonuses approved 74
Automatic processes report - exception management cash bonuses used 75
description 7 - 32 update failures 69 listing 76
listing short 77
B F
Fee collection & Funds H
Balance inquiry
overview 33 disbursement - report 70 HOST
Blocked card 43 File layout authorization process 26 - 29
Bonus - card See Interface files
Files I
report - changes 54
Bonus - group See also Interface files International card
report - changes 71 Fraud See also Service codes
fraud weight Issuer
C overview 36 - 37 report - log 78
Card reports reports report - log (declines) 79
bonus changes 54 authorizations exceeding
center limit 52 L
bonuses approved 55
bonuses used 56 authorizations exceeding Lists
cash bonuses approved 57 high count 53 See Reports
cash bonuses used 58 card bonus changes 54 Loading interface files
high authorization amount 62 card bonuses approved 55 See also Interface file loading
listing 59 card bonuses used 56 Log
listing short 60 card cash bonuses See Reports
near credit limit 61 approved 57
Chargebacks cards with high M
new received - report 83 authorization amount 62 Manual advices
reversals - report 65 cards with high approved - report - 80
Chip card authorization amount in used - report - 81
center currency 63 Manual card status change 82

INDEX
MasterCard authorization exceed center S

authorization process 16 - 19 limit 52
MasterCard Reason Codes 117 - authorization exceed high SingleConnect - Visa
118 count 53 chargeback reversals 65
MC Corporate Fleet Card card bonus changes 54 reports
authorization process 20 card bonuses approved 55 acquirer log 50
MCC card bonuses used 56 all pending
checking 40 - 42 card cash bonuses chargebacks 51
MCC Product Velocity approved 57 chargeback reversals 65
Checks 41 - 42 card cash bonuses used 58 fee collections 70
MDS Reason Codes card listing 59 fund disbursements 70
See MasterCard Reason Codes card listing short 60 new chargebacks
Merchant cards near credit limit 61 received 83
category code checking 40 - cards with high auth. reconciliations 85
42 amount 62 - 63 representments 86
cards with high number Spending restrictions
P auth. 64 authorization process 7 - 32
PIN chargeback reversals 65 report - cards high auth.
blocking card 43 dropped authorizations 66 amount 62
retries overview 43 - 44 exception management 67 report - cards near limit 61
verification overview 43 - 44 exception management delete Stand-In Processor
Product type 119 - 120 failures 68 report 87
Product Velocity Checks 41 - 42 exception management update STIP
failures 69 See Stand-In Processor
R Fee collect. & Funds Stop list
Reconciliation disbursement 70 See Exception file
report 85 group bonus changes 71 Suppress inquiry 87
transaction matching 45 group bonuses approved 72 T
Reconciliation processing 45 - 46 group bonuses used 73
Report categories group cash bonuses Terminal
control report 48, 50, 59 - 60, approved 74 See POS terminal
70, 76 - 77, 84, 86 group cash bonuses used 75 Transaction
customer services 61, 84 group listing 76 matching 45
fraud detection 53, 62 - 64, group listing short 77 report 88
66, 79 issuer log 78 report - unauthorised 89 - 90
Fraud detection 52 issuer log (declines) 79 transaction match 45
internal fraud 54 - 58, 71 - 75, manual advices approved 80 Travel & Entertainment
80 - 82 manual advices used 81 See T&E
operational 51, 65, 67 - 70, manual card status change 82 V
78, 83, 85 - 86, 88 - 89 new chargebacks received 83
risk control 61 outstanding authorizations 84 Velocity check
Report options reconciliations 85 Authorisation logic 41 - 42
notes for printing 47 - 90 representments 86 Velocity checks 41 - 42
Reports STIP authorizations 87 VISA
acquirer log 48 transactions 88 authorization process 12 - 15
acquirer log (MDS) 49 unauthorised transactions 89 - reason codes 112 - 116
acquirer log (SMS) 50 90
all pending chargebacks 51 Representments 86


Online Authorisation System Version 3.7 R02 Processing Reference Guide

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

Online Authorisation System Version 3.7 R02 Processing Reference Guide

Uploaded by

Copyright:

Available Formats

ONLINE

ONLINE Version 3.7 R02 Processing Reference Guide

Publication: P1665 — Release: 001

How to use this manual … … … … … … … … vi

Balance inquiry response … … … … … … … 33

MCC Product Velocity Checks … … … … … … 41

PIN verification during authorisation … … … … … 43

PIN verification - VISA, MasterCard and Host … … … … 44

ISO Response codes … … … … … … … … 93

Issuer Response Reason Codes… … … … … … 95

Acquirer Response Reason codes … … … … … 110

Visa Reason Codes … … … … … … … … 112

MasterCard Reason Codes … … … … … … … 117

Routing Product List … … … … … … … … 119

Region coding for exception files … … … … … 121

How to use this manual

Important notes are printed in a box.

© Card Tech Limited 2003-2006. All rights reserved