Integration Testing

You will be provided with unique test Merchant Account IDs during the onboarding process. Refer to Prerequisites section for more information.

Test Merchant Accounts are connected to our Simulator and not to an actual Acquirer. The Simulator will emulate the function of an Acquirer and provide simulated responses and authorisation codes.

Test Amounts

When testing the transaction amount can be used to trigger different authorisation and settlement outcomes as follows:

Min.Amount	Max.Amount	Authorisation Response	Settlement Outcome
100 (1.00)	2499 (24.99)	(0) AUTH CODE: XXXXXX	ACCEPTED
2500 (25.00)	4999 (49.99)	(0) AUTH CODE: XXXXXX	REJECTED
5000 (50.00)	7499 (74.99)	(1) CARD REFERRED (0) AUTHCODE: XXXXXX	ACCEPTED
7500 (75.00)	9999 (99.99)	(1) CARD REFERRED (0) AUTHCODE: XXXXXX	REJECTED
10000 (100.00)	14999 (149.99)	(5) CARD DECLINED	N/A
15000 (150.00)	19999 (199.99)	(4) CARD DECLINED – KEEP CARD	N/A
20000 (200.00)	24999 (249.99)	(65) CARD DECLINED - SCA REQUIRED (0) AUTH CODE: XXXXXX	ACCEPTED
25000 (250.00)	29999 (299.99)	(65) CARD DECLINED – SCA REQUIRED (5) CARD DECLINED	N/A

Any other amount will return a responseCode of 66311 (Invalid Test Amount).

The settlement outcome only applies to transactions which reach settlement due to being successfully authorised and captured and not cancelled. The amount captured is used when determining the settlement outcome rather than the amount authorised.

The range 20000 to 29999 can be used to test SCA soft declines. If the transaction is eligible[1] to request SCA then the Simulator will return a responseCode of 65 (SCA REQUIRED). If not, then it will return a responseCode of 0 (SUCCESS) for the range 20000 to 24999 or 5 (DO NOT HONOR) for the range 25000 to 29999. Successful transactions will be approved at settlement.

Note: you cannot emulate SCA REQUIRED responses using the Virtual Terminal.

[1] A cardholder-initiated e-commerce sale or verify transaction that is enabled for 3-D Secure but is not already authenticated. SCA exemptions are not supported by the simulator and so cannot be used to request that SCA is not required.

Overriding the Simulator Amount Response

The amount can be changed, and the simulated response overridden if required. Use the Cardholder's Name as 'Test' and include the value amount you want the transaction to trigger for in brackets after the word Test. This will override the amount being submitted for the transaction.

For example, a transaction with Cardholder Name 'Test [20]' and an amount of ‘£10,000’ will trigger the Simulator to give a settlement outcome of ACCEPTED as the value, £20, is between the minimum and maximum values below:

Min. Amount	Max. Amount	Authorisation response	Settlement outcome
100 (1.00)	2499 (24.99)	(0) AUTH CODE: XXXXXX	ACCEPTED

Test Cards

The test accounts will only accept card numbers that are designated for test purposes. These test cards cannot be used on production accounts.

To test AVS and CV2 verification then the associated CVV and billing addresses are provided for each card. If a different value is used, then the Simulator will mark the responses as ‘not matched’.

The expiry date used for each test card should be December of the current year, in two-digit format (unless simulating 3DS authorisation states as described in the ‘3-D Secure version 2' section).

Credit and debit cards

We provide test card numbers for the following credit and debit cards:

• Visa Credit

• Visa Debit

• Electron

• Mastercard Credit

• Mastercard Debit

• JCB

• American Express

• Diners Club

Our test cards are split into two groups to allow for the simulation of no Method Data being sent, as this payment flow is followed by some Access Control Servers (ACS) who may not provide a Method URL. For those card numbers marked with an * , the Method Data is not sent, and 3-D Secure transactions will skip the 3DS method check.

Visa Credit

Card Number	CVV	Address
4929 4212 3460 0821	356	Flat 6 Primrose Rise 347 Lavender Road Northampton NN17 8YG
4543 0599 9999 9982*	110	76 Roseby Avenue Manchester M63X 7TH
4543 0599 9999 9990*	689	23 Rogerham Mansions 4578 Ermine Street Borehamwood WD54 8TH

Visa Debit

Card Number	CVV	Address
4539 7910 0173 0106	289	Unit 5 Pickwick Walk 120 Uxbridge Road Hatch End Middlesex HA6 7HJ
4462 0000 0000 0003	672	Mews 57 Ladybird Drive Denmark 65890

Electron

Card Number	CVV	Address
4917 4800 0000 0008	009	5-6 Ross Avenue Birmingham B67 8UJ

Mastercard Credit

Card Number	CVV	Address
5301 2500 7000 0191	419	25 The Larches Narborough Leicester LE10 2RT
5413 3390 0000 1000	304	Pear Tree Cottage The Green Milton Keynes MK11 7UY
5434 8499 9999 9951*	470	34a Rubbery Close Cloisters Run Rugby CV21 8JT
5434 84999 999 9993*	557	4-7 The Hay Market Grantham NG32 4HG

Mastercard Debit

Card Number	CVV	Address
5573 4712 3456 7898	159	Merevale Avenue Leicester LE10 2BU

JCB

Card Number	CVV	Address
3540 5999 9999 1047	209	2 Middle Wallop Merideth-in-the-Wolds Lincolnshire LN2 8HG

American Express

Card Number	CVV	Address
3742 4545 5400 001	4887	The Hunts Way Southampton SO18 1GW

Diners Club

Card Number	CVV Number	Address
3643 2685 2602 94	111	N/A

Diners Club do not support AVS. For testing purposes, use a separate MID with AVS turned off.

3-D Secure version 2 Testing

Your test accounts are connected to our 3-D Secure Product Integration Testing (PIT) system rather than to the production 3-D Secure servers.

You can use any of the test cards with this PIT system, and the authentication status returned by the Directory Server (for frictionless flow simulation) can be selected using the value of the card expiry month as follows:

Card Expiry Month	Auth Status	Simulation (Frictionless)
01 - Jan	Y	Fully authenticated
02 - February	N	Not authenticated
03 - March	U	Unknown authentication status
04 - April	A	Attempted authentication
05 - May	D	Decoupled authentication
06 - June	R	Transaction rejected (do not attempt to send for authorisation)
07 – July	E	Unknown error performing 3-D Secure checks
08 - August	E	Error due to timeout communicating with the Directory Server
09 – September	E	Error due to corrupt response from the Directory Server.
10 – October	I	Information only
11 – November	U	Unknown authentication due to Cardholder not enrolled (error 13)
12 - December	C	Frictionless not possible, challenge Cardholder

If the month required has passed for the current year, the card will show as expired. Use the month required and the next year's date to receive the expected response.

An expiry month of 12 will simulate the non frictionless flow and desired authentication status (threeDSAuthenticated) can be selected on the challenge dialog shown by the PIT Access Control Server.

PayPal Sandbox Accounts

Please contact customer support to have your own PayPal test Merchant account created that connects to your own PayPal sandbox account, thus enabling you to view the transactions as they are sent to PayPal.

Amazon Pay Sandbox Accounts

Please contact customer support to have your own Amazon Pay test Merchant account created that connects to your own Amazon Pay sandbox account, thus enabling you to view the transactions as they are sent to Amazon Pay.