Each country has its specific requirements, including mandatory fields for processing transactions and document validation, among others. Identify the key aspects necessary to understand and implement payout operations across various countries.

Key aspects of payout operations

Payment methods

Payouts can be executed through various payment methods, depending on the country, regulatory requirements, and recipient preferences. Each method may have specific compliance, technical, and operational requirements based on the country.

Payment method	Description
Bank transfers	Traditional electronic fund transfers to the recipient's bank account.
Instant Payments	Real-time payment systems, such as Pix (Brazil) and UPI (India), and digital wallets, where recipients can hold funds identified by phone numbers, aliases, or specific account identifiers.
Cards	Payouts are directed to debit or prepaid card accounts, allowing immediate access to funds through ATM withdrawals or card-based purchases.
Cash Pick-Up	Physical cash disbursement points where recipients can collect their funds in person upon verification.

Flow types

Payout flows describe the relationship between the sender and the receiver, influencing regulatory compliance and technical configurations. Correctly identifying the flow type is crucial for ensuring regulatory compliance and applying the correct transaction parameters.

Flow Type	Description
B2C (Business-to-Consumer)	A business entity sends funds to an individual. Standard in the gig economy, freelance platforms, or payments for services.
B2B (Business-to-Business)	A business transfers funds to another business entity, typically for supplier payments, service fees, or settlements.
P2P (Peer-to-Peer)	An individual sends funds to another individual. Often applicable in personal remittance use cases or social payment applications.

Purposes

The Purpose field specifies the reason for the payout transaction. This information is crucial for:

Regulatory compliance: Many jurisdictions mandate the declaration of transaction purposes to prevent money laundering, terrorist financing, and other illicit activities.
Transaction screening: Financial institutions may screen or block transactions based on the declared purpose, particularly for high-risk categories.
Reporting obligations: Accurate purpose classification ensures that cross-border payments meet statutory reporting requirements.

Each country may have a predefined list of acceptable purposes that must be adhered to. Find the complete list of purposes accepted in the API Reference section.

Request for Information (RFI)

An RFI (Request for Information) is a compliance check that requires additional documents to validate a payout before it can proceed. Common triggers include sanction screening matches and amount thresholds. The requirements for a trigger will vary depending on:

Trigger	Description
Country	Local regulations may require specific documents.
Purpose	Certain purposes (e.g., remittances, capital injections) have higher scrutiny.
Threshold amount	Transactions above defined limits need extra verification.
Flow type	Some flows (e.g., B2B vs. P2P) have different compliance requirements.

RFI flow process

Phase	Description
1. Compliance Triggered	A potential risk factor is detected during the transaction screening (e.g., a sanction screening match, an amount exceeding a defined threshold, or other compliance flags).
2. Documents Requested	The payout transaction is temporarily placed on hold. The sender (merchant) receives a notification and is required to collect specific supporting documents from their user (the recipient) and submit them to DLocal for review.
3. Document Review	DLocal's compliance team or automated system meticulously reviews the submitted documentation to validate the transaction against regulatory requirements and internal policies.
4. Final Verdict	Based on the document review, a decision is made regarding the payout: - APPROVED → The payout successfully proceeds to the recipient. - REJECTED → The payout is canceled due to insufficient or invalid documentation, or failure to meet compliance standards. - REVIEW → Additional or clearer documents are requested from the sender to further clarify or verify the transaction.

Requirements by regions

Please see each country below for specific country requirements and example requests.

You need to complete the fields login and pass with yourx_login and x_trans_key credentials. Find them in the Merchant Dashboard, under the Settings > Integration section.