Skip to main content

POST /tokenize

Create a token from sensitive card or bank account data. Card data can include an optional CVV, which is stored in a separate CVC session (90-second TTL; deleted after use in proxy). Auth: X-API-Key (or JWT) is always required. X-Pub-Key is required when using a production vault API key; test/sandbox API keys do not require it. Get an API key by creating an account at Ozura Vault. For a production pub key, contact ammar@ozura.com.

Request

Request body

CVV/CVC handling

  • If cvv or cvc is provided: stored in a separate CVC session, 90-second TTL, deleted after use in proxy; response includes cvc_session_id.
  • If omitted: no CVC session; no cvc_session_id in response; CVC cannot be used in proxy.
For long-lived test CVC sessions (e.g. 1-year), use POST /test-tokens.

Response

201 Created

Request may include optional maskingConfig for custom masking behavior.

Validation

  • Card number: 13–19 digits, Luhn valid; spaces/dashes stripped.
  • Expiration: month 01–12; year current or future.
  • CVV: 3 digits (Visa, MC, Discover), 4 (Amex).

Error responses

See Status codes and Common errors.