FAQS

Simplify payments for your streaming platform with local solutions that ensure smooth transactions and improve customer retention.

• Who is dLocal designed for?

  dLocal is a payment infrastructure provider built for global enterprises and digital platforms that need to accept and send payments in emerging markets across Latin America, Africa & the Middle East, and Asia through a single API integration.

  dLocal is a strong fit if you:

  • Serve customers, users, or merchants across multiple emerging markets and want one provider for technology, coverage, and compliance instead of stitching together local solutions.
  • Need to offer local pay-ins (collections) and/or local payouts (disbursements) at scale.
  • Operate in verticals like ecommerce, SaaS, marketplaces, travel, fintech, gaming, or remittances.
     

• What kinds of businesses is dLocal best suited for?

  We work with companies of many sizes, but dLocal is especially well‑suited to organizations that bring together the right business profile, geography, and readiness.

  Business profile

  We work best with:

  • Enterprise merchants and platforms operating in or expanding into emerging markets.
  • Digital‑first businesses with strong or accelerating online transaction volumes.

  These can be ecommerce brands, marketplaces, SaaS platforms, subscription services, travel and mobility players, fintechs, and more.

  Typical use cases

  We add the most value when you need:

  • Local pay‑ins from customers using their preferred methods.
  • Local payouts to workers, sellers, or partners.
  • Multi‑sided flows for platforms and marketplaces (for example, splitting payments between buyers, sellers, and the platform).

  Often this spans several countries and involves multiple payment methods and currencies.

  Geography

  We focus on businesses that:

  • Serve users in Latin America, Africa & the Middle East, or Asia, or have concrete plans to enter those regions.
  • Want a single partner to consolidate local payment methods, currencies, and regulatory requirements across multiple markets.

  Readiness

  We move fastest with teams that:

  • Can integrate via API or supported connectors.
  • Are ready to work with us on compliance, KYC/KYB, AML, risk, and settlement across markets.

  If you recognize your business in most of these points and see payments as a way to drive growth and customer experience, dLocal is likely a strong fit.

• What if we’re a startup, just getting started, or still pre-launch?

  dLocal works with businesses at different stages of growth, typically with a large volume in place. The best next step is to speak with our team about your planned markets, payment needs, and launch timeline.

  We’ll help you understand whether dLocal is a good fit for your current stage and recommend an appropriate path forward.

• Which industries does dLocal focus on?

  We support many use cases, but we have deep experience in a set of strategic verticals where local payments and regulation matter most:

  • Digital subscriptions & streaming
  • Gaming & digital goods
  • E‑learning & education technology
  • SaaS & cloud software
  • Travel & hospitality (OTAs, travel tech, airlines, mobility, suppliers, aggregators)
  • Retail & marketplaces (including social commerce)
  • Financial services & remittances
  • On‑demand delivery & ride‑hailing
  • Emerging segments: Crypto & AI‑driven financial products

  If you see your business reflected in one or more of these categories, you're likely close to our sweet spot.
   

• What scale or payment volume do you typically work with?

  Our platform is designed for companies that process significant monthly online payment volume today, or have a clear path to get there.

  We create the most value when:

  • You are serving millions of consumers or users across multiple markets.
  • You expect volumes, countries, and use cases to grow over time and need a partner that supports multi‑country rollouts without re‑architecting your stack each time.

  If you're earlier in your journey or still at smaller volumes, we're still happy to speak and may recommend alternative paths or partners that better fit your current stage.
   

• Which regions and markets does dLocal specialize in?

  We focus on emerging and high‑growth markets across three main regions:

  • Latin America
  • Africa & the Middle East
  • Asia

  You can always find the exact country list in the Coverage section of dlocal.com.
   

• What level of integration and internal readiness do you expect?

  We're a good fit when you:

  • Can integrate via API or existing connectors and are ready to invest in a proper rollout.
  • Are comfortable partnering closely on compliance, KYC/AML, risk, and settlement requirements across markets.
  • Want one platform and one SLA instead of managing multiple local providers.
     

• Who are the typical stakeholders for a dLocal project inside my organization?

  Payments sit at the intersection of product, finance, risk, and operations.

  Typical stakeholders include:

  • Heads of Payments / Global Payments – acceptance, conversion, and cost.
  • Treasury & Finance leaders – settlement, liquidity, FX, and cash flow.
  • Risk & Fraud leaders – protection, controls, and chargebacks.
  • Product leaders for checkout, platforms, and user experience.
  • Operations leaders – reconciliation, reporting, and local execution.

  We speak their language — technical, financial, and regulatory — and provide a coherent view of your payment operations across markets.
   

• How do I know if dLocal is a good fit for my company?

  You're likely our ideal customer if:

  • You operate (or are expanding) in emerging markets and need more than one or two countries covered.
  • You process meaningful online payment volume and expect it to grow.
  • You need to offer local payment methods (cards, wallets, bank transfers, instant payments, installments) and/or local payouts at scale.
  • You're in one of our priority industries or a closely related digital business.
  • You're ready to integrate via API and dedicate a team to make the project successful.

  If that sounds like you, dLocal is designed to be "the local way for you to go global."
   

• What if our company is earlier-stage or has lower payment volumes?

  We’re happy to learn about your business and growth roadmap.

  Depending on your use case, markets, and operational needs, our team can recommend the most appropriate next steps for working with dLocal or our partners.

• What if our company is earlier‑stage or has lower payment volumes?

  We primarily serve companies with significant current or near‑term volumes, because that's where we add the most value.

  If you're earlier‑stage or at lower volumes:

  • We're still happy to understand your roadmap.
  • In some cases we may suggest alternative routes — for example, going through a partner or starting with fewer markets — until you reach the right stage for a direct dLocal relationship.
     

• What solutions does dLocal offer?

  dLocal provides a modular payments platform for emerging markets that includes:

  • Payins – All‑in‑one payment processing for global enterprises, so customers in emerging markets can pay using their preferred local methods.
  • Payouts – Local‑currency payouts to staff, customers, and partners, enhancing satisfaction and simplifying operational flows.
  • dLocal for Platforms – Handling payins and payouts in local currency for marketplaces and platforms through a single integration.
  • Defense Suite – Real‑time monitoring, chargeback management tools, dispute‑resolution services, and analytics to protect your revenue.
  • Invoice Collection – Local‑currency collection for invoicing flows, so your customers can pay in the currency and methods they trust.

  These components can be combined to support a range of vertical and platform use cases.
   

• How does dLocal's international payment gateway work for online payins?

  Our Payins solution acts as an international payment gateway optimized for emerging markets:

  • You integrate once via API or supported connectors.
  • We expose local payment methods per country (cards, wallets, bank transfers, cash, instant payments, etc.).
  • Customers pay in their local currency and preferred method.
  • You receive consolidated reporting and settlement according to your chosen configuration.

  This lets you accept payments across dozens of markets without managing separate local integrations.
   

• How does dLocal support cross‑border payouts?

  With Payouts, you can send funds to staff, customers, and partners in their local currency and preferred rails:

  • Support for a range of payout methods depending on market (bank accounts, wallets, cash‑out locations, etc.).
  • Configurable payout cycles (for example, daily/weekly cycles for gig workers or vendors).
  • Centralized reconciliation and reporting so you can track flows across multiple countries.
     

• What is dLocal for Platforms and when should I use it?

  dLocal for Platforms is designed for marketplaces, platforms, and multi‑sided models that need to manage both payins and payouts in local currencies:

  Use it when you:

  • Onboard multiple sellers, creators, drivers, or merchants.
  • Need to split payments, manage balances, and pay out locally.
  • Want unified reporting and risk/compliance coverage across markets.
     

• What is the Defense Suite?

  The Defense Suite provides tools to protect your business from fraud and chargebacks while preserving user experience:

  • Real‑time monitoring of transactions.
  • Chargeback management tools and workflows.
  • Dispute‑resolution services and supporting data.
  • Analytics to help you understand dispute drivers and trends.
     

• What is Invoice Collection and who is it for?

  Invoice Collection helps you receive payments in your customer's local currency for invoicing flows:

  • Useful for B2B or high‑value transactions where invoices are the primary trigger.
  • Customers can pay using the local payment methods they trust.
  • You benefit from simplified FX and reconciliation instead of opening local accounts or managing local providers yourself.

• How does dLocal adapt to different verticals?

  For each industry, we tailor:

  • The payment method mix (for example, installments for retail in Brazil, wallets in Mexico, instant methods in gaming).
  • The flows (recurring billing for SaaS, refund dynamics for travel, multi‑party flows for marketplaces).
  • The risk & compliance posture to match regulatory and business needs (for example, remittances vs. subscription media vs. ride‑hailing).
     

• Which regions does dLocal cover?

  dLocal focuses on high‑growth, emerging markets across three main regions:

  • Africa & the Middle East
  • Asia
  • Latin America

  In these regions we provide local payment methods (cards, digital wallets, cash payments, bank transfers, real‑time rails, and more) through a single API, so you can scale globally while tailoring payment experiences to each market.
   

• Which specific countries does dLocal cover?

  dLocal covers 64 emerging markets across three regions: Latin America (17 countries), Africa and the Middle East (36 countries), and Asia (11 countries). All markets are accessible through a single API integration.

  Latin America (17 markets): Argentina, Bolivia, Brazil, Chile, Colombia, Costa Rica, Dominican Republic, Ecuador, El Salvador, Guatemala, Honduras, Mexico, Nicaragua, Panama, Paraguay, Peru, Uruguay.

  Africa and the Middle East (36 markets): Algeria, Bahrain, Benin, Burkina Faso, Cameroon, Central African Republic, Chad, Ivory Coast, DR Congo, Egypt, Equatorial Guinea, Ghana, Guinea-Bissau, Jordan, Kenya, Kuwait, Madagascar, Malawi, Mali, Morocco, Mozambique, Niger, Nigeria, Oman, Qatar, Rwanda, Saudi Arabia, Senegal, South Africa, Swaziland, Tanzania, Türkiye, Uganda, United Arab Emirates, Zambia, Zimbabwe.

  Asia (11 markets): Bangladesh, China, India, Indonesia, Japan, Malaysia, Pakistan, Philippines, Sri Lanka, Thailand, Vietnam.

   

• How do I know if a specific country is covered?

  The Coverage page on dlocal.com always shows the latest list of covered markets, grouped by region (Africa & the Middle East, Asia, Latin America).

  To check a specific country:

  • Go to the Coverage section.
  • Select the region (Africa & the Middle East, Asia, or Latin America).
  • Look for the country name in the list.

  If the country is listed there, we currently provide coverage for that market.
   

• Which countries does dLocal not cover?

  dLocal focuses on emerging markets in the regions above, so we do not currently provide local coverage in:

  • North America (for example, the United States, Canada).
  • Most Western European countries (for example, France, Germany, Spain, United Kingdom, Italy, etc.).
  • Other regions or countries that are not listed on the Coverage page.

  In those markets, you may still work with other providers or global acquirers, but dLocal's core value is in local payments in emerging markets, not global acquiring in mature markets.
   

• Can you help if I sell from a non‑covered country into your covered markets?

  Yes. Many of our customers are global merchants based outside our coverage footprint (for example, in the US or Europe) who want to sell into Latin America, Africa & the Middle East, or Asia.

  In that scenario:

  • Your business can be incorporated outside the countries we cover.
  • dLocal acts as your local payments partner in the covered markets, giving you access to local payment methods and rails there.

  What we don't provide today is local market coverage (local acquiring, local APMs) in countries that do not appear on our Coverage list.
   

• How quickly do you add new countries or regions?

  We continuously review expansion opportunities based on:

  • Customer demand.
  • Regulatory readiness and licensing.
  • Local partner and infrastructure maturity.

  When we launch new countries or expand capabilities in existing ones, we update the Coverage page and communicate through our usual channels (website, sales teams, and resources like the Emerging Markets Payments Handbook).

  If you have an interest in a specific market that is not listed, your account team can share whether it's on our roadmap or suggest alternatives.
   

• Which payment method categories does dLocal support?

  Across covered countries, we support a wide range of local and alternative payment methods (APMs):

  • Local and international cards.
  • Digital wallets (eWallets).
  • Bank transfers and real‑time payment schemes.
  • Cash‑based methods (vouchers or cash on delivery) for digital purchases.
  • Mobile money (especially in African markets).
  • Buy Now, Pay Later (BNPL) options.
  • Interoperable QR solutions where standardized QR ecosystems exist.

  The exact set of methods varies by country. Our Payment Types section provides detailed explanations and examples per category.
   

• What do you mean by "local or alternative payment methods (APMs)"?

  When we say local or alternative payment methods (APMs), we mean any solution that is not a major international credit or debit card brand.

  This includes:

  • Domestic cards.
  • Cash‑based vouchers like Boleto in Brazil or Oxxo in Mexico, used to pay for digital purchases with cash.
  • Digital wallets and mobile money.
  • Bank transfers and real‑time payment schemes.
  • QR‑based and other localized solutions.

  APMs are critical in emerging markets, where card penetration, credit access, and trust in traditional banking can be limited.
   

• How does dLocal support cash‑based payments?

  Cash is still popular in several high‑growth markets, even for digital purchases.

  There are two main ways to pay with cash when transacting digitally:

  • Cash vouchers – the customer receives a voucher or reference, then pays in cash at an authorized location (for example, Oxxo in Mexico, Boleto in Brazil, and other local networks).
  • Cash on delivery (COD) – the customer pays in cash when the product or service is delivered.

  We support cash‑based methods in markets where they are prevalent, such as Mexico, Egypt, and Morocco, through local rails and partners like Fawry, Oxxo, Wafacash, Pago Fácil, Rapipago, Boleto, Efecty, and others.
   

• What digital wallet options does dLocal support?

  Digital wallets (eWallets) are widely used because they are simple, cost‑effective, and often more accessible than traditional banking.

  They enable instant transfers funded by:

  • Linked cards.
  • Bank accounts.
  • Cash top‑ups or other local mechanisms.

  We support a range of wallets depending on the market, including examples like Alipay, WeChat Pay, Yape, JazzCash, DeUna!, OVO, Shopeepay, EasyPaisa, GCash, TrueMoney, MoMo, Touch 'n Go, Modo, Nequi, and others, in markets such as Peru, Indonesia, and Pakistan.

  We'll recommend specific wallets based on your target countries and vertical.
   

• How do bank transfers work with dLocal?

  Bank transfer is a traditional and trusted way to pay in many markets, where customers pay directly from their local bank accounts.

  Key points:

  • Customers use local account details or bank interfaces to send funds from Bank A to Bank B.
  • dLocal's integration allows you to offer localized bank transfer options without managing separate bank integrations in each country.

  Bank transfers are prevalent in markets like Saudi Arabia, Nicaragua, Colombia, and others, with local schemes such as PSE, SINPE, VNPay, Capitec Pay, DoitNow, and more.
   

• What is mobile money and where does dLocal support it?

  Mobile money is a payment method that allows users to send and receive funds using a basic mobile phone and a mobile number, without a bank account or smartphone. dLocal supports mobile money in African markets including Kenya, Ghana, Tanzania, Uganda, Nigeria, and Rwanda.

  Mobile money is operated primarily by telecom companies rather than banks, using simple USSD/SMS menus, making it one of the most financially inclusive payment methods available in sub-Saharan Africa.

  dLocal connects to major mobile money schemes across these markets, including M-Pesa, MTN Mobile Money, Airtel Money, Paga, and Orange Money.

  For merchants entering African markets, mobile money is often the primary — and in some cases only — digital payment method available to a large portion of the population.
   

• What are real‑time payments and how does dLocal support them?

  Real‑time payments are instant transfers between bank accounts, 24/7, with immediate payment confirmation.

  They benefit:

  • Customers, who see immediate confirmation.
  • Merchants, who enjoy faster cash flow and lower settlement delays.

  dLocal supports real‑time schemes in multiple markets, for example:

  • Brazil – PIX.
  • India – UPI.
  • Malaysia – DuitNow.

  and other local instant‑payment networks.
   

• How does dLocal support Pix in Brazil?

  Pix is Brazil's real-time payment rail, available 24/7 with instant confirmation. dLocal supports Pix as a core payment method for merchants in Brazil, along with three advanced Pix products designed for recurring, card-on-file-style, and biometric payment experiences.

  The four Pix capabilities dLocal offers are:

  • Pix (standard): instant bank-to-bank transfers, the most widely adopted payment method in Brazil.
  • Pix Automático: designed for recurring payments via Pix, such as subscription billing cycles.
  • SmartPix: merchant-initiated Pix payments based on a single user consent, enabling a card-on-file-like experience without requiring manual approval on each transaction.
  • Pix with Biometrics: uses biometric authentication to make Pix payments faster and more secure.
     

• Does dLocal support Buy Now, Pay Later (BNPL)?

  Yes. Buy Now, Pay Later (BNPL) gives customers the ability to pay over time, which can:

  • Increase conversion and average order value (AOV).
  • Expand access in markets where traditional credit access is limited.

  BNPL is growing in markets such as India, Indonesia, Malaysia, Philippines, South Africa, and Mexico.

  We support popular BNPL providers like Atome, Payflex, Valu, Kueski, Pareto, and others, via our platform.
   

• What is BNPL Fuse?

  BNPL Fuse is dLocal's BNPL aggregator built for emerging markets. It is designed to simplify access to BNPL in high‑growth markets by bringing BNPL options together under a single solution, instead of integrating each provider separately.

  For details on participating providers and geographies, please refer to our BNPL documentation or speak with our team.
   

• What is Interoperable QR and where is it supported?

  Interoperable QR is a standardized QR‑based payment method that lets users make and receive payments across different providers using a single QR code.

  • Allows consumers, merchants, and financial institutions to operate in a unified QR ecosystem.
  • Simplifies the checkout experience and expands access to digital payments.

  Interoperable QR is particularly popular in Brazil, India, Thailand, Indonesia, and Malaysia, with schemes like PIX, UPI, ThaiQR, QRIS, DuitNow acting as the underlying rails.

  dLocal integrates with these local ecosystems so you can offer one QR experience while reaching users across multiple platforms.
   

• How does dLocal’s pricing model work?

  dLocal provides tailored commercial proposals based on each customer’s business needs and the solutions they want to enable.

  To receive a proposal, contact our team and share details about your use case, target markets, and planned payment flows.

• What factors shape my price with dLocal?

  Commercial proposals are tailored to each business and reflect the solutions, markets, and operational requirements involved.

  Our team will review your requirements and provide a proposal designed for your use case.

• How is pricing structured for my business?

  dLocal supports businesses in retail and ecommerce, travel and tourism, marketplaces and platforms, SaaS and subscriptions, fintechs and PSPs, gaming and digital goods, crypto and Web3, remittances, and payroll/gig/workforce platforms with payment solutions adapted to their operational needs across emerging markets.

  Commercial terms are tailored to each business. Contact our team to discuss your target markets, payment flows, and requirements.

• How is pricing structured for retail & ecommerce?

  For retail and ecommerce, we optimize around conversion across local cards, wallets, installments, and bank transfers.

  What shapes your price:

  • Payment‑method mix (for example, installments in Brazil, wallets in Mexico).
  • Average ticket size, refund/chargeback profile, and seasonality.
  • Multi‑country rollout and preferred settlement currencies.

  Typical structure:

  • Transaction fees by method and market.
  • A base component reflecting your active geographies and support tier.
  • Pass‑through items where applicable (for example, statutory or network fees).
     

• How is pricing structured for travel & tourism?

  For travel and tourism, we focus on high cross‑border intent, varied AOVs, and refund dynamics.

  What shapes your price:

  • Markets and routes (domestic vs. cross‑border collections).
  • Refund frequency, reversals, and dispute‑handling needs.
  • Wallet and installment adoption by country.

  Typical structure:

  • Transaction fees tailored to method and corridor.
  • A base component calibrated to coverage and operational support.
  • Pass‑through items where applicable.
     

• How is pricing structured for marketplaces & platforms?

  For marketplaces and platforms, we design around multi‑party flows, compliance, and scalable onboarding.

  What shapes your price:

  • Countries of buyer/seller activity and payment‑method coverage.
  • Split settlement needs, reconciliation complexity, and KYC workflows.
  • Payout cadence and currency preferences.

  Typical structure:

  • Transaction fees for collections; optional payout and compliance capabilities.
  • A base component aligned to platform scope, countries, and service levels.
  • Pass‑through items where applicable.
     

• How is pricing structured for SaaS & subscriptions?

  For SaaS and subscriptions, we support recurring billing, tokenization, and stable authorization rates.

  What shapes your price:

  • Recurring vs. one‑time mix and dunning needs.
  • Card‑on‑file tokenization and retry logic.
  • Geographic expansion roadmap.

  Typical structure:

  • Transaction fees with recurring‑friendly economics.
  • A base component tied to enabled regions and support model.
  • Pass‑through items where applicable.
     

• How is pricing structured for fintechs & PSPs?

  For fintechs and PSPs, we design for multi‑rail connectivity, scale, and programmatic control.

  What shapes your price:

  • Coverage breadth (markets/methods) and throughput requirements.
  • Risk posture, compliance controls, and reporting SLAs.
  • Settlement, treasury, and FX needs.

  Typical structure:

  • Transaction fees per method and country.
  • A base component reflecting program scope and service guarantees.
  • Pass‑through items where applicable.
     

• How is pricing structured for gaming & digital goods?

  For gaming and digital goods, we prioritize instant methods, strong fraud controls, and micro‑to‑mid ticket sizes.

  What shapes your price:

  • Adoption of instant rails and wallets by market.
  • Fraud prevention, velocity controls, and dispute exposure.
  • Content distribution countries and currency options.

  Typical structure:

  • Transaction fees optimized for instant/local methods.
  • A base component for coverage and risk services.
  • Pass‑through items where applicable.
     

• How is pricing structured for crypto & Web3?

  For crypto and Web3, we focus on compliant on‑ramp collections in key LATAM markets.

  What shapes your price:

  • Target countries, local methods, and compliance rigor.
  • Volatility considerations and operational support needs.
  • Settlement currency preferences.

  Typical structure:

  • Transaction fees by local method and market.
  • A base component aligned to compliance scope and service levels.
  • Pass‑through items where applicable.
     

• How is pricing structured for remittance & cross‑border financial services?

  For remittances and cross‑border financial services, pricing reflects high‑stakes compliance and corridor‑specific performance.

  What shapes your price:

  • Corridors, expected volumes, and payment‑method availability.
  • KYC/AML requirements and monitoring SLAs.
  • Settlement currencies and cadence.

  Typical structure:

  • Transaction fees tailored to corridor/method.
  • A base component for compliance coverage and operational support.
  • Pass‑through items where applicable.
     

• How is pricing structured for payroll, gig & workforce platforms?

  For payroll, gig, and workforce platforms, we optimize for predictable cycles, reconciliation, and regional coverage.

  What shapes your price:

  • Countries of worker onboarding and preferred payout rails.
  • Funding cycles, reconciliation, and reporting needs.
  • Support and service‑level expectations.

  Typical structure:

  • Transaction fees for collections; optional payout capabilities.
  • A base component aligned to geographic scope and support model.
  • Pass‑through items where applicable.
     

• How can I get a tailored quote for my business?

  Contact our Sales team to discuss your business and payment needs.

  They will guide you through the relevant information and prepare a proposal based on your requirements.
   

• How do I contact Sales or request a demo?

  You can reach our team directly from the website via Contact Sales, or through the contact options provided in your region. We'll then schedule time to understand your use case and explore fit.

• What information should I prepare before speaking with dLocal?

  It helps to have:

  • A short description of your business model and vertical.
  • The countries where you operate today and where you plan to expand.
  • High‑level volume expectations (monthly processed volume, average ticket).
  • Your use cases (payins, payouts, platforms, or a combination).
  • Your preferred integration model (own stack, platform, PSP, etc.).

  This allows us to quickly assess fit and suggest the right solution mix.
   

• What does a typical onboarding timeline look like?

  Timelines vary based on complexity and regions, but typical steps include:

  • Discovery and solution design.
  • Commercial agreement and due diligence.
  • Integration and testing (in sandbox and/or pilot markets).
  • Go‑live in priority markets, followed by phased expansion.

  We'll define a joint plan with your team so responsibilities and milestones are clear.
   

• Can I run a pilot before full deployment?

  In many cases, yes. We often:

  • Start with a limited set of markets and methods.
  • Validate performance, conversion, and operational fit.
  • Expand to additional countries and rails once metrics and processes are stable.
     

• We’re developers evaluating dLocal. Should we start with the sandbox or with a commercial assessment?

  You can explore dLocal’s public documentation, API Reference, and developer resources at any time but we recommend starting with the commercial assessment first. 

  For guidance on the most relevant integration path and production readiness, contact our team. They can help align the technical approach with your use case, markets, and operational requirements.

  Sandbox access is intended for technical evaluation and does not constitute approval for production use since it will not be tied to your particular quotation. 

• Which integration options does dLocal support?

  You can integrate with dLocal via:

  • REST APIs documented in the dLocal Docs and API Reference.
  • Hosted pages or components, depending on your use case.
  • Developer tools, including Postman collections, to accelerate testing.

  Your integration approach will depend on your architecture, PCI approach, and vertical.
   

• Where can I find technical documentation and API references?

  All technical documentation is available under Developers on dlocal.com:

  • dLocal Docs – quick setup and integration guides.
  • API Reference – full endpoint‑level documentation.
  • Developer tools – Postman collections and utilities.
  • API status page – real‑time performance and service health.
     

• Does dLocal provide SDKs, sample code, or tools?

  Yes. We provide:

  • Sample requests and responses in the API Reference.
  • A Postman collection and other tools to help you explore and test endpoints quickly.

  Your account or solutions engineer can share the most relevant assets for your stack.
   

• How can I test my integration?

  You can use:

  • The sandbox/test environment to simulate flows.
  • The developer tools and Postman collection to test key flows (payins, payouts, callbacks).

  We recommend validating end‑to‑end journeys — including error handling and reconciliation — before going live.
   

• Does access to the sandbox mean my company is fully onboarded and approved to go live?

  No. Sandbox access is intended for technical evaluation and does not mean a company is approved to process live transactions.

  Before going live, businesses complete the applicable onboarding, due-diligence, and account-configuration processes. Our team will guide you through the requirements for your specific use case.

• What's the recommended path for developers from first tests to production?

  A typical path includes:

  1. Explore dLocal’s documentation and developer resources.
  2. Evaluate relevant payment flows in the sandbox.
  3. Contact dLocal  with dLocal to complete the applicable onboarding and configuration steps.
  4. Complete production validation and launch in the approved scope.

  Your dLocal contact can help define the right approach for your business, markets, and integration needs.
   

  •  

• Which documents are required for KYC/KYB with dLocal?

  As a regulated payments provider, dLocal must perform Know Your Customer (KYC/KYB) checks. Exact requirements depend on your entity, structure, and markets, but we typically request:

  • Company registration documents.
  • Ownership and control information.
  • Identification for key individuals (for example, UBOs, directors).
  • Supporting information linked to your business model and geographies.

  Your onboarding package will include a clear checklist for your case.
   

• How does dLocal handle AML and sanctions screening?

  We apply AML, sanctions, and transaction‑monitoring controls consistent with our regulatory obligations and international best practices.

  This can include:

  • Screening counterparties against sanction and watch lists.
  • Monitoring transactions for unusual or suspicious patterns.
  • Escalation and reporting where required by law.

  These controls help protect both your business and end users.
   

• What are your policies for high‑risk or restricted industries?

  Certain high‑risk industries or activities may be:

  • Restricted, requiring enhanced review and controls.
  • Not supported, in line with our risk and compliance policy.

  If your use case may fall into these categories, our team will assess it as part of the qualification process and will clarify whether we can support you and under what conditions.
   

• How does dLocal support chargeback management and disputes?

  Through the Defense Suite and our operational processes, we support:

  • Notification and handling of chargebacks and disputes.
  • Tools and workflows to respond with evidence where appropriate.
  • Analytics to help you understand dispute drivers and trends.

  Your exact configuration will depend on your vertical, card schemes, and contractual setup.
   

• How do settlements work with dLocal?

  Settlement configurations are defined during onboarding and can include:

  • Settlement currency (for example, local or hard currency, subject to availability).
  • Settlement cadence (for example, daily, weekly).
  • Settlement method (for example, bank account details and routing).

  We aim to balance operational simplicity, FX needs, and local market constraints in your settlement design.
   

• How do refunds and reversals work?

  You can initiate:

  • Full or partial refunds, depending on the payment method and scheme rules.
  • Reversals or voids when supported by the underlying method and transaction status.

  Refund flows will be covered in your integration and operational documentation so your teams know exactly how and when they can be used.
   

• What reconciliation and reporting tools are available?

  We provide:

  • Transaction‑level data for all payins and payouts.
  • Summaries and reconciliation reports to bridge payment data and bank statements.
  • Dashboards and exports to support your finance and operations teams.

  This helps you manage multi‑country operations through a single view rather than fragmented local providers.
   

• I’m interested in using dLocal. How can I contact your sales team?

  If you are interested in using dLocal, visit our Contact Sales page.

  Our team will learn about your business and payment needs, then guide you through the relevant next steps.
   

• We are already a dLocal merchant. How do we get support?

  If you are an existing merchant:

  • Your primary contact is your dLocal dashboard and account manager.
  • For day‑to‑day operational issues, please use the support/contact options available inside your merchant dashboard.
  • For commercial or strategic topics, please reach out to your account manager directly.
  • The merchant Help Center and support tools are not public – they are accessed through the dashboard once you are onboarded as a dLocal customer.

  If you are unsure who your account manager is, use the contact options in the dashboard and our team will route your request.
   

• I'm an end user and I see "dLocal" on my statement. How do I get help?

  When you see "dLocal" on your bank statement or in a payment receipt, it means we processed the payment on behalf of an online business (our customer). We are not the seller of the product or service.

  If you are an end user (you bought something from a website/app that uses dLocal):

  • To check the status of your payment or refund and contact our end‑user support team, you can use our public End User Help Center: https://support.dlocal.com/en/
  • Or email our end‑user support team at: [email protected]

  To help you, we usually need:

  • Transaction ID (if shown on a receipt or confirmation screen).
  • Email address used at checkout.
  • Amount and date of the transaction.
  • The merchant name (site/app where you made your purchase).
     

• Which contact channels should I use, and which should I avoid?

  To ensure your request reaches the right team quickly, please use these official channels:

  • Leads / prospects
    • Contact Sales form: https://www.dlocal.com/contact-sales/
    • Email: [email protected]
  • Existing merchants
    • Dashboard support (Help / Support section inside your merchant dashboard).
    • Account manager (for commercial and strategic topics).
  • End users of our merchants
    • End User Help Center (transaction status + contact form): https://support.dlocal.com/en/
    • Email: [email protected]

  To protect you and ensure data security, we do not recommend using:

  • Social media (comments, DMs, posts) as a support channel.
  • Unofficial or third‑party contact details that are not listed on our website or Help Centers.

  Always rely on the contact options listed on dlocal.com or in our official Help Centers.
   

• Why can't dLocal fully handle my complaint as an end user?

  dLocal's role is to process payments securely on behalf of our merchant customers. We do not:

  • Own or operate the websites/apps where you shop.
  • Control stock, shipping, or delivery.
  • Define refund/return policies for those businesses.

  Because of this:

  • We can inform you about your payment or refund status.
  • We cannot force a merchant to ship a product, grant a refund, or change your order.

  That's why our FAQs and Help Center always direct you to:

  • The merchant, for any issue about the product or service itself.
  • dLocal's End User team, for questions about the payment itself (status, details, refunds once initiated).

  This separation keeps responsibilities clear and helps you get to the right resolution as fast as possible.