Payment methods for testing

Use these test cards and accounts to simulate transactions in your sandbox. You can use these example cards and accounts to make test transactions via the API or any of Payabli’s hosted payment solutions, like the virtual terminal or payment pages.

Simulate a successful transaction

Use these test cards and accounts for transactions in sandbox.

Cards

Use these with any future expiration date.

ACH

Use this with any account type.

Simulate a decline

You can use test cards to simulate declines. This is useful for testing how your application handles declined transactions.

Decline rate limiting

Using a test card repeatedly in a short period can sometimes cause it to be blocked. As a best practice, Payabli recommends adhering to the fraud control limits. See fraud control for more information. Reach out to your Payabli Solution Engineer with any questions or issues related to testing declines.

Transaction declines

You can simulate a transaction decline by using the following card in a transaction request with any future date for the expiration date:

The transaction request should return a decline response like this:

1
{
2
    "responseText": "Declined",
3
    "isSuccess": false,
4
    "pageIdentifier": null,
5
    "responseData": {
6
        "authCode": null,
7
        "referenceId": "124-d541b0a9d1774bf3871f1d967abaaaaaa",
8
        "resultCode": 2,
9
        "resultText": "201: Do not honor. The customer’s issuing bank is unwilling to accept the transaction.. DECLINED",
10
        "avsResponseText": null,
11
        "cvvResponseText": null,
12
        "customerId": 12345,
13
        "methodReferenceId": null
14
    }
15
}

Stored method declines

To simulate a decline when charging a stored payment method, you can store a payment method with any of the following test cards and a future expiration date. The stored payment method can be charged with an amount of $0.20 (20 cents) to cause a declined transaction.

The request to charge the stored payment method should return a decline response like this:

1
{
2
    "responseText": "Declined",
3
    "isSuccess": false,
4
    "pageIdentifier": null,
5
    "responseData": {
6
        "authCode": null,
7
        "referenceId": "124-d541b0a9d1774bf3871f1d967abaaaaaa",
8
        "resultCode": 2,
9
        "resultText": "201: Do not honor. The customer’s issuing bank is unwilling to accept the transaction.. DECLINED",
10
        "avsResponseText": null,
11
        "cvvResponseText": null,
12
        "customerId": 12345,
13
        "methodReferenceId": null
14
    }
15
}

Invalid CVV declines

To simulate a decline due to an invalid CVV, you can use any of the following test cards with an incorrect CVV:

The transaction request should return a decline response like this:

1
{
2
  "responseText": "Declined",
3
  "isSuccess": false,
4
  "pageIdentifier": null,
5
  "responseData": {
6
    "authCode": null,
7
    "referenceId": "226-ab732d2a1c7e4117a32133f9e92673b2",
8
    "resultCode": 2,
9
    "resultText": "850: AVS or CVV failed.. DECLINED",
10
    "avsResponseText": "AVS not available",
11
    "cvvResponseText": "CVV2/CVC2 no match",
12
    "customerId": 1799,
13
    "methodReferenceId": null
14
  }
15
}