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:

New set of mock card numbers for future remapping changes.

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

NZ Bank Transactions

PayTo Account Details

📘

Important Note:

PayTo is only available for AU region. Please reach out to Ezypay before testing the PayTo simulated accounts.

PayTo Simulation accounts

❗️

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). 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.