With the marketplace solution you create and onboard all the related accounts, trigger payments and manage transactions.
There are two types of accounts:
|Main Account||Marketplace associate account as principal. The Main Account contains the default configuration that will be applied automatically to the created Sub-Account, such as available payment methods, fees, and settlement period. Each configuration will be identified with a specific Merchant Type.|
|Sub-Account||All financial activities happen through accounts. It applies to third parties in your marketplace—sellers, service providers, contractors, and so on. The Main Account can have multiple Sub-Accounts but a single account is sufficient in most use cases.|
The Merchant Types are defined with the creation of the Marketplace’s dLocal account (Main Account). It’s possible to define different Merchant Types for each country, industry, or any other Sub-Accounts characteristic if needed. For example, it’s possible to have a different list of payment methods available or settlement fees for each country.
To obtain the Main Account, we encourage you to contact our Sales team.
They will guide you in the following steps for the Main Account creation.
Start the onboarding process by creating a Sub-Account. To create a Sub-Account, you need to get the legal entity type, collect the minimum required information, and send the information in an API request.
dLocal Marketplace API is designed to be used with two alternatives.
In this solution, dLocal is presented to the Sub-Account as a payment provider.
The Sub-Account has access to the dLocal Merchant Dashboard, so KYC information and changes on his bank account can be made automatically by it, without interaction with the Main Account. All communication regarding the Sub-Account dLocal account is managed by dLocal. This is the simplest solution to integrate and is recommended for most use cases.
In this solution, dLocal works as a payment provider for the Marketplace.
The Sub-Account doesn’t know about dLocal, only the Marketplace. The Sub-Account won’t use the dLocal Merchant Dashboard, so the Marketplace must manage all Sub-Account settlements and account data changes using the API. It must also implement all communication with the Sub-Account regarding his dLocal payment account (for example, when we need to ask him for more KYC documentation). This is the most flexible solution, but it’s the one that requires more effort from the Marketplace.
|Feature||dLocal Managed||White Label|
|dLocal Merchant Dashboard access||✅|
|Bank account changes managed by the Sub-Account||✅|
|KYC information changes managed by the Sub-Account||✅|
|Settlement process managed by the Sub-Account||✅|
|Communication with the Sub-Account managed by dLocal||✅|
|Sub-Account knows about dLocal||✅|
|Total customization of the onboarding and operational process||✅|
ℹ️Sub-Account profile: Business or Person?
dLocal’s Marketplace API has support for Sub-Accounts that represent a business (company or individual) or a person without a business. The chosen option will depend on the Marketplace business characteristics.
The KYC information needed for each case will vary depending on the Sub-Account profile.
Updated 3 months ago