Securely store sensitive strings like card numbers.
This page is part of the REST API Guides. Using the JavaScript library instead? See Payments Library Guides.
Prerequisites:API key configured.The StringTokens service lets you tokenize and store any sensitive string: card numbers, full card details as JSON, addresses, or any data up to 16,384 characters. The token can then be used in place of the raw data in subsequent API calls.
PCI Compliance: If you store card details and later retrieve them, your system is exposed to raw card data and is in scope for PCI compliance. Consider using tokens only for storage and referencing them in payment requests without retrieval.
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)
Security Best Practice: Store each piece of sensitive data in its own individual token rather than combining multiple values into a single token. For example, create separate tokens for the card PAN, CVV, and cardholder ID. This approach limits exposure if a token is compromised and provides more granular control over data access and lifecycle management.