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:Create a batch endorsement
Start first operation
Look for batch option
Create batch

Creating a new batch
Complete first operation details
Save to batch
Add more operations

Batch operations screen
Review batch
Submit batch for approval

Batch submission screen
Approve if authorized

Batch approval confirmation
View pending batches
Open activity or operations
Filter by batch
View batch details
- All operations in the batch
- Approval status of the batch
- Who submitted and who must approve
- Expected execution timeline
Approving a batch
Locate pending batch
Review all operations
- All destinations are correct
- All amounts are accurate
- No suspicious or unintended operations
Approve the batch
Biometric authentication
Operations execute
Rejecting a batch
If you spot an issue with any operation in a batch:Locate the batch
Review the problematic operation
Reject the batch
Provide reason (optional)
Notify submitter
Editing a batch before submission
If you haven’t submitted a batch yet, you can edit it:Find the pending batch
Select the batch
Edit operations
- Modify amounts or destinations in operations
- Remove operations from the batch
- Add new operations
Resubmit when ready
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