Yuno
A payment orchestration platform founded in Colombia, with routing, fallbacks and a vault across 1,000+ connections.
Yuno sells payment orchestration: one API that connects merchants, banks and wallets to payment methods, PSPs and fraud tools, more than 1,000 of them by its own count, with its largest provider list in Latin America. Routing rules pick a provider by card type, amount, currency or origin, and fallback steps retry chosen declines, timeouts and errors on another connection. Its PCI DSS Level 1 vault issues tokens that work across connected processors. Yuno does not publish pricing.
- Website
- y.uno
- Infrastructure layers
- Payment orchestration, tokenization
- Products (as published)
- Payment orchestration (conditional routing, fallback steps, Smart Routing by conversion, latency or cost)
Vault (vaulted tokens across processors, network tokens, Account Updater)
PCI Proxy (forward stored card data to third-party APIs)
Checkout SDKs (Full Checkout, Lite Checkout, Secure Fields)
Fraud and 3-D Secure connections, chargeback management
Payouts, reconciliation, subscriptions - Client types
- Enterprise merchants, banks and wallets (named: McDonald's, NetEase Games, GoFundMe, inDrive, Rappi)
- Regions served
- Global; provider counts published for Latin America, North America, Europe, Africa, the Middle East and Asia-Pacific
- API documentation
- docs.y.uno
- Date checked
- Profile type
- Standard
Questions
Where does Yuno list the most providers?
Does Yuno’s routing retry on another provider?
Does Yuno hold a licence in Saudi Arabia?
See also
Sources
- Yuno home page
- Yuno docs: routing
- Yuno docs: create a routing
- Yuno docs: tokens
- Yuno docs: PCI Proxy
- Yuno: PTSP certification from SAMA (April 22, 2026)
- SAMA Rulebook: rules for dealing with e-commerce payment service and support providers
- Yuno: Series B (August 12, 2026)
- Checked September 27, 2026.
Source: each provider’s own documentation, product pages, official announcements and filings, and official registers for licences, as linked in each profile. Fields a provider does not publish stay empty. How we build profiles: methodology.