Skip to main content
POST
/
v1
/
tokens
{
  "account_id": "fe14c7c6-c75e-43b7-bdbe-4c87ad52c482",
  "card_data": {
    "number": "4111111111111111",
    "expiration_month": 12,
    "expiration_year": 25,
    "security_code": "123",
    "holder_name": "Dee Hock"
  }
}
{
  "token": "9107a30f-564c-4469-bd7c-8e1f249fb016",
  "card_data": {
    "holder_name": "Dee Hock",
    "iin": "41111111",
    "lfd": "1111",
    "brand": "VISA",
    "type": "DEBIT",
    "issuer_name": "CONOTOXIA SP Z O O"
  }
}
Creates a one-time-use token from the customer’s card data as part of the DIRECT workflow. This endpoint is exclusively for PCI-compliant merchants who collect card data on their own servers.
This endpoint requires PCI DSS certification. If you are not PCI certified, use the SDK Checkout token flow instead, which handles card data securely on the client side.

Authentication

Requires both public-api-key and private-secret-key headers.

Request Body

account_id
string
required
The unique identifier of the account. Found in Yuno’s Dashboard.Constraints: MAX 64; MIN 36
card_data
object
required
Card details to tokenize.
country
string
Customer’s country. ISO 3166-1 alpha-2 code.Example: US
customer_payer
object
Optional customer information for fraud screening and 3DS.
stored_credentials
object
Stored credential details for recurring or merchant-initiated transactions.
{
  "account_id": "fe14c7c6-c75e-43b7-bdbe-4c87ad52c482",
  "card_data": {
    "number": "4111111111111111",
    "expiration_month": 12,
    "expiration_year": 25,
    "security_code": "123",
    "holder_name": "Dee Hock"
  }
}
{
  "token": "9107a30f-564c-4469-bd7c-8e1f249fb016",
  "card_data": {
    "holder_name": "Dee Hock",
    "iin": "41111111",
    "lfd": "1111",
    "brand": "VISA",
    "type": "DEBIT",
    "issuer_name": "CONOTOXIA SP Z O O"
  }
}

Response Fields

token
string
The one-time-use token. Use this in the Create Payment request as payment_method.token.
card_data
object
Tokenized card metadata (no sensitive data).