Test Tokens
Create test tokens with long-lasting CVC sessions for development and testing.Overview
Test tokens differ from regular tokens:Endpoint
Authentication
- API Key:
X-API-Keyheader - JWT Token:
Authorization: Bearerheader or cookie
Request
Fields
Note: Unlike regular tokenization, CVV is required for test tokens.
Response
Example
Key Differences
1. CVC Session TTL
This allows repeated testing without re-tokenizing.
2. CVC Persistence
Test tokens keep their CVC session for multiple proxy requests.
3. CVV Requirement
Use Cases
Integration Testing
Development Environment
Set up test tokens in your development seed data:CI/CD Pipelines
Test Card Numbers
Best Practices
1. Don’t Use in Production
Test tokens are for development only. Use regular/tokenize in production.
2. Separate Test Projects
Create a dedicated project for testing to avoid mixing test and production data.3. Clean Up Old Test Tokens
Periodically delete unused test tokens:Error Responses
Missing CVV
Invalid Card
Next Steps
- Card Tokenization - Production tokenization
- Proxy Service - Test proxy requests
- Examples - Integration examples