*All random cards generated are structurally valid but have no actual balance and cannot be used for online payments or real transactions. Any attempt to use these test card numbers for actual purchases is strictly prohibited and illegal. For more details, visit our Terms of Service.
Result by last digit
Return codes in the sandbox differ from production.
| Code | Result | Notes |
|---|---|---|
| XXXX XXXX XXXX XXX0 / 1 / 4 | Authorized | Return code 4 or 6: operation successful |
| XXXX XXXX XXXX XXX2 | Not authorized | Return code 05: not authorized |
| XXXX XXXX XXXX XXX3 | Not authorized | Return code 57: expired card |
| XXXX XXXX XXXX XXX5 | Not authorized | Return code 78: blocked card |
| XXXX XXXX XXXX XXX6 | Not authorized | Return code 99: timeout |
| XXXX XXXX XXXX XXX7 | Not authorized | Return code 77: cancelled card |
| XXXX XXXX XXXX XXX8 | Not authorized | Return code 70: problems with the credit card |
| XXXX XXXX XXXX XXX9 | Random result | Return code 6 (successful) or 9 (timeout) |
Source: official Cielo documentation, checked on 2026-09-18
Example from the documentation
| Card number | Result | Notes |
|---|---|---|
| 4024 0071 5376 3191 | Authorized | Ends in 1, so it is authorized. It does not pass the Luhn check, which the sandbox ignores for plain transactions. |
Source: official Cielo documentation, checked on 2026-09-18
- To test tokenization (saving the card), Cielo recommends using a card generator so the number passes the Luhn (mod 10) check, which is enforced in both sandbox and production. Generate one with the last digit you need using the test card generator.
- The sandbox evaluates only the format and the last digit, so even a real card number behaves as in the table above.
- These numbers only work in the provider's test mode. They have no balance and are rejected in production.
- Providers change their sandbox cards from time to time. If a number stops working, check the linked documentation.
- Need numbers for a specific BIN instead? Use the test card generator.