Providers

Payment providers behind Yuno’s orchestration: how the abstraction works, how routing picks one per transaction, and how failover cascades.

What a provider is

A provider in Yuno is a payment processor, acquirer, or gateway that executes transactions. Yuno abstracts each provider’s API behind one unified interface, so you integrate once and can route to any connected provider.

Examples include Stripe, Adyen, Mercado Pago, dLocal, PagSeguro, and hundreds of regional acquirers across Latin America, North America, Europe, and Asia.

Multi provider architecture

Connect multiple providers for the same payment method and country. Yuno picks the optimal provider for each transaction based on your routing rules.

Smart routing

Smart routing decides which provider processes each transaction. Configure rules in Dashboard > Routing.

Strategy	Description	Best for
Priority based	Route to providers in a fixed order	Simple setups, single provider preference
Cost optimization	Route to the provider with the lowest fees	Reducing processing costs
Approval rate	Route based on historical success rates	Maximizing conversion
Geographic	Route to local acquirers for domestic transactions	Improving approval rates in specific regions
Custom rules	Route based on BIN, amount, method, or metadata	Advanced orchestration

Routing decisions happen per transaction, not per payment. When a payment cascades, the routing engine re evaluates the best option for each retry independently.

See multi provider orchestration and BIN routing strategy for concrete configuration patterns.

Failover and cascading

When a provider declines or fails to respond, Yuno can retry automatically with the next provider in your configuration.

Configure cascading:

Setting	Description	Example
Max retries	Maximum number of providers to try before giving up.	3
Retry on	Decline codes that trigger a cascade to the next provider.	timeout, do_not_honor, issuer_unavailable
Exclude on	Decline codes that must not cascade. A retry wastes budget and risks scheme violations.	stolen_card, fraud_suspected, restricted_card

Not every decline should cascade. Hard declines (stolen card, fraud) should not retry on another provider. Configure your exclude rules to avoid wasted retries and to stay compliant with scheme rules.

See transaction retries for retry configuration and the Dashboard routing builder.

Provider configuration

Set providers up in Dashboard > Providers.

1. Add a provider

   Navigate to Dashboard > Providers > Add Provider and pick from the available integrations.

2. Enter credentials

   Provide the provider’s API keys, merchant IDs, and any required configuration. Each provider has different credential requirements.

3. Enable payment methods

   Select which methods this provider should handle (cards, SEPA, UPI, Pix, Alipay, and so on).

4. Configure routing

   Go to Dashboard > Routing to set priority, failover rules, and any conditional routing logic.

See Dashboard connections for the step by step setup.

Normalized responses

Yuno normalizes every provider response into a standard status. The raw provider response is preserved in the transaction for debugging.

Yuno status	Typical provider meaning
SUCCEEDED	Approved, authorized
DECLINED	Insufficient funds, do not honor, restricted card
REJECTED	Invalid data, fraud suspicion
FAILED	Timeout, network error, provider outage

What next

Multi provider orchestration

How to set up routing across multiple providers.

BIN routing strategy

Send cards to the acquirer most likely to approve them.

Transactions

What each provider attempt looks like under the hood.

Dashboard routing

Configure providers and routing without code.