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 TypeTest Card Number
Visa Consumer Credit Card4212222222222222
Visa Customer Debit Card4111111111111111
Visa Purchase Card4312222222222221
Visa Prepaid Card4444222222222222
Mastercard Consumer Credit Card5544666666666664
Mastercard Customer Debit Card5555555555555557
Mastercard Prepaid Card5555222222222224
Mastercard Purchase Card5566444444444447
Discover6011001122111117
American Express371449635392376
International Diners38555565010005
JCB3530142019955809

Test ACH Payment Accounts

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

BankRouting Number
Citi028000082
Bank of America021000322
City Credit Union301080428

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 AmountResponse rcodeResponse rmsgTest Case
0.05005Do not honorSimulate a decline for a sale or authorization request
0.06006ErrorSimulate a decline for a sale or authorization request
0.07007Pick up cardSimulate a decline for a sale or authorization request
0.41041Lost card (fraud)Simulate a decline for a sale or authorization request
0.43043Stolen card (fraud)Simulate a decline for a sale or authorization request
0.51051Insufficient fundsSimulate a decline for a sale or authorization request
0.59059Suspected fraudSimulate a decline for a sale or authorization request
0.10010Partial approvalIf 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.10005DeclineIf 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:

CardsResponse CodeDescription
5888888888888801M001New account information available
5788888888888802M002Try again later
5688888888888803M003Do not try again for recurring payments transaction
5488888888888821M021Recurring 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:

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_zipResponse 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/absentThe 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 presentAny value, or empty/absentN
Any value that does not start with 123 Main St5 NY
Any value that does not start with 123 Main St9 NX
Any value that does not start with 123 Main StAny length that is not 5 N or 9 NA
No value5 NZ
No value9 NW
No valueAny length that is not 5 N or 9 NN

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 ValueResponse Code
111M
112N
113P
114S
115U

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 NumberExpiration DateReason CodeReason Description
4111111111118116mmyy000One of the following has occurred:
- No response was provided by the card brand.
- This is a new account.
4111111111111111mmyy200No update.
60110011221111170540201The expiration date was updated.
42424200000011110929202One of the following has occurred:
- The account number was updated.
- Both the account number and the expiration date were updated.
55671100000017510540202One of the following has occurred:
- The account number was updated.
- Both the account number and the expiration date were updated.
4887888888888888mmyy203The account is closed.
5555555555554444mmyy204The card brand advises you to contact the cardholder.