PaymentTrust RiskGuardian, Implementation Guide
Annons
Annons
RiskGuardian & PaymentTrust –
Implementation Guide
Version: 2.0
April 2007
Copyrights
Copyright 2006, PaymentTrust Limited.
All rights reserved.
Version 2.0
Issue Date: April 2007
Prepared by: PaymentTrust Ltd
Trademarks
Risk Guardian and PaymentTrust logo is trademark or service marks of Payment Trust
Limited. All other marks listed in this document may be trademarks of their respective owners and are mentioned for identification purposes only.
This User Manual is protested by the copyright laws and treaties and may not be reproduced without permission from PaymentTrust Limited. You may not use this guide to reverse engineer the PaymentTrust Limited PaymentTrust software.
C o n t e n t s
1.
Document Overview......................................................................................................... 1-1
1.1 P
URPOSE OF THE
D
OCUMENT
................................................................................ 1-1
1.2 W
HO SHOULD READ THIS DOCUMENT
................................................................... 1-1
1.3 T
ERMINOLOGY
....................................................................................................... 1-1
1.4 R
ELATED
D
OCUMENTS
.......................................................................................... 1-2
2.
Communication ................................................................................................................ 2-3
2.1 STL
INK
O
VERVIEW
............................................................................................... 2-3
2.2 N
ETWORK
L
AYER
.................................................................................................. 2-5
2.3 S
ECURITY
L
AYER
................................................................................................... 2-5
2.4 STL
INK
A
PPLICATION
........................................................................................... 2-5
2.5 N
ETWORK
R
EQUIREMENTS
................................................................................... 2-6
2.6 E
XAMPLE
R
EQUEST
(STN S
TRING
)....................................................................... 2-7
2.7 E
XAMPLE
R
EQUEST
(STN
XML) .......................................................................... 2-7
2.8 E
XAMPLE
XML
WITH ESCAPING
........................................................................... 2-8
2.9 E
XAMPLE
HTTP POST
REQUEST FOR
STL
INK
................................................... 2-8
2.10
E
XAMPLE
HTTP POST
REQUEST FOR
STL
INK
B
ATCH
.................................... 2-8
3.
RiskGuardian ................................................................................................................... 3-9
3.1 R
ISK
G
UARDIAN
I
MPLEMENTATION KEY STAGES
................................................. 3-9
3.2 L
OGIC
(T
SCORE AND
TR
ISK
)............................................................................... 3-10
4.
PaymentTrust ................................................................................................................. 4-11
4.1 W
HAT IS
P
AYMENT
T
RUST
? ................................................................................. 4-11
4.2 R
EQUESTYPES
...................................................................................................... 4-11
4.3 P
AYMENT
T
RUST
I
MPLEMENTATION KEY STAGES
.............................................. 4-12
4.4 M
ETHOD OF
P
AYMENTS
(MOP’
S
)....................................................................... 4-12
4.5 S
TORE
ID
S
............................................................................................................. 4-13
4.6 T
HE
D
IFFERENCES WITH
D
OMESTIC
M
AESTRO AND
S
OLO
............................... 4-14
4.7 R
ESPONSE
C
ODES
................................................................................................. 4-14
5.
3DSecure with PaymentTrust ....................................................................................... 5-17
5.1 W
HAT IS
3DS
CECURE
? ........................................................................................ 5-17
A T
YPICAL
3DS
ECURE
T
RANSACTION USING
P
AYMENT
T
RUST
’
S
H
OSTED
MPI........ 5-17
5.2 M
ERCHANT APPLICATION REQUESTS VIA
STL
INK FOR
3D S
ECURE ENROLMENT
VERIFICATION
.
(R
EQUES
T
YPE
V) ................................................................................. 5-17
5.3 E
NROLMENT RESPONSE CONTAINS CUSTOMERS ISSUING BANK
URL.
T
HE
MERCHANT APPLICATION INSTRUCTS CUSTOMER
’
S BROWSER TO REDIRECT TO THE
PROVIDED
URL. ............................................................................................................ 5-18
5.4 B
ROWSER REDIRECTS TO CUSTOMER
’
S ISSUING BANK
URL
INCLUDING THE
T
ERM
U
RL AND
MD
FIELDS
.
C
USTOMERS ATTEMPT TO AUTHENTICATE THEMSELVES BY
ANSWERING THEIR CHALLENGE QUESTION OR ENTERING THEIR PIN
.......................... 5-19
5.5 A
UTHENTICATION RESULT IS POSTED BACK TO MERCHANT
’
S COMMERCE
APPLICATION
. ................................................................................................................ 5-20
5.6 M
ERCHANT
’
S APPLICATION REQUESTS VIA
STL
INK FOR VALIDITY OF THE
AUTHENTICATION RESPONSE
.
(R
EQUES
T
YPE
A).......................................................... 5-20
5.7 M
ERCHANT
’
S APPLICATION PREPARES A STANDARD AUTH
/
SALE WITH PROVIDED
3D S
ECURE FIELDS
: ECI, CAV, S
ECURE
I
D AND SENDS A REQUEST TO
STL
INK
. ....... 5-22
5.8 A
RECEIPT PAGE IS RETURNED TO THE CUSTOMER WITH ACCEPTED OR DECLINED
MESSAGE
. ....................................................................................................................... 5-24
6.
Bank Indentification Table (BIN) Table ...................................................................... 6-25
6.1 S
CREENSHOT OF DATA
(
CSV FORMAT
) ................................................................ 6-25
6.2 S
CREENSHOT OF DATA
(
TXT FORMAT
) ................................................................ 6-26
7.
URL’s and Tools............................................................................................................. 7-27
A
LL
T
EST AND
L
IVE TRANSACTION SYSTEM
................................................................ 7-27
RG T
EST WEBSITE
......................................................................................................... 7-27
PT T
EST WEBSITE
.......................................................................................................... 7-27
8.
Appendix I – RG Set-up Form...................................................................................... 8-28
9.
Appendix II – PayBack (Credit Card) Set-up Form................................................... 9-36
10.
Appendix III – PT Acquiring Set-up Form ............................................................... 10-37
11.
Appendix IV – Domestic Maestro and Solo Bins ...................................................... 11-38
12.
Appendix V: message/response codes......................................................................... 12-41
13.
Appendix VI: currency codes...................................................................................... 13-48
14.
Appendix VII: country codes ...................................................................................... 14-50
15.
Appendix VIII: state/province/region codes .............................................................. 15-56
16.
Appendix IX: how to contact us.................................................................................. 16-59
17.
Glossary of payment processing terminology............................................................ 17-60
1.
D
OCUMENT
O
VERVIEW
1.1
Purpose of the Document
This document provides an overview of how to implement PaymentTrust’s core services, Risk Guardian and PaymentTrust. Additionally to this there are subsequent documents listed below covering our Payback services and Bank Transfer Service these documents should be read in conjunction with this when implementing these services.
The Developer’s guide is the main document for understanding message formats and communication methods.
1.2
Who should read this document
System Integrators and Project Managers responsible for implementing
PaymentTrust’s products and services.
1.3 Terminology
The following is a glossary of terms and abbreviations used in this document:
Term or Abbreviation Definition
PT:
PaymentTrust
STLink:
STN:
PaymentTrust’s Secure Transaction Link
PaymentTrust’s Secure Transaction Network
SSL:
API:
ASP:
Secure Sockets Layer
Application Program Interface
Active Server Pages
RG -RM:
PT -PP:
Transaction Services
RiskGuardian - Risk Management
PaymentTrust - Payment Processing
Includes PaymentTrust (PT), RiskGuardian (RG), Bins (BN),
Bank Transfer Service (BT), Foreign Exchange (FX),
3DSecure (3D) and others.
1-1
All Integration related documents can be downloaded from the following URL. http://www.paymenttrust.ca/devtools/
PaymentTrust User Guide - PaymentTrust User Guide 2.4.pdf
RiskGuardian User Guide - RiskGuardian User Guide 3.0.pdf
Developer’s Guide - MerchantServices-DevGuide-08.20.00.doc
3DSecure Flow Chart - Hosted_MPI_Flow_002 dec06.doc.doc
1-2
2. C
OMMUNICATION
The PaymentTrust Secure Transaction Network (STN) is a collection of robust, multithreaded and real-time transaction systems (See Figure 1 below). STN is composed of the PaymentTrust Secure Transaction Link (STLink) system and back-end Transaction
Services. STLink receives transaction information from merchants, processes the information through one of the many transaction services, and sends the response back to the merchant’s requesting system. All Internet communication mentioned in this document is executed via an Internet 128 bit Secure Sockets Layer (SSL) connection, or an Internet Virtual Private Network (VPN) connection using the Triple DES standard.
Fig 1: Overview of PaymentTrust’s Secure Transaction Network
2.1
STLink Overview
PaymentTrust’s Secure Transaction Link (STLink) is a high performance communication solution.
STLink is a service of on-demand secure communication links between the
PaymentTrust Secure Transaction Network (STN) and a PaymentTrust Client
(Merchant). STLink conforms to encryption and protocol standards as described below (See Figure 2 for network implementation).
Transactions sent between a PaymentTrust Merchant and the PaymentTrust STN travel securely via a 128-bit SSL Internet connection. The STLink system also allows for a hardware encryption method/solution using VPN technology & IPSEC standards.
The Merchant’s own application will reside on his system and will be accessible via major web servers, Transaction platforms, and back-end systems. Merchants will be using PaymentTrust’s technical specs as guidance to develop their own applications.
PaymentTrust provides Merchants example code in ASP/VB, C++, Java, HTML and
2-3
XML. Merchants may choose to use their own samples and applications to send transaction information but must conform to the string requirements set in this document.
Fig 2: Overview of Network Implementation Possibilities
The STN is comprised of three layers. Descriptions of these layers can be found below in Figure 3.
Authentication
Communication
STlink within STN
Security
TM Access
SSL / VPN
(Cryptography)
Network TCP/IP (Internet)
* Platform Independent
Fig. 3 TM Secure Transaction Services Network - Communication Protocol
Layers
2-4
This layer is handled exclusively by the designated Internet Service Provider.
The Security Layer will be handled either by 128 bit SSL certificate or a secure tunnel
Triple DES VPN conforming to the IPSEC standard. PaymentTrust will provide at an additional cost the VPN hardware equipment if required.
The Security Layer also includes the Merchant access layer into the PaymentTrust
Secure Transaction Network (STN). This involves the use of a Merchant ID, a
Username and Password, which are sent as a string to STLink.
The Application Layer manipulates data using HTTP(S) GET/POST request or an
XML request and communicates via standard ports 443 for SSL or port 80 for VPN.
The system can intelligently process a request whether GET/POST or XML. The request (an input string) is routed with the STN to the appropriate service for processing – PT, RG, and others. The system returns the response to the requesting
URL. Should the delivery fail, the system will capture the error, inform the merchant and store the information for later reporting. Captured errors are further analyzed.
When the delivery is successful, the merchant receives a response and stamps each transaction with an appropriate message code. Please note that for larger strings sizes the GET method should not be used.
The input string/message sent by the Merchant is stored in a serialised database with a unique serial number. PaymentTrust maintains a log of any transaction requested by the Merchant and responds with a real-time message which will encapsulate information regarding:
Integrity of the message sent by the Merchant – if a message is received truncated/ incomplete or in a tampered condition, the STLink application will capture the error and will respond with the appropriate error message to the merchant’s system;
Authentication of sending and receiving agents (attributes that assure a given request is received from a specific trading partner) – messages between Merchant and
PaymentTrust must contain attributes that identify and recognize a specific Merchant;
The Type of Transaction requested along with processing statistics. I.e. an RG transaction that took 2 seconds to process from IP NNN.NNN.NNN.NNN using SSL etc.
It must be noted that the STLink system is Payload independent – data within the communication link is independent and can accommodate any type of Transaction, for example, an RG transaction with the same ease as a PT transaction. This eases the transition when new services become available.
The STLink system is based on HTTP/1.1 as a transport protocol as well as XML 1.0.
It uses generic protocols for communication between user agents and proxies/gateways and other Internet systems. Communication between a
PaymentTrust Merchant and a PaymentTrust STN will be achieved through request
2-5
messages and response messages. The STLink system implements and exploits the advantages provided by HTTP(S) and XML.
The following is required prior to testing of the STN and STLink system by
Merchants.
Internet access or dedicated link into the TMI Secure Transaction Network
The originating external IPs if SSL is used or the internal IP addresses of the computers that will participate in the VPN, as well as the external IP it will use.
Name and phone number of the designated technician or administrator responsible for the integration process.
Notification when the testing process is complete.
Our Network Operations Team will at that point take over of the process. The
Merchant will receive the following items from TMI:
VPN hardware if this is the solution chosen.
SSL URL if SSL is chosen (High Encryption Pack).
A merchant must follow a few simple steps to send transactions to the STN.
1. Build the HTTP headers
2. Build the transaction data.
3. Encode the transaction data.
4. Attach the transaction data to the HTTP headers.
5. Open a TCP/IP connection to STN.
6. Establish secure communication to STN using SSL.
7. Send the HTTP request to STN.
8. Receive HTTP response with transaction result from STN.
All transaction requests must be submitted to STLink and all batch requests to STLink
Batch in either the STN’s string format or as XML documents. Both STLink and
STLink Batch accept the HTTP and HTTPS protocols, though it is recommended that the HTTPS protocol be used to safely transmit the requests via the Internet. HTTP is the message protocol used to make request to the STN servers. HTTPS refers to the fact that the HTTP request is done over an encrypted/secure network connection.
The HTTP header should consist of the request method (POST), the requested resource (STLink), the HTTP version (1.1), a new line, the amount of data being posted (Content-Length) and 2 new lines. The 2 new lines at the end of the header allow the separation of the HTTP header from the data being posted.
All requests must be submitted using the HTTP POST method. The POST method works by supplying key/value pairs, where the key and value are split by the “=”
2-6
symbol and key/value pairs by the “&” symbol. For instance: key1=some value&key2=some value... In the case of STLink, there is one key value pair. The key is StringIn and the value is any of TMI transaction types. The POST data is always attached to the HTTP header after 2 new lines “\n”. An additional 2 new lines must be appended after the POST data to terminate the HTTP request as a whole.
2.6 Example Request (STN String)
This string demonstrates the key value pair of a POST request and contains the data of a partial transaction.
StringIn=VersionUsed^1~MerchantId^100000~UserName^Mariah~UserPassword^rr
87uy~TransactionType^A~IsTest^1~TimeOut^90000~
2.7 Example Request (STN XML)
This XML document demonstrates the key value pair of a POST request and contains the data of a partial transaction.
StringIn=<?xml version=”1.0”?><TMSTN><VersionUsed>1</VersionUsed><MerchantId>100000</
MerchantId><UserName>Mariah</UserName><UserPassword>rr87uy</UserPasswo rd><TransactionType>A</TransactionType><IsTest>1</IsTest><TimeOut>90000</
TimeOut></TMSTN>
Though STLink Batch accepts POST requests, it is important to note that the StringIn key is not required and must not be submitted to the STLink Batch for batch requests.
If not the batch request will be rejected for reason of being a malformed XML document.
The “=” and “&” symbols are standard characters used in the HTTP protocol to separate key/value pairs, there fore it is important that no “=” and “&” symbols be found in the transactions, although this can be overcome by escaping all characters after the StringIn key by using URL encoding. URL encoding allows the “=”, “&” and other HTTP characters to be included in the transaction.
Example:
StringIn=<URL encoded transaction>
Because STLink Batch does use the StringIn key, the batch request must not be URL encoded. If not the batch request will be rejected for reason of being a malformed
XML document.
XML has its own encoding rules. For one, the STLink and STLink Batch will support any XML document that has been encoded in an 8-bit ANSI character set, such as:
ISO-8859-1. Second of all XML has its own share of “special” characters. If any of these characters are to be included within the data of a specified transaction tag, they to must be escaped. The table below lists those characters and their escape sequence.
2-7
Character Description Escape Sequence
2.8 Example XML with escaping
<?xml version=”1.0”?>
<root>
<tag1>The text in here contains a less than symbol. Here it is: <</tag1>
<tag2>The text in here contains a double quote symbol. Here it is: "</tag2>
</root>
2.9 Example HTTP POST request for STLink
This shows what an HTTP request to Stlink should be, using the following STN URL: https://stn01.sectranet.com/stlinkssl/stlink.dll
. \n depicts a new line. The content length is the total amount of bytes including the key pair and the URLEncoded data.
POST /stlinkssl/stlink.dll HTTP/1.1\n
Content-Length: 123456\n
\n
StringIn=<URL encoded string or XML document>\n
\n
2.10 Example HTTP POST request for STLink Batch
This shows what an HTTP request to Stlink Batch should be, using the following STN
URL: https://stn01.sectranet.com/stlinkssl/stlink.dll
. \n depicts a new line. The content length is the total amount of bytes the XML document.
POST /stlinkssl/stlinkbatch.dll HTTP/1.1\n
Content-Length: 123456\n
\n
<XML document with no URLencoding>\n
\n
2-8
3. R
ISK
G
UARDIAN
RiskGuardian is a secure risk management solution that allows merchants to securely manage the risk associated with doing business on the Internet. RiskGuardian provides a set of static risk factors, determined by TMI, and a set of customizable risk factors, which the merchant can alter to manage their risk on an individual basis.
RG Features:
• Provides risk management and assessment for online transactions
• Total overhead is less than three seconds
• Merchant controlled parameters and values
• Online reporting and administration tools
• Export and Import capabilities for mass updates
• Focused on identity theft through Internet aware as well as traditional parameters
• Over 60 parameters and 300 algorithms and cross checks performed
3.1 Risk Guardian Implementation key stages
Technical evaluation
Understanding our API and what impact it will have on your system
Development
Actual coding based on API and system changes required.
Profiling
Understanding the merchant’s requirements in terms of blocking lists, previous fraud etc etc. Appendix X is the set-up form for RG where most of this information is obtained.
Testing
Full end to end testing of your application.
Fine Tuning
Sending live data to the Risk Guardian test system for the initial 2 weeks, in order that the risk profile previously completed is 100% in line with the Merchant’s requirements. Please note, this is still testing and the logic talked about earlier in this document should be ignored until go-live. Basically, the merchant should not act upon the TScore’s until profiling is complete.
Go-live….
3-9
3.2 Logic (Tscore and TRisk)
Risk Guardian is works on a scoring basis, 1 meaning an instant pass and 100 meaning an instant failure. Enclosed is a sample transaction.
Request
StringIn=VersionUsed^3~MerchantId^100162~OrderNumber^HelpDeskTest~Typeof
Sale^H~TransactionType^RG~IsTest^1~TimeOut^90000~UserName^umberdella~Us erPassword^della~AcctName^Eric
Smith~MOP^CC~AcctNumber^4000000000000002~ExpDate^092002~CurrencyId^1
24~Amount^56.78~Title^Mr.~FirstName^Eric~MiddleName^~LastName^Smith~Suf fix^3rd~Address1^2130 Gold~Address2^Suite
101~Address3^~City^Chicago~StateCode^il~ZipCode^12345-
6789~CountryCode^us~PhoneNumber^6188565656~Email^[email protected]~ShipTo
Title^Mr.~ShipToFirstName^Eric~ShipToMiddleName^~ShipToLastName^Smith~S hipToSuffix^3rd~ShipToAddress1^123
Road~ShipToAddress2^~ShipToAddress3^~ShipToCity^Seattle~ShipToStateCode^ wa~ShipToZipCode^34567-
8907~ShipToCountryCode^us~ShipToPhoneNumber^6188565656~REMOTE_ADD
R^205.188.146.23~HTTP_USER_AGENT^MSIE 5.0;Windows
NT~HTTP_ACCEPT_LANGUAGE^en,fr-CA~HTTP_ACCEPT_CHARSET^iso-
8859-1,*,utf-8~HTTP_REFERER^www.cnn.com~IsMember^3
Response
MerchantId^100162~TransactionType^RG~OrderNumber^HelpDeskTest~StrId^1780
431~MessageCode^100~GttId^1329853~tScore^100.0000~tRisk^56
This transaction scored 100 because the card number is invalid. Please note that transactions can score for a number of reasons i.e. cross reference or velocity controls.
Simply if the TScore is Greater than the TRisk then the transaction had failed your risk profile and shouldn’t be processed. By default, if the TScore is equal to or Lower that the TRisk then the transaction should proceed for processing with the acquiring bank either via PaymentTrust or another Payment Processor.
3-10
4. P
AYMENT
T
RUST
4.1 What is PaymentTrust?
PaymentTrust is capable of receiving multiple request types within the PT Transaction
Type. Each request type instructs the system to perform a different financial transaction. It is important to note that all requests types must follow a logical sequence so prior to a Deposit request one must have an Authorization request. There are cases where the PT TRX is an independent TRX not requiring any other Request type such in the case of a payback TRX or Bank Transfer. Following the submission of a request, the system will return an appropriate response code that will flag the transaction as being either successful, unsuccessful (with reason) or pending (awaiting third party confirmation). Each numeric response code is accompanied by a text definition.
4.2 Requestypes
An Authorization (A) request will reduce the cardholder’s open to buy (credit limit).
It places a hold on the funds for the merchant with the cardholder’s bank for a limited period of time (defined by the credit card associations) before it expires. An authorization does not move any funds to the merchant’s bank account. A deposit request type is required to initiate fund collection and is described below.
A Settlement (D) request marks a previously authorized transaction for funds collection during the next deposit cycle with the financial institution. Merchants who do not ship goods immediately should only perform this transaction request at the order fulfillment stage (shipment).
Important Note: A merchant can only submit one deposit request per authorization and this must be for a value lesser or equal to the authorized amount.
A Refund (R) request returns a specified amount to the cardholder’s account. The following refund is submitted where a previous deposit transaction has been processed by the system.
Please note that refunds for gaming clients as part of the Visa Credit Funds Transfer programme (CFT) must be sent to PaymentTrust as ‘Forced Refunds’. Details of this
Transaction can be found in the Developer’s Guide V8.0.16 page 31.
A Simultaneous Authorization and Settlement (S) charges the specified amount against the cardholder’s account and marks the transaction for funds collection during the next deposit cycle with the financial institution. This single request initiates both an authorization and a deposit request in the PT system. It should only be used in situations where merchants fulfil their orders immediately. The deposit portion of the
‘S’ request will only proceed once a successful authorization has been obtained.
A Cancellation (C) - Any transaction that is showing 2050 – request pending can be cancelled.
A Payback (P) request has three methods;
4-11
1. Credit card
This is a payment going back to a Credit Card Issuer, quoting the full card number as a reference and is only available to UK issued Mastercard and Visa. Payments are made via BACS Ltd in the UK.
2. Physical Cheque
This is a physical cheque being sent out to the recipient via the conventional post or via courier.
3. Electronic Credit
This is an Electronic payment going back directly to a Clients bank account.
A document entitled ‘Payback Service Overview’ is available on request which cover the payback service in detail.
A Bank Transfer (B) a document entitled ‘Bank Transfer Service Overview’ is also available on request.
4.3 PaymentTrust Implementation key stages
Technical evaluation
Understanding our API and what impact it will have on your system.
Development
Actual coding based on API and system changes required.
Testing
Full application end to end testing.
Live bank set-up
Merchant account details are given to the merchant by the Acquiring Bank based on
Currency, transaction type, channel (Internet, Moto, digital TV etc ), these details are entered into the PaymentTrust live back end systems. Terminal ID’s are allocated by
PaymentTrust and sent to the Acquiring bank for set-up on their live systems. Once the details are active on both systems then everything is ready and go-live can commence.
Go-live….
4.4 Method of Payments (MOP’s)
• CC – Visa and Mastercard credit and debit products (visa credit, visa delta, visa electron, Mastercard Credit, International Maestro)
• DS – Domestic Maestro and Solo
• CQ – Payback via Cheque
• EC – Payback via Electronic Credit
• NT – Neteller
• P2 – Pay2
• DC – PIN enabled debit cards
• PC – Purchasing cards
4-12
4.5 StoreIDs
Storeid is mandatory for all TransactionType^PT~. The Storeid is the same number as the Acquiring bank MerchantID. This is required in each transaction in order that
PaymentTrust can settle into the correct currency account with the bank.
Typical set-up with Natwest Streamline,
Australian Dollars
Danish Kroner
E-commerce sales
64383638
81524262
Australian Dollars
Danish Kroner
Euro - Laser Card
Swedish Kronor
Swiss Franc's
Taiwanese New Dollar (settle in
GBP)
Thai Baht
US Dollars
British Pounds
42524262
22840507
Euro - Laser Card
Swedish Kronor
79585958
63734324
Swiss Franc's
Taiwanese New Dollar (settle in
GBP)
Thai Baht 13538292
26836383
12154121
E-commerce Refunds
US Dollars
British Pounds
Moto sales
52722722
26242846
47383563
13252322
46474647
53735373
72537363
93739383
83638251
23262028
Moto refunds
Australian Dollars
Danish Kroner
63836383
74846384
Australian Dollars
Danish Kroner
75857575
63736373
Euro - Laser Card
Hong Kong Dollars
Swedish Kronor
Swiss Franc's
Taiwanese New Dollar (settle in
GBP)
Thai Baht
US Dollars
British Pounds
63736387
75957595
74948494
51625171
76584575
62826282
84374847
23241911
Euro - Laser Card
Hong Kong Dollars
Swedish Kronor
Swiss Franc's
Taiwanese New Dollar (settle in
GBP)
Thai Baht
US Dollars
British Pounds
Typical set-up with Barclaycard Merchant Services,
34542872
53635396
25262522
86323242
12415161
86785744
56252425
25262526
5464543
Sterling sales
3637363
Sterling refunds
3738373
Multi Currency Sales
8474847
Multi currency refunds
Storeid’s for all payback requests is the same as the PaymentTrust Merchant ID ie
100625.
4-13
4.6 The Differences with Domestic Maestro and Solo
All Payment Transactions are relevant for switch and solo - Authorisation, Sale,
Forced Refund. The difference here is the MOP = DS, the Issuenumber and Startdate.
Following fields become mandatory for switch and solo transactions along with all other fields (See the API document for full detailed table);
Field Name
MOP
Data
Type
Alpha
Dat a
Siz e
Description
2 ‘DS' for Switch/Solo debit cards
Issue number stands for the number of cards issued on that bank account. Maximum of 2 between 1 and 99, however normally it's between 1 and 10.
Startdate Numeric Example “092003”
The additional error codes for switch and solo are;
2280 Incorrect start date congratulations
2282 Invalid issue number
Please note that all switch and solo transaction have to be sent in GBP sterling currency only. CurrencyID = 826.
‘Appendix D’ shows which switch/ solo card range need an issue number or a start date to process a transaction.
4.7 Response Codes
A full list of response codes can be found in the Developer’s guide. Enclosed here is a list of the common response codes.
Payment processing with acquiring bank (Streamline and Barclays)
2100 – Transaction Approved
2200 - Transaction Declined
2958 – Call Acquirer/Issuer
2614 - Acquirer/Issuer Unavailable
2210 – Invalid Credit card number
2212 – Card expired
2644 – Insufficient Terminal ID’s
Payback – Credit card
2050 – Request pending (successfully processed, will be processed in next batch)
2223 – No sort code and account number in the payback system
4-14
2219 – Not supported the card number is non UK
Please note, for transactions that go on-line in the case of RequestType’s A’s and S’s, if successful the transactions will received a response code 2100 transaction approved.
This is also the case for Switch/Solo refunds.
For transactions which are batched and processed at a later time, like refunds R’s or payback P’s then a successful response is 2050 – request pending.
Switch Refund request example;
Request
StringIn=VersionUsed^1~MerchantId^100625~TransactionType^PT~IsTest^1~Type ofSale^S~TimeOut^90~UserName^TMISUPPORT~UserPassword^tmisupport~Acct
Name^Alex~MOP^DS~AcctNumber^4936540000400016~ExpDate^122002~Curren cyId^826~Amount^1.00~RequestType^R~issuenumber^1~
Response
MerchantId^100625~TransactionType^PT~OrderNumber^5209075289~StrId^82744
20~PTTID^10414920~MOP^DS~CurrencyId^826~Amount^1.00~AuthCode^B01637
~RequestType^R~MessageCode^2100~Message^Transaction Approved
Visa card Refund request example;
Request
StringIn=VersionUsed^1~MerchantId^100625~TransactionType^PT~IsTest^1~Type ofSale^S~TimeOut^90~UserName^TMISUPPORT~UserPassword^tmisupport~Acct
Name^Alex~MOP^cc~AcctNumber^4779160330716625~ExpDate^122005~Currenc yId^826~Amount^1.00~RequestType^R~
Response
MerchantId^100625~TransactionType^PT~OrderNumber^536177545~StrId^827448
2~PTTID^10414921~MOP^CC~CurrencyId^826~Amount^1.00~RequestType^R~M essageCode^2050~Message^Request pending
Visa card Authorisation request example;
Request
StringIn=VersionUsed^1~MerchantId^100625~TransactionType^PT~IsTest^1~Type ofSale^S~TimeOut^90~UserName^TMISUPPORT~UserPassword^tmisupport~Acct
Name^Alex~MOP^cc~AcctNumber^4779160330716625~ExpDate^122005~Currenc yId^826~Amount^1.00~RequestType^A~
Response
MerchantId^100625~TransactionType^PT~OrderNumber^7470534577~StrId^82745
42~PTTID^10414923~MOP^CC~CurrencyId^826~Amount^1.00~AuthCode^B0466
F~RequestType^A~MessageCode^2100~Message^Transaction Approved
MasterCard Payback request example;
Request
4-15
StringIn=VersionUsed^1~MerchantId^100625~TransactionType^PT~IsTest^1~Type ofSale^S~TimeOut^90~UserName^TMISUPPORT~UserPassword^tmisupport~Acct
Name^Alex~MOP^cc~AcctNumber^5301207010000012~ExpDate^122005~Currenc yId^826~Amount^1.00~RequestType^P~Storeid^100625~
Response
MerchantId^100625~TransactionType^PT~OrderNumber^637464746~StrId^827448
2~PTTID^10414967~MOP^CC~CurrencyId^826~Amount^1.00~RequestType^R~M essageCode^2050~Message^Request pending
4-16
5. 3DS
ECURE WITH
P
AYMENT
T
RUST
5.1 What is 3DSecure?
3DSecure enables cardholders to authenticate themselves to their issuers through the use of a unique, personal code. It’s an industry wide initiative that is being undertaken in order to address current consumer concerns about security of online shopping. This includes Verified By Visa and MasterCard Secure Code.
A Typical 3DSecure Transaction using PaymentTrust’s
Hosted MPI
Customer confirms his purchase. A form is posted to the merchant’s commerce application (php, asp, jsp, cold fusion etc.)
5.2 Merchant application requests via STLink for 3D
Secure enrolment verification. (RequesType V)
Customer
Browser
Customer's
Bank
INTERNET
1
STLink
2
Merchant
Commerce
Application a. If enrolment response is successful (CHEnrolled = Y). See Step 5.3.
5-17
b. If enrolment verification failed based on the 3D Secure CHEnrolled value, the merchant sends an authorization as follows.
MasterCard CHEnrolled VISA
N Merchant sends authorization request with 3D Secure fields.
ECI: 06
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant sends authorization request with 3D Secure fields.
ECI: N/A
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
U
N/A
Merchant sends authorization request with 3D Secure fields.
ECI: 07
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant can decide to send authorization request with 3D
Secure fields.
ECI: 07
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant sends authorization request with 3D Secure fields.
ECI: N/A
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant can decide to send authorization request with 3D
Secure fields.
ECI: N/A
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
5.3 Enrolment response contains customers issuing bank
URL. The merchant application instructs customer’s browser to redirect to the provided URL.
Note 1: This is typically done through hidden form fields and JavaScript that automatically posts the form to the bank URL.
Note 2: The merchant session is re-established as follows. When the merchant application instructs the browser to redirect, there are 2 hidden form fields TermUrl and MD (Merchant Data). The TermUrl tells the issuing bank where to POST back the results. The MD field may contain any value the merchant may require to establish back the session. Before placing any sensitive data in the MD field it must be encrypted.
5-18
Customer
Browser
Customer's
Bank
INTERNET
1 3
STLink
2
Merchant
Commerce
Application
See Step 5.4.
5.4 Browser redirects to customer’s issuing bank URL including the TermUrl and MD fields. Customers attempt to authenticate themselves by answering their challenge question or entering their pin
Customer
Browser
Customer's
Bank
4
INTERNET 1 3
STLink
2
Merchant
Commerce
Application
See Step 5.5.
5-19
5.5 Authentication result is posted back to merchant’s commerce application.
Note 1: In Step 5.3, one of the hidden form fields (TermUrl) contains a merchant assigned URL that is used to receive the authentication response.
Note 2: The MD field will also be posted back as a hidden form field. This is the data the merchant opted to include during Step 5.3.
Customer
Browser
Customer's
Bank
4
INTERNET 1 3 5
STLink
2
Merchant
Commerce
Application
See Step 5.6.
5.6 Merchant’s application requests via STLink for
validity of the authentication response. (RequesType
A)
a) If authentication succeeded (customer answered challenge correctly). See Step 5.7. b) If authentication failed based on the 3D Secure TXStatus value, the merchant may be able to send an authorization.
5-20
STLink
Customer's
Bank
INTERNET
4
Customer
Browser
1 3 5
2
6
Merchant
Commerce
Application
5-21
TXStatus
N
A
U
N/A
VISA
Merchant must not send authorization and decline customer’s purchase.
See Step 5.8.
Merchant sends authorization request with 3D Secure fields.
ECI: 06
CAV: Send if available.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant can decide to send authorization.
ECI: 07
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant must not send authorization and decline customer’s purchase.
See Step 5.8.
MasterCard
Merchant must not send authorization and decline customer’s purchase.
See Step 5.8.
Merchant sends authorization request with 3D Secure fields.
ECI: 01
CAV: Send if available.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant can decide to send authorization.
ECI: N/A
CAV: N/A.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 5.8.
Merchant must not send authorization and decline customer’s purchase.
See Step 5.8.
5.7 Merchant’s application prepares a standard auth/sale with provided 3D Secure fields: ECI, CAV, SecureId and sends a request to STLink.
5-22
Customer's
Bank
INTERNET
4
Customer
Browser
1 3 5
STLink
TXStatus
Y
2
6
7
Merchant
Commerce
Application
VISA
Merchant sends authorization request with 3D Secure fields.
ECI: 05
CAV: Send if available.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 8.
MasterCard
Merchant sends authorization request with 3D Secure fields.
ECI: 02
CAV: Send if available.
SecureId: SecureId submitted to
MPI during enrolment verification.
See Step 8.
5-23
5.8 A receipt page is returned to the customer with accepted or declined message.
Customer
Browser
Customer's
Bank
4
INTERNET
1 3 5 8
STLink
2
6
7
Merchant
Commerce
Application
5-24
6. B
ANK
I
DENTIFICATION
T
ABLE
(BIN) T
ABLE
To down load the latest BIN table go to the following URL https://www.trustmarque.ca/Paymenttrust1.2-Live/BINSDownload/
And type in the username and password (If asked), below;
Username: support
Password:tmicsupport
Right click on tmibin.csv
A pop up window appears click on save
Change the file extension from csv to txt and then click save to your desired location.
It will take approximately 4 minutes to download and will be a 7 MB file. The BIN table may be downloaded as often as required. PaymentTrust will update the table weekly on a
Wednesday, at 8.00am GMT. PaymentTrust will erase all BINs on this day and upload the new table from NatWest. Therefore there is no update just a complete replace.
6.1 Screenshot of data (csv format)
Below is a screenshot showing the fields of data provided. The list is CardBIN1, CardBin2,
CardName, CardType and CountryCode.
6-25
6.2 Screenshot of data (txt format)
6-26
7. URL’
S AND
T
OOLS
All Test and Live transaction system
Primary
https://stn01.sectranet.com/stlinkssl/stlink.dll
? https://stn01.sectranet.com/stlinkssl/stlinkbatch.dll
? (Batch)
Secondary
https://stl007.kontek.cc/stlinkssl/stlink.dll
? https://stl007.kontek.cc/stlinkssl/stlinkbatch.dll
? (Batch)
RG Test website
https://merchantadmin.riskguardian.com/test/
PT Test website
https://merchantadmin.paymenttrust.com/test/
7-27
8. A
PPENDIX
I – RG S
ET
-
UP
F
ORM
PaymentTrust Ltd
Sales Representative
Product Profile:
What products are sold?
Do you provide hard, digital or service goods?
Identifier (PTMID)
Please provide details of accepted currencies and associated values.
Are the majority of sales to male or females?
How often will a consumer buy on average?
Do you require the consumer to register?
Will registration i.e. length of membership be passed to RG?
Do you require consumers to use a wallet/account?
8-28
How long does it take to refill the wallet/account:
Have you experienced any fraud problems? Please provide details below
Which countries do you sell to?
Which countries do you not wish to sell to?
Which countries have you experienced problems?
Algeria DZ
American AS
Samoa
Andorra AD
Angola AO
Anguilla AI
Antarctica AQ
Antigua and
Barbuda
AG
Argentina AR
Armenia AM
Aruba AW
Australia AU
Austria AT
Azerbaijan AZ
Bahamas BS
Bahrain BH
Bangladesh BD
Barbados BB
Belarus BY
Belgium BE
Belize BZ
Benin BJ
Bermuda BM
Bhutan BT
Bolivia BO
Bosnia and BA
Herzegovina
Botswana BW
Bouvet Island BV
8-29
Brazil BR
British Indian
Ocean
IO
Territory
Brunei BN
Darussalam
Bulgaria BG
Burkina Faso BF
Burundi BI
Cambodia KH
Cameroon CM
Canada CA
Cape Verde
Cayman
CV
KY
Islands
Central
African
CF
Republic
Chad TD
Chile CL
China CN
Christmas
Island
(Australia)
CX
Cocos
(Keeling)
CC
Islands
Colombia CO
Comoros KM
Congo CG
Cook Islands
Costa Rica
CK
CR
Cote D'Ivoire
(Ivory Coast)
Croatia
(Hrvatska)
CI
HR
Cuba CU
Cyprus CY
Czech
Republic
CZ
Denmark DK
Djibouti DJ
Dominica DM
Dominican
Republic
DO
8-30
East Timor TP
Ecuador EC
Egypt EG
El Salvador SV
Equatorial
Guinea
GQ
Eritrea ER
Estonia EE
Ethiopia ET
Faeroe Islands FO
Falkland
Islands
FK
(Malvinas)
Fiji FJ
Finland FI
France FR
French Guiana
French
Polynesia
GF
PF
Gabon GA
Gambia GM
Georgia GE
Germany DE
Ghana GH
Gibraltar GI
Great Britain GB
Greece GR
Greenland GL
Grenada GD
Guadeloupe GP
Guam GU
Guatemala GT
Guinea GN
Guinea Bissau GW
Guyana GY
Haiti HT
Honduras HN
Hong Kong HK
Hungary HU
Iceland IS
India IN
Indonesia ID
Iran IR
Iraq IQ
Ireland IE
8-31
Isle of Man IM
(U.K.)
Israel IL
Italy IT
Jamaica JM
Japan JP
Johnston
Island
JT
Jordan JO
Kazakhstan KZ
Kenya KE
Kiribati KI
Korea (North)
Korea (South)
KP
KR
Kuwait KW
Kyrgyzstan KG
Lao P.Dem.R. LA
Latvia LV
Lebanon LB
Lesotho LS
Liberia LR
Libyan Arab
Jamahiriya
LY
Liechtenstein LI
Lithuania LT
Luxembourg LU
Macau MO
Macedonia MK
Madagascar MG
Malawi MW
Malaysia MY
Maldives MV
Mali ML
Malta MT
Marshall MH
Islands
Martinique MQ
Mauritania MR
Mauritius MU
Mexico MX
Micronesia FM
Midway
Islands
MI
Moldova MD
Monaco MC
8-32
Mongolia MN
Montserrat MS
Morocco MA
Mozambique MZ
Myanmar MM
Namibia NA
Nauru NR
Nepal NP
Netherlands NL
Netherlands
Antilles
AN
New Caledonia
New Zealand
NC
NZ
Nicaragua NI
Niger NE
Nigeria NG
Niue NU
Norfolk Island NF
MP Northern
Mariana
Islands
Norway NO
Oman OM
Pakistan PK
Palau PW
Panama PA
Papua New
Guinea
PG
Paraguay PY
Peru PE
Philippines PH
Pitcairn PN
Poland PL
Portugal PT
Puerto Rico PR
Qatar QA
Reunion RE
Romania RO
Russian
Federation
RU
Rwanda RW
Saint Helena SH
KN Saint Kitts and
Nevis
Saint Lucia LC
8-33
Saint Pierre and Miquelon
Saint Vincent
PM
VC and The
Grenadines
Samoa WS
San Marino SM
Sao Tome and
Principe
ST
Saudi Arabia SA
Senegal SN
Seychelles SC
Sierra Leone SL
Singapore SG
Slovakia SK
Slovenia SI
Solomon
Islands
SB
Somalia SO
South Africa ZA
Spain ES
Sri Lanka LK
Sudan SD
Suriname SR
Svalbard and SJ
Jan Mayen
Islands
Swaziland SZ
Sweden SE
Switzerland CH
Syrian Arab
Rep.
SY
Taiwan TW
Tajikistan TJ
Tanzania TZ
Thailand TH
Togo TG
Tokelau TK
Tonga TO
Trinidad and
Tobago
TT
Tunisia TN
Turkey TR
Turkmenistan TM
Turks and TC
8-34
Caicos Islands
Tuvalu TV
Uganda UG
Ukraine UA
United Arab
Emirates
AE
United States US
Uruguay UY
Uzbekistan UZ
Vanuatu VU
Vatican City
State (Holy
VA
See)
Venezuela VE
Viet Nam
Virgin Islands
(British)
VN
VG
VI Virgin Islands
(US)
Wake Island WK
WF Wallis and
Futuna Islands
Western
Sahara
EH
Yemen YE
Yugoslavia YU
Zaire ZR
Zambia ZM
Zimbabwe ZW
8-35
9. A
PPENDIX
II – P
AY
B
ACK
(C
REDIT
C
ARD
) S
ET
-
UP
F
ORM
Merchant Name
………………………………………………………………………………………………
Bank Sort Code
………………………………………………………………………………………………
Account Number
………………………………………………………………………………………………
File Name
………………………………………………………………………………………………
BACS User Number
………………………………………………………………………………………………
..
Originator’s Reference
……………PaymentTrust………………………………………………………………….
9-36
10. A
PPENDIX
III – PT A
CQUIRING
S
ET
-
UP
F
ORM
PaymentTrust Ltd
Sales Representative Identifier (TMID)
Merchant Acquiring Bank Name
Merchant ID:
Credit & Debit Cards Accepted
2
Visa
Visa (Purchasing)
Master Card
Maestro
JCB
Switch/ Solo
Delta
Electron
American Express *
*American Express/Diners separate authorisations are required for these credit cards see PPD for latest information
Trading Currencies
Please list all the currencies that you currently trade in.
Currencies;
10-37
11. A
PPENDIX
IV – D
OMESTIC
M
AESTRO AND
S
OLO
B
INS
Country
Code
633300000 633300999 SWITCH SW GB
633301000 633301999 SWITCH SW GB
633302000 633302999 SWITCH SW GB
633303000 633303999 SWITCH SW GB
633304000 633304999 SWITCH SW GB
CardIssuer
HSBC
ROYAL BANK OF
633311000 633311999 SWITCH SW GB
633312000 633312999 SWITCH SW GB
ROYAL BANK OF
633450000 633450999 SOLO SW GB
ROYAL BANK OF
633451000 633451999 SOLO SW GB
ROYAL BANK OF
633452000 633452999 SOLO SW GB
ROYAL BANK OF
SCOTLAND 633453000 633453999 SOLO
633454000 633454999 SOLO
633455000 633455999 SOLO
633456000 633456999 SOLO
633457000 633457999 SOLO
633461000 633461999 SOLO
SW GB
SW GB
SW GB
SW GB
SW GB
SW GB HSBC
CLYDESDALE BANK
633473000 633473999 SOLO
633476000 633476999 SOLO
SW GB
SW GB
CLYDESDALE BANK
PLC 633478000 633478999 SOLO
633481000 633481999 SOLO
633490000 633490999 SOLO
633491000 633491999 SOLO
633492000 633492999 SOLO
633493000 633493999 SOLO
SW GB
SW GB
SW GB
SW GB
SW GB
SW GB
CLYDESDALE BANK
633494000 633494999 SOLO
633495000 633495999 SOLO
633496000 633496999 SOLO
633497000 633497999 SOLO
633498000 633498999 SOLO
SW GB
SW GB
SW GB
SW GB
SW GB
633499000 633499999 SOLO
671850000 671850999 SWITCH
671851000 671851999 SWITCH
671852000 671852999 SWITCH
671853000 671853999 SWITCH
671854000 671854999 SWITCH
671855000 671855999 SWITCH
SW
SW
SW
SW
SW
SW
SW
GB
GB
GB
GB
GB
GB
GB
671856000 671856999 SWITCH SW GB
675901000 675901999 SWITCH SW GB
675905000 675905999 SWITCH SW GB
HALIFAX
HALIFAX
HALIFAX
NATWEST
CLYDESDALE BANK
PLC
NATWEST
Card
Length
IssueNo
Length
16 0
19 1
16 0
16 0
16 0
IssueNo
Required
N
Y
N
N
N
StartDate
Required
Y
N
Y
Y
Y
16 0
16 0
16 0
16 0
16 0
16 0
18 1
19 1
18 1
19 1
16 1
16 1
16 1
16 1
16 2
16 2
16 2
19 1
18 1
0
0
0
0
0
0
0
19 1
19 1
N
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
Y
Y
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
N
11-38
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
N
N
675906000 675906999 SWITCH SW GB
675907000 675907999 SWITCH SW GB
675908000 675908999 SWITCH SW GB
675909000 675909999 SWITCH SW GB
675910000 675910999 SWITCH SW GB
675918000 675918999 SWITCH SW GB
675938000 675938999 SWITCH SW GB
675939000 675939999 SWITCH SW GB
675940000 675940999 SWITCH SW GB
675950000 675950999 SWITCH SW GB
675951000 675951999 SWITCH SW GB
675952000 675952999 SWITCH SW GB
675953000 675953999 SWITCH SW GB
675954000 675954999 SWITCH SW GB
675955000 675955999 SWITCH SW GB
675956000 675956999 SWITCH SW GB
675957000 675957999 SWITCH SW GB
675958000 675958999 SWITCH SW GB
675959000 675959999 SWITCH SW GB
675960000 675960999 SWITCH SW GB
675961000 675961999 SWITCH SW GB
675962000 675962999 SWITCH SW GB
675963000 675963999 SWITCH SW GB
675964000 675964999 SWITCH SW GB
675965000 675965999 SWITCH SW GB
675966000 675966999 SWITCH SW GB
675967000 675967999 SWITCH SW GB
675968000 675968999 SWITCH SW GB
675969000 675969999 SWITCH SW GB
675970000 675970999 SWITCH SW GB
675971000 675971999 SWITCH SW GB
675972000 675972999 SWITCH SW GB
675973000 675973999 SWITCH SW GB
675982000 675982999 SWITCH SW GB
675995000 675995999 SWITCH SW GB
675996000 675996999 SWITCH SW GB
675998000 675998999 SWITCH SW GB
676701000 676701999 SOLO
676703000 676703999 SOLO
676705000 676705999 SOLO
676706000 676706999 SOLO
676707000 676707999 SOLO
SW
SW
SW
SW
SW
GB
GB
GB
GB
GB
676708000 676708999 SOLO SW GB
676709000 676709999 SOLO SW GB
CLYDESDALE BANK
PLC
CLYDESDALE BANK
PLC
NATWEST
NATWEST
HSBC
HALIFAX
HALIFAX
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
SCOTLAND
HALIFAX
HALIFAX
HALIFAX
HALIFAX
HALIFAX
NATWEST
HSBC
HSBC
HSBC
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
SCOTLAND
ROYAL BANK OF
ROYAL BANK OF
SCOTLAND 16 0
16 0
16 0
16 0
16 0
16 0
16 0
16 0
19 1
19 1
18 1
19 1
16 2
16 2
16 0
16 0
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
16 0
16 0
16 0
16 0
16 0
19 1
18 1
18 1
18 1
19 1
16 0
16 0
16 0
16 0
16 0
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
Y
Y
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
11-39
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
N
N
N
N
N
Y
Y
Y
Y
Y
676710000 676710999 SOLO
676779000 676779999 SOLO
676782000 676782999 SOLO
SW GB
676711000 676711999 SOLO SW GB
676712000 676712999 SOLO SW GB
676713000 676713999 SWITCH SW GB
676714000 676714999 SWITCH SW GB
676715000 676715999 SOLO SW GB
676718000 676718999 SOLO
676740000 676740999 SOLO
676750000 676750999 SOLO
676751000 676751999 SOLO
676752000 676752999 SOLO
676753000 676753999 SOLO
SW
SW
SW
GB
GB
GB
SW GB
SW GB
SW GB
676754000 676754999 SOLO
676755000 676755999 SOLO
676756000 676756999 SOLO
676757000 676757999 SOLO
676758000 676758999 SOLO
676759000 676759999 SOLO
676760000 676760999 SOLO
676761000 676761999 SOLO
676762000 676762999 SOLO
676770000 676770999 SOLO
SW GB
SW GB
SW
SW
SW
SW
GB
SW GB
SW GB
GB
SW GB
SW GB
GB
GB
676774000 676774999 SOLO SW GB
SW
SW
GB
GB
SW GB
SW GB
676795000 676795999 SOLO
676798000 676798999 SOLO
ROYAL BANK OF
ROYAL BANK OF
SCOTLAND
NATWEST
HSBC
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
NATWEST
CLYDESDALE BANK
CLYDESDALE BANK
CLYDESDALE BANK
CLYDESDALE BANK
NATWEST
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
19 1
16 0
16 0
16 0
16 0
16 0
19 1
18 1
19 1
19 1
19 1
19 1
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
19 1 Y N
11-40
12. A
PPENDIX
V:
MESSAGE
/
RESPONSE CODES
The following list reflects all currently defined RiskGuardian response codes. One of the following codes is returned with each transaction that is submitted into the RiskGuardian system. Many of these codes will never be returned in your output.
Message Code Description
100 Ok
200 Transaction does not exist
300 Field(s) (Basic)
301
302
303
Field(s) Missing (Transaction Specific)
Wrong MerchantId, User Name or Password
DB/System undefined errors or packet loss during transmission - Please send again
Time out during Transmission - Please send again 304
305
306
307
HTTP(S) method not supported – Please call support
Batch Transmission Error - Failed to write to file
Invalid document or Wrong XML Format
401
402
500
900
Wrong Format (Transaction Specific)
(GP) Wrong Format or Parameter(s) Missing
Transaction Type not Supported
Security ERROR - Please call Support
PaymentTrust Result Codes
ST – Streamline
BMS – Barclays
LY – Lloyds
PH – PaymentTech
PT – PaymentTrust
EC – EuroConnex
PN – Pacnet
NT – Neteller
P2 – Pay2
FS – Swedish Acquirer
BV – Bank of Valleta
FX – Foreign Exchange
3D – 3DSecure Verification/Authentication
NA – Not applicable to any Acquirer
Message
Code
Description Explanation
Acquirer
12-41
Message
Code
2000
2001
2040
2050
2051 Request Pending with
Errors.
2053 Notification Received
2100 Transaction
Authorized/Approved
2101 Validated
2102 Verified
2103 Prenoted
2104
2105
Description
No answer
Dropped the transaction
Pending to be finalized
Request pending
Transaction approved
Notification Cleared successfully successfully
Explanation
Received no answer from banking network. Resend transaction.
No need to do this transaction
Request submitted and waiting for processing to be completed next cycle.
Request submitted and waiting for processing to be completed next cycle.
Cannot find the BTID for the original request
Notification Received
Transaction Authorized/Approved
Validated
Verified
Prenoted
Transaction was approved - Base 24
Notification Cleared
Deposit request previously submitted has been processed successfully
Refund request previously submitted has been processed successfully
Cancellation request has been processed successfully
Transaction Declined/Not Authorized/Not Settled
Cancellation Declined by Acquirer
Acquirer
PH
NA
ALL
ALL
PN
PN
ALL
NA
NA
NA
NA
PN
NA
NA
PT successfully
2200 Transaction Declined
2202 Cancellation Declined
ALL
LY
2203 Cancellation cannot be performed.
2204 Soft AVS
Cancellation transaction failed. PT
2206 Invalid currency
Card was authorized but AVS did not match.
Contact client.
Incoming record currency type does not match system stored currency
PH
PT
Invalid merchant account number PT number
2210 Invalid credit card number Bad check digit, length, or other credit card problem PT expiration date
Credit card has expired or incorrect date entered.
Confirm date.
2214 Credit card expired Credit card has expired
PT, EC,
LY, PH and
BV
AX, FS, LY and PH
PT 2216 Invalid amount Amount sent was 0 or unreadable
2218 Invalid method of payment Method of payment is invalid for this account number
The specific credit card will not accept payment. this transaction
2220 Invalid method of payment for merchant account number
2222 Invalid field data
Method of payment is invalid for this merchant
Invalid information entered
PT
BACS
PT
LY and PH
2223 No Sort code or Account
Number in Payback system
No Sort code or Account Number in Payback system
BACS
12-42
Message
Code
Description
2224 Data is inaccurate or missing
2226 Duplicated transaction
2228 Invalid transaction
2229 Invalid transaction number
2234 Invalid response code
Entered
2237 Invalid refund not allowed
(CFT)
2238 Invalid for debit
2240 Invalid SEC code - Amex
2280 Incorrect start date
2282 Invalid issue number
2284 Invalid transaction
2286 Bank not supported by
Switch
2300 Card does not exist number (ABA code)
2304 Missing name
2306 Bank account closed
2308 Invalid account type
2310 Account does not exist
2312 No account
2314 Account holder deceased
2316 Beneficiary deceased
2318 Account frozen
2320 Customer opt out
2322 ACH non-participant
2324 Invalid account number
2326 Authorization revoked by customer
Explanation
Specific and relevant data within transaction is inaccurate or missing
Same transaction had been submitted
Issuer does not allow this transaction
Processor permits only one deposit request per authorization
Invalid merchant account number
Acquirer
PT
FS, PH and
BV
PT
PT
AX
Invalid response code
Currency code submitted is different than code submitted with original authorization request
Invalid for credit
Invalid refund not allowed (CFT)
Invalid for debit
Amex CID is incorrect
Switch/Solo - Incorrect start date or requires an issue number. Please correct
Switch/Solo - 1-digit number submitted when 2-digit number should have been sent. Please correct
Switch/Solo - a format issue, re-examine transaction layout. Please correct
Bank not supported by Switch
FS
PH
PH
PH
LY, BC,
ST, FS
PH
PH
PH, BMS,
ST and LY
PH, BMS,
ST and LY
PH, BMS,
ST and LY
PH
No card record
Invalid bank routing number
NA
PH
Missing the check writer’s name.
Bank account has been closed
Account type is invalid or missing. Deposit transactions only
Account does not exist
Account number does not correspond to the individual
Account holder deceased. No further debits will be accepted by the bank
Beneficiary deceased. No further debits will be accepted by the bank
The funds in this account are unavailable. No further debits will be accepted by the bank
Customer has refused to allow the transaction
Banking institute does not accept ACH transactions
(For US ECP)
Account number is incorrect
Customer has notified their bank not to accept these transactions
PH
PH
PH
PH
PH
PN
NA
NA
NA
PH
FS, LY,
NT, P2 and
PH
PH
12-43
Message
Code
Description
2328 Customer advises not authorized
2330 Invalid CECP action code
Explanation
Customer has not authorized bank to accept these transactions
Pertains to Canadian ECP only. format
Format of account number does not pass check digit routine for that institution. (For CDN ECP)
2334 Bad account number data Invalid characters in account number
2350 Card surpassed daily limit Card has surpassed daily transaction amount limit
2352 Times card used limit
2354 Over credit limit
The limit of number of times used for the card has been surpassed
Card has surpassed its credit limit
2356 Enter lesser amount Enter a lesser amount
2358 No credit amount
2360 One purchase limit
2362 Over Sav limit
2364 Over Sav frequency.
2366 Card not supported
2368 Invalid PIN.
No credit amount
Card is limited to one purchase
Over Sav limit
Over Sav frequency.
Card not supported
Invalid PIN
2370 Allowable PIN tries exceeded.
2372 PIN required
Allowable PIN tries exceeded
PIN required
2374 Card failed MOD 10 check Card failed MOD 10 check verification
2380 On negative file Account number appears on negative file
2382 Stop Payment Issued Stop Payment Issued
2402 Unable to process transaction
2403 Duplicate transaction
2404 Cutoff in progress
2405 Incorrect PIN
2406
2611
PIN tries exceeded frequency
2410 Invalid 3D Secure Data
2610 Timeout error
Timeout error down or unavailable
Resend
Unable to process transaction
Duplicate transaction
Cutoff in progress
Incorrect PIN
PIN tries exceeded
Exceeds withdrawal frequency
Invalid 3D Secure Data
Timeout waiting for host response
Internal timeout bank, which issued the card or Acquirer.
BV
BV
LY, PH and
BV
PN
BV
NA
NA
LY
PN
FS, LY, NT and BV
FS and LY
FS and LY
BMS, ST and LY
FS, AX,
BV, ST and
LY
PT
BV
BMS. ST,
LY, EC, AX and PH
LY and PH
Acquirer
PH
PH
PH
PH
PH
PH
LY and PH
NA
NA
PH
BV
PH
LY
EC, FS and
PH
PH and BV
12-44
Message
Code
2618
2620
2622
Description
Unidentified error
Unable to process.
Unable to authorize. incomplete
2627 Invalid track2 data
2628 Transaction not supported Merchant not Support this transaction
2630 Invalid store ID
2634 Invalid format
2636 Invalid message type
2638 Invalid POS system type
2640 This transaction has been cancelled
2642 This TrxSource is not supported by the bank
2644 Insufficient Terminal IDs, please try again
2700 Invalid file
2702 Amounts do not compute
2704 Line items do not add up to summary total
2706 Not supported for batch
2712 Mandatory field is invalid or missing
2714 Total line items do not add up
2716 Line items missing
2718 Commodity code is invalid or missing
2720 Cross border information is invalid or missing
2722 Invalid purchase card number
2802 Invalid ICC parameter.
2952 Pick up card
Unidentified error. Unable to process transaction
Unable to process transaction due to system malfunction
Unable to authorize due to system malfunction
Merchant information incomplete
Invalid CVN value
The track2 format information is incorrect
No such store ID for the merchant
Invalid format
Invalid message type
Invalid POS system type
A message has be sent to reverse previous time out transaction
This TrxSource is not supported by the bank PT
Not enough terminal ID at the time of transaction
General error for PC card
Amount is invalid
Line items do not add up to summary total
Not supported for batch
Mandatory field is invalid or missing
Total line items do not add up
Line items missing
Not a purchase card
Explanation
Commodity code is invalid or missing
Cross border information is invalid or missing
One of the ICC parameters submitted was invalid.
Card issuer wants card returned. Call issuer
Acquirer
BMS, ST,
PH and BV
FS, LY and
BV
LY and BV
NT and P2
FS and LY
PT
LY
PT
NA
AX and LY
NA
NA
AX and LY
ST
NA
PT
PT
PT
PT
PT
NA
AX
PT
PT
2954
2956
2958
2960
2962
Card stolen
Do not honour
Call Bank
Insufficient funds
CVV2 failure
Card reported as lost/stolen
Generic decline. No other information is being provided by the issuer
Issuer wants voice contact with cardholder
Insufficient funds
Issuer has declined request because CVV2 edit failed
PT
EC, LY, PH and BV
FS, LY, PH and BV
FS, LY and
PH
AX, ST,
BMS, EC,
FS, LY, BV and PH
FS, LY,
NT, P2 and
PH
LY and PH
12-45
Message
Code
Description
2964 Delinquent account.
2990 Cancellation
Explanation
Delinquent account
Cancellation is going to reverse the authorization
A new rate is assigned for the transaction
Acquirer
BV
NA
FX
FX rate escalated
3111 Rate escalated Transaction rate escalated
Transaction cancelled successfully
FX
FX
FX successfully
3200
3203
Rate expired
Cancellation cannot be performed
3204 Cancellation not enabled
3207 Exchange currency not supported
Conversion to same currency redundant
ConvertedCurrencyId
3209 Currency pair not supported Cannot convert to requested currency
3210 CurrencyId does not match
FX request
Rate requested has expired and no new rate is available
The deposit/refund transaction being cancelled cannot be because it has already been submitted
Cancellation disabled in merchant set-up
Invalid currency of record
Exchange currency not setup in merchant account
Currency submitted does not match the original rate request
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX 3218 Issuer is not available.
Please try again
Unexpected error
Credit card is not valid for this transaction this transaction
3220 Currency Not Supported
3224 Data is inaccurate or missing
3226 Duplicated transaction
3228 Invalid transaction
3321 Invalid account data
3341 Non-executable rate
3354 Refund amount over limit
4050 Cardholder enrolled
4100 Cardholder authenticated
4200 Cardholder not enrolled
Currency of card not supported
One or more required parameters are not present
Duplicated transaction
Generic error message for invalid transactions
Invalid account data
Quoted rate is not executable
Refund is over the original value of the deal
Quoted rate is invalid
3362 Rate expired not escalated Expired rate cannot be escalated
3371 Rate revoked Rate has been revoked
Transaction min/max limits reached amount limit
3391 Batch size exceeds the maximum allowed
3614 FX system unavailable
3781
Refund not enabled
3783 Refund not possible
3785 Refund period expired
Batch size exceeds the Maximum allowable size transaction/payment not written to database
FX system cannot be reached
Refund disabled in merchant set-up
Refund cannot be processed
Refund period expired
Cardholder enrolled for 3D Secure
Cardholder answered password/challenge question correctly
Cardholder not enrolled for 3D Secure
FX
FX
FX
FX
3D
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
FX
3D
3D
12-46
Message
Code
Description
4202 Card not participating in 3D
Secure
Explanation
Credit card is not recognized as a 3D Secure card authenticated
Cardholder failed to answer password/challenge question
Invalid currency
Invalid merchant setup. Please call support.
Please call support.
Invalid merchant account number number
4210 Invalid credit card number Invalid credit card number
Invalid credit card expiration date expiration date
4224 Data is inaccurate or missing
Specific and relevant data within transaction is inaccurate or missing
4240 Cardholder enrolment failed Enrolment process failed
Authentication process failed failed
4614 MPI not available
4616 Directory server not available
MPI not available
Directory server not available
4618 Internal MPI error Internal MPI error
3D
3D
3D
3D
3D
3D
3D
3D
3D
Acquirer
3D
3D
3D
3D
3D
3D
3D
12-47
13. A
PPENDIX
VI:
CURRENCY CODES
The ability to accept new currencies will enable you to attract a larger customer base.
Processing in multiple currencies eliminates your customers’ foreign exchange risks and issues, which typically stem from local charges to foreign credit cards. PaymentTrust
TM currently processes Visa®, Master Card®, and American Express® transactions in the following currencies:
Country Name
Count ry
Code
Currency Name
Currency
ID
Currency Code
AUSTRALIAN AUD
CZECH REPUBLIC
EUROPEAN UNION
CZE
EUR
CZECH KORUNA
EURO
203
978
CZK
EUR
FRENCH POLYNESIA PYF CFP FRANC 953 XPF
DEUTSCHE DEM
HONG KONG HKG HONG KONG DOLLAR 344 HKD
HUNGARY HUN HUF
ICELAND ISK
JAPAN JPN JPY
KOREA, REPUBLIC OF KOR WON 410 KRW
KUWAITI KWD
NEW ZEALAND
MOROCCAN MAD
NZL NEW ZEALAND DOLLAR 554 NZD
PORTUGAL
RUSSIAN FEDERATION
SAUDI ARABIA
SOUTH AFRICA
QATARI QAR
RUS RUSSIAN RUBLE
SAU SAUDI RIYAL
643
682
RUB
SAR
ZAF RAND 710 ZAR
13-48
Country Name
Count ry
Code
Currency Name
Currency
ID
Currency Code
UNITED ARAB EMIRATES (UAE)
UNITED KINGDOM
UNITED STATES OF AMERICA
TURKISH TRL
ARE UAE DIRHAM
GBR POUND STERLING
USA US DOLLAR
784
826
840
AED
GBP
USD
13-49
14. A
PPENDIX
VII:
COUNTRY CODES
Country Name ISO Country Code
Afghanistan AF
Albania AL
Algeria DZ
American Samoa AS
Andorra AD
Angola AO
Anguilla AI
Antarctica AQ
Antigua and Barbuda AG
Argentina AR
Armenia AM
Aruba AW
Australia AU
Austria AT
Azerbaijan AZ
Bahamas BS
Bahrain BH
Bangladesh BD
Barbados BB
Belarus BY
Belgium BE
Belize BZ
Benin BJ
Bermuda BM
Bhutan BT
Bolivia BO
Bosnia and Herzegovina BA
Botswana BW
Bouvet Island BV
Brazil BR
British Indian Ocean Territory IO
Brunei Darussalam BN
Bulgaria BG
Burkina Faso BF
Burundi BI
Cambodia KH
Cameroon CM
Canada CA
14-50
Country Name ISO Country Code
Cape Verde
Cayman Islands
CV
KY
Central African Republic CF
Chad TD
Chile CL
China CN
Christmas Island (Australia) CX
Cocos (Keeling) Islands CC
Colombia CO
Comoros KM
Congo CG
Cook Islands CK
Costa Rica CR
Cote D'Ivoire (Ivory Coast)
Croatia (Hrvatska)
CI
HR
Cuba CU
Cyprus CY
Czech Republic CZ
Denmark DK
Djibouti DJ
Dominica DM
Dominican Republic
East Timor
DO
TP
Ecuador EC
Egypt EG
El Salvador SV
Equatorial Guinea GQ
Eritrea ER
Estonia EE
Ethiopia ET
Faeroe Islands FO
Falkland Islands (Malvinas) FK
Fiji FJ
Finland FI
France FR
French Guiana GF
French Polynesia PF
Gabon GA
Gambia GM
Georgia GE
Germany DE
Ghana GH
Gibraltar GI
14-51
Country Name ISO Country Code
Great Britain GB
Greece GR
Greenland GL
Grenada GD
Guadeloupe GP
Guam GU
Guatemala GT
Guinea GN
Guinea Bissau GW
Guyana GY
Haiti HT
Honduras HN
Hong Kong HK
Hungary HU
Iceland IS
India IN
Indonesia ID
Iran IR
Iraq IQ
Ireland IE
Isle of Man (U.K.) IM
Israel IL
Italy IT
Jamaica JM
Japan JP
Johnston Island JT
Jordan JO
Kazakhstan KZ
Kenya KE
Kiribati KI
Korea (North) KP
Korea (South) KR
Kuwait KW
Kyrgyzstan KG
Lao P.Dem.R. LA
Latvia LV
Lebanon LB
Lesotho LS
Liberia LR
Libyan Arab Jamahiriya LY
Liechtenstein LI
Lithuania LT
Luxembourg LU
14-52
Country Name ISO Country Code
Macau MO
Macedonia MK
Madagascar MG
Malawi MW
Malaysia MY
Maldives MV
Mali ML
Malta MT
Marshall Islands MH
Martinique MQ
Mauritania MR
Mauritius MU
Mexico MX
Micronesia FM
Midway Islands MI
Moldova MD
Monaco MC
Mongolia MN
Montserrat MS
Morocco MA
Mozambique MZ
Myanmar MM
Namibia NA
Nauru NR
Nepal NP
Netherlands NL
Netherlands Antilles AN
New Caledonia
New Zealand
NC
NZ
Nicaragua NI
Niger NE
Nigeria NG
Niue NU
Norfolk Island NF
Northern Mariana Islands MP
Norway NO
Oman OM
Pakistan PK
Palau PW
Panama PA
Papua New Guinea PG
Paraguay PY
Peru PE
14-53
Country Name ISO Country Code
Philippines PH
Pitcairn PN
Poland PL
Portugal PT
Puerto Rico PR
Qatar QA
Reunion RE
Romania RO
Russian Federation RU
Rwanda RW
Saint Helena
Saint Kitts and Nevis
Saint Lucia
SH
KN
LC
Saint Pierre and Miquelon
Saint Vincent and The Grenadines
PM
VC
Samoa WS
San Marino
Sao Tome and Principe
SM
ST
Saudi Arabia SA
Senegal SN
Seychelles SC
Sierra Leone SL
Singapore SG
Slovakia SK
Slovenia SI
Solomon Islands SB
Somalia SO
South Africa ZA
Spain ES
Sri Lanka LK
Sudan SD
Suriname SR
Svalbard and Jan Mayen Islands SJ
Swaziland SZ
Sweden SE
Switzerland CH
Syrian Arab Rep. SY
Taiwan TW
Tajikistan TJ
Tanzania TZ
Thailand TH
Togo TG
Tokelau TK
14-54
Country Name ISO Country Code
Tonga TO
Trinidad and Tobago TT
Tunisia TN
Turkey TR
Turkmenistan TM
Turks and Caicos Islands TC
Tuvalu TV
Uganda UG
Ukraine UA
United Arab Emirates AE
United States US
Uruguay UY
Uzbekistan UZ
Vanuatu VU
Vatican City State (Holy See) VA
Venezuela VE
Viet Nam
Virgin Islands (British)
VN
VG
Virgin Islands (US)
Wake Island
Wallis and Futuna Islands
VI
WK
WF
Western Sahara EH
Yemen YE
Yugoslavia YU
Zaire ZR
Zambia ZM
Zimbabwe ZW
14-55
15. A
PPENDIX
VIII:
STATE
/
PROVINCE
/
REGION CODES
State/Region Code Country
Alabama AL us
Alaska AK us
American Samoa AS us
Arizona AZ us
Arkansas AR us
Armed Forces - Europe
Armed Forces - Pacific
Armed Forces - The Americas
AE
AP
AA us us us
California CA us
Colorado CO us
Connecticut CT us
Delaware DE us
District of Columbia DC us
Federated States of Micronesia FM us
Florida FL us
Georgia GA us
Guam GU us
Hawaii HI us
Idaho ID us
Illinois IL us
Indiana IN us
Iowa IA us
Kansas KS us
Kentucky KY us
Louisiana LA us
Maine ME us
Marshall Islands MH us
Maryland MD us
Massachusetts MA us
Michigan MI us
Minnesota MN us
Mississippi MS us
Missouri MO us
Montana MT us
Nebraska NE us
Nevada NV us
New Hampshire NH us
New Jersey NJ us
15-56
State/Region Code Country
New Mexico
New York
North Carolina
North Dakota
Northern Mariana Islands
NM
NY
NC
ND
MP us us us us us
Ohio OH us
Oklahoma OK us
Oregon OR us
Palau PW us
Pennsylvania PA us
Puerto Rico
Rhode Island
South Carolina
PR
RI
SC us us us
South Dakota SD us
Tennessee TN us
Texas TX us
Utah UT us
Vermont VT us
Virgin Islands VI us
Virginia VA us
Washington WA us
West Virginia WV us
Wisconsin WI us
Wyoming WY us
Alberta AB ca
British Columbia BC ca
Manitoba MB ca
New Brunswick NB ca
Newfoundland NF ca
Nova Scotia
Northwest Territories
NS
NT ca ca
Nunavut NN ca
Ontario ON ca
Prince Edward Island PE ca
Quebec QC ca
Saskatchewan SK ca
Yukon YT ca
Eastern Cape
Free State
EC
FS za za
Gauteng GG za
KwaZulu-Natal KN za
Mpumalamanga MG za
Northern Cape NO za
15-57
State/Region Code Country
Northern Province
North West
Western Cape
Australian Capital Territory
New South Wales
NP
NW
WC
ACT
NSW za za za au au
Northern Territory NT au
Queensland QLD au
South Australia SA au
Tasmania TAS au
Victoria VIC au
Western Australia WA au
15-58
16. A
PPENDIX
IX:
HOW TO CONTACT US
Our product support specialists provide technical assistance to current customers or maintenance customers, prospective customers who are evaluating our products and services. Our support specialists handle questions on the use, configuration and functionality of our products and services and are committed to providing timely responses to your enquiries.
Contact us at
.
Supportline (office hours)
Dialing from within the UK -
0845 3007567
Dialing from outside the UK -
+44 (0) 1932 690237
16-59
17. G
LOSSARY OF PAYMENT PROCESSING TERMINOLOGY
A
ABA
See American Bankers Association.
ABA Routing Number
The American Bankers Association (ABA) routing number is a unique, bank identifying number that directs electronic ACH deposits to the proper bank. The routing number precedes the account number printed at the bottom of a check and is usually printed with magnetic ink.
Account Number
A unique sequence of numbers assigned to a cardholder's account, which identifies the issuer and type of financial transaction card.
ACH
See Automated Clearing House.
ACI
See Authorization Characteristics Indicator.
Acquirer
A bank or financial institution that acquires data relating to transactions from a merchant or card acceptor for processing. The acquirer enters this data into interchange, either directly or indirectly. See Interchange.
Acquiring Bank
A bank that receives credit card transactions and then deposits them with the issuing banks. This is an acquirer.
Address Verification Service
A service that verifies the cardholder's billing address in order to help combat fraud in card-notpresent transactions (e.g. mail order, telephone order, internet, etc.). Used only in the United
States.
Agent Bank
A bank that participates in another bank's acquiring program, usually by turning over its applicants for bank cards to the bank administering the acquiring program.
American Banker's Association
The trade association of American bankers. This body also has the responsibility of assigning the registration authority for identification numbers.
American Express
An organization that issues cards and acquires transactions, unlike Visa and MasterCard, which are bank associations. American Express processes their own transactions through their network.
Amex
See American Express.
API
The Application Programming Interface (API) is the interface by which an application program
17-60
accesses the operating system and other services. An API is defined at source code level and provides a level of abstraction between the application and the kernel to ensure the portability of the code.
Approval
Any transaction that is approved by the cardholder or the check issuer's bank. Approvals are requested via an authorization. An approval is the opposite of a declined transaction.
Arbitration
The procedure used to determine the responsibility for a chargeback-related dispute between a merchant and buyer.
Asynchronous
A method of transmitting data in which the data elements are identified with special start and stop characters. An asynchronous modem cannot communicate with a synchronous modem. Compare with Synchronous (e.g. standard Hayes compatible modem).
ATM
See Automated Teller Machine.
Auth Only
A transaction in which the merchant does not intend to charge the cardholder until a later time, if at all. See Prior Authorized Sale.
Authorization
An authorization is a request to charge a cardholder. It reduces the cardholder's open to buy, but does not actually capture the funds. An authorization is the first transaction in the delayed deposit process. It does not bill the card until a delayed capture transaction is issued. The authorization must be deposited in order to charge the account. If it is not used within a certain time period, it will drop off. The issuing bank determines the time period for drop off. Authorizations can only be used for credit card transactions.
Authorization Code
Approved sale and authorization transactions always receive a numeric or alphanumeric authorization code referencing the transaction for processing purposes.
Automated Clearing House
The Automated Clearing House (ACH) network is a nationwide, wholesale electronic payment and collection system. It is a method of transferring funds between banks via the Federal Reserve
System. Most, but not all, financial institutions use it.
Average Ticket
The average dollar amount of merchant credit transactions.
AVS
See Address Verification Service.
B
Bank card
A debit or credit card issued by a bank.
Bank Identification Number
The digits of a credit card that identifies the issuing bank. It is sometimes the first six digits and is often referred to as a BIN. Also referred to as Issuer Identification Number.
17-61
Basis Point
One one-hundredth of a percent. Discount rates are expressed as basis points.
Batch
A collection of transactions submitted for deposit. Usually a merchant has one batch per day or per shift.
Batch ID
Once a batch is deposited, it is assigned a batch ID. Every transaction in the batch shares this ID.
If a transaction does not have a batch ID associated with it, the transaction has not been deposited.
Batch Processing
A type of data processing where related transactions are transmitted as a group for processing.
Batch Deposit
An electronic bookkeeping procedure that sends all funds from captured transactions to the merchant's acquiring bank for deposit. PaymentTrust
TM
automatically submits all captured transactions for deposit on a daily basis. The time span, in which funds reach the merchant account after deposit, is 1-5 days, but varies by acquiring bank.
BIN
See Bank Identification Number.
Binary Executable
A universal character coding system.
Bundled Rate
A discount rate that includes communication costs as well as transaction fees. Also referred to as a flat rate.
C
Cancellation
Reversal of a partial or an entire authorization charge prior to the deposit process. It prevents a transaction from being deposited. A Cancellation does not remove any hold on the cardholder's open to buy.
Capture
The process of capturing funds from an authorized transaction.
Card Issuer
See Issuer, Issuing Bank.
Card-Not-Present
A merchant environment where the cardholder and the card are not physically present at the time of purchase. The following are typical card-not-present transactions: mail/telephone order, business to business and internet based transactions.
Card-Present
A merchant environment where the cardholder and the card are physically present at the time of purchase. Card-present transactions account for the majority of credit card transactions in the world.
17-62
Card Verification Value
A unique verification value encoded on the magnetic strip of a card to validate card information during the authorization process. The card verification value is calculated from the data encoded on the magnetic strip using a secure cryptographic process. This method is used by Visa and
Master Card.
CAV
Cardholder Authentication Value used by PaymentTrust Ltd. and Acquirer. Base64 encoded data structure containing 3D Secure authentication results provided by the 3D Secure MPI, usually
Visa’s CAVV or MasterCard’s UCAF.
CAVV
Visa’s Cardholder Authentication Verification Value. Base64 encoded data structure containing
3D Secure authentication results provided by the 3D Secure MPI.
CGI
See Common Gateway Interface.
Chargeback
The act of taking back funds that have been paid to a merchant for a disputed or improper credit card transaction. The issuer can initiate this procedure 30 days after the deposit.
Chargeback Period
The number of calendar days in which a card member may charge sales back to the merchant, beginning with the day after the date the record is first received by the member or agent and continuing until the end of the day on which it is dispatched as a chargeback item.
Chargeback Reason Code
A two-digit code identifying the specific reason for the chargeback.
Check Guarantee
A service which guarantees check payments (up to the limit defined for the account) provided that the merchant follows correct procedures in accepting the check. The service determines whether the check issuer has previously written delinquent checks. Companies like TeleCheck provide this type of service.
Chip Card
Also known as a smart card. A chip card holds details on a computer chip, which can store and process information. It usually also has a traditional magnetic stripe.
Clearing
The process of exchanging financial details between an acquirer and an issuer to facilitate posting of a cardholder's account and reconciliation of a merchant's deposit position.
Common Gateway Interface
An interface program that enables an Internet server to run external programs to perform a specific function. Also referred to as gateways or CGI scripts; these programs generally consist of a set of instructions written in a programming language like C or PERL that process requests from a browser, executes a program and formats the results in HTML. Gateway scripts often add interactivity to a Web page by enabling users to fill out and submit forms for processing.
Confirmation Letter
A letter sent by a processor to a merchant on a daily or weekly basis to verify batch deposits.
Converted Currency ID
ISO standard numeric ids of the converted currency.
Example: USA = 840, GBP = 826, JPY = 392
17-63
Conversion Rate
The conversion rate applied to the transaction amount in U.S. dollars.
Copy Request
See Retrieval Request.
Credit
Also known as a refund. A credit is a transaction that transfers funds from the merchant's account back in to the customer's credit card. This type of transaction is usually performed when a product is returned to the merchant. A credit can be performed through the e-Transaction
Terminal area of PaymentTrust
TM
Payment Manager or through a merchant's storefront application. Check refunds can only be issued via credit card or through a non-electronic paper check. A credit can only be issued to an account that has not had a previous authorization.
Credit Limit
The limit of credit a cardholder is approved to borrow. Credit card purchases are loans to the cardholder by the issuer.
Currency ID
ISO standard numeric ids of the converted currency.
Example: USA = 840, GBP = 826, JPY = 392
CVC
See Card Verification Code.
CVV
See Card Verification Value.
CVV2
See Card Verification Value.
D
DDA
See Demand Deposit Account.
Debit Card
An ATM bank card used to purchase goods and services, and to obtain cash. A debit card debits the cardholder's bank account and requires a Personal Identification Number (PIN). Debit cards branded with a bank card logo (e.g. Visa) can be accepted without a PIN for Internet transactions.
Decline
A transaction in which the issuing bank will not authorize the transaction.
Delayed Capture
A delayed capture is a transaction type that uses the information from an authorization transaction to capture funds. This is the second step in the delayed deposit process and should be used by merchants who do not provide immediate shipment of goods.
Delayed Deposit
This is a two-phase process that utilizes an authorization and a delayed capture transaction to process customer orders. This procedure is recommended when the merchant delivers goods or services after a 48-hour period.
17-64
Demand Deposit Account
A standard checking or savings account into which electronic funds can be transferred.
Deposit
The process of transmitting a batch of transactions from the merchant to the acquiring institution for deposit preparation. It marks a previously authorized transaction for funds capture during the next deposit period. Merchants who do not ship goods immediately should use this transaction type after fulfilling their sales obligation.
Discount fee
Fee paid by the merchant to the merchant bank or other contracted party for processing the merchant's credit card sales transactions.
Discount Rate
Amount charged to a merchant by the acquiring bank for transaction processing. It usually represents a percentage of the transaction amount. The rate is typically based on monthly transaction volume (total dollars) and average ticket. The discount fee is the dollar amount charged.
Downgraded ICC:
A chip card that only contains track 2 information on it.
Draft Capture
Refers to Deposit.
E
ECR
See Electronic Cash Register.
EFT
See Electronic Funds Transfer.
Electronic Cash Register
The combination of a cash register and a POS terminal, often PC based.
Electronic Funds Transfer
The paperless act of transmitting money through a computer network.
External Sales Agent
Amex term for ISO or MSP.
F
Floor Limit
A preset limit established by an issuer that allowed merchants to accept credit card sales without authorization provided the merchant verifies the card number on a warning bulletin for lost or stolen cards. Floor limits are now rarely used.
Fraudulent User
An individual who is not the cardholder or designee and who uses a card to obtain goods or services without the cardholder's consent.
17-65
Fraudulent Transaction
A transaction unauthorized by the cardholder of a bank card. Such transactions are categorized as lost, stolen, not received, issued on a fraudulent application, counterfeit, fraudulent processing of transactions, account takeover, or other fraudulent conditions as defined by the card company or the member company.
H
HTTP Protocol
Hardware and/or software that connects computer networks and allows them to communicate.
I
ICC (Integrated Circuit Card)
See chip card.
Independent Sales Organization
Visa term for a company that is sponsored by an acquiring bank to solicit and sometimes support merchants.
Interchange
The flow of information between issuers and acquirers (e.g. transactions, retrieval requests, chargebacks).
Interchange Fee
The fee charged by Visa and MasterCard for each credit card transaction. This fee is part of the discount rate.
Internet Merchant Bank Account
A special account required for merchants who wish to sell goods and services over the Internet and accept credit cards as payment. This type of account is different than a typical merchant account and is considered similar to a card-not-present transaction.
Internet Service Provider
A company that offers access to individuals or companies to connect to the Internet.
ISO
See Independent Sales Organization.
ISP
See Internet Service Provider.
Issuer
An institution that issues plastic cards to cardholders.
Issuing Bank
See Issuer.
M
Magnetic Ink Character Recognition (MICR)
The process used to read the string of numbers on the bottom of a check. The MICR characters
(0-9 and 4 special characters) are printed in special toner or ink. When the check is passed
17-66
through a reader/sorter, it passes through two magnetic heads. The first one magnetizes the
MICR character and the second one reads the (now) magnetic MICR character. Also referred to as Magnetic Ink Check Reader.
Manual Entry
Credit card information that is entered via the e-Transaction Terminal of PaymentTrust
TM
Payment Manager.
Manual Refund
A transaction that returns the specified amount to the cardholder's account.
MasterCard
An association of banks that governs the issuing and acquiring of MasterCard credit card transactions and Maestro debit transactions.
Member
A financial institution that is a member of Visa USA and/or MasterCard International. A member is licensed to issue cards to cardholders and/or accept merchant drafts.
Merchant
A retailer, or any other entity (pursuant to a Merchant Agreement), that agrees to accept credit cards, debit cards, or both, when properly presented.
Merchant Agreement
A written agreement between a merchant and a bank (or possibly between a merchant, a bank and ISO) summarizing their respective rights, duties and warranties with respect to acceptance of the bank card and matters related to bank card activity.
Merchant Bank
A bank issuing an agreement to a merchant to accept (acquire) deposits generated by bank card transactions.
Merchant Category Code
A code assigned by an acquirer to a merchant to identify the merchant's principal trade, profession, or line of business. This 4-digit code is also know as the SIC code.
Merchant Discount
Compensation received by a bank from a merchant for processing and accepting credit card risk on the merchant's credit card sales.
Merchant Number
A series or group of digits that uniquely identifies the merchant to the merchant's signing bank for account and billing purposes.
Merit
Refers to the qualification levels for a MasterCard transaction. Merit III is the highest discount, followed by Merit II, Merit I, and then Standard.
MICR Number
See Magnetic Ink Character Recognition.
MO/TO
Mail Order/Telephone Order credit card transactions.
MPI
Merchant Plugin. 3 rd
party software used by a merchant to authenticate 3D Secure transactions.
17-67
MSP
See Member Service Provider.
N
Network
See Processor. Also used to refer to communication networks like AT&T or CompuServe.
Non-Qualified
A broad term that describes a transaction that did not interchange at the best rate, because it was entered manually, was not deposited in a timely manner, or the data set required for the best interchange was not provided.
O
ODFI
See Originating Depository Financial Institution.
Open to buy
The amount of credit available at a given time on a cardholder's account.
Operator
A central clearing facility that provides distribution and deposit of ACH transactions. ACH operators clear debits and credits electronically, rather manually. Currently four ACH Operators exist: the Federal Reserve System, which clears approximately 80% of all ACH transactions,
Visanet ACH, New York ACH, and American ACH.
Original Draft
The original copy of the forms and signatures used in the transaction. Also referred to as the hard copy.
Originating Depository Financial Institution
A financial institution that initiates and warrants electronic payments through the ACH network on behalf of its customers.
Originator
A company or other business entity that creates entries for introduction into the ACH network. For example, a billing company produces debit entries from customers' financial institution accounts who have authorized direct payment for products and services.
P
PAN
See Primary Account Number.
PIN
Personal Identification Number used by a cardholder to authenticate card ownership for ATM or debit card transactions. The cardholder enters his/her PIN into a keypad. The PIN is required to complete an ATM/debit card transaction.
Point Of Sale
The place and time at which a transaction occurs. Point of Sale (POS) also refers to the devices or software used to capture transactions.
17-68
POS
See Point Of Sale.
Post Authorization
A transaction for which a voice authorization was received. See Prior Authorized Sale.
Post-Auth
See Post Authorization.
Posting
The process of recording debits and credits to a cardholder's account balances.
Pre-Auth
Same as Auth Only.
Prenote
See Pre-Notification.
Pre-Notification
Prior to the initiation of the first ACH entry to an ACH receiver or the ACH receiver's account with an RDFI, an ACH originator may, at its option, deliver or send a pre-notification through an ODFI to its ACH operator for transmittal to the appropriate RDFI. The pre-notification shall provide notice to the RDFI that the originator intends to initiate one or more entries to that receiver's account in accordance to the receiver's authorization.
Primary Account Number (commonly called PAN)
The number that is embossed, encoded, or both on a plastic card that identifies the issuer and the particular cardholder account. The PAN consists of a major industry identifier, issuer identifier, individual account identifier, and check digit.
Prior
See Prior Authorized Sale.
Prior Authorized Sale
A transaction for which authorization was obtained before a transaction takes place, e.g. when a merchant has to call for authorization before services are rendered. The approved authorization request may be held for an extended length of time before a card is present or not.
Prior-Auth
See Prior Authorized Sale.
Private Label Card
A bank card that can be used only in a specific merchant's store. Typically not a bank card.
Processing Date
The date on which the acquiring bank processes the transaction.
Processor
A large data center that processes credit card transactions and deposits funds to merchants. A processor connects to the merchant on behalf of an acquirer via a gateway or POS system to process payments electronically. Processors edit and format messages and switch to bank card networks. They provide files for clearing and deposit, and other value added services.
Q
17-69
Qualification
A level at which a transaction interchanges. The level of qualification is dependent on how a credit card number is entered, how quickly a transaction is deposited, the type of industry, and other specific information.
R
RDFI
See Receiving Depository Financial Institution.
Receipt
A hard copy description of the transaction that occurred at the point of sale. Minimum information contained on a receipt is date, merchant name and location, account number, type of account used (e.g. Visa, MasterCard, Amex, etc.), amount, reference number and/or authorization code, and action code.
Receiver
A consumer, customer, employee, or business who has authorized ACH payments by Direct
Deposit or Direct Payment to be applied against a depository account.
Receiving Depository Financial Institution
A financial institution that provides depository account services to customers, employees and businesses, and accepts electronic debits and credits to and from these accounts.
Recurring Transaction
A transaction in which a cardholder has given a merchant permission to periodically charge the cardholder's account.
Refund
A transaction that returns the specified amount to the cardholder's account.
Response Code
A numeric code that indicates whether a transaction was approved or declined. Response codes are used in the PaymentTrust
TM
system to indicate transaction responses to merchants.
Retrieval
See Retrieval Request.
Retrieval Request
A request to a merchant for documentation concerning a transaction, usually initiated by a cardholder's dispute or suspicious sale/return. A retrieval request can lead to a chargeback.
Return Code
Any of the codes returned by PaymentTrust
TM
when a transaction is processed.
S
Secure Sockets Layer
An encryption system that allows merchants to securely process electronic transactions.
Deposit
The process by which transactions with authorization codes are sent to the processor for payment to the merchant. Deposit is a sort of electronic bookkeeping procedure that causes all
17-70
funds from captured transactions to be routed to the merchant's acquiring bank for deposit.
PaymentTrust
TM
automatically submits all captured transactions for deposit on a daily basis. The time that it takes for these funds to reach the merchant account after deposit is 1-5 days, but varies according to the merchant's agreement with their respective card processing company.
Also referred to as Deposit.
SIC Code
Refers to Standard Industry Classification. These codes are 4-digit numbers used to identify a business type.
Simultaneous Authorization And Deposit
Charges the specified amount against the account, and marks the transaction for immediate funds transfer during the next deposit period.
Smart Card
A credit or debit card embodying a computer chip with memory and interactive capabilities used for identification and to store additional data about the cardholder, cardholder's account, or both.
Also called an integrated circuit card or a chip card.
SSL
See Secure Sockets Layer.
Standard
The lowest qualification level at which a Visa or MasterCard transaction may interchange. This occurs when a transaction is deposited several days after the original authorization.
Surcharges
Any additional charges to a merchant's standard processing fee. They are a result of nonqualified transactions of different communication methods.
Suspense
A state in which a batch of transactions is not released to interchange, because of problems noticed by the host computer. Requires human intervention to fix the problem and deposit the batch.
Swiped Card
Credit card information that is transferred directly as a result of swiping or sliding the credit card through a card reader. Swiped cards are used in retail and other card-present situations. The information magnetically encoded in the magnetic strip includes confidential data that helps validate the card.
Synchronous
A method of transmitting data in which the data elements are sent at a specific rate so that start and stop characters are not needed. Used by older modems such as, Amex PIP terminals. See
Asynchronous.
T
T & E Card
See Travel and Entertainment Card.
Tender Type
The type of "money" used when processing a transaction, for example, credit card, check, ACH,
Purchase Card, etc.
17-71
Third Party Processor
A non-member agent employed by an acquiring bank, which provides authorization, deposit and merchant services to the bank's merchant.
Track 1
Bank discretionary data encoded on a magnetic stripe. Includes credit card account number, cardholder name, and expiry date. This magnetic strip is read-only, and its contents are defined in
ISO 7813.
Track 2
Bank discretionary data encoded on a magnetic stripe. Track 2 includes credit card account number and expiry date. This magnetic strip is read-only, and its contents are defined in ISO
7813.
Transaction
The action between a cardholder and a merchant that results in activity on the cardholder's account.
Transaction Fee
A per transaction charge in addition to the percentage discount fees, incurred by merchants who are on scale pricing.
Transaction Date
The date on which a transaction between a cardholder and a merchant, an acquirer, or a carrier, occurs.
Transaction ID
A is a 16-character numeric string that PaymentTrust
TM
assigns to every transaction that it processes.
Transaction Type
A specific financial detail transaction activity that can be submitted to the clearing system
Travel and Entertainment Card
Credit cards that typically require payment in full each month, (e.g. American Express, Diner's
Club, and Carte Blanche).
U
UCAF
MasterCard’s Universal Cardholder Authentication Field. Base64 encoded data structure containing 3D Secure authentication results provided by the 3D Secure MPI.
Undeposited Transactions
PaymentTrust
TM
automatically deposits deposit transactions on a daily basis. Please note that authorization transactions are not captured until they are completed by a deposit transaction.
PaymentTrust
TM
transaction types that are automatically flagged for capture include simultaneous authorization, deposit, and refund.
V
Visa
An association of banks that governs the issuing and acquiring of Visa credit card transactions.
17-72
Ladda ner
Offentlig länk uppdaterad
Den offentliga länken till din chatt har uppdaterats. You may view and manage your chat links after registration here.
Offentlig länk till dokument
Annons
