Fully PCI certified customers may want to provision their own network tokens rather than relying on our network token provisioning. To allow for this, we’ve enabled support for network token pass through via our API, either with or without cryptogram, straight through to a connector.

  • Any network token can be passed through, though acceptance (especially in sandbox) will vary by connector used
  • Network tokens can benefit from our BIN insights, though in the sandbox environment the number of cards that will result in a valid BIN insights is limited
  • Storing externally provisioned network tokens in our vault is currently not supported


To pass through a network token, set the method value to network-token when creating a transaction. The cryptogram value can be set as well, but is optional in our API. Acceptance of network tokens downstream will vary per connector.

curl -i -X POST "https://api.{gr4vy_id}.gr4vy.app/transactions" \
    -H "Authorization: Bearer [JWT_TOKEN]" \
    -H "Content-Type: application/json" \
    -d '{
          "amount": 1299,
          "currency": "AUD",
          "intent": "capture",
          "payment_method": {
            "method": "network-token",
            "number": "4111111111111111",
            "expiration_date": "11/25",
            "cryptogram": "..."