PaymentCompanies.com — an index of the payments industry
Processing & AcquiringCross-Border Acquiring

dLocal

A Nasdaq-listed, Uruguay-founded cross-border payments company that lets global merchants collect from and pay out to consumers in more than 60 emerging markets through one API and one contract.

Last reviewed July 2026 · independently researched · not sponsored

What dLocal actually is

dLocal solves one specific problem. A global digital company wants revenue from Brazil, Nigeria, Mexico or Indonesia, and finds that reaching those consumers requires a local legal entity, a local bank account, a local acquiring relationship, local licensing and support for payment methods that exist nowhere else. Multiply by twenty countries and the project stops being a payments integration and becomes a corporate expansion program.

dLocal replaces all of it with one API and one contract, handling local acquiring, local payment methods, local currency settlement and local regulatory compliance in each market. Its merchants — streaming services, marketplaces, SaaS companies, advertising platforms, travel, gaming and ride-hailing businesses headquartered in developed markets — never establish local infrastructure at all.

Local payment methods. The rails consumers in a given country actually use, which are frequently not international cards: Pix in Brazil, SPEI in Mexico, PSE in Colombia, UPI in India, boleto bancário and OXXO cash vouchers, mobile money across much of Africa. In several of dLocal's largest markets a large share of consumers cannot pay by international card at all, so these rails are not an optimization but the difference between having a market and not having one.

Two flows run through the same platform. Pay-in collects from consumers; pay-out disburses to local sellers, drivers, creators and contractors in local currency. Marketplaces and ride-hailing platforms need both, and getting them from one integration is much of the appeal.

What dLocal is not is a global processor. It covers emerging markets only, so it is almost always an addition to an incumbent acquirer in North America and Europe rather than a replacement — and it does no card-present acceptance in any form.

How the model works, and who carries the risk

The essential thing to understand is that dLocal is the licensed and regulated party in most of its markets, not an introducer to one. It holds an EU electronic money institution license, a UK payment institution license approved by the Financial Conduct Authority in December 2024, FinCEN money services business registration in the United States, and licenses or approvals across roughly eighteen further countries in Latin America, Africa, Asia and the Middle East, with more in progress.

That license stack is the product. A merchant buying dLocal is buying the transfer of local regulatory burden to a counterparty that has done the work — and an escape from currency risk and capital controls. When a Brazilian consumer pays in reais, someone must hold those reais, convert them and move the proceeds out of the country under whatever rules apply. dLocal does that, which means dLocal carries the FX exposure, the settlement timing risk and the repatriation risk.

Those risks are real rather than theoretical. dLocal's own filings repeatedly reference the Central Bank of Argentina, and the business depends on converting and repatriating funds from markets with active FX restrictions. The risk does not vanish because a merchant outsourced it; it reappears as settlement timing and as the rate applied at conversion.

Within each country dLocal routes across multiple local acquirers and methods, with smart routing and retries. That is genuine capability, but it happens inside a single provider's platform — not vendor-neutral orchestration across competing processors, and with no failover to a rival if dLocal itself has trouble in a market.

How dLocal prices, and why the FX spread is the real question

Pricing is enterprise and negotiated per merchant: no rate card, no fee schedule, no self-serve signup, no published contract or termination terms. Normal for the category — and it makes the structure of the pricing more important than usual.

Take rate. Revenue expressed as a share of total payment volume — the blended amount a payments company keeps out of everything flowing through it. dLocal reports its economics this way and discloses that the figure varies materially by country and payment method.

Here is the part a merchant must not miss. dLocal's take rate combines two very different things: an explicit processing fee, and revenue from currency conversion. A substantial share of what the company earns comes from the spread applied when local-currency collections become the merchant's settlement currency. That spread is negotiated, not published, and it never appears as a line item the way a processing fee does.

Model the FX spread, not the processing fee. Two proposals with identical stated processing fees can differ substantially in all-in cost depending on the conversion rate applied at settlement. Ask how the reference rate is determined, when it is struck, and whether the spread is contractually capped. A merchant who negotiates only the visible fee has negotiated the smaller half of the price.

The FX component was also the crux of the 2022 short-seller critique, which estimated that roughly half of reported revenue derived from FX gains and fees. dLocal disputed that analysis. Whatever one concludes about the accounting argument, the commercial fact is undisputed and disclosed: currency conversion is a major revenue line, which makes it a major cost line for merchants.

Where it is genuinely strong

Several capabilities are core, and the evidence is in coverage and volume rather than marketing.

  • Local method depth. dLocal acquires local-only card schemes such as Elo and Hipercard in Brazil that international acquirers cannot reach, alongside instant rails, cash vouchers, direct debit, wallets and mobile money. Where conversion depends on the method a consumer already uses, this is the whole proposition.
  • Instant rails and payouts as first-class products. Pix in Brazil and UPI in India are processed as native capabilities, and the payouts product disburses to local bank accounts and wallets in local currency. Few competitors do collections and disbursements equally well.
  • Recurring billing on local rails. Subscription billing across local payment methods, not just card-on-file, is why streaming and SaaS companies are among dLocal's largest customer segments — those businesses cannot bill monthly in a market where cards are a minority payment method.
  • A single documented API replacing dozens of integrations. The founding proposition, documented for both pay-in and pay-out flows.

The financial position is a separate strength. dLocal reported full-year 2025 revenue of US$1.09 billion, up from US$746.0 million in 2024, with profit for the year of US$196.9 million; first-quarter 2026 payment volume was US$14.1 billion, up 73% year on year. A merchant trusting a counterparty to hold its collections in a dozen countries can read audited numbers instead of taking a private company's word for it.

Where it falls short

Cost modeling is the practical weakness. No rate card exists, the FX spread is unpublished, and a merchant cannot verify from public information what conversion rate was applied to its own settlements. For a finance team that must forecast cost of revenue precisely, that is a structural problem rather than a negotiation point. Coverage is also partial by design: dLocal serves emerging markets only, so it adds a provider rather than consolidating one.

Small businesses cannot use it. There is no self-serve onboarding, no payment-links or invoicing product, and no route in that avoids a negotiated enterprise contract. The product is an API and a hosted checkout built for enterprises.

Card-present acceptance is absent entirely, as are payment-facilitator products with programmatic sub-merchant underwriting — platforms can collect from and pay out to their users, but that is not the same as boarding sub-merchants through an API. High-risk verticals are served selectively and country by country; dLocal works with gaming and crypto on-ramp merchants in some markets but is not a high-risk acquirer, so availability cannot be assumed.

Fraud tooling exists but is not differentiating, and little detail on the underlying models is published. And there is no vendor-neutral orchestration: routing happens inside dLocal's platform, not across competing providers.

Ownership, governance and the short-seller record

dLocal was founded in Montevideo in 2016 by Sergio Fogel and Andrés Bzurovski, became Uruguay's first unicorn in 2020 and listed on Nasdaq under DLO on 3 June 2021. Pedro Arnt became chief executive in 2024. It acquired PrimeiroPay in 2021 and announced the acquisition of AZA Finance in 2025, expanding its African footprint.

Voting control is concentrated. Per the FY2025 Form 20-F filed in March 2026, Class B holders together owned 43.76% of outstanding shares but 79.55% of voting rights, so public shareholders cannot meaningfully influence the board.

The company has faced two short-seller reports from Muddy Waters Capital. The first, on 16 November 2022, alleged contradictory disclosures on payment volume and receivables, concealment of an insider option exercise, questions over fund flows in the PrimeiroPay acquisition, and that roughly half of revenue derived from FX gains and fees; it concluded dLocal was "likely a fraud." The company rejected it the same day and published a point-by-point rebuttal on 20 December 2022, stating that merchant cash and company cash sit in separate bank accounts, that the PrimeiroPay acquisition was arm's length, and that its Audit Committee's independent review — run with external counsel and forensic accountants — had found the key allegations without merit.

A second Muddy Waters note followed in May 2023, after which the shares fell about 21% in a day. This profile does not repeat its central claim: no primary source corroborating it could be located, and no enforcement action, fine or sanction against dLocal was found. A full-text search of dLocal's SEC filings returned no reference to a subpoena or to the Department of Justice.

The related US securities class action, alleging that dLocal's IPO registration statement and prospectus were materially misleading about trends in its take rate, was dismissed — and on 20 April 2026 the Appellate Division, First Department of the New York Supreme Court unanimously affirmed that dismissal. The FY2025 20-F disclosed no outstanding contingent liabilities other than labor contingencies.

How to evaluate dLocal

A cross-border provider is judged on things that never appear in a feature comparison.

  • Get the FX mechanism into the contract. Which reference rate, struck at which moment, with what spread, and is the spread capped? It determines a large share of your all-in cost and is published nowhere.
  • Ask about settlement timing per market. Capital controls and FX restrictions affect when funds can be converted and repatriated. Get contractual settlement timelines by country, and the remedy if they are missed.
  • Confirm which legal entity contracts with you. The license stack spans many jurisdictions; know which entity holds your funds in each market and which authority supervises it.
  • Test the methods, not the country list. "Available in country X" and "supports the rail your customers actually use in country X" are different claims. Ask for method-level coverage and authorization-rate data for your real mix.
  • Ask what happens on exit. Whether tokenized credentials and local recurring mandates are portable determines how trapped your subscriber base is. Get the answer before migrating customers onto local rails.
  • Check restricted-category status in advance. High-risk availability varies by country. In gaming, crypto or another regulated vertical, get written confirmation market by market rather than a general assurance.
  • Read the 20-F. The advantage of a listed counterparty is that risk factors, legal proceedings and country exposure are disclosed annually and audited. Ignoring it wastes the main reason to prefer dLocal over a private rival.

Capability assessment

Every company profiled on this site is assessed against the same eighteen dimensions, so the profiles can be read against one another. Each rating carries one sentence of evidence. There is no score out of ten, because a score is not defensible and a sentence is.

Core strength means a primary, differentiating capability. Supported means genuinely offered and documented, but not a differentiator. Limited means partial, geographically restricted, gated behind an enterprise tier, or delivered through a third party. Not offered means what it says. Unclear means the company markets the capability but does not document it well enough to judge — which is itself a finding.

Card processing
Core strength
dLocal acquires international and local-only card transactions in each market it serves, including domestic schemes such as Elo and Hipercard in Brazil that international acquirers cannot reach.
Online & e-commerce
Core strength
Online cross-border collection for global digital merchants selling into emerging markets is dLocal's founding product and the bulk of its total payment volume.
In-person / POS
Not offered
dLocal is a cross-border online payments company and does not sell point-of-sale terminals or card-present acquiring.
Mobile & contactless
Limited
dLocal supports mobile wallets and mobile money as payment methods within its checkout, but does not provide contactless card-present acceptance.
Recurring & subscription billing
Core strength
dLocal supports recurring and subscription billing across local payment methods, including card-on-file and local rails, which is why streaming and SaaS merchants are among its largest customer segments.
ACH & bank debit
Core strength
Local bank transfer and direct debit rails are central to dLocal's product, including Pix in Brazil, SPEI in Mexico and PSE in Colombia.
Instant / real-time payments
Core strength
dLocal processes on instant local rails including Pix in Brazil and UPI in India, and its payouts product disburses to bank accounts and wallets in local currency.
Cross-border & FX
Core strength
Cross-border collection and FX conversion is dLocal's core economic function, and FX and currency-conversion revenue is a substantial component of its reported take rate.
Embedded payments / PayFac
Limited
dLocal enables platforms and marketplaces to collect from and pay out to their own users, but it does not market a payment-facilitator-as-a-service product with programmatic sub-merchant underwriting.
Payment orchestration
Supported
dLocal routes across multiple local acquirers and payment methods within each country and markets smart routing and retries, but it is a single-provider platform rather than a vendor-neutral orchestration layer.
Payment links & invoicing
Limited
dLocal's product is an API and hosted checkout for enterprise merchants rather than a payment-link or invoicing tool for small businesses.
High-risk acceptance
Limited
dLocal serves gaming, crypto on-ramp and other regulated verticals in some markets, but availability is country-by-country and it is not positioned as a high-risk acquirer.
Fraud & risk tooling
Supported
dLocal provides fraud screening and chargeback management as part of its platform, but it is not a differentiating product and it publishes little detail on the underlying models.
Developer API & docs
Core strength
dLocal's central proposition is a single API and single contract replacing dozens of local acquirer integrations, and it publishes developer documentation for both pay-in and pay-out flows.
Fee transparency
Limited
dLocal publishes no rate card and its revenue mixes processing fees with FX conversion revenue, so a merchant's all-in cost depends on an FX spread that is negotiated rather than published.
Vertical specialisation
Supported
dLocal targets a defined set of global digital verticals — streaming, marketplaces, SaaS, advertising, travel, gaming and on-demand — rather than serving all merchant types.
Crypto & stablecoin
Supported
dLocal works with cryptocurrency exchanges as merchants, providing local on- and off-ramp collection and payout rails in emerging markets, rather than settling merchants in crypto.
Agentic & AI-initiated payments
Unclear
dLocal publishes no documented agentic-commerce or AI-agent payment protocol support as of July 2026.

Who dLocal suits

  • Global digital businesses — streaming, SaaS, marketplaces, advertising, gaming — that want to sell into Latin America, Africa and Southeast Asia without incorporating a local entity, opening a local bank account or signing a local acquirer in each country.
  • Merchants whose conversion depends on local payment methods rather than international cards, since in markets like Brazil, Mexico and Nigeria a large share of consumers cannot or will not pay with an international card.
  • Platforms that need two-way flow — collecting from consumers and paying out to local sellers, drivers or contractors in local currency — in the same integration.
  • Companies that want the regulatory burden of operating in each market transferred to a licensed counterparty, given dLocal's EU EMI, UK payment institution and country-level licences.
  • Merchants who want a publicly listed, audited counterparty with disclosed financials rather than a private emerging-markets aggregator.

Who dLocal is a poor fit for

  • Merchants who need to model their all-in cost precisely. dLocal publishes no rate card, and a substantial part of its revenue comes from FX and currency-conversion spread rather than an explicit processing fee — the mechanism at the centre of the Muddy Waters allegations that its take rate was overstated by FX gains. A merchant cannot verify the spread applied to its settlements from public information.
  • Merchants who cannot tolerate emerging-market macro and capital-controls risk. dLocal's own filings repeatedly reference the Central Bank of Argentina, and its business depends on being able to convert and repatriate funds from markets with FX restrictions; that risk is passed to the merchant in settlement timing and rate.
  • Investors and merchants sensitive to governance concentration. Class B shareholders held 43.76% of shares but 79.55% of voting rights as of the FY2025 20-F, so public shareholders cannot meaningfully influence the board.
  • Merchants who want card-present, point-of-sale or terminal acceptance — dLocal offers none.
  • Small businesses. dLocal is an enterprise-contract, negotiated-pricing provider with no self-serve signup, no published pricing and no payment-links product; a small merchant cannot onboard.
  • Merchants who need a single provider for both developed and emerging markets — dLocal covers emerging markets only, so it is almost always an addition to an incumbent processor rather than a replacement.
  • Buyers uncomfortable with a company that has been the subject of two short-seller reports and a since-dismissed securities class action, even though the class action was dismissed and the dismissal affirmed on appeal in April 2026, and the FY2025 20-F disclosed no outstanding contingent liabilities other than labour contingencies.

Competitors and alternatives

CompanyWhy a business would choose it instead
EBANXThe most direct competitor — a Brazil-founded rival offering the same single-integration access to local payment methods across Latin America and other rising markets.
AdyenGlobal acquirer with growing local-method coverage; a merchant may prefer one provider for developed and emerging markets rather than two.
PayU / PayU GPOLong-established emerging-markets payment provider with overlapping country coverage in Latin America, Africa, Asia and Central Europe.
RapydCompetes on cross-border pay-in and pay-out coverage with a similar single-API pitch.
NuveiOffers alternative payment methods and payouts across many markets and competes for the same digital-vertical merchants.
StripeFor merchants whose emerging-market volume is small enough that Stripe's local-method coverage suffices, one provider is simpler than two.
Local direct acquirers (for example Cielo or Getnet in Brazil)A merchant with enough volume and a local entity can cut out the aggregation layer and acquire locally at lower cost.

dLocal — frequently asked questions

What does dLocal actually do?

It gives a global merchant one API and one contract to collect payments from, and send payouts to, consumers in more than 60 emerging markets. dLocal handles local acquiring, local payment methods, local currency settlement and local licensing, so the merchant does not need a local entity, local bank account or local acquiring relationship in each country. It covers emerging markets only and does not offer card-present or point-of-sale acceptance.

Is dLocal a public company?

Yes. DLocal Limited listed on Nasdaq under the ticker DLO on 3 June 2021 and files Form 20-F as a foreign private issuer. Voting control is concentrated: per the FY2025 20-F filed in March 2026, Class B holders owned 43.76% of outstanding shares but 79.55% of voting rights, so public shareholders cannot meaningfully influence the board.

How does dLocal make money?

Through a blended take rate — revenue as a percentage of total payment volume — that combines explicit processing fees with revenue from currency conversion. The FX component is substantial, which means a merchant's true all-in cost depends heavily on the spread applied when local-currency collections are converted to the settlement currency. That spread is negotiated per merchant and is not published.

What was the Muddy Waters report about?

Muddy Waters Capital published a short report on 16 November 2022 alleging accounting inconsistencies between total payment volume and receivables, discrepancies between subsidiary payables and receivables, concealment of an insider option exercise's timing and funding, questions over the PrimeiroPay acquisition, and that around half of revenue came from FX gains and fees; it called dLocal "likely a fraud." dLocal rejected the report and published a rebuttal on 20 December 2022 saying an Audit Committee review with external counsel and forensic accountants had found the key allegations without merit. A second Muddy Waters note followed in May 2023, after which the shares fell about 21% in a day.

Was dLocal found guilty of securities fraud?

No. The US securities class action alleging that dLocal's IPO registration statement and prospectus contained materially misleading statements about trends in its take rate was dismissed, and on 20 April 2026 the Appellate Division, First Department of the New York Supreme Court unanimously affirmed the dismissal. The court found that plaintiffs had failed to identify a material trend given dLocal's growth in volume, revenue and gross profit before the IPO.

Which countries does dLocal cover?

More than 60 across Latin America, Africa, Asia and the Middle East as of the first quarter of 2026. It holds licenses or approvals in Brazil, Mexico, Argentina, Chile, Peru, Ecuador, Costa Rica, Honduras, the Dominican Republic, Uruguay, Nigeria, Kenya, Tanzania, Uganda, Rwanda, South Africa, the Philippines and the United Arab Emirates, plus an EU electronic money institution license, a UK payment institution license approved in December 2024, and FinCEN money services business registration.

How is dLocal different from EBANX?

Both give global merchants a single integration for local payment methods in emerging markets. dLocal is Uruguay-founded and Nasdaq-listed since 2021, publishes audited financials — FY2025 revenue of US$1.09 billion and profit of US$196.9 million — and covers more than 60 countries with a strong push into Africa and Asia. EBANX is Brazil-founded and privately held, so its financial standing cannot be independently verified. Neither publishes pricing.

Sources

This profile was built from the following primary and secondary sources. Where sources disagreed, the disagreement is stated in the text rather than resolved silently.

Not verified. The following could not be confirmed from a source we consider reliable, and is therefore not asserted anywhere above.
  • The May 2023 Argentina matter. Muddy Waters stated dLocal was under investigation in Argentina and the shares fell about 21%, but the investigating authority, the scope, the legal basis and the outcome could not be confirmed from any primary source. dLocal's filings mention the Central Bank of Argentina in several 6-Ks and in the FY2025 20-F, but no enforcement action, fine or sumario against dLocal was located. Do not state that dLocal was fined or sanctioned in Argentina.
  • No SEC or US Department of Justice inquiry into dLocal could be confirmed. A full-text search of dLocal's EDGAR filings returned zero hits for 'Department of Justice' and zero for 'subpoena', so any claim of a DOJ or SEC investigation should not be published without a primary source.
  • Employee headcount. The figure of around 1,000 as of 2024 comes from Wikipedia and was not confirmed against a company filing.
  • The AZA Finance acquisition price of US$150 million and the 2021 PrimeiroPay price of US$40 million come from Wikipedia rather than a filing or press release reviewed in this research.
  • The IPO valuation of around US$9.5 billion is a widely reported figure sourced here from Wikipedia rather than the prospectus.
  • dLocal's exact take rate, FX spread methodology and per-country pricing are not published, so the merchant's all-in cost cannot be stated.
  • Current office list and count. 'More than 20 offices' is a 2024 Wikipedia figure and may be stale.
  • Whether dLocal has any documented agentic-commerce or AI-agent payment capability — nothing was found either way.