What is a batch endorsement
A batch endorsement is:- A group of operations — Multiple related transactions bundled together
- Single approval — All operations in the batch are approved together (not individually)
- Reduced quorum — Some organizations allow reduced approval requirements for batches
- Atomic execution — All operations in the batch execute together, or none do
- Daily withdrawals to multiple vendors
- Weekly stablecoin conversions
- Multiple policy adjustments
- Recurring transfers to trusted counterparties
Eligible operations for batching
Not all operations can be batched. Typically eligible:
Check with your administrator which operations your organization allows for batching.
Create a batch endorsement
1
Start first operation
From your vault, select the asset and begin initiating a withdrawal or transfer.
2
Look for batch option
During the operation flow, look for Add to batch, Batch endorsement, or Group operations. Tap it.
3
Create batch
Select Create new batch or Add to existing batch. If new, name it (e.g., “Daily vendor settlements”).
4
Complete first operation details
Enter the destination, amount, and other details for the first operation.
5
Save to batch
Tap Add to batch instead of Submit for approval. The operation is saved but not submitted.
6
Add more operations
Repeat the process for each additional operation you want to batch together.
7
Review batch
Once you’ve added all operations, review the full batch to confirm all details.
8
Submit batch for approval
Tap Submit batch or Request approval. The entire batch is submitted at once.
9
Approve if authorized
If you have approval permissions, complete biometric authentication to approve the full batch.
Operations in a batch must be compatible. You typically cannot mix different types (e.g., withdrawals and policy changes) in a single batch. Check your organization’s batch policies for details.
View pending batches
1
Open activity or operations
Go to the Activity section or Pending approvals.
2
Filter by batch
Look for operations grouped as “Batch endorsement” or with a batch label.
3
View batch details
Tap the batch to see:
- All operations in the batch
- Approval status of the batch
- Who submitted and who must approve
- Expected execution timeline
Approving a batch
1
Locate pending batch
Go to Activity or Pending approvals and find the batch awaiting approval.
2
Review all operations
Expand the batch to see every operation. Verify:
- All destinations are correct
- All amounts are accurate
- No suspicious or unintended operations
3
Approve the batch
If all looks correct, tap Approve batch or Endorse.
4
Biometric authentication
Complete Face ID or Touch ID to authorize approval of the full batch.
5
Operations execute
Once the batch has the required approvals, all operations execute in order.
Rejecting a batch
If you spot an issue with any operation in a batch:1
Locate the batch
Find the pending batch in Activity or Pending approvals.
2
Review the problematic operation
Identify which operation (or operations) is incorrect.
3
Reject the batch
Select Reject batch, Decline, or Refuse approval.
4
Provide reason (optional)
You may be able to add a comment explaining why the batch was rejected.
5
Notify submitter
The person who created the batch will be notified of the rejection and the reason.
Editing a batch before submission
If you haven’t submitted a batch yet, you can edit it:1
Find the pending batch
Go to Pending batches or Draft operations.
2
Select the batch
Tap the batch you want to edit.
3
Edit operations
You can:
- Modify amounts or destinations in operations
- Remove operations from the batch
- Add new operations
4
Resubmit when ready
Once edits are complete, tap Submit batch to send it for approval.
Once a batch is submitted for approval, individual operations cannot be edited. If you need to change something, the batch must be rejected and resubmitted.
Batch execution
Once a batch has all required approvals:- Operations execute in order — Porto executes each operation sequentially
- All succeed or all fail — If one operation fails, the entire batch may fail (depends on your setup)
- Activity log records all — Each operation appears in Activity with batch timestamp
- Blockchain confirmation — On-chain operations confirm at normal speeds
Batching best practices
- Group related operations — Batch withdrawals to the same type of recipient (vendors, exchanges, etc.)
- Reasonable batch size — Don’t batch hundreds of operations at once — keep batches to 5-20 operations
- Clear naming — Name batches so approvers understand their purpose (“Tuesday vendor payments,” “Monthly stablecoin rebalancing”)
- Regular timing — Create batches on predictable schedules if they’re recurring (daily, weekly, monthly)
- Verify before submission — Review amounts and destinations carefully before submitting; rejection and resubmission is inconvenient
- Document the batch — Add notes explaining why operations are being batched together
Batch approval policies
Your organization may have policies around batch approvals:- Batch approval thresholds — Maximum total amount per batch
- Reduced quorum — Batches might require fewer approvers than individual operations
- Frequency limits — How often batches can be submitted
- Recipient restrictions — Batches to trusted destinations may have different rules than new addresses
Troubleshooting batches
Batch won’t submit:- Ensure all operations are compatible
- Check that you have permission to batch these operation types
- Verify the total batch amount isn’t exceeding organization limits
- Check the rejection reason from the approver
- Fix the problematic operation(s)
- Resubmit after making corrections
- Check Activity log to see which operation failed and why
- Resubmit just that operation individually, or fix and resubmit the batch