Yuno tokenization coverage
Yuno’s tokenization platform is not limited to cards. Tokens are issued for any payment method flowing through Yuno, including:- Credit and debit cards
- Digital wallets such as Apple Pay, Google Pay, and Click to Pay
- Bank transfers and local payment methods including ACH, PIX, and regional alternatives
- Alternative payment methods for buy-now-pay-later, vouchers, and more
Token types
Yuno issues three types of tokens, each suited to a different integration scenario.One-time use token
When using Yuno’s SDK, all necessary payment information is gathered and stored in a one-time use token scoped to a single checkout session. This token is used once when creating the payment and cannot be reused. One-time tokens are the right choice for:- Guest checkouts with no stored payment method
- Single-use transactions where vaulting is not required
Vault on successSet
vault_on_success: true in the token request, or payment_method.vault_on_success: true on the payment, to automatically enroll and vault the payment method if the payment succeeds. This converts a one-time token into a persistent vaulted token without a separate enrollment step.Vaulted token
A vaulted token is created when a payment method is enrolled and securely stored in Yuno’s centralized vault alongside the customer’s information. You can use the vaulted token to authorize future payments without the customer re-entering their details. Vaulted tokens are the right choice for:- Returning customers with saved payment methods
- Subscriptions and recurring billing
- One-click checkout flows
Network token
A network token is a digitized representation of a card’s Primary Account Number (PAN). It’s issued directly by card networks such as Visa, Mastercard, or American Express. When network tokenization is enabled, Yuno automatically provisions and manages network tokens for all enrolled cards. These tokens replace the actual card data during authorization. Network tokens are the right choice for:- High-value recurring transactions where maximizing authorization rates matters
- Scenarios requiring enhanced fraud protection at the network level
Learn moreFor a full overview of network tokens, lifecycle statuses, and integration options, see Network Tokens.
Provider token
Some payment methods are authorized at the provider, such as a Pix Automático authorization with EBANX. The provider identifies that authorization with its own reference, the provider token. Yuno stores it inside the customer’s vaulted payment method, so your integration never handles it: you charge with thevaulted_token and Yuno sends the provider token with the payment. Only the provider that issued it can use it, so route payments made with that vaulted_token to that provider; Yuno sends it to the provider your routing selects.
Saving a payment method while paying
For Pix with EBANX, the authorization is created during the first payment: sendpayment_method.vault_on_success: true on that payment. Yuno stores the provider token and saves the payment method for the customer:
- First payment (customer-initiated): create the payment with the customer (
customer_payer.id),payment_method.vault_on_success: trueand asubscriptionblock that describes the authorization. The customer approves it outside your page. - The vaulted token: the saved payment method appears in Retrieve Enrolled Payment Methods as soon as the payment is created, and its token is in
transactions[].payment_method.vaulted_tokenin Retrieve Payment once the payment reachesSUCCEEDED. It is not in the create response. Charge it only after the customer approves: before that, charges are declined. - Later payments (merchant-initiated): send
payment_method.vaulted_token. Yuno charges the stored authorization without a new customer approval. - Checkout: returning customers see the saved Pix in the SDK checkout and can pay with one click, when you create the checkout session with their
customer_id.
type: "CARD", provider_data.token_source: "PROVIDER_TOKEN", the provider in provider_data.id, the connection in provider_data.connection_id and the provider reference in provider_data.payment_method_token. Yuno returns a vaulted_token you use the same way.
For a complete example, see Pix with vault on success.
Token comparison
Additional tokenization capabilities
Card fingerprinting
Every card enrolled through Yuno receives afingerprint, a stable, cryptographic identifier derived from the PAN. Fingerprints remain consistent across multiple enrollments of the same card. This lets you detect duplicates and deduplicate your vault without ever accessing or storing raw card numbers. See Card Fingerprint.