> ## Documentation Index
> Fetch the complete documentation index at: https://www.cashfree.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Data to Test Integration

> Use the test card numbers, UPI IDs, netbanking credentials, and OTPs supplied here to validate your Cashfree integration in the sandbox environment.

Use the test data on this page to validate your Cashfree integration before going live. Check [Supported sandbox features](#supported-sandbox-features) to confirm availability before testing.

<CardGroup cols={2}>
  <Card title="Core payment modes" icon="credit-card" href="#core-payment-modes">
    Test card numbers, netbanking credentials, and UPI VPAs for standard checkout flows.
  </Card>

  <Card title="Third-Party Verification (TPV)" icon="shield-check" href="#third-party-verification-tpv">
    Netbanking and UPI parameter configurations for TPV account validation testing.
  </Card>

  <Card title="Tokenisation and instalment programs" icon="lock" href="#tokenisation-and-instalment-programs">
    Token Vault BINs and credit and debit card EMI test credentials.
  </Card>

  <Card title="Alternative financing options" icon="hand-holding-dollar" href="#alternative-financing-options">
    Mobile numbers and PAN or OTP inputs for Paylater and Cardless EMI testing.
  </Card>
</CardGroup>

## Supported sandbox features

The following table lists the payment modes and functionality available for testing in the sandbox environment.

| Payment mode or feature | Sandbox support status |
| :- | :- |
| Card | Supported. Use the test card details provided below. |
| Netbanking | Supported. Use the test netbanking account provided below. |
| UPI | Supported. Use the test UPI Virtual Payment Addresses (VPAs). |
| Wallet | Supported through a single generic test wallet. Individual wallet providers, such as Paytm or AmazonPay, are not available for testing. |
| Credit and debit card EMI | Supported. Use the test EMI card details. |
| Paylater | Supported. Use the test details provided below. |
| Cardless EMI | Supported for transactions with a minimum amount of `1,000` (INR). |
| Preauthorisation (API) | Supported for card and UPI modes via the Order Pay `link` channel. |

<Warning>
  The sandbox environment does not support PayPal or bank transfer payment modes at this time.
</Warning>

### Test a preauthorisation transaction

To test a preauthorisation transaction, complete the following steps.

1. Create an order with the `order_note` parameter set to `preauth_transaction`.
2. Capture or void the authorised funds using the [Preauthorisation API](/docs/api-reference/payments/latest/payments/preauthorisation).

## Core payment modes

Use the test card credentials, netbanking simulation account, or UPI addresses below to validate standard checkout flows.

### Test card details

To test card transactions in the sandbox environment, select a card number from the tables below based on the transaction state you want to simulate.

#### Standard successful checkout testing

Use these configurations to simulate successful domestic card payments. For all cards in this table, use `111000` as the OTP, `03/2028` as the fixed expiry, `123` for CVV, and `Test` as the cardholder name.

<Accordion title="View standard successful checkout cards">
  | Scheme | Card type | Card sub-type | Card number 1 | Card number 2 |
  | :- | :- | :- | :- | :- |
  | Visa | Debit | Retail | `4706131211212123` | `4062288312345026` |
  | Visa | Credit | Retail | `4576238912771450` | `4444333322221111` |
  | Visa | Credit | Premium | `4466050254381183` | `4136880012657791` |
  | Visa | Credit | Corporate | `4074970084343075` | `4770355457382883` |
  | Mastercard | Debit | Retail | `5409162669381034` | `5445856839524391` |
  | Mastercard | Credit | Retail | `5105105105105100` | `5176539438527826` |
  | Mastercard | Credit | Premium | `5242535837492075` | `5203860658394375` |
  | Mastercard | Credit | Corporate | `5552190758372734` | `5506908329471983` |
  | Rupay | Debit | Retail | `6074825972083818` | `6074828163369590` |
  | Rupay | Credit | Retail | `6528591234543575` | `65292523412356` |
</Accordion>

#### International and USD scenario testing

Use these configurations to validate cross-border payment routing, currency conversion, subscription flows, and multi-factor bank authentication loops.

<Accordion title="View USD and international scenario cards">
  | Testing scenario | Card number | Expiry | CVV | Cardholder name |
  | :- | :- | :- | :- | :- |
  | Standard USD flow | `7000 0083 1380 6604` | `09/2027` | `581` | `Test` |
  | Standard USD flow | `7000 0091 5369 7715` | `12/2021` | `591` | `Test` |
  | Standard USD flow | `7000 0094 7240 2110` | `05/2024` | `204` | `Test` |
  | Standard USD flow | `7000 0055 0418 0328` | `08/2026` | `324` | `Test` |
  | Standard USD flow | `7000 0014 6659 2972` | `02/2026` | `153` | `Test` |
  | Recurring subscriptions | `4138 6748 6000 0008` | `01/2027` | `123` | `Test` |
</Accordion>

### Test netbanking

To test netbanking integrations, use the default test bank identifier below.

| Bank name | Payment code | Bank API code |
| :- | :- | :- |
| TEST Bank | `3333` | `TESTR` |

### Test UPI Virtual Payment Addresses (VPAs)

Pass the following test VPAs in your payment request payload to simulate specific transaction outcomes and error states.

<Accordion title="View UPI test VPAs and simulated responses">
  | Virtual Payment Address (VPA) | Simulated transaction response |
  | :- | :- |
  | `testsuccess@gocash` | Simulates a successful transaction. |
  | `testfailure@gocash` | Simulates a failed transaction. |
  | `testinvalid@gocash` | Simulates an invalid VPA error. |
  | `testdeclineuser@gocash` | Simulates a cancellation by the user. The application prompts the user to retry. |
  | `testexpired@gocash` | Simulates a session timeout where the user does not complete the transaction in time. |
  | `testtimeoutbank@gocash` | Simulates an issuing bank timeout. |
  | `testremitterunavailable@gocash` | Simulates an unavailable remitter bank instance. |
  | `testinsufficientfunds@gocash` | Simulates insufficient account funds. |
  | `testbankdeclined@gocash` | Simulates a generic reject response from the user's bank. |
  | `testriskflagged@gocash` | Simulates a transaction rejected due to bank security and risk assessments. |
  | `testnetworkerror@gocash` | Simulates a core network infrastructure failure. |
  | `testinvalidpin@gocash` | Simulates an incorrect PIN entry error. |
  | `testremitterdispatchfailed@gocash` | Simulates a delivery dispatch failure from the remitter bank. |
  | `testbeneficiarytimeout@gocash` | Simulates a timeout failure at the destination beneficiary bank. |
  | `testuserdropped@gocash` | Simulates an unattempted transaction abandonment by the customer. |
  | `testtransactionrisk@gocash` | Simulates a customer risk rejection profile check. |
  | `testfingerprintmismatch@gocash` | Simulates a hardware device biometric or fingerprint mismatch. |
  | `testinvalidvpa@gocash` | Simulates an improperly configured payment instrument. |
  | `testbankriskrejected@gocash` | Simulates an internal banking security policy rejection. |
  | `testremittertimeout@gocash` | Simulates a delayed response from the remitter bank. |
  | `testfraud@gocash` | Simulates an automated anti-fraud block by the payment service provider. |
  | `testvalidationerror@gocash` | Simulates a Third-Party Verification (TPV) account mapping failure. |
  | `testdebitfailed@gocash` | Simulates a failure during the account debit process. |
  | `testpspunregistered@gocash` | Simulates a blocked network state on the client application. |
</Accordion>

<Tip>
  Use the VPA that matches the error state you want to handle in your integration. This helps you verify that your error handling covers each failure mode before going live.
</Tip>

## Third-Party Verification (TPV)

### Test TPV netbanking

Third-Party Verification (TPV) ensures that the funding bank account matches your database records. Use these parameters to simulate a validated netbanking setup.

| Bank parameter | Static testing value |
| :- | :- |
| `accountNumber` | `1111222233` |
| `ifsc` | `TEST0001234` |

### Test TPV UPI

Use these parameters to test account authorisation over the UPI rails.

<Accordion title="View TPV UPI configurations and parameter testing values">
  | Parameter | Testing value |
  | :- | :- |
  | `userVPA` (success) | `testtpvsuccess@gocash` |
  | `userVPA` (fail) | `testtpvfail@gocash` |
  | `accountNumber` | `1111222233` |
  | `ifsc` | `TEST0001234` |
</Accordion>

## Tokenisation and instalment programs

### Token Vault test cards

To build a test card number for Token Vault API configurations, append any random 10-digit sequence to the card BINs below. Expiry can be any future date and CVV any 3-digit number.

<Accordion title="View Token Vault supported card BIN groups">
  | Scheme | Supported card BIN |
  | :- | :- |
  | Visa | `470613, 457623, 436534, 415527, 466535` |
  | Mastercard | `559423, 544405, 533983, 555219, 524877` |
</Accordion>

### Credit card EMI test cards

Use the following credit cards to validate EMI calculations and processing endpoints. Expiry can be any future date and CVV any 3-digit number.

<Accordion title="View credit card EMI identifiers and testing credentials">
  | Issuing bank | Bank card parameter name (`card_bank_name`) | Card number |
  | :- | :- | :- |
  | Axis Bank | Axis | `4111 4647 7655 4152` |
  | Standard Chartered Bank | Standard Chartered | `4622 7185 3202 3725` |
  | ICICI Bank | ICICI | `4748 4661 2346 7526` |
  | Kotak Bank | Kotak | `4363 9070 5531 5237` |
  | HDFC Bank | HDFC | `5241 8100 0000 0000` |
  | RBL Bank | RBL | `4112 5597 3537 3674` |
  | Bank of Baroda | BOB | `4111 5638 8133 3699` |
  | AU Bank | AU | `4111 5849 6705 0056` |
  | Citi Bank | CITI | `4112 5229 6265 9579` |
  | Yes Bank | YES | `4111 6514 1790 3257` |
  | IndusInd Bank | INDUS | `4111 5351 6094 6904` |
  | HSBC Bank | HSBC | `4111 6668 0832 0291` |
  | Federal Bank | FED | `4111 5924 7037 2263` |
</Accordion>

### Debit card EMI test cards

Use this configuration to test debit card EMI processing.

| Issuing bank | Bank card parameter name (`card_bank_name`) | Card number |
| :- | :- | :- |
| HDFC Bank | HDFC | `4386 2412 2321 5159` |

## Alternative financing options

### Paylater integration details

To test standard Paylater partner platforms, use the registered mobile number below.

| Provider instance | Registered mobile number |
| :- | :- |
| Any | `8714268343` |

### Cardless EMI integration details

Use the following mobile number to simulate user registration states for Cardless EMI options.

| Provider instance | Registered mobile number | Required input parameters |
| :- | :- | :- |
| Any | `8714268343` | If prompted for **PAN**, use `1234`.<br />If prompted for **OTP**, use `777777`. |

<Note>
  Complete all integration testing in the sandbox environment before deploying to production. For broader recommendations on building reliable integrations, see [API best practices](/docs/api-reference/api-best-practices).
</Note>

<div class="hidden" data-table-of-contents="bottom">
  <p class="mt-4 font-medium flex items-center gap-2 related-docs-heading">
    <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" class="w-4 h-4">
      <path d="M3 4h7a2 2 0 0 1 2 2v13a2 2 0 0 0-2-2H3z" />

      <path d="M21 4h-7a2 2 0 0 0-2 2v13a2 2 0 0 1 2-2h7z" />
    </svg>

    <span>Related topics</span>
  </p>

  <ul>
    <li><a href="/docs/payments/overview">Payments Overview</a></li>
    <li><a href="/docs/api-reference/integration-troubleshooting/payments-ts">Payments API troubleshooting</a></li>
    <li><a href="/docs/api-reference/api-best-practices">API best practices</a></li>
  </ul>
</div>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.