Available in Mexico and ChileYou can create batch transfers from the Fintoc Dashboard or with the API. You always authorize them from the Dashboard.In Chile, organizations on a legacy Security setup can create batch transfers from the Dashboard in
live mode only.Overview
This page explains how to create, authorize, and track up to 5,000 transfers using one Dashboard file or one API request. Use batch transfers for payroll, supplier payouts, or daily client disbursements.Key benefits
Batch transfers provide these controls:- Upload up to 5,000 transfers in one file.
- Validate data automatically.
- Review batches before executing them.
- Require multifactor authentication before funds move.
- Track the progress and outcome of each batch or transfer.
How it works
1. Create a batch transfer
- Go to Transfers → Batch Transfers in your Fintoc Dashboard and select Create.
- Assign a description, for example
Pagos de octubre. - Download the template for your country:
2. Fill out the template
Each row represents one transfer. The columns depend on your organization’s country.Mexico
Use these fields for each transfer row:Chile
Use these fields for each transfer row:
For example, a Chile file with one transfer looks like this:
Chile batch file
3. Upload your file
When you upload the file:- Fintoc supports CSV files.
- Fintoc checks the file format and columns as soon as you upload it.
4. Review and confirm
Before creating your batch:- Review the total number of transfers and total transfer amount.
- If needed, go back and upload a new file.
5. Authorize the batch
- Go to the Authorizations tab and select your batch to open its details.
- Review the batch one last time.
- Select one of these irreversible actions:
- ✅ Authorize (requires multifactor authentication)
- ❌ Reject
6. Execution and tracking
Fintoc processes and tracks batches as follows:- The batch moves to
in_progressafter full authorization. - Each transfer appears individually in your Transfers view as
pending, thensucceededorfailed. - If some transfers fail, for example because of insufficient balance, the batch ends as
partially_succeeded. - Batches expire automatically after two weeks if they remain unauthorized.
Create a batch with the API
Instead of uploading a file, send the transfers of a batch in one request to Create a transfer batch. The request needs a JSON Web Signature (JWS) in theFintoc-JWS-Signature header, as it does for a single transfer. See Generate JWS keys.
The batch starts in pending_authorization. Authorize it from the Dashboard as described in Authorize the batch. A batch you create in test mode waits for you to authorize it from the Dashboard in test mode.
Track the batch with these tools:
- Webhooks: Receive a
transfer_batch.*event each time the batch changes status. See Types of events. - Batch status: Call Get a transfer batch or List transfer batches.
- Transfers of the batch: Call List transfers with the
transfer_batch_idquery parameter.
Test the integration
Confirm that the batch reachessucceeded or partially_succeeded. If any transfers appear as failed in your Transfers view, check the failure reason before retrying the transfers.