> ## Documentation Index
> Fetch the complete documentation index at: https://razorpay-881012b3.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Test Cards for Indian Recurring Payments - Card
> Use test cards to simulate card mandate registration and subsequent recurring payments, including success and error scenarios.
Available in
🇮🇳 India
Use these test cards to test card-based recurring payment flows in **test** mode. The flow has two stages:
1. **Mandate registration (initial payment)** – the customer authorises the card mandate.
2. **Subsequent (auto-debit) payments** – Razorpay charges the registered token each time you initiate a debit.
**Watch Out!**
* You can use these test cards to make payments in **test** mode only.
* Test mode features a mock bank page with **Success** and **Failure** buttons to replicate the live payment experience.
* No real money is deducted due to the usage of test API keys. This is a simulated transaction.
* A subsequent (auto-debit) payment is simulated to reach its terminal state (**Success** or **Failure**) about **5 minutes** after it is created, with the relevant Razorpay [webhook](/docs/payments/recurring-payments/subscribe-to-webhooks) triggered. This is done to let you validate the flow quickly without waiting. This differs from Live Mode, where a PDN (Pre-Debit Notification) is sent first, and the actual debit can happen only after a mandatory [24-hour TAT](/docs/payments/recurring-payments/cards/faqs#what-is-the-tat-for-processing-debits-of-cards-mandates). Test Mode does not make calls to the Mandate Hubs, so no PDN (Pre-Debit Notification) or AFA (Additional Factor of Authentication) messages are triggered for any of the simulated scenarios below.
* If you use these test cards for **live** mode payments, either of the following error messages is displayed: `card issuer is invalid` or `invalid card input`.
1. At the Checkout, select **Card** as the payment method.
2. Enter the card number for the scenario you want to test.
3. Enter any random CVV and any future date as the expiry date.
4. Consent to tokenisation for the recurring mandate when prompted.
5. Click **Pay**. A sample bank/payment page is displayed.
* Select **Success** to complete the mandate registration.
* Select **Failure** to simulate a failed mandate registration.
6. For a subsequent payment, first register the mandate with the same card number, then charge the token via the [Charge a Token](/docs/payments/recurring-payments/cards/apis) API or the Dashboard. The payment reaches its terminal state about 5 minutes later.
Use the following cards for testing. You can use any random CVV and any future date as the expiry date.
## Test Cards for Mandate Registration (Happy Flow)
Use these cards to register a card mandate successfully (initial authorisation transaction).
| Network | Card Number | CVV & Expiry Date |
| ---------- | ------------------- | ------------------------------------ |
| Visa | 4100 2800 0000 1007 | Use a random CVV and any future date |
| Mastercard | 5305 6200 0006 0000 | Use a random CVV and any future date |
| RuPay | 6527 6589 0000 1005 | Use a random CVV and any future date |
For backward compatibility, the Visa card `4718 6091 0820 4366` (previously documented for Subscriptions) continues to work for the happy mandate-registration flow.
## Test Cards for Subsequent Payments (Happy Flow)
First register the mandate using one of the cards below, then attempt the subsequent (auto-debit) payment using the **same** card number. The subsequent payment moves to **Success** about 5 minutes after it is created.
| Network | Card Number | CVV & Expiry Date |
| ---------- | ------------------- | ------------------------------------ |
| Visa | 4100 2800 0000 1007 | Use a random CVV and any future date |
| Mastercard | 5305 6200 0006 0000 | Use a random CVV and any future date |
| RuPay | 6527 6589 0000 1005 | Use a random CVV and any future date |
## Error Scenarios – Mandate Registration
Use these test cards to simulate error conditions during **mandate registration**. Once you initiate the payment, on the success/failure screen you must select **Failure** to get the relevant error.
| Error reason | Error description | Network | Card number | Testing scenario |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `insufficient_funds` | Your payment could not be completed due to insufficient account balance. Try another card or payment method. | Visa | 4100 2800 0008 0001 | Card mandate registration payment- failed due to Insufficient balance in customer bank account |
| `insufficient_funds` | Your payment could not be completed due to insufficient account balance. Try another card or payment method. | Mastercard | 5305 6200 0005 0001 | Card mandate registration payment- failed due to Insufficient balance in customer bank account |
| `payment_timed_out` | Payment was not completed on time. | Visa | 4100 2800 0009 0000 | Card mandate registration payment- failed due to timeout from customer end. |
| `payment_timed_out` | Payment was not completed on time. | Mastercard | 5305 6200 0006 0000 | Card mandate registration payment- failed due to timeout from customer end. |
| `card_declined` | Your payment didn't go through as it was declined by the bank. Try another payment method or contact your bank. | Visa | 4100 2800 0005 0004 | Card mandate registration payment- failed due to bank decline. |
| `card_declined` | Your payment didn't go through as it was declined by the bank. Try another payment method or contact your bank. | Mastercard | 5305 6200 0002 0004 | Card mandate registration payment- failed due to bank decline. |
| `payment_cancelled` | Your payment has been cancelled. Try again or complete the payment later. | Visa | 4100 2800 0007 0002 | Card mandate registration payment- failed due to user cancellation during payment |
| `payment_cancelled` | Your payment has been cancelled. Try again or complete the payment later. | Mastercard | 5305 6200 0004 0002 | Card mandate registration payment- failed due to user cancellation during payment |
| `card_mandate_card_`
`not_supported` | This card is not eligible for recurring payments. Please use a different card. | Visa | 4100 2800 0006 0011 | Card mandate registration payment- failed as the card is not eligible for recurring payments. |
| `card_mandate_card_`
`not_supported` | This card is not eligible for recurring payments. Please use a different card. | Mastercard | 5305 6200 0003 0011 | Card mandate registration payment- failed as the card is not eligible for recurring payments. |
| `card_mandate_card_`
`not_supported` | This card is not eligible for recurring payments. Please use a different card. | RuPay | 6527 6589 0004 0011 | Card mandate registration payment- failed as the card is not eligible for recurring payments. |
| `card_mandate_bin_`
`not_supported` | Card BIN not supported for recurring payments. | RuPay | 6527 6500 0007 0022 | Card mandate registration payment- failed as the card number BIN is not eligible for recurring payments at Rupay Mandate Hub. |
| `card_disabled_for_`
`online_payments` | Your card has been disabled for online payments by your issuing bank. Please reach out to your bank or re-try the payment with another card or method. | Visa | 4100 2800 0003 0006 | Card mandate registration payment- failed as the card is disabled for online payments. |
| `card_disabled_for_`
`online_payments` | Your card has been disabled for online payments by your issuing bank. Please reach out to your bank or re-try the payment with another card or method. | Mastercard | 5305 6200 0000 0006 | Card mandate registration payment- failed as the card is disabled for online payments. |
| Error reason | Error description | Network | Card number | Testing scenario |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ------------------- | -------------------------------------------------------------------------------------------- |
| `card_not_enrolled` | Your payment could not be completed as this card is not enabled for online payments. Try another payment method or contact your bank for details. | Visa | 4100 2800 0004 0013 | Card mandate registration payment- failed as the card enrollment is not captured at Gateway |
| `card_not_enrolled` | Your payment could not be completed as this card is not enabled for online payments. Try another payment method or contact your bank for details. | Mastercard | 5305 6200 0001 0013 | Card mandate registration payment- failed as the card enrollment is not captured at Gateway |
| `card_not_enrolled` | Your payment could not be completed as this card is not enabled for online payments. Try another payment method or contact your bank for details. | RuPay | 6527 6589 0002 0013 | Card mandate registration payment- failed as the card enrollment is not captured at Gateway |
| `gateway_technical_error` | Your payment could not be completed due to incorrect OTP or verification details. Try another payment method or contact your bank for details. | Visa | 4100 2800 0000 0009 | Card mandate registration payment- failed as incorrect OTP / verification details are passed |
| `gateway_technical_error` | Your payment could not be completed due to incorrect OTP or verification details. Try another payment method or contact your bank for details. | Mastercard | 5305 6200 0007 0009 | Card mandate registration payment- failed as incorrect OTP / verification details are passed |
**BIN Not Supported Scenario: Token Rejected Despite Successful Registration for Visa and Mastarcard**
For the following Visa and Mastercard cards, the mandate registration payment **succeeds** (select **Success** on the payment page), but the recurring token is later **rejected at the Mandate Hub** because the card BIN is not supported. The rejection is communicated via a Razorpay webhook when mandate creation is attempted (`card_mandate_bin_not_supported`).
| Network | Card number | Testing scenario |
| ---------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Visa | 4100 2800 0005 0012 | Recurring mandate token rejection due to card BIN not supported at Mandate Hubs end. For Visa card the scenario arises as: The card mandate registration payment- succeeds(hence, select Success in payment page), but recurring token gets rejected by triggering a webhook when mandate creation is attempted at Mandate Hubs. |
| Mastercard | 5305 6200 0002 0012 | Recurring mandate token rejection due to card BIN not supported at Mandate Hubs end. For Mastercard card the scenario arises as: The card mandate registration payment- succeeds(hence, select Success in payment page), but recurring token gets rejected by triggering a webhook when mandate creation is attempted at Mandate Hubs. |
## Error Scenarios – Subsequent Payments
Use these test cards to simulate error conditions during **subsequent (auto-debit) payments**. First successfully register the mandate using the same card number, then attempt the subsequent payment. The payment reaches its terminal (failed) state about **5 minutes** after it is created, with the relevant Razorpay webhook triggered.
| Error reason | Error description | Network | Card number | Testing scenario |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ---------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `insufficient_funds` | Your payment could not be completed due to insufficient account balance. Try another card or payment method. | Visa | 4718 6000 0007 0021 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to Insufficient balance in customer bank account |
| `insufficient_funds` | Your payment could not be completed due to insufficient account balance. Try another card or payment method. | Mastercard | 5370 2800 0004 0021 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to Insufficient balance in customer bank account |
| `insufficient_funds` | Your payment could not be completed due to insufficient account balance. Try another card or payment method. | RuPay | 3539 2000 0005 0021 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to Insufficient balance in customer bank account |
| `token_not_eligible` | Token is not confirmed for recurring payments. | Visa | 4718 6091 2002 0014 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to an attempt made on a unconfirmed token. |
| `token_not_eligible` | Token is not confirmed for recurring payments. | Mastercard | 5370 2800 2009 0014 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to an attempt made on a unconfirmed token. |
| `pre_debit_notification_`
`failed` | The payment request failed as the pre-debit notification was not sent to the customer. | Visa | 4718 6091 2001 0015 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due PDN failure(i.e. customer not notified error). |
| `pre_debit_notification_`
`failed` | The payment request failed as the pre-debit notification was not sent to the customer. | Mastercard | 5370 2800 2008 0015 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due PDN failure(i.e. customer not notified error). |
| `card_mandate_not_active` | Card mandate is not active. | Visa | 4718 6091 2000 0016 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due customer cancellation of the mandate after the payment is created, it is determined when PDN is verified. |
| `card_mandate_not_active` | Card mandate is not active. | Mastercard | 5370 2800 2007 0016 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due customer cancellation of the mandate after the payment is created, it is determined when PDN is verified. |
| `card_mandate_not_active` | Card mandate is not active. | RuPay | 3539 2024 2000 0016 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due customer cancellation of the mandate after the payment is created, it is determined when PDN is verified. |
| `customer_action_required` | The payment request failed as the pre-debit notification was not approved. | Visa | 4718 6091 2009 0017 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed as customer did not approve Additional Factor of Authentication (AFA) request when debit amount is greater than the AFA limits([link](https://razorpay.com/docs/payments/recurring-payments/cards/faqs/#is-there-a-maximum-monetary-limit-for-processing-card-based-mandates)), it is determined when PDN is verified. |
| `customer_action_required` | The payment request failed as the pre-debit notification was not approved. | Mastercard | 5370 2800 2006 0017 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed as customer did not approve Additional Factor of Authentication (AFA) request when debit amount is greater than the AFA limits([link](https://razorpay.com/docs/payments/recurring-payments/cards/faqs/#is-there-a-maximum-monetary-limit-for-processing-card-based-mandates)), it is determined when PDN is verified. |
| `token_expired` | Token has expired and cannot be used for recurring payments. | Visa | 4718 6091 2008 0018 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed when its found out that the recurring token will be expiring before the debit attempt is tried(which is after 5 minutes in Test mode) |
| `token_expired` | Token has expired and cannot be used for recurring payments. | Mastercard | 5370 2800 2005 0018 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed when its found out that the recurring token will be expiring before the debit attempt is tried(which is after 5 minutes in Test mode) |
| `token_expired` | Token has expired and cannot be used for recurring payments. | RuPay | 3539 2024 2008 0018 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed when its found out that the recurring token will be expiring before the debit attempt is tried(which is after 5 minutes in Test mode) |
| `card_mandate_paused` | Card mandate is not active, it is paused by the user. | Visa | 4718 6091 2007 0019 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to customer pausing the mandate after the payment is created but before the debit is executed, it is determined when PDN is verified. |
| `card_mandate_paused` | Card mandate is not active, it is paused by the user. | Mastercard | 5370 2800 2004 0019 | First successfully register the mandate using this same card number, then attempt the subsequent payment. Card mandate subsequent payment- failed due to customer pausing the mandate after the payment is created but before the debit is executed, it is determined when PDN is verified. |
**Handy Tips**
* The `customer_action_required` scenario simulates a debit amount greater than the Additional Factor of Authentication (AFA) limit, where the customer did not approve the AFA request. Know more in the [Card Recurring Payments FAQs](/docs/payments/recurring-payments/cards/faqs/#is-there-a-maximum-monetary-limit-for-processing-card-based-mandates).
* The `card_mandate_not_active` and `card_mandate_paused` scenarios simulate the customer cancelling or pausing the mandate after the payment is created but before the debit is executed. This is determined when the pre-debit notification (PDN) is verified.