Nothing Special   »   [go: up one dir, main page]

S2I Test Cards 1 2

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

Mandatory Testing

The purpose of the mandatory testing is to ensure that your integration is performing correctly
with the payment server and receiving the appropriate responses to display to your card holder.
For example if an insufficient funds or invalid card response is returned it is important your
integration can interpret this and display appropriately to your card holder.
To ensure there has been enough testing to identify any problems and to familiarize yourself
with the product we require a minimum of 20 test transactions across all the scenarios.

Response Codes Testing


The information below is applicable only in the testing environment, i.e. when you are using your
test merchant profile.
The test bank simulator is configured to allow the user to change the responses received
against the test card numbers. For ease of testing the merchant may decide to test either by
Cent Value (Table 1) or by Expiry Date (Table 2). Please use the appropriate testing for your
configuration. AMEX and JCB do not allow testing by Expiry date.
To view the responses for each transaction you must log-in to the Merchant Administrator portal
and perform an Order or Financial transaction Search. The TEST merchant profile is accessed
when you log-in to the Merchant Administrator portal by prefixing TEST to the Merchant ID
field (e.g. TESTxxxxxxxxxx).
Table 1 - Testing by Cent Value - Cards and Responses
BRAND

PAN

Expiry

AMEX

371449635311004

05/17

DINERS CLUB

30123456789019

05/17

MASTERCARD

5123456789012346

05/17

VISA

4987654321098769

05/17

JCB

3528123456789012

05/17

Cent Value

Response code definition

Acquirer Response Code

.00

Transaction approved

.10

Transaction could not be processed

.01

Transaction declined - contact issuing bank

.05

Transaction declined - contact issuing bank

.68

No reply from Processing Host

.54

Card has expired

.51

Insufficient credit

Note: You cannot use an amount value of $0.00 to obtain a response code of 0 as this amount is an illegal value.
Use an amount value of $1.00 or $2.00 or $3.00, etc. For example, to obtain a response code of 1 on a MasterCard,
simply send a transaction for $x.10 against one of the above MasterCard numbers.

**Please note that when a 68 cent value transaction is processed; the payment server will throw an error
for the next 15 minutes

MIGS S2I Test Transport


Last Update: 2015.09.07

Page 1 of 4

Mandatory Testing
The below test card numbers (Table 2) can be used to trigger the different response codes by
varying the Expiry Date for the transaction. The following table shows how the various response
codes can be triggered varying the Expiry Date.
The test bank simulator is configured to allow the user to change the response received against
the above test card numbers by varying the Expiry Date for the transaction. The following table
shows how the various response codes can be triggered varying the Expiry Date.
Table 2 - Testing by EXP - Cards and Responses
BRAND

PAN

DINERS CLUB

30123400000000

MASTERCARD

5577810000000004

VISA

4434260000000008

Expiry Date

Response code definition

Acquirer Response Code

1705

Transaction approved

1902

Transaction could not be processed

1801

Transaction declined - contact issuing bank

1805

Transaction declined - contact issuing bank

2701

No reply from Processing Host

2304

Card has expired

2301

Insufficient credit

*For example, to obtain a response code of 1 on a MasterCard, simply send a transaction with expiry date
19/02 (yy/mm) against one of the above MasterCard numbers.
**Please note that when a 2701 Expiry Date value transaction is processed; the payment server will throw
an error for the next 15 minutes

MIGS S2I Test Transport


Last Update: 2015.09.07

Page 2 of 4

Mandatory Testing
Card security code (CSC) Result Code
The CSC is in addition to the bank card number which is embossed or printed on the card. The
CSC is used as a security feature, in situations where a PIN cannot be used.
The following table shows how the various CSC response codes that can be triggered by
varying the CSC value. Please note that in the test environment transactions will not fail
due to CSC code. Most Issuing banks will fail a transaction due to incorrect CSC in production.
To view the responses for each CSC test you must log-in to the Merchant Administrator portal
and perform a Financial transaction Search. Click on Transaction Number then Order ID.
Here you will see the response under Card Details - "CSC Result Code = P
BRAND

PAN

Expiry

DINERS CLUB

30123456789019

05/17

MASTERCARD

5123456789012346

05/17

VISA

4987654321098769

05/17

CSC Value

Name

Response Code

100

Valid or Matched CSC

104

Code Invalid or Not Matched

102

CSC Not Processed

---------

Merchant Indicates CSC not present on card (Suspicious)

*For example, to obtain a response code of P on a MasterCard, simply send a transaction with CSC 102 against one
of the above MasterCard numbers

MIGS S2I Test Transport


Last Update: 2015.09.07

Page 3 of 4

Mandatory Testing
3-Domain Secure (3DS) emulator
3DS payment authentications are designed to reduce credit card fraud by authenticating
cardholders when performing transactions over the Internet.
A payment authentication is performed immediately before a merchant performs an
authorization or purchase. Authenticating ensures that the card is being used by its legitimate
owner.
3DS simulation can be performed using the Test profiles if the below conditions are met:
Merchant profile has 3DS enabled
Merchant is performing 2.5 Party or 3 Party transaction
Once a successful request is sent, the test transaction will be re-directed to the 3DS emulator:
See below 3DS Emulator and the ability to select different results:

MIGS S2I Test Transport


Last Update: 2015.09.07

Page 4 of 4

You might also like