Payouts: Banks & PSPs

When to use payouts

• Custody wallets — move balances to cold/warm storage.
• Liquidity wallets — fund hot wallets that service end-user withdrawals.
• Bank accounts — off-ramp via SEPA/SWIFT to cover operating expenses or settlements.
• Partners / PSPs / money services — allocate funds to third-party providers or corridors.

Execution model

• Manual by design. Every payout requires review and approval before execution.

• Policy thresholds. Configure who approves and which amounts require approval.

• Validation. Destination checks are enforced:

  • On-chain: address format/network validation; reject on mismatch.
  • Banking/PSP: corridor and beneficiary details must be complete and valid.

How payouts work (at a glance)

Create payout request → Pending review → Approval → Execute → Reconcile

1. Create request in the dashboard (or API, if enabled).
2. Select destination (custody, liquidity, bank, PSP).
3. Approval according to your policy and thresholds.
4. Execution once approved.
5. Reconciliation: record on-chain tx (if any), corridor reference, timestamps, amounts, and approver details.

Timelines (typical)

• SEPA (EUR): T+1 business day.
• SWIFT (USD/others): T+2 business days.
• PSPs / money services: often instant or same-day; corridor-dependent.
• On-chain Withdrawals Instant

Relation to withdrawals

• Withdrawals = the general mechanism for moving funds out of a wallet (can be automatic or manual).
• Payouts = a subset of manual withdrawals with treasury intent (custody, liquidity, bank/PSP off-ramp). Keeping payouts separate from customer-facing withdrawals improves clarity and control.

Compliance notes

• 3PAY provides the infrastructure and controls; you define approval thresholds and destination policies consistent with your licensing and risk program.
• Apply sanctions/AML screening to outbound movements and retain evidence of checks.
• Enforce restricted-jurisdiction rules across corridors and beneficiaries.