> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synclear.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Payment Flows: Batch, Scheduled, and Auditable Disbursements
> Execute stablecoin payroll, vendor payments, and inter-entity transfers with multi-sig approval flows, on-chain receipts, and exportable audit history.
Synclear's payment flows module provides on-chain businesses with a structured, auditable mechanism for all disbursement types — from monthly payroll runs in stablecoins to one-off vendor settlements and recurring inter-entity transfers. Payments are assembled into batches, routed through your configured multi-signature approval policy, and executed on-chain as a single atomic transaction. Every batch produces an on-chain receipt with a permanent transaction hash, and the full payment history is exportable for accounting and compliance purposes.
Payment flows eliminate the operational risk of manually assembling individual on-chain transfers: human error in address entry, missed approvals, and missing payment records are all addressed by the structured batch and approval workflow.
## Supported Assets
| Asset | Network | Notes |
| ----- | --------------------------------- | -------------------------------------------------- |
| USDC | Ethereum, Base, Arbitrum, Polygon | Primary stablecoin for payroll and vendor payments |
| USDT | Ethereum, Arbitrum, Polygon | Supported for counterparties requiring USDT |
| DAI | Ethereum | Supported for DAI-denominated obligations |
Cross-network payments (e.g., disbursing from an Ethereum treasury wallet to a Base recipient) are not supported in a single batch. Each batch operates within a single network.
## Payment Types
A batch payment groups multiple individual transfers into a single on-chain transaction. The most common use case is payroll: a CSV of recipient addresses and amounts is uploaded, reviewed, approved, and executed in one atomic transaction. All recipients in the batch receive funds in the same block, ensuring no partial disbursements if the transaction reverts.
Recurring payments are configured with a recipient, amount, asset, and cadence (weekly, bi-weekly, monthly). The Synclear payment scheduler triggers a new batch at each recurrence. Recurring batches follow the same approval flow as manual batches — the scheduled trigger initiates approval, but execution requires authorization from configured signers before the disbursement window closes.
For businesses with multiple Synclear-verified entities (e.g., a holding company and an operating subsidiary), inter-entity transfers can be executed within the platform. Both entities must be verified on Synclear. The transfer is recorded on both entities' payment histories, producing a matched audit record useful for intercompany accounting.
## Approval Workflows
Every payment batch requires approval before execution. The approval configuration is inherited from the treasury policy of the source wallet.
* **Single-signer wallets (EOA)**: The wallet owner reviews and approves the batch from the dashboard. Approval signs the batch transaction; execution is immediate.
* **Multisig wallets (Safe)**: The batch is queued as a Safe transaction. Each configured signer receives an approval request in the dashboard. Execution proceeds once the configured threshold of signatures is collected. Signers can also reject a batch, which cancels it and returns it to draft state.
* **Time-locked wallets**: Batches above the configured size threshold enter a mandatory delay period after approval. Execution occurs automatically after the time lock expires unless a signer cancels during the window.
Approved batches that are not executed within the execution window (default: 24 hours after final approval) expire and must be re-submitted. This prevents stale approvals from executing after treasury conditions have changed. Configure the execution window under **Treasury → Policies**.
## On-Chain Receipts and Audit Trail
Every executed batch produces:
* **On-chain transaction hash**: the Ethereum (or L2) transaction that executed the batch, verifiable on any block explorer.
* **Synclear batch receipt**: a structured record including batch ID, source wallet, recipient list, amounts, asset, network, execution timestamp, and approving signers. Available in the dashboard under **Payments → History**.
* **Line-item receipt per recipient**: individual payment confirmations downloadable as PDF or JSON, suitable for sending to payees or attaching to vendor invoices.
The full payment history for your entity is available in the dashboard with filtering by date range, wallet, asset, and payment type. Exports include the on-chain transaction hash for every line item.
## Creating a Payment Batch
Go to **Operate → Payments → New Batch**. Select the source wallet (from your connected treasury wallets) and the network. The dashboard displays the available balance for the selected asset on that wallet before you proceed.
Add recipients individually (address + amount) or upload a CSV file. The CSV format requires two columns: `recipient_address` and `amount`. Amounts are entered in token units (e.g., `5000` for 5,000 USDC). The dashboard validates all addresses and flags any that are not checksum-valid or that match Synclear's sanctions screening list before you proceed.
```csv theme={null}
recipient_address,amount
0xRecipient1...,5000
0xRecipient2...,3250.50
0xRecipient3...,7500
```
Choose the disbursement asset (USDC, USDT, or DAI). The dashboard calculates the total batch amount, the estimated gas fee, and the net balance remaining in the source wallet after execution. Confirm that the source wallet holds sufficient balance to cover both the payment total and the gas fee.
Assign a label to the batch (e.g., "November 2025 Payroll" or "Vendor Settlement – Q4"). The label is stored in Synclear's payment records and appears in exports. An optional on-chain memo field (32 bytes) can be included in the transaction calldata for counterparties who index memos.
Submit the batch. For single-signer wallets, review the batch summary and approve directly. For multisig wallets, the batch is queued for signer review. Each signer receives a dashboard notification. The batch status moves to **Pending Approval** and cannot be edited until the approval process resolves.
Once the required approval threshold is met, the batch status changes to **Ready for Execution**. For non-time-locked wallets, execution proceeds automatically. For time-locked batches, execution triggers automatically after the lock expires unless cancelled. You can also initiate manual execution from the dashboard immediately after approval if the time lock allows.
After execution confirms on-chain, navigate to **Payments → History** to find the completed batch. Download the batch receipt (PDF or JSON) and individual payee receipts as needed. The on-chain transaction hash is displayed on the batch record for independent verification.
## Exporting Payment History
Navigate to **Payments → History → Export**. Select the date range, wallet(s), asset(s), and payment type. Export formats:
* **CSV**: Flat file with one row per payment line item, including transaction hash, batch ID, recipient, amount, asset, network, and timestamp. Suitable for import into accounting software.
* **JSON**: Structured export with nested batch and recipient data. Includes signer addresses and approval timestamps for audit purposes.
* **PDF Report**: Human-readable summary of all batches in the selected period, formatted for board or auditor reporting.
Payment history is retained indefinitely within Synclear's indexed records. On-chain data is, by definition, permanently accessible. If you need to verify a historical payment not shown in the dashboard, the on-chain transaction hash from any prior export can be used to retrieve the full record from the relevant block explorer.