Initiate an application for a new seller for Dintero Payout with
split-payment. The application will contain a link to an URL where the
signatory of the seller will need to finish submission of the
case contract and sign it. Dintero will perform a KYC, AML and bank ownership
check on the seller before the application case_statuswill be
updated to ACTIVE. Once the application is approved, the payout
destination will be added automatically to the Dintero Payout service.
scopes:
For testing purposes it is possible to auto-approve or decline a new seller
by adding one of the following values to payout_destination_description:
ACTIVEDECLINEDWAITING_FOR_SIGNATURENOTE: This behavior is only available in test mode, i.e. with an aid prefixed with “T”.
Documentation Index
Fetch the complete documentation index at: https://docs.dintero.com/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication (token authentication) should be used for accessing the API.
Use Get Token to get an access token for client credentials. Pass the token in the request header:
Authorization: Bearer {access_token}
where the access_token is JSON Web Tokens (JWT).
An id that uniquely identifies the account.
9ID of seller to create when the contract has been completed, signed, and approved.
40A static reference that will be included on bank payments, the name of the service the payout-destination will be enrolled into. Eg. if yor platform is an "Uber for lawnmowers" called "Mowber" the payout_reference should be "Mowber".
60Bank account information about the seller. Currently the contract service only supports one bank_account per payout destination.
1 elementThe language that will be used in emails, declaration form, signing page etc.
en, no 2The name of the seller
60Description of the seller
1000company or leave blank. Required fields are
organization_number and country_code.individual. Provide optional fields in
the individual object.company, individual Country code, must be a two letter ISO 3166-1-alpha-2 country code.
Required if type is omitted or set to company.
2National organization number valid in the country specified. Required
if type is omitted or set to company.
Used only if type is individual.
The interval of the payout. The interval can be daily, weekly, monthly or manual.
daily, weekly, monthly, manual The user that will submit the form. If the email is set the user will be notified about the form via email.
See Seller onboarding - Reminder emails for the reminder schedule.
Optional settings for automatically creating report configurations when the payout destination is created.
Created ApprovalsPayoutDestinationResponse
ID of seller to create when the contract has been completed, signed, and approved.
40A static reference that will be included on bank payments, the name of the service the payout-destination will be enrolled into. Eg. if yor platform is an "Uber for lawnmowers" called "Mowber" the payout_reference should be "Mowber".
60Bank account information about the seller. Currently the contract service only supports one bank_account per payout destination.
1 elementAn UUID that uniquely identifies the resource
The date-time when the resource was created
The ID of the user/client created the resource
"1c92f7e1-2897-4d46-bdcc-c127a914fb4e"
The date-time when the resource was last updated
The ID of the user/client created the resource
"1c92f7e1-2897-4d46-bdcc-c127a914fb4e"
The language that will be used in emails, declaration form, signing page etc.
en, no 2The name of the seller
60Description of the seller
1000company or leave blank. Required fields are
organization_number and country_code.individual. Provide optional fields in
the individual object.company, individual Country code, must be a two letter ISO 3166-1-alpha-2 country code.
Required if type is omitted or set to company.
2National organization number valid in the country specified. Required
if type is omitted or set to company.
Used only if type is individual.
The interval of the payout. The interval can be daily, weekly, monthly or manual.
daily, weekly, monthly, manual The user that will submit the form. If the email is set the user will be notified about the form via email.
See Seller onboarding - Reminder emails for the reminder schedule.
Optional settings for automatically creating report configurations when the payout destination is created.
ACTIVE, DECLINED, UNDER_MANUAL_REVIEW, AUTOMATIC_REVIEW, WAITING_FOR_SIGNATURE, WAITING_FOR_DECLARATION, ERROR, ARCHIVED, WAITING_FOR_DETAILS, TERMINATED