Yuno replaces sensitive payment credentials with a token: a non-sensitive string your systems store and pass back at payment time. You never touch raw card data, and Yuno handles vaulting, retries, and routing across every connected processor.
Tokens are non-convertible. Once issued, a token cannot be reverse-engineered back into the card number it represents.
Yuno runs a fully managed, PCI DSS Level 1 tokenization service. Sensitive data is captured directly by Yuno's SDK and replaced with a token before it ever reaches your servers. That keeps card data out of your environment and reduces your compliance scope: most merchants integrating with the SDK qualify for the short self-assessment (SAQ A) instead of a full audit.
Tokenization is not limited to cards. The same token abstraction covers every method flowing through Yuno, so your integration stores one identifier regardless of how the customer pays.
Yuno issues three token types. Each maps to a different integration scenario. Color coding below is reused in the comparison table.
The SDK gathers everything needed for a payment and stores it in a token scoped to a single checkout session. Used once to create the payment, then it is dead. Generate a new one per session.
Best for guest checkout and one-off payments with no saved method.
Created when a payment method is enrolled and stored in Yuno's centralized vault against the customer. Reuse it to charge future payments without the customer re-entering details. Lives until the method is unenrolled.
Best for returning customers, subscriptions, and one-click checkout.
A digitized version of the card PAN issued by Visa, Mastercard, or Amex. When enabled, Yuno provisions network tokens for all enrolled cards and substitutes them at authorization. The network keeps them current.
Best for recurring billing and lifting authorization rates.
A single flow ties the three tokens together. The customer enters details once, you get an OTT to charge, and optionally promote it into a vaulted (and network) token for next time.
Yuno returns a customer id. Every payment and every stored token links back to it.
The session carries the amount and country, and scopes the token you are about to generate.
Sensitive fields go straight to Yuno's vault. Your app receives a one-time token (token) plus safe display data: brand, last four (lfd), BIN (iin).
Pass the token to Create Payment. Yuno routes it to the processor in your card route and runs 3DS or fraud checks as configured.
Set vault_on_success: true on the request. If the payment succeeds, the method is enrolled and Yuno returns a vaulted_token in one step, no separate enrollment call.
When the feature is enabled, enrolled cards get a network token that Yuno substitutes at authorization and the network keeps updated through reissues.
| One-time token | Vaulted token | Network token | |
|---|---|---|---|
| Created by | SDK, per checkout session | Yuno on enrollment | Visa, Mastercard, Amex |
| Validity | Single transaction | Until unenrolled | Auto-renewed by network |
| Primary use case | Guest checkout, single payments | Returning customers, subscriptions | Recurring, higher auth rates |
| Works across processors | No | Yes | Yes |
| Requires enrollment | No | Yes | Yes, applied automatically |
| Key API field | token | vaulted_token | network_token |
Because vaulted and network tokens live in Yuno's central vault, switching or adding a processor needs no re-tokenization. The same stored credential works across every connected provider.
Every enrolled card gets a stable fingerprint derived from the PAN. It stays constant across enrollments, so you can detect duplicates and dedupe your vault without ever seeing the card number.
Yuno refreshes vaulted cards automatically when issuers change a number or expiry date. Your stored tokens stay valid through reissues, cutting declines from stale card data with no cardholder action.
Moving to Yuno from another provider? Import existing tokenized cards straight into the vault. Customers keep saved methods and history, with no re-enrollment. Export is supported too if you ever move away.
The practical effect for an integration: store one identifier, never raw card data, and let Yuno handle recurring payments, fallbacks, and retries across processors without changing the customer experience.