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

# Test Cards

> This document provides a list of test credit card details that merchants can use to simulate transactions while integrating with the payment gateway API. These test cards help ensure that your payment processing system functions correctly without real transactions.

## **Important Note**

<Warning>
  These test card details are only for testing purposes and cannot be used for actual transactions. Always ensure you are in the development environment before using these cards.
  For additional scenarios, please reach out our [Support Team](/support/contact).
</Warning>

## **Test Card Details**

Below are the test card numbers for simulating different transaction scenarios:

| Scenario                                             | Description                                                                                                     | Card Values                                                                                      |
| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------- |
| **Successful frictionless 3DS** - Authorized Payment | Issuer assessment resulted in a frictionless 3DS authentication                                                 | **Visa**:4000000000001000 <br />**Mastercard**:5200000000001005  <br />**AMEX**: 340000000001007 |
| **Successful 3DS challenge** - Authorized Payment    | Issuer prompts a challenge in authentication, customer responds successfully                                    | **Visa**:4000000000001091<br />**Mastercard**:5200000000001096<br />**AMEX**:340000000001098     |
| **Failed frictionless 3DS authentication**           | Issuer failed the 3DS authentication without offering a challenge                                               | **Visa**:4000000000001018<br />**Mastercard**:5200000000001013<br />**AMEX**:340000000001015     |
| **Failed challenged 3DS authentication**             | Issuer prompts a challenge in authentication, customer responds with incorrect details (e.g., OTP, fingerprint) | **Visa**:4000000000001109<br />**Mastercard**:5200000000001104<br />**AMEX**:340000000001106     |
| **Refused Payment**                                  | The issuer refused the payment, if 3DS is used it’s frictionless                                                | **Visa**:4000000000001042<br />**Mastercard**:5200000000001047<br />**AMEX**:340000000001049     |

<Note>
  For all the test cards listed above:

  * Visa and Mastercard : Use any three-digit CVV.

  * American Express : Use any four-digit CVV.

  * Expiry Date : Any future date is valid.\
    These test cards are designed to simulate successful transactions.
</Note>

## **Usage Instructions**

1. **Integrate the Payment Gateway API**: Follow the integration guidelines in the payment gateway API documentation.

2. **Use Test Card Details**: Replace the card details in your API requests with the test card numbers provided above. You may use any CVC value (e.g., 100).

3. **Simulate Transactions**: Use the test cards to simulate various transaction scenarios (e.g., successful payments, declined transactions) to validate your integration.

## **Additional Testing Scenarios**

* **Successful Payment**: Use any valid card number from the table above to simulate a successful transaction.

* **Declined Payment**: Use a card number specifically designated for declined payments.

* **Expired Card**: Enter an expired date (e.g., 01/20) to test how your integration handles expired cards.

<Tip>
  Testing with various scenarios helps ensure that your integration handles all possible outcomes effectively.
</Tip>

<Card title="Need Assistance?" icon="life-ring" href="/support/contact">
  If you need further assistance, please [reach out to our support team](./support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.
</Card>