Skip to main content

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.

Vaulting is Gr4vy’s secure card storage and forwarding capability. It covers three related workflows:
  1. Tokenization — capture and store card details in the Gr4vy vault. Using Secure Fields or the mobile SDK keeps raw PAN off your servers; direct API tokenization requires a PCI-compliant environment.
  2. PSP tokenization — provision a provider-specific token for a vaulted card on a payment service. Use this when a downstream service requires its own token format rather than raw card data.
  3. Vault Forwarding — proxy stored card data directly to a third-party PCI-compliant endpoint, such as a booking system, loyalty platform, or order management service.
Together these capabilities let you handle card data securely across your entire stack — from first capture through to downstream partners — while helping to reduce your PCI scope.

​
Get started

  1. Tokenize a card to store it in the vault
  2. Provision a PSP token if a downstream service requires a provider-specific token
  3. Forward vaulted data to a third-party API endpoint

​
Explore further

Once the basics are in place, the feature guides cover the rest of what Vaulting can do.

PSP Tokenization

Provision, list, and delete provider-specific card tokens

Enable an endpoint

Allow a host to receive forwarded PCI data in production

CVV & Secure Fields

Forward a security code collected via Secure Fields or a checkout session

3DS forwarding

Forward 3DS authentication data alongside card details

Network token forwarding

Forward network tokens and cryptograms to third-party endpoints

Advanced authentication

Configure request signing, mutual TLS, or payload encryption