Attach a token to a customer
A tokenization call returns a short-lived token. The attach call turns that token into a payment instrument on a customer record, consuming the token in the process.
Risk metadata
riskMetadata is the field on a tokenization request that carries the customer's device, browser, and session context to the issuer. The richer the data you send, the higher the chance of a frictionless 3DS outcome and the better Payments AI can score the transaction for fraud.
Token lifecycle
A payment-instrument token is a short-lived value created during tokenization. It has a defined lifecycle and is single-use: it can be spent exactly once, either on a transaction or on an attach call, at which point it is consumed. The token also carries the CVV the customer typed, and that CVV covers exactly one charge.
When to use FramePay vs the server-side tokenization endpoint
Payments AI offers two ways to turn raw card data into a token your server can store. They serve different integration shapes; pick the one that matches yours.