Mock Credit Card and Bank Numbers

Ezypay provides these mock credit card numbers for your testing purposes. Each sample payment number can be used to test a different test case reason as described below.

Credit Card Details:

Test Case Reason

Action

Mock Card Number

Insufficient funds

Payment failed

4556175161745153

Invalid details

Payment failed

5596398242217872

Invalid details

Refund failed

4024007157038612

New set of mock card numbers for future remapping changes.

Test Case Reason

Action

Mock Card Number

Expired card

Payment failed

5500000000000004

Invalid payment method

Payment failed

4868470817885831

Customer to contact bank

Payment failed

4237990879556339

limit exceeded

Payment failed

4554831955801980

Example for the new failed payment remapping codes:

{
  "failedPaymentReason": {
    "code": "insufficient_funds",
    "description": "Payment method has insufficient funds at the time of the transaction."
  },
  "paymentProviderResponse": {
    "code": "Refused",
    "description": "51: Insufficient funds/over credit limit / Not sufficient funds"
  }
}
{
  "failedPaymentReason": {
    "code": "expired_card",
    "description": "The credit card has expired. Please use a different payment method."
  },
  "paymentProviderResponse": {
    "code": "Refused",
    "description": "54: Expired card"
  }
}
{
  "failedPaymentReason": {
    "code": "invalid_payment_method",
    "description": "Payment method details are invalid. Please use a different payment method."
  },
  "paymentProviderResponse": {
    "code": "Refused",
    "description": "12: Invalid transaction"
  }
}
{
  "failedPaymentReason": {
    "code": "customer_to_contact_bank",
    "description": "Transaction rejected by customer's bank. Please use a different payment method or ask the customer to contact the bank."
  },
  "paymentProviderResponse": {
    "code": "Refused",
    "description": "05: Do not honor"
  }
}
{
  "failedPaymentReason": {
    "code": "limit_exceeded",
    "description": "Transaction exceeded the customer's payment method daily withdrawal or activity limit."
  },
  "paymentProviderResponse": {
    "code": "Refused",
    "description": "61: Exceeds withdrawal amount limit(s) / Withdrawal amount limit exceeded"
  }
}

Bank Account Details:

AU Bank Transactions

Potential Use Case

Transaction Type

BSB

Last Four Digits of Account Number

Bank Error Code

Failed transaction code

Insufficient funds for refund

Refund

NA

1686

6

insufficient_funds

Insufficient funds for payment

Payment

NA

5596

6

insufficient_funds

Payment stopped

Payment

NA

1534

2

authority_withdrawn

Account closed

Payment

NA

3119

3

bank_account_closed

Customer deceased

Payment

NA

2222

4

authority_withdrawn

No account or incorrect account number

Payment

NA

8811

5

invalid_payment_method

Invalid BSB Number

Payment

NA

8812

1

invalid_payment_method

Deleted

Payment

NA

8813

7

bank_system_error

Invalid User ID Number

Payment

NA

8814

8

ezypay_error

NZ Bank Transactions

Potential Use Case

Transaction Type

BSB

Account Number

Bank Error Code

Failed transaction code

Account closed

Refund

NA

0061686

L

bank_account_closed

No authority loaded

Payment

NA

0231534

X

authority_withdrawn

Account not found

Payment

NA

0223119

Z

invalid_payment_method

Insufficient funds for payment

Payment

NA

0035596

U

insufficient_funds

Authority cancelled

Payment

NA

0256890

C

authority_withdrawn

Account closed

Payment

NA

0432222

L

bank_account_closed

Account transferred

Payment

NA

0237881

T

bank_account_closed

Payment limit exceeded

Payment

NA

0192494

E

limit_exceeded

❗️

Difference in receiving the invoice status changes

When testing on the sandbox environment, integrators must be aware that the transaction period when the invoice status is updated different compared to the production environment.

Sandbox behaviour

Cards: The integrators will received the status change within a few seconds.
Bank : The status will be updated the following day, as a backend job will automatically run the billing simulator the next day.

Production behaviour

Cards: The integrators will received the status change within a few seconds
Bank : Bank transactions are processed at midday every business day( local time for the region) and Transactions can take up to 3 business day before they are changed to success , If transactions are sent after midday they will be processed on the next available business day

❗️

What action is required

Sandbox:

Once an invoice is returned with the "PAST_DUE" status, integrators will need to "REPLACE" the payment method using the "replace payment method" API before triggering the "retry invoice" API.

Production:

Depending if the payment method token is still valid or not, replacing the payment method token might not be required.


Did this page help you?