Verify and store a card token
POST/v1/tokenization/tokenize
Receives a BasisTheory token ID created client-side by the frontend SDK, verifies it against BasisTheory, and persists card metadata (last4, expiry) for future use including saved-card functionality for returning customers.
Returns the verified token ID that can subsequently be used with Coinflow for payment processing.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
- 502
Token verified successfully
Invalid or missing request parameters
Unauthorized. When returned from tokenization/checkout handlers this reflects an upstream credential or permission failure (for example BasisTheory), not a missing merchant API key on the request.
Forbidden (e.g. merchant account inactive)
Resource not found
Upstream rate limit exceeded. The response does not currently include a Retry-After header.
Internal server error
Upstream provider error (e.g. BasisTheory)