Network tokens

A network token is a network-issued surrogate for a card’s PAN — a reusable value scoped to your merchant account that the schemes will keep in sync with the underlying card automatically (a reissued or expired card updates the token behind the scenes, so a stored token stays valid longer than a raw PAN would). Requesting one is a single flag on the card payment intent — there is no separate tokenization endpoint.

Requesting a token

Add create_token: true when you create the intent. It defaults to false, so existing integrations are unaffected unless you opt in.

Create an intent that requests a network token

curl https://api.paygasus.com/payments/card \
  -H "Authorization: Bearer sk_test_…" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1000,
    "currency": "USD",
    "capture_method": "automatic",
    "create_token": true
  }'

Authorize the intent exactly as in the Quickstart — the token request rides along with the charge, it doesn’t change the authorize call itself.

Reading the outcome

After authorization, the response carries a network_token object reporting what actually happened on the processor’s side. It’s null whenever no token outcome applies (create_token was left false, or the network didn’t return one).

200 OK — network token minted

{
  "id": "pi_card_9Z3K01ARZ3NDEKTSV4RRFFQ69G5FAV",
  "amount": 1000,
  "amount_captured": 1000,
  "status": "committed",
  "capture_method": "automatic",
  "create_token": true,
  "payment_method": { "brand": "visa", "last4": "0019" },
  "network_token": {
    "token": "4895142213539871",
    "source": "TRANSARMOR",
    "authorized_source": "PAN",
    "lookup_result": null
  },
  "created": 1746500000,
  "updated": 1746500071,
  "livemode": false
}

Field	Description
token	The reusable token value, present only when one was minted. Persist this if you intend to reference it on future charges outside this flow.
source	The token service provider or network scheme that issued it (e.g. TRANSARMOR).
authorized_source	Whether this specific authorization was actually completed using the raw PAN or an existing TOKEN — the network’s tokenization can be transparent to the request you sent.
lookup_result	The network-token-vs-PAN lookup outcome the processor returned, when it returns one.

All fields are independently optional

network_token’s fields are forward-compatible and reported only when the processor returns them — don’t assume token is present just because create_token was true on the request, and don’t treat a null network_token object as an error.

Next steps

• Review the Quickstart for the create → authorize → commit lifecycle this flag attaches to.
• See Stored credentials if you’re also chaining recurring or card-on-file charges — the two features are independent and can be combined on the same intent.
• Browse the full API reference for the complete CreateCardPaymentIntentRequest and NetworkToken schemas.