Skip to main content
POST /api/v1/tokenization/generate

โ€‹
Request parameters

ParameterTypeRequiredDescription
tokenRequestIdStringYesIdempotency key for the card binding request
merchantUserIdStringYesUser ID on the merchant side
tokenTypeStringYesToken type, fixed as "CARD"
merchantInfoObjectYesMerchant information (includes merchantId)
notifyUrlStringYesWebhook callback URL for the card binding result
tokenDataObjectNoCard data (PCI-DSS merchants only)

โ€‹
tokenData (PCI-DSS merchants only)

ParameterTypeDescription
panStringCard number
nameStringCardholder name
expiryStringExpiration date (MM/YYYY)
cvvStringCVV

โ€‹
Response parameters

ParameterTypeDescription
tokenSessionIdStringSession ID, pass to the frontend SDK tokenizationSubmit
tokenIdStringToken ID (returned only when PCI-DSS merchants submit directly)

โ€‹
Request example

โ€‹
Standard flow (submitted via frontend SDK)

{
  "tokenRequestId": "treq_a1b2c3d4e5f6",
  "merchantUserId": "user_123",
  "tokenType": "CARD",
  "merchantInfo": { "merchantId": "M000001" },
  "notifyUrl": "https://your-site.com/webhook/tokenization"
}

โ€‹
Response example

{
  "code": "0",
  "msg": "Success",
  "data": {
    "tokenSessionId": "tsess_xxxxxxxxxxxx"
  }
}
After obtaining tokenSessionId, pass it to the frontend SDK method tokenizationSubmit to complete card submission.

โ€‹
Card binding result notification

After card binding is completed, Waffo sends a Webhook notification to notifyUrl containing tokenId. The merchant must store this tokenId for subsequent payments.