Your Merchant of Record for emerging markets, built for revenue growth.

A Merchant of Record (MoR) is the legal entity responsible for the transaction with the end customer. A MoR like dMoRe sits behind the sale, handling payment processing, invoicing, taxes, and regulatory compliance, so these responsibilities don’t fall on your business in every market.

A Merchant of Record takes responsibility for the full transaction lifecycle, including:

• Processing payments
• Issuing end-user invoices and receipts
• Calculating, collecting, and remitting taxes
• Meeting local regulatory and compliance requirements

With a Merchant of Record like dMoRe, these responsibilities don’t sit across multiple teams or providers. They’re handled under one operating model, designed to scale across emerging markets.

With dMoRe, payments are processed directly with the end customer under the Merchant of Record (MoR) entity. dMoRe runs on, and was built on top of, dLocal’s payment infrastructure, which means transactions are processed on local rails, using the payment methods customers already use and trust in each market, with no additional integrations.

A Payment Service Provider (PSP) like dLocal focuses on payment processing. It authorizes the transaction and moves funds, but the legal, tax, and regulatory responsibility for the sale remains with the merchant.

A Merchant of Record like dMoRe goes a step further. dMoRe becomes the legal seller for the transaction, taking responsibility for payments, invoicing, taxes, compliance, disputes, and chargebacks, all running on dLocal’s payment infrastructure.

In simple terms, with dLocal, you process payments; with dMoRe, we run the transaction model behind those payments.

In emerging markets, regulation, tax rules, FX constraints, and payment behavior change a lot from country to country. A Merchant of Record like dMoRe removes the operational burden of rebuilding your operating model for each market, making expansion faster and more predictable.

Yes. dMoRe is designed to support a single Merchant of Record operating model across multiple emerging markets.

That said, many businesses don’t apply the same model everywhere. Some markets require a Merchant of Record, while others don’t. dMoRe supports that flexibility, so you’re not forced into an all-or-nothing setup.

That’s OK, and dMoRe is built for it. dMoRe supports hybrid and graduated setups, where you use a Merchant of Record in markets with higher regulatory, tax, or payment complexity, and keep your existing model or PSP setup in others. As markets mature or your footprint changes, you can adjust the model over time.

Many MoR providers are optimized for standard markets and global cards. dMoRe is built to operate where MoR is hardest — navigating tax, FX, and local payment constraints in emerging markets.

dMoRe supports 1000 local payment methods in emerging markets across Africa & the Middle East, Asia, and Latin America, all through dLocal’s network coverage.

Local teams work directly with regulators, banks, and payment partners to keep the operating model compliant and active.

With dMoRe, tax calculation, collection, and remittance are handled as part of the Merchant of Record service. This includes market-specific requirements and reporting, without relying on your internal teams or local tax advisors.

No, you don’t need to set up or manage local entities in supported markets. dMoRe acts as the legal seller for the transaction.

dMoRe is designed for markets where regulation changes frequently. Local teams work close to regulators, tax authorities, and payment partners to maintain compliance as rules evolve.

As the Merchant of Record, dMoRe carries regulatory responsibility for the transaction. This is a core part of the MoR model and one of the main reasons teams adopt it.

Correct. With dMoRe, there’s no need to create or manage local legal entities in supported markets.

No. dMoRe manages settlement and fund flows on your behalf, including the repatriation of funds to your preferred account.

No. dMoRe takes full tax responsibility, so that you can focus on your business. We centralize tax handling across markets, removing the need to coordinate multiple local advisors.

Finance and legal teams remain involved at a strategic level, but no longer need to manage execution market by market. dMoRe removes repetitive operational work from internal teams.

You keep:

• Product ownership and delivery
• Pricing and go-to-market strategy
• Brand, UX, and customer experience

dMoRe takes on:

• Payment processing via dLocal
• Tax and compliance
• Invoicing and receipts
• Customer support for any payment issues

dMoRe is delivered through one API and one contract, built on dLocal’s payment infrastructure.

This allows you to support multiple markets and payment methods without separate integrations.

One integration. Markets, payment methods, and billing flows are handled within the same setup.

Yes. dMoRe supports native checkout experiences that fit into your existing UX.

Yes. Checkout pages, emails, and invoices can all be fully branded.

Yes. dMoRe supports recurring billing, usage-based models, and high-volume transaction flows across local payment methods.

Yes. dMoRe supports direct integration into your existing checkout experience. Because dMoRe runs on top of dLocal’s payment infrastructure, merchants can integrate through one API and offer local payment methods within their own checkout environment. This allows you to maintain your brand, UX, and payment flow, while dMoRe handles the Merchant of Record responsibilities behind the transaction, without redirects that can create friction for users.

No. You retain visibility and control, while dMoRe uses dLocal’s local processing to optimize acceptance.

By processing payments locally through dLocal’s infrastructure, dMoRe improves authorization rates, especially in markets where global card-only setups underperform.

Of course. Checkout design and payment method presentation remain configurable.

Retries and recovery flows are handled within dLocal’s payment stack, using locally appropriate methods and logic.

Many local payment methods don’t carry traditional chargeback risk. dMoRe manages disputes operations where applicable, based on the method and market.

Yes, of course. Reporting and visibility are available through dashboards and exports.

Yes. dMoRe supports in-game purchases, subscriptions, and one-off digital transactions through direct-to-consumer (D2C) payment flows.

Both. Many teams start with dMoRe to accelerate expansion and keep it as their long-term operating model.

Yes. Markets can be added over time without changing your core setup.

Gaming companies use dMoRe to localize payments, manage fraud and chargebacks, and operate under one Merchant of Record model across regions, even at high volume.

Yes. dMoRe supports recurring and usage-based billing, with compliant invoicing and tax handling built in.

You start a conversation with our team about your markets, business model, and expansion goals. We’ll look at where you’re selling today, where you want to go next, and what’s getting in the way — no assumptions, just context.

Yes. We’ll walk through your current setup together and help you understand where a Merchant of Record model makes sense, where it doesn’t, and what a hybrid or graduated approach could look like for your business.

Timelines vary by market, but dMoRe is designed to remove the biggest blockers to launch — like local entities, tax setup, and fragmented integrations — so teams can move faster than building everything from scratch.