Tokenization replaces a raw card number (PAN) with a secure token that can be stored and reused. This can help reduce your PCI scope, but your scope depends on how you collect and send card data. Gr4vy supports two types of tokenization:Documentation Index
Fetch the complete documentation index at: https://docs.gr4vy.com/llms.txt
Use this file to discover all available pages before exploring further.
- Gr4vy vault token — the card is stored in the Gr4vy vault and referenced by a payment method ID. Use this for checkout, recurring payments, and vault forwarding.
- PSP token — the card is additionally tokenized on a specific payment provider. Use this when a downstream service needs a provider-specific token rather than raw card data.
Store a card in the vault
To store a card you create a payment method. This can be done via the API directly, or through one of the Gr4vy SDKs.Via the API
Use thePOST /payment-methods endpoint to store a card. The card is immediately vaulted and a payment method ID is returned for future use.
id of the new payment method, which you can use for transactions or vault forwarding.
API reference
POST /payment-methods
Via the mobile SDK
For mobile apps, use the native SDKtokenize method to securely collect and vault card details without the raw data passing through your servers.
Mobile SDK vaulting guide
Vaulting cards with the native SDKs