Tokeni docs

Tokeni is card tokenization infrastructure. You send card data into an isolated CDE. You get back an opaque token. Your application stores the token, not the PAN.

Sandbox: https://sandbox-api.tokeni.io

Production: https://api.tokeni.io

Dashboard: https://dashboard.tokeni.io

Start here

Quickstart

Keys, sandbox, first token.

Hosted fields

Collect PANs in a Tokeni iframe.

Charge a token

Tokenize, store, debit.

API

Every merchant endpoint.

What Tokeni does

Vault. Tokenize and detokenize. AES-256-GCM at rest. Tokens are opaque. Display uses BIN + last four (411111******1111).
Hosted fields. Card data is typed into a Tokeni iframe. Your origin never sees the PAN.
Pay by link. Hosted checkout links that return a token when the customer pays.
Profiles. Store tokens against a customer profile for recurring use.
PCI compatibility. TokenEx-shaped /v2/Pci routes if you are migrating.

Raw card data does not leave the CDE. CVV is never stored after authorization.

Ask the docs

Use Ask AI on any page, or point an MCP client at https://docs.tokeni.io/mcp. The assistant searches these docs. It will not take a PAN or CVV, and it cannot call the API for you.