Skip to main content

Overview

Selecting the right payment providers is one of the most impactful decisions in your orchestration setup. This reference helps merchants and Solutions Engineers evaluate providers across geography, payment method coverage, feature support, cost structure, and reliability. Use this matrix to:
  • Compare providers side by side before configuring your routing rules
  • Identify coverage gaps that require adding a secondary or tertiary provider
  • Estimate costs and plan your multi-provider architecture
  • Plan onboarding timelines for new market launches
Coverage depends on your configured providers. Enable providers in Dashboard > Connections to activate payment methods for specific countries.
Exact pricing, SLA terms, and feature availability depend on individual merchant agreements negotiated directly with each provider. The figures in this document represent typical market ranges and should be used for planning purposes only. Always confirm terms with your provider and Yuno account manager.

Provider Catalog

Global Gateways

Adyen is a global payments platform with direct acquiring licenses in multiple regions.
AttributeDetails
Countries30+ countries including AR, BR, CL, CO, MX, PE, US, EU
Payment methodsCards (Visa, Mastercard, Amex), PIX, Boleto, OXXO, SPEI, bank transfers, wallets
Key features3DS2, network tokens, Apple Pay, Google Pay, tokenization, recurring, split payments, RevenueProtect fraud tools
Settlement currenciesUSD, EUR, BRL, MXN, COP, ARS, CLP, PEN, and 20+ others
Onboarding time2—4 weeks (KYC dependent)
Best forHigh-volume merchants needing single-provider global coverage with advanced fraud tools

Regional Providers. Brazil

AttributeDetails
CountriesBR
Payment methodsCards (Visa, MC, Amex, Elo, Hipercard), PIX, Boleto
Key featuresTokenization, installments (up to 12x), recurring, fraud screening
Settlement currenciesBRL
Onboarding time3—7 business days

Regional Providers. Mexico

AttributeDetails
CountriesMX
Payment methodsCards (Visa, MC, Amex, Carnet), OXXO, SPEI
Key features3DS, tokenization, installments (MSI up to 12x), recurring, marketplace splits
Settlement currenciesMXN
Onboarding time3—7 business days

Regional Providers. Colombia, Argentina, Chile, Peru

AttributeDetails
CountriesCO, MX, AR, BR, CL, PE, PA
Payment methodsCards (Visa, MC, Amex, Codensa), PSE, Efecty, Baloto, bank transfers
Key featuresTokenization, installments, recurring, antifraud module
Settlement currenciesCOP, MXN, ARS, BRL, CLP, PEN, USD
Onboarding time5—15 business days

Provider Comparison Matrix

The following table compares payment method support across all major providers available through Yuno.
ProviderCountriesCardsPIXBoletoOXXOPSEBank Transfer3DSTokenizationInstallmentsRecurringSettlement Speed
Adyen30+YesYesYesYesYesYes3DS2YesYesYesD+1 to D+3
Stripe25+YesNoYesYesNoYes3DS2YesLimitedYesD+2 to D+7
dLocal40+YesYesYesYesYesYes3DS2YesYesYesD+3 to D+15
Checkout.com20+YesYesYesYesNoYes3DS2YesLimitedYesD+1 to D+3
PagSeguroBRYesYesYesNoNoNoLimitedYesYesYesD+1 to D+14
CieloBRYesYesYesNoNoNo3DS2YesYesYesD+1 to D+30
RedeBRYesYesNoNoNoNo3DS2YesYesLimitedD+1 to D+30
StoneBRYesYesYesNoNoNoLimitedYesYesLimitedD+1 to D+30
Mercado PagoAR, BR, MX, CL, CO, PE, UYYesYesYesNoNoYesLimitedYesYesYesD+1 to D+14
ConektaMXYesNoNoYesNoYes3DSYesYesYesD+2 to D+5
OpenPayMX, COYesNoNoYesNoYesLimitedYesYesYesD+2 to D+7
PayUCO, MX, AR, BR, CL, PE, PAYesNoYesNoYesYesLimitedYesYesYesD+3 to D+10
KushkiCO, MX, CL, PE, ECYesNoNoNoYesYes3DS2YesYesYesD+2 to D+7
Prisma/DecidirARYesNoNoNoNoYesLimitedYesYesYesD+2 to D+10
Settlement speed ranges depend on payment method (cards vs. cash vouchers), installment plans, and negotiated terms. PIX settlements in Brazil are typically D+0 to D+1 regardless of provider.

Feature Support Matrix

Advanced feature availability across providers. “Partial” indicates the feature is available with restrictions or limited to certain payment methods.
ProviderNetwork TokensApple PayGoogle PaySplit PaymentsPayoutsCurrency ConversionFraud Tools
AdyenYesYesYesYesYesYesRevenueProtect (built-in)
StripeYesYesYesYes (Connect)YesYesRadar (built-in)
dLocalNoPartialPartialNoYesYes (core feature)Basic rules
Checkout.comYesYesYesPartialYesYesFraud Detection Pro
PagSeguroNoNoNoPartialNoNoBasic screening
CieloNoNoNoNoNoNoBasic rules
RedeNoNoNoNoNoNoBasic rules
StoneNoNoNoYesNoNoBasic screening
Mercado PagoNoNoNoYesYesNoBuilt-in ML scoring
ConektaNoNoPartialYesNoNoBasic antifraud
OpenPayNoNoNoNoNoNoBasic rules
PayUNoNoNoPartialPartialPartialAntifraud module
KushkiNoNoNoPartialYesPartialBasic rules
Prisma/DecidirNoNoNoNoNoNoCybersource integration

Cost Benchmarks

The fee ranges below are industry estimates based on publicly available information and typical merchant agreements as of early 2026. Your actual rates will depend on volume, risk profile, industry, and direct negotiations. Always confirm pricing with your provider and Yuno account manager before making architectural decisions.

Fee Structure by Provider Type

Provider TypePer-Transaction FeePercentage FeeCross-Border SurchargeMonthly Minimum
Global gateway (Adyen, Stripe, Checkout.com)0.100.10 -- 0.30 USD2.4% — 3.5%+0.5% — 1.5%00 -- 500
Cross-border specialist (dLocal)0.150.15 -- 0.40 USD3.0% — 5.0%Included in rate00 -- 250
Local acquirer (Brazil) (Cielo, Rede, Stone, PagSeguro)R0.10R0.10 -- R0.501.5% — 3.2%N/A (domestic only)Varies
Local acquirer (Mexico) (Conekta, OpenPay)MXN 1.501.50 -- 4.002.5% — 3.6%N/A (domestic only)Varies
Regional multi-country (PayU, Kushki, Mercado Pago)0.100.10 -- 0.35 USD2.5% — 4.5%+0.3% — 1.0%00 -- 200

Cost by Payment Method

Payment MethodTypical Provider FeeChargeback FeeRefund Fee
Credit card (domestic)1.5% — 3.5% + fixed1010 -- 25 USD00 -- 0.25
Debit card0.8% — 2.0% + fixed1010 -- 25 USD00 -- 0.25
PIX0.5% — 1.2% (flat in some cases)N/A$0
BoletoR1.50R1.50 -- R5.00 flatN/AN/A
OXXOMXN 5.005.00 -- 12.00 flatN/AN/A
PSECOP 800800 -- 3,000 flatN/AN/A
Bank transfer0.3% — 1.0% or flatN/AVaries

Effective Cost per Approved Transaction

When comparing providers, consider the effective cost rather than the listed rate. Use this formula:
Effective Cost = (Total Fees Paid) / (Total Approved Transactions)
A provider with a lower listed rate but a 75% approval rate will cost more per successful transaction than a provider with a slightly higher rate and a 92% approval rate. For detailed routing optimization strategies, see Multi-Provider Orchestration.
Local acquirers typically achieve 5—15% higher approval rates for domestic transactions compared to cross-border global gateways. Factor this into your cost-per-approved-transaction calculations.

Provider Selection Guide

By Geography

Use this table to identify recommended providers for each country based on coverage depth.
CountryPrimary RecommendationSecondary RecommendationGlobal Fallback
BrazilCielo, Stone, or PagSeguroMercado PagoAdyen or dLocal
MexicoConekta or OpenPayMercado Pago MXAdyen or Stripe
ColombiaPayUKushki or Mercado Pago COAdyen or dLocal
ArgentinaPrisma/DecidirMercado Pago ARdLocal
ChileKushkiMercado Pago CLdLocal or Adyen
PeruKushkiMercado Pago PEdLocal or Adyen
EcuadorKushkidLocalAdyen
Multi-country LATAMdLocalMercado PagoAdyen
US + LATAMStripe or AdyendLocal (LATAM)Checkout.com

By Payment Method

Payment MethodBest Provider(s)Reasoning
Cards (Brazil)Cielo, Rede, StoneHighest domestic approval rates, local BIN routing
Cards (Mexico)Conekta, AdyenStrong MSI (installment) support, local acquiring
PIXPagSeguro, Cielo, AdyenDirect PIX integration, fastest settlement
BoletoPagSeguro, Cielo, dLocalNative boleto generation, reconciliation tools
OXXOConekta, OpenPayNative voucher support, widest store network integration
PSEPayU, KushkiDirect bank integration in Colombia
Rapipago / Pago FacilPrisma/Decidir, Mercado PagoNative cash network integration in Argentina

By Volume Tier

Volume TierMonthly TransactionsRecommended Setup
Startup<1,000Single global gateway (Stripe or Adyen) for simplicity
Growth1,000 — 10,000One global gateway + one local acquirer per primary country
Scale10,000 — 100,000Two local acquirers per country + one global fallback
Enterprise<100,000+Three providers per major country with smart routing and failover

By Feature Needs

Use CaseRecommended ProvidersKey Reason
Marketplace / Split paymentsStripe (Connect), Adyen, StoneNative split and sub-merchant management
Subscriptions / RecurringStripe, Adyen, Mercado PagoBuilt-in billing engines, card updater services
Cross-border into LATAMdLocal, AdyenLocal payment method support without local entity
High-risk / Fraud-sensitiveAdyen, Stripe, Checkout.comAdvanced ML-based fraud tools included
Payouts to sellers/driversdLocal, Adyen, KushkiMulti-country payout rails

Provider Onboarding

ProviderTypical Onboarding TimeKYC RequirementsIntegration ComplexitySandbox Available
Adyen2—4 weeksFull corporate KYC, UBO disclosure, processing historyMedium—HighYes
Stripe1—3 days (self-serve)Automated identity verification, business docs for higher volumesLow—MediumYes
dLocal2—4 weeksCorporate KYC, country-specific tax IDs, compliance reviewMediumYes
Checkout.com1—3 weeksCorporate KYC, UBO disclosure, PCI compliance evidenceMediumYes
PagSeguro3—7 daysBrazilian CNPJ, company docsLowYes
Cielo5—10 daysBrazilian CNPJ, banking details, credit analysisMediumYes
Rede5—10 daysBrazilian CNPJ, banking detailsMediumYes
Stone3—7 daysBrazilian CNPJ, company docsLow—MediumYes
Mercado Pago1—5 daysLocal tax ID, business verificationLowYes
Conekta3—7 daysMexican RFC, company docsLow—MediumYes
OpenPay5—10 daysMexican RFC, banking detailsMediumYes
PayU5—15 daysLocal tax ID per country, corporate docs, compliance reviewMediumYes
Kushki5—10 daysLocal tax ID, corporate KYCMediumYes
Prisma/Decidir5—15 daysArgentine CUIT, corporate docs, credit analysisMedium—HighYes
Start sandbox integration in parallel with KYC onboarding. Most providers allow API testing immediately while production credentials are being processed. Configure your Yuno connections with sandbox keys first, then swap to production keys once approved.

SLA and Reliability

ProviderUptime SLAAvg API Response TimeSupport ChannelsIncident Transparency
Adyen99.99%<200ms24/7 dedicated support, email, portalPublic status page
Stripe99.99%<300ms24/7 email, chat (enterprise: phone)Public status page, incident reports
dLocal99.9%<400msEmail, dedicated account managerPrivate status updates
Checkout.com99.99%<250ms24/7 support, Slack (enterprise), portalPublic status page
PagSeguro99.9%<500msEmail, phone (BR business hours)Limited public reporting
Cielo99.9%<400msPhone, email (BR business hours)Limited public reporting
Rede99.9%<400msPhone, email (BR business hours)Limited public reporting
Stone99.9%<350msEmail, phone, dedicated account managerLimited public reporting
Mercado Pago99.9%<500msEmail, developer forums, phonePublic status page
Conekta99.9%<400msEmail, Slack, developer forumsPublic status page
OpenPay99.5%<500msEmail, phone (MX business hours)Limited public reporting
PayU99.9%<500msEmail, phone, dedicated account managerLimited public reporting
Kushki99.9%<400msEmail, Slack, dedicated account managerPublic status page
Prisma/Decidir99.5%<600msEmail, phone (AR business hours)Limited public reporting
Yuno’s orchestration layer adds automatic failover capabilities. When a provider experiences downtime, transactions can be rerouted to a backup provider within milliseconds if you have configured multiple providers for the same payment method and country. See Routing Rules for configuration.

Combining Providers

Multi-provider setups increase approval rates and provide resilience against downtime. Below are recommended configurations and anti-patterns.
CountryProvider A (Primary)Provider B (Failover)Rationale
BrazilCielo or StoneAdyenLocal acquirer maximizes domestic approval rates; global gateway handles international cards
MexicoConektaAdyen or StripeConekta for OXXO/SPEI and domestic cards; global gateway for international and wallet payments
ColombiaPayUKushkiPayU for PSE and broad method coverage; Kushki as card processing alternative
ArgentinaPrisma/DecidirMercado PagoPrisma for card installments; Mercado Pago for wallet and cash methods
ChileKushkidLocalKushki for local cards; dLocal for broader method coverage and cross-border
PeruKushkidLocalSame rationale as Chile
CountryPrimarySecondaryTertiary / FallbackStrategy
BrazilCieloStoneAdyenSplit domestic card volume between two local acquirers for redundancy; Adyen handles international cards and acts as final fallback
MexicoConektaMercado PagoAdyenConekta for cards/OXXO, Mercado Pago for wallet users, Adyen for international fallback
ColombiaPayUKushkidLocalPayU primary for PSE/cards, Kushki for card retries, dLocal for cross-border
Multi-country LATAMdLocalMercado PagoAdyendLocal for broad LATAM coverage, Mercado Pago where available, Adyen as global fallback

Anti-Patterns to Avoid

These configurations lead to suboptimal results and should be avoided.
Anti-PatternWhy It FailsBetter Approach
Two global gateways only (e.g., Stripe + Adyen for Brazil)Both process as cross-border, losing 5—15% approval rate vs. localAdd at least one local acquirer per major country
Single provider per countryNo failover during outages, zero leverage for rate negotiationAlways configure at least two providers for countries with significant volume
Retrying declined transactions on the same providerSame decline reason will repeat; wastes API calls and may trigger rate limitsRoute retries to a different provider with different acquiring bank relationships
Too many providers (<5 per country)Splits volume, weakens negotiating position, increases reconciliation complexityLimit to 2—3 providers per country and optimize routing rules
Ignoring provider-specific BIN routingGeneric routing misses optimization opportunities per card brand/issuerConfigure BIN-level routing rules to match card issuers with their preferred acquirer

Requesting New Coverage

To request a new country, payment method, or provider connection:
1

Assess requirements

Identify the country, payment methods, expected monthly volume, and any specific feature needs (installments, recurring, payouts).
2

Check this matrix

Review the provider catalog above to identify candidate providers that match your requirements.
3

Contact your Yuno account manager

Provide your requirements and preferred providers. Yuno will assess availability, onboarding timelines, and any provider-specific prerequisites.
4

Begin parallel onboarding

Start sandbox integration through Yuno while provider KYC is in progress. Configure connections in Dashboard > Connections with sandbox credentials.
5

Go live

Once production credentials are received, update your Yuno connection settings and configure routing rules to include the new provider.
Yuno continuously expands provider coverage. If a provider you need is not yet available through Yuno’s orchestration layer, request it through your account manager. Custom integrations for high-priority providers are typically completed within 4—8 weeks.