What Is "DLOCAL" on My Bank Statement?

dLocal says it processes payments for online businesses and is not the seller itself. Its End User Help Center is the primary route to check a payment or refund.

Sources: dLocal End User Help Center

dLocal is the processor, not necessarily the store

dLocal’s end-user guidance explains that it processed a payment on behalf of an online business. The processor name alone does not identify the seller, product, or whether the payment was one-time or recurring.

Start with the checkout you remember: online shops, apps, digital services, travel, and subscriptions can use a payment provider whose name was not prominent at checkout.

Sources: dLocal End User Help Center · dLocal payment platform

Read the complete descriptor and receipt

dLocal’s Create Payment API defines a descriptor as a dynamic descriptor, so a payment can combine dLocal and merchant text. The supplied research brief says the configurable descriptor supports up to 22 characters; the API verifies configurability, while that character limit is brief-supplied rather than visibly stated by the linked API field.

A Microsoft Q&A community report, for example, shows the statement text “Dlocal * microsoft Pc.” This is one cardholder report, not evidence that another dLocal charge is from Microsoft. Open the full bank detail rather than relying on a shortened notification, then match every available word, amount, currency, and date with orders, subscriptions, invoices, and confirmation email.

Sources: dLocal Create Payment API: Dynamic Descriptor · dLocal End User Help Center · Microsoft Q&A cardholder report (community example)

Check payment or refund status in End User Help

dLocal maintains a dedicated End User Help Center where consumers can choose payment or refund help and contact support. This is the relevant dLocal route when a merchant says a payment is pending or a refund has not appeared.

Gather the transaction ID, checkout email, amount and date, plus the merchant, site, or app name before contacting support. Keeping those identifiers together helps distinguish the seller’s order from dLocal’s processing record.

  1. Choose the payment or refund path that matches the issue.
  2. Provide the checkout details requested by the official form.
  3. Keep the support response with the seller’s receipt or order record.

Sources: dLocal End User Help Center

Choose the right business to contact

Use the merchant text and confirmation email to decide which business should handle the order, service, cancellation, or product question. Use dLocal’s consumer support for the payment or refund status it processed.

If neither route can connect the charge with a purchase, preserve the complete descriptor and both support responses rather than assuming dLocal itself was the seller.

Sources: dLocal End User Help Center

If it remains unrecognized

If the official lookup or portal and your receipts still do not match the charge, contact the card issuer using the number on the card or its official app. Ask about the transaction and its unauthorized-transaction process; do not enter card details into unofficial lookup sites.

Frequently asked questions

Is dLocal the seller?

Not necessarily. dLocal says it processes payments for online businesses; the seller may be a different business.

Sources: dLocal End User Help Center

What should I send dLocal support?

Have the transaction ID, checkout email, amount and date, and merchant, site, or app name available.

Sources: dLocal End User Help Center

Related charges

  • Stripe — Another payment processor
  • Worldpay — Another payment processor

Part of: Payment processors & POS →