dLocal
dLocal (NASDAQ: DLO) is a Uruguay-headquartered emerging-markets payment infrastructure platform connecting global merchants with billions of consumers across 60+ countries in Latin America, Africa, the Middle East, and Asia. dLocal exposes a unified set of REST APIs for accepting payments (Payins) via 1,000+ local methods, disbursing funds (Payouts V3) to beneficiaries via local rails, tokenizing cards, managing marketplace sub-merchants (dLocal for Platforms), performing KYC verifications, handling chargebacks, enrolling users for recurring Pix flows, and pulling real-time exchange rates. Native iOS and Android SDKs are published as open source on GitHub.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles dLocal the way a machine reads it — 124 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — dLocal scores 69.9/100 (strong), with a separate agent-readiness read of 63/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile dLocal
Each block below is one kind of artifact we hold for dLocal. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
dLocal Payments API
Create, retrieve, cancel, and authorize payments using 1,000+ local payment methods including cards, Pix, UPI, M-Pesa, Boleto, OXXO, SPEI, mobile money, cash vouchers, BNPL, wal...
dLocal Refunds API
Create, retrieve, and inspect refunds against previously successful payments. Refunds may be full or partial and are settled in the original payment currency.
dLocal Cards API
Securely tokenize cards (server-side) for repeat usage. Returns a card_id token consumable by subsequent Payments and Authorizations.
dLocal Chargebacks API
Retrieve chargeback details and status, simulate chargebacks in the sandbox, and receive asynchronous chargeback notifications via webhook.
dLocal Enrollments API
Enroll payers for recurring Pix Automático, Pix Biometrics, and SmartPix transactions. Once enrolled, payers can be charged repeatedly without re-authorization.
dLocal Accounts API
Create and manage sub-merchant accounts.
dLocal Authorizations API
Authorize a card transaction and capture or cancel later.
dLocal Balance API
Inspect available merchant balance for payouts.
dLocal BankAccounts API
Manage bank accounts attached to sub-merchant accounts.
dLocal Documents API
Upload and retrieve verification documents.
dLocal ExchangeRates API
Retrieve real-time FX rates.
dLocal KYC API
Submit KYC data and documents for accounts.
dLocal Payouts API
Request, retrieve, release, and cancel payouts.
dLocal Quotes API
Lock in an FX quote before requesting a payout.
dLocal Transfers API
Settle and transfer between accounts.
dLocal Verifications API
Create and inspect KYC verifications.
Scroll within the panel for all 16 ·
Postman Collections 9
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
dLocal Cards API
POSTMANdLocal Chargebacks API
POSTMANdLocal Enrollments API
POSTMANdLocal Exchange Rates API
POSTMANdLocal KYC Verifications API
POSTMANdLocal Payments API
POSTMANdLocal Payouts V3 API
POSTMANdLocal For Platforms API
POSTMANdLocal Refunds API
POSTMANScroll within the panel for all 9 ·
Open Collections 9
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
dLocal Cards API
OPEN COLLECTIONdLocal Chargebacks API
OPEN COLLECTIONdLocal Enrollments API
OPEN COLLECTIONdLocal Exchange Rates API
OPEN COLLECTIONdLocal KYC Verifications API
OPEN COLLECTIONdLocal Payments API
OPEN COLLECTIONdLocal Payouts V3 API
OPEN COLLECTIONdLocal For Platforms API
OPEN COLLECTIONdLocal Refunds API
OPEN COLLECTIONScroll within the panel for all 9 ·
Arazzo Workflows 15
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
dLocal Authorize and Capture Payment
Authorize a card transaction, confirm the authorization, then capture the funds.
ARAZZOdLocal Cancel Pending Payment
Create an alternative payment, check its status, and cancel it while it is still PENDING.
ARAZZOdLocal Create and Resolve KYC Verification
Create a KYC verification, confirm it persisted, then branch on its status to update state or list documents.
ARAZZOdLocal Create Payment and Confirm Status
Discover a supported payment method, create a payment, then poll its status until it settles.
ARAZZOdLocal Enroll and Charge Recurring
Enroll a payer for Pix Automatico, confirm the enrollment is ACTIVE, then place the first recurring charge.
ARAZZOdLocal FX Preview and Pay
Preview the exchange rate for a corridor, then create a payment in the local currency.
ARAZZOdLocal Hold and Release Payout
Request a payout on hold, review it, then release or cancel based on the review.
ARAZZOdLocal List and Inspect Payment Refunds
Confirm a payment, list all refunds raised against it, then retrieve one refund in detail.
ARAZZOdLocal Manage Account Bank Accounts
Add a bank account to a sub-merchant, list the account's bank accounts, retrieve one, then disable it.
ARAZZOdLocal Onboard Sub-Merchant Account
Create a platform sub-merchant account, attach a bank account, then confirm KYC and balance.
ARAZZOdLocal Quote and Request Payout
Check balance, lock an FX quote, request a payout against the quote, then confirm its status.
ARAZZOdLocal Refund Payment and Confirm
Confirm a payment is PAID, issue a refund against it, then verify the refund status.
ARAZZOdLocal Settle Transfer Between Accounts
Check the source account balance, transfer funds to another account, then confirm the transfer.
ARAZZOdLocal Simulate and Inspect Chargeback
Create a payment, simulate a chargeback against it in sandbox, then inspect the chargeback and its status.
ARAZZOdLocal Tokenize Card and Charge
Tokenize a card, verify the stored token, then charge it in a card payment.
ARAZZOScroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
D Local Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
D Local Finops
FINOPSFeatures 23
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 23 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
D Local Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
dLocal API Rules
SPECTRALdLocal API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
dLocal Card Token
JSON SCHEMAdLocal Payment
JSON SCHEMAdLocal Payout
JSON SCHEMAdLocal for Platforms Account
JSON SCHEMAdLocal Refund
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Payments Payment Structure
JSON STRUCTUREPayouts V3 Payout Structure
JSON STRUCTUREExamples 10
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 10 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Global subscription billing in emerging markets
Charge LatAm, African, and Asian customers in their preferred local currency and method (Pix, UPI, mobile money) for SaaS, streaming, and gaming subscriptions.
Cross-border payroll and contractor payouts
Pay employees and contractors in 60+ countries using instant local rails, bank transfers, mobile money, and cash pick-up.
Marketplace and platform payouts
Onboard sub-merchants via dLocal for Platforms, split payments, and settle balances between accounts.
Remittances
Power consumer remittance corridors with FX quoting, KYC verification, and local-currency disbursement.
Travel and ride-hailing
Enable global travel and mobility platforms to collect from local consumers and pay out to local drivers/hosts.
E-commerce expansion
Help global merchants like Amazon, Shein, and Shopify accept local methods such as Boleto, OXXO, SPEI, and Pix.
Stablecoin settlement
Use Stablecoin Full for cross-border settlement when fiat rails are slow or expensive.
Scroll within the panel for all 7 ·
Integrations 9
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Brazil Pix
Native Pix, Pix Automático (recurring), Pix Biometrics, and SmartPix support.
India UPI and network tokenization
UPI collect/intent flows plus RBI-compliant network tokenization.
Africa M-Pesa and Mobile Money
M-Pesa, MTN MoMo, Orange Money, and other Mobile Money rails.
Mexico SPEI and OXXO
Bank transfer (SPEI) and cash voucher (OXXO) coverage.
Stablecoins
Stablecoin Full product for crypto-rail settlement.
Google Pay (Paytm bridge)
Google Pay integration via the Paytm bridge.
Mercado Pago
Device ID object support for fraud signals on Mercado Pago.
Postman
Official Postman collection covering the full REST API.
Model Context Protocol (MCP)
Built-in dLocal MCP server exposes API operations to LLM agents.
Scroll within the panel for all 9 ·
Solutions 10
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Payins
Accept local payment methods across 60+ countries.
Payouts
Disburse funds via local rails to employees, contractors, partners, and consumers.
dLocal for Platforms
Marketplace and platform multi-merchant payment solution.
Defense Suite
Fraud-management and chargeback-prevention toolkit.
Invoice Collection
Local-currency billing and collection.
Stablecoin Full
Stablecoin payin/payout rails for cross-border settlement.
dLocal Direct
Mobile SDK product for native iOS and Android in-app checkout.
SmartFields
Client-side field-level tokenization via dlocal.js.
dLocal Go
Hosted checkout product.
Payment Links
Shareable links for one-off collections.
Scroll within the panel for all 10 ·
Resources
Every other property we hold for dLocal — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 15
Reference material describing how the API behaves
Scroll within the panel for all 15 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 22
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 22 ·
Build 15
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 15 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/d-local · machine-readable index on apis.io