This handles bulk payments processing from merchant accounts to multiple beneficiaries at once through their bank accounts and mobile wallets either using a file (Microsoft Excel or CSV) or JSON payload. Depending on your merchant account configurations, the payout transactions fall under these authorization level workflows:

ā€‹
2-eye Principle

The diagram below illustrates the flow of batch payouts when a single merchant user initiates it to transfer funds. 2-eye Principle
  1. The merchant user uploads a batch either using a file (Microsoft Excel or CSV) or JSON payload containing beneficiary transactions.
  2. OneKhusa platform receives the request and responds with 200-OK that the batch is queued for further processing. If you have configured webhooks, your system will receive batch.received or batch.failed payload notification based on the processing outcome.
  3. When the batch is received successfully, call the transfer funds API endpoint to start paying out to beneficiaries.
    Warning: You cannot undo this process.
  4. To avoid throttling your system once the transactions are processed, OneKhusa will send batch.payout.success payload containing up to 10 successful transactions or batch.payout.failed payload containing up to 10 failed transactions. This will continue until the last set of transactions are sent to your system.

ā€‹
4-eye Principle

The diagram below illustrates the flow of batch payouts for Initiator + Approver workflow. 4-eye Principle
  1. The first merchant user uploads a batch either using a file (Microsoft Excel or CSV) or JSON payload containing beneficiary transactions.
  2. OneKhusa platform receives the request and responds with 200-OK that the batch is queued for further processing. If you have configured webhooks, your system will receive batch.received or batch.failed payload notification based on the processing outcome.
  3. When the batch is received successfully, the second merchant user approves by calling the approve batch API endpoint to start paying out to beneficiaries.
    Warning: You cannot undo this funds transfer process.
  4. To avoid throttling your system once the transactions are processed, OneKhusa will send batch.payout.success payload containing up to 10 successful transactions or batch.payout.failed payload containing up to 10 failed transactions. This will continue until the last set of transactions are sent to your system.

ā€‹
6-eye Principle

The diagram below illustrates the flow of batch payouts for Initiator + Reviewer + Approver workflow. 6-eye Principle
  1. The first merchant user uploads a batch either using a file (Microsoft Excel or CSV) or JSON payload containing beneficiary transactions.
  2. OneKhusa platform receives the request and responds with 200-OK that the batch is queued for further processing. If you have configured webhooks, your system will receive batch.received or batch.failed payload notification based on the processing outcome.
  3. When the batch is received successfully, the second merchant user marks the batch as reviewed by calling the review batch API endpoint pending for final approval.
  4. After batch reviewal, the third merchant user approves by calling the approve batch API endpoint to start paying out to beneficiaries.
    Warning: You cannot undo this funds transfer process.
  5. To avoid throttling your system once the transactions are processed, OneKhusa will send batch.payout.success payload containing up to 10 successful transactions or batch.payout.failed payload containing up to 10 failed transactions. This will continue until the last set of transactions are sent to your system.