onboardInBanks array at creation time. The operation is idempotent — if an onboarding process for the given bank partner is already in progress or has completed, the endpoint returns the existing process state instead of creating a duplicate.
Endpoint
com.diameterpay.api/end-users.write
Request Headers
string
required
Bearer token obtained from your OAuth 2.0 token endpoint. Format:
Bearer {access_token}string
required
A UUID v4 string you generate for each unique request. Ensures safe retries in case of network failures without starting duplicate onboarding processes.
Path Parameters
string
required
UUID v4 of the existing end user (individual or organization) to onboard with an additional bank partner.
Request Body
string
required
The bank partner to initiate onboarding with. One of:
PORTAGE, SLOVAK_SAVINGS_BANK.Response
Returns200 OK with an onboarding process object describing the current or newly created state.
string
Outcome of the request. One of:
CREATED— a new onboarding process was started.EXISTING_PROCESS_FOUND— an onboarding process for this end user and bank partner was already in progress; no new process was created.ALREADY_ONBOARDED— the end user has already completed onboarding with this bank partner; no new process was created.
string
UUID v4 of the onboarding process (new or existing).
string
The bank partner this onboarding process is associated with.
string
Current state of the onboarding process (e.g.
PENDING, IN_REVIEW, APPROVED, REJECTED, COMPLETED).string
UUID v4 of the end user being onboarded.
string
Human-readable description of the outcome, useful for logging and debugging. For example:
"Onboarding process created successfully." or "End user is already onboarded with this bank partner.".This endpoint is fully idempotent. Sending the same
bankPartner for an end user who is already onboarded will return ALREADY_ONBOARDED with the existing process details and will not create a new onboarding process or generate any side effects.