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

# 3-D Secure Testing

Before testing 3DS in `sandbox` there is some configuration required:

* Configure 3DS for each of the schemes that you want test with against your primary card connector
* Ensure Flow rules do not `skip` 3DS for your specific test scenarios

Our 3DS server uses different card numbers to simulate various responses. You can use the following test cards.

<Note>
  Each connector handles sandbox testing and test PANs differently, so it may or may not be possible to use these PANs to test end-to-end in sandbox.  Please reach out should you have
  any questions about testing different 3DS scenarios end-to-end.
</Note>

### Frictionless flow - Successful - status 'Y' (ECI 05)

| Test PAN           | Scheme       | Expiry | Security Code |
| ------------------ | ------------ | ------ | ------------- |
| `5200000000001203` | `mastercard` | 03/30  | 100           |
| `4111111111101203` | `visa`       | 03/30  | 100           |
| `340000000022003`  | `amex`       | 03/30  | 1000          |
| `3558111111121203` | `jcb`        | 03/30  | 100           |
| `8171998927611203` | `unionpay`   | 03/30  | 100           |

### Challenge flow - Successful or Declined - status 'Y' (ECI 05) or 'N'

| Test PAN           | Scheme       | Expiry | Security Code |
| ------------------ | ------------ | ------ | ------------- |
| `5240000000001072` | `mastercard` | 03/30  | 100           |
| `4111111111181072` | `visa`       | 03/30  | 100           |
| `340000000082072`  | `amex`       | 03/30  | 1000          |
| `3558111111121872` | `jcb`        | 03/30  | 100           |
| `8171998927611872` | `unionpay`   | 03/30  | 100           |

<Note>
  `status` in the above table refers to the transaction API response field `three_d_secure.response_data.authentication_response`
</Note>