Batch transfers

Available only in the Fintoc Dashboard.

​

Overview

This guide explains how to create and track up to 5,000 transfers from a single CSV file. Use batch transfers for payroll, supplier payouts, or client disbursements.

​

Key benefits

Batch transfers let you:

• Upload up to 5,000 transfers in one file.
• Validate data automatically.
• Review batches before executing them.
• Require multi-factor authentication (MFA) before funds move.
• Track progress and outcomes for each batch and transfer.

---

​

How it works

​

1. Create a batch transfer

1. Go to Transfers → Batch Transfers in your Fintoc Dashboard and click Create.
2. Add a description, such as Pagos de octubre.
3. Download the country-specific template:
   • 🇨🇱 Template Chile (CLP)
   • 🇲🇽 Template Mexico (MXN)

​

2. Fill out the template

Each row represents one transfer.

⚠️ In Chile, Fintoc automatically splits rows over 7,000,000 CLP into multiple transfers. Each resulting transfer is independent.

​

3. Upload your file

Upload the completed template:

• Save and upload the template as a CSV file.
• Review any validation messages from the dashboard.

If you see an error, correct the file and upload it again. The dashboard displays warnings, such as duplicate rows, but the warnings do not block the upload.

​

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.

After you confirm the batch, it appears under Pending Authorizations.

​

5. Authorize the batch

1. Go to the Authorizations tab and select your batch to open its details.
2. Review the batch one last time.
3. Choose an action. You cannot undo either action:
   • ✅ Authorize (requires MFA)
   • ❌ Reject

​

6. Track execution

Once fully authorized:

• The batch moves to in_progress.
• Each transfer appears in your Transfers view as pending, then succeeded or failed.
• If some transfers fail because of an insufficient balance, the batch ends as partially_succeeded.
• Batches expire automatically after 2 weeks if not authorized.

​

Batch statuses

The following statuses describe the batch lifecycle: