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

# Test Credentials

> Card numbers and credentials for sandbox testing.

# Test Credentials

## Test Card Numbers

Ozura Checkout accepts card numbers of **13–19 digits** (Luhn-valid). Any of these test card numbers will work in sandbox mode.

| Card Type   | Number             |
| :---------- | :----------------- |
| Visa        | `4000000000000002` |
| Mastercard  | `5121212121212124` |
| Amex        | `370000000000002`  |
| Discover    | `6011000000000004` |
| Diners Club | `36111111111111`   |
| JCB         | `3566664444444445` |

**CVV:** Any 3 digits (4 digits for Amex)
**Expiry:** Any future date

<Note>
  **Outcome is determined by the amount, not the card.** Ozura's processor (Elavon) decides approval or decline from the transaction amount: `.00` approves, `.88` declines, `.13` returns an amount error. See the [Checkout Testing Guide](/guides/payments/checkout/testing-guide#elavon-sandbox-testing) for the full amount-based model and tax pitfalls.
</Note>

<Note>
  These test cards only work in the sandbox environment. Production keys will reject them.
</Note>

## Getting a Test Vault Key

A test vault key is required for sandbox testing. See [Sandbox → Getting a Test Vault Key](/guides/sandbox#getting-a-test-vault-key) for the full numbered steps.

The same test vault key works directly with the [Elements SDK](/sdks/elements/installation) — omit `pubKey` from `OzVault.create()` and the vault will accept the test key without an `X-Pub-Key` header.