Skip to main content
PSP tokenization provisions a card stored in the Gr4vy vault as a token on a specific payment provider (PSP). The provider issues its own token that references the card on their side. This token is the provider’s reusable reference to the stored card, not a single-use token. PSP tokens are used when a downstream service requires a provider-specific reference rather than raw card data — for example, when migrating recurring mandates or storing a card on a provider for future use.

PSP tokens vs network tokens

For most use cases, network tokens are preferred because they can be more portable across supported providers and provide higher authorization rates. PSP tokens are useful when a specific provider requires its own token format.

Provisioning a PSP token

To provision a PSP token, the card must already be stored in the Gr4vy vault as a payment method. Call the provision endpoint with the target payment service ID.
The response contains the provisioned token details, including the provider’s token reference.

Listing PSP tokens

To retrieve existing PSP tokens for a payment method:

Deleting a PSP token

When you delete a PSP token, Gr4vy removes it from the payment method. For connectors that support deleting tokens, Gr4vy also asks the provider to delete its stored copy. If the provider declines that request, the API returns an error and Gr4vy keeps the token. For other connectors, Gr4vy removes the token only on its side, and the stored card stays with the provider. Connectors that support it list Delete token in the Capabilities section of their connection page. You can delete PSP tokens for card payment methods only.

API reference

Provision PSP token

POST /payment-methods/payment_method_id/payment-service-tokens

List PSP tokens

GET /payment-methods/payment_method_id/payment-service-tokens

Delete PSP token

DELETE /payment-methods/payment_method_id/payment-service-tokens/payment_service_token_id