This page is part of the REST API Guides. Using the JavaScript library instead? See Payments Library Guides.
Why Tokenize
- Security: Sensitive data stays in Orchestra’s vault, not your systems
- Compliance: Reduces PCI scope when storing card numbers
- Flexibility: Store any string data (card numbers, JSON, addresses)
Create a Token
Store a string and receive a token reference. Endpoint:POST /StringTokens
StringTokens API Reference
Complete parameter reference and response fields
Retrieve Token Contents
Retrieve the original string stored behind a token. Endpoint:GET /StringTokens/{token}
Retrieve Token Metadata
Get metadata about a token without retrieving the actual contents. Endpoint:GET /StringTokens/{token}/meta
Delete a Token
Permanently delete a stored token. Endpoint:DELETE /StringTokens/{token}
Using Tokens with Payment Gateway
Reference a token in thecardNumber field with an @ prefix when making payment requests:
The
@ prefix tells Orchestra to look up the token value. Without it, the string is treated as a literal card number.Storing Full Card Details
You can store any string, including JSON-stringified card details:Related
Charge Payments
Use tokens in payment requests
StringTokens API
Full endpoint documentation