Skip to main content
PGSwift

Batch payout

Send bulk payouts from one CSV file.

Each account number is checked with the bank before anything is sent. Payouts your approval rules hold back wait for an approver, and every row can be followed to completion. For supplier payments, commissions, refunds and payroll.

What you get

Checks before any money moves.

CSV upload

Recipient, bank or e-wallet, account number and amount. Rows with missing or invalid fields are rejected and can be downloaded to fix.

Account name check

Each account number is checked with the bank or e-wallet, and the registered name is compared with the name in your file.

Approval rules

Payouts above your amount threshold, or with a name that does not match, wait for approval in the dashboard or in Telegram.

Proof of transfer

Every completed payout has a full status history and a downloadable PDF proof of transfer.

How an upload runs

  1. Step 1

    Upload the file

    A CSV with one payout per row. Uploading requires a two-factor code, and each row is validated before it is queued.

  2. Step 2

    Review and approve

    Rows that trip your approval rules wait for someone with approval rights. Upload and approve are separate permissions, so different people can hold them.

  3. Step 3

    Follow each payout

    Each row moves to success or failed on its own, with a webhook and a status history. The amount of a failed payout returns to your balance.

Send us a sample payout file

We will walk your team through the upload, name checks and approvals using your own file format.