Merchant Settlements
Last updated
Clients can manage their own on-platform liquidity by depositing fiat into their CAMS account, or withdrawing fiat from their CAMS account to their bank.
, and registering the banking instructions used for withdrawals. These operations are performed on the tenant's own corporate account (see Corporate / Client Customer Onboarding) and are distinct from any individual customer's funding or payout activity.
To fund their on-platform account with fiat, for example, in order to top-up liquidity before processing payouts, clients must retrieve the account's deposit instructions using GET/v1/accounts/{accountId}/configuration
The returned banking instructions (including IBAN or account number) must be used to ensure fiat delivery to the clients on-platform account. Special care should be given to the "beneficiaryBankMemo" which will be used to identify the clients on-platform account.
Once the funds are received, the account balance is updated, notifying webhook is sent and a corresponding deposit transaction appears in GET /v1/transactions endpoint (transactionType: DEPOSIT).
Before the client can withdraw fiat to their own bank account, the destination bank account must be registered using POST /v1/customers/{customerId}/bankinfo
This endpoint associates a new external bank account with the clients profile record. Each customer can have up to 20 external bank accounts saved on file.
Use GET /v1/customers/{customerId}/bankinfo to list all bank accounts on file for a customer
GET or DELETE /v1/customers/{customerId}/bankinfo/{bankAccountId} to retrieve or remove a specific bank account.
Once a bank account has been registered (and any optional cooling-off period has elapsed), the client can withdraw fiat from their on-platform account to their bank account using POST /v1/withdrawals.
Last updated