What this brand represents in LocalPayMap
dLocal is treated as a PSP or aggregator. It may help merchants access multiple payment methods, but each method still has its own market rules and risk controls.
This is a brand-level overview, not a live quote, official pricing page, endorsement, or onboarding guarantee. Country pages explain local payment habits; PSP contact records explain who may be able to connect your business.
Merchant brand notes
dLocal is treated on LocalPayMap as a cross-border PSP for emerging-market routes, not as a recommendation or availability promise. Use this page to understand the brand's usual payment role, then place it beside PSPs, local methods, wallet, bank, or BNPL routes for the target market. Frame questions about local acceptance and payout discovery, and verify details with the provider before build work.
How merchants should read this brand
Read dLocal as a cross-border PSP for emerging-market routes. Treat brand recognition as context for discovery, then confirm the exact merchant use case through official material.
Where it fits in a shortlist
Place dLocal beside local PSPs, direct methods, and bank or wallet routes when reviewing local acceptance and payout discovery. Keep another route in scope while facts are checked.
What to verify with the provider
Ask the official provider or partner to confirm eligible merchant profiles, countries, methods, integration steps, support ownership, refunds, disputes, reporting, and terms.
Record-specific caution
Use this page to frame a cross-market PSP check: confirm target countries, payment methods, merchant entity fit, restricted categories, settlement currency, refunds, disputes, reserves, and support ownership in writing.
Merchant usage and connection route
dLocal in the payment stack
dLocal is a provider-brand candidate for merchants evaluating cross-border pay-ins, local payment methods, cards, bank transfers, wallets, and payment operations across emerging markets. Use it to frame country-by-country questions before relying on one aggregator for conversion and operations.
Connection route
Merchants should verify direct contracting, target-country method access, local processing model, FX, settlement reporting, refund paths, and support responsibilities. Some routes may depend on local partners, so ask which methods are native, partner-routed, or subject to separate enablement.
Verification questions
- Which target countries, currencies, payment methods, merchant entity profiles, and industries are in scope?
- Is the merchant using dLocal for pay-ins, payouts, local acquiring, alternative payments, or multi-country aggregation?
- Who handles local processing, FX, settlement statements, refunds, disputes, chargebacks, and failed payments?
- Which methods require separate review, local partner routing, or additional documents?
- What reserve, risk, compliance, pricing, and support terms must be confirmed directly?
Merchant caveats
- Emerging-market coverage should be verified country by country.
- Aggregator access does not prove every local method fits the merchant.
- FX, settlement, refunds, and disputes may vary by route.
- Provider examples are discovery examples only.
Provider examples to verify
Related markets
Keep researching
- dLocal Payment Acceptance
- Dlocal vs Ebanx
- Payment Channel Directory
- Submit payment requirements
- psp contacts
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
Why merchants ask about it
Merchants ask about dLocal because it may bundle local payment methods, onboarding, risk review, checkout, settlement, and support into one provider relationship.
Role clarification
- Brand type
- PSP / aggregator
- Payment types
- To be confirmed by market
- Related countries
- Africa, Asia, Emerging markets, Latin America
- Country URLs
- Market-specific entries remain available for country research.
Related market links
Market-specific entries
Each row below is a country or payment-scenario record. It is kept because the same brand can behave differently by market, entity requirement, settlement route, and provider coverage.
No public channel entries are linked yet.
Related PSP contact leads
These public contact routes are prioritized toward official forms, contact pages, and direct public routes when available. Confirm market scope, merchant eligibility, pricing, settlement, and support coverage directly before relying on any listing.
dLocal
Serves global merchants; Costa Rica methods: Sinpe, Sinpe Movil, PayCash, BN Servicios, local cards.
dLocal
Explicitly built for global merchants selling in 60+ emerging markets via one API; serves Panama.
dLocal Uruguay
Cross-border merchants needing LATAM local payins and payouts.
Next actions for merchants
Use this brand page as a navigation layer. Before outreach, narrow the target market, decide whether you need a PSP, gateway, acquirer, wallet operator, or platform route, then confirm eligibility directly with the provider.
Questions merchants ask
Is dLocal enough to make a provider decision?
No. Use the brand page to shape discovery, then compare it with market pages, PSP contacts, and written answers from the provider.
Can LocalPayMap confirm dLocal availability for my business?
No. Availability can depend on country, entity, product category, risk review, currency, and integration model. Confirm it officially.
What should I ask before adding dLocal to checkout work?
Ask about supported markets and methods, onboarding documents, fees, settlement setup, refunds, disputes, reporting, and production support.
FAQ for first-time merchants
Can a cross-border merchant accept dLocal?
Possibly, but acceptance depends on account location, supported industries, risk review, settlement currency, and the specific country. Ask the provider whether it onboards merchants from your company location.
Do I need a local company or local bank account?
It depends on the country, industry, transaction model, and provider route. Some psp / aggregator records can be reached by cross-border merchants; others require a local entity, local bank account, local tax registration, or extra licensing.
Are fees and settlement terms fixed?
Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.
What should I ask before integration?
Ask who signs the merchant agreement, which countries and currencies are covered, whether your industry is allowed, how refunds and disputes work, whether reserves apply, what settlement timing is available, and which official contact route handles onboarding.
Is this page the same as a country payment-channel page?
No. This page aggregates brand context. Country payment-channel pages keep the local market, checkout, entity, pricing, and settlement questions visible.
Pricing note
Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.