# Test Cards for Payments API
Use these test card numbers to simulate different payment scenarios during development and testing. These cards will trigger various responses and help you test different flows in your integration.
## How to Use Test Cards
- **Environment:** Test cards only work in development/sandbox environments
- **CVV:** Use any 3-digit number for CVV (e.g., 123, 456, 789)
- **Expiry Date:** Use any future date (e.g., 12/25, 06/26, 10/27)
- **Cardholder Name:** Use any name for testing
- **Transaction Amount:** Set it when creating the transaction. Amounts are defined as minor units (e.g., 100 for €1.00)
## Test Payment Cards
Use these test card numbers for payment integration testing:
```grid
card:
title-left: Visa
title-right: Test Card
content: 4427800000180034
additional note: Use case: Visa testing
additional note: CVV: Any 3-digit number (e.g., 123)
additional note: Expiry: Any future date
additional note: Amount: Any amount
card:
title-left: Mastercard
title-right: Test Card
content: 5555555555554444
additional note: Use case: Mastercard testing
additional note: CVV: Any 3-digit number (e.g., 456)
additional note: Expiry: Any future date
additional note: Amount: Any amount
card:
title-left: American Express
title-right: Test Card
content: 373953192351004
additional note: Use case: American Express testing
additional note: CVV: Any 4-digit number (e.g., 6789)
additional note: Expiry: Any future date
additional note: Amount: 7600 (e.g. 76.00€)
card:
title-left: Mastercard
title-right: DCC Test Card (EUR)
content: 2223600089700011
additional note: Use case: Mastercard DCC testing (EUR)
additional note: CVV: Any 3-digit number (e.g., 123)
additional note: Expiry: Any future date
additional note: Amount: Any amount
```
## Testing Best Practices
- **Test All Scenarios:** Use cards from each category to ensure your integration handles all possible responses
- **Error Handling:** Pay special attention to declined and error cards to test your error handling logic
- **Async Processing:** Use processing delay cards to test your webhook and polling implementations
- **Security:** Test 3D Secure cards to ensure your authentication flows work correctly
- **Amount Variations:** Test with different amounts (small, large, with decimals) to ensure proper handling
- **Currency Testing:** Test with different currencies (EUR, USD, GBP) if your integration supports multiple currencies
## Important Notes
```admonition
icon: fas fa-exclamation-triangle
content: These test card numbers will only work in development/sandbox environments. Never use real card details in testing, and ensure test cards don't work in production.
```
- **Production Safety:** Test cards are automatically rejected in production environments
- **PCI Compliance:** Never store test card details in production systems
- **Logging:** Be careful when logging test card data - treat it like real card data
- **Documentation:** Always document which test cards you're using in your test scenarios