Test Conventions

The sections below provide conventions for use in testing Maast payment integrations. See our Test and Go Live guide for instructions on performing the recommended tests of your integration.

Test Card Numbers

Use one of the test credit or debit card numbers in the table below to test a specific brand and type of card:

Card Type	Test Card Number
Visa Consumer Credit Card	4212222222222222
Visa Customer Debit Card	4111111111111111
Visa Purchase Card	4312222222222221
Visa Prepaid Card	4444222222222222
Mastercard Consumer Credit Card	5544666666666664
Mastercard Customer Debit Card	5555555555555557
Mastercard Prepaid Card	5555222222222224
Mastercard Purchase Card	5566444444444447
Discover	6011001122111117
American Express	371449635392376
International Diners	38555565010005
JCB	3530142019955809

Test ACH Payment Accounts

Use one of the test ACH payment routing numbers in the table below to test payment from a specific bank:

Bank	Routing Number
Citi	028000082
Bank of America	021000322
City Credit Union	301080428

Test Response Codes

In the testing environment, you can use the following test transaction amounts in transactions to simulate different responses. This table shows test amounts and the response that each produces:

Test Amount	Response rcode	Response rmsg	Test Case
0.05	005	Do not honor	Simulate a decline for a sale or authorization request
0.06	006	Error	Simulate a decline for a sale or authorization request
0.07	007	Pick up card	Simulate a decline for a sale or authorization request
0.41	041	Lost card (fraud)	Simulate a decline for a sale or authorization request
0.43	043	Stolen card (fraud)	Simulate a decline for a sale or authorization request
0.51	051	Insufficient funds	Simulate a decline for a sale or authorization request
0.59	059	Suspected fraud	Simulate a decline for a sale or authorization request
0.10	010	Partial approval	If the sale or authorization request includes "partial_auth": true, then the response will also contain field amt_tran with the amount that was actually approved. (It will be less than the amount requested.)
0.10	005	Decline	If the sale or authorization request does not include "partial_auth": true, then the request will be declined because the merchant did not want a partial approval.

Mastercard Merchant Advice Codes

The table below shows the card numbers you can use to simulate a variety of Mastercard merchant_advice_code values in the response. The response code itself will continue to depend on the test amount:

Cards	Response Code	Description
5888888888888801	M001	New account information available
5788888888888802	M002	Try again later
5688888888888803	M003	Do not try again for recurring payments transaction
5488888888888821	M021	Recurring payment cancellation

Test Address Verification Service (AVS) Data

Address Verification Service (AVS) is an anti-fraud tool offered by the credit card brands via the credit card issuers. The service compares information collected at time of payment to address information on file with the issuer. AVS may also help reduce the cost of the transaction and protect your chargeback rights.

These API requests support AVS, and you can use them to test the AVS response:

• Authorize Transaction
• Force Transaction Approval
• Issue Credit to Cardholder
• Sale (Auth + Capture)
• Tokenize (when sent with Verify)
• Verify

To test, vary the values sent in avs_address and avs_zip to invoke certain response codes in auth_avs_result. The table below shows the combinations of avs_address and avs_zip formats you can send to receive the following response codes. See Payment Result Codes for AVS for response code descriptions.

avs_address (up to 20 AN, case insensitive)	Format of avs_zip	Response code (auth_avs_result)
Any value that starts with123 Main St where Apt is also present and is followed by a space (ex: 123 Main St Apt 900)	Any value, or empty/absent	The character immediately after the space following Apt(ex: "avs_address": "123 Main St Apt 900" returns "auth_avs_result": "9")
Any value that starts with123 Main St where Apt is not present	Any value, or empty/absent	N
Any value that does not start with 123 Main St	5 N	Y
Any value that does not start with 123 Main St	9 N	X
Any value that does not start with 123 Main St	Any length that is not 5 N or 9 N	A
No value	5 N	Z
No value	9 N	W
No value	Any length that is not 5 N or 9 N	N

Test Card Verification Value (CVV2) Data

Card Verification Value (CVV2) is an anti-fraud tool offered by the credit card brands via their issuers. The service compares the CVV2 information on file with the issuer to the information collected at time of payment. By collecting CVV2 information at the time of payment, you may validate that the credit card is present. The CVV2 value cannot be stored.

The table below contains values for the CVV2 field that can be used to generate various CVV2 result codes in the response message:

CVV2 Value	Response Code
111	M
112	N
113	P
114	S
115	U

Account Updater Test Cards

When testing Account Updater integration, you can use specific test card numbers to invoke a certain response. This table provides the test card numbers and the response each invokes. Where you see an expiration date value of mmyy, any month/year combination is accepted, provided the date is in the future:

Test Card Number	Expiration Date	Reason Code	Reason Description
4111111111118116	mmyy	000	One of the following has occurred: - No response was provided by the card brand. - This is a new account.
4111111111111111	mmyy	200	No update.
6011001122111117	0540	201	The expiration date was updated.
4242420000001111	0929	202	One of the following has occurred: - The account number was updated. - Both the account number and the expiration date were updated.
5567110000001751	0540	202	One of the following has occurred: - The account number was updated. - Both the account number and the expiration date were updated.
4887888888888888	mmyy	203	The account is closed.
5555555555554444	mmyy	204	The card brand advises you to contact the cardholder.