Fintoc's Transfers API lets you receive bank transfers from your customers in real time and send bank transfers to any account — all programmatically, with webhooks for every state change. This page walks through the five most common ways companies use Transfers, what each one is best for, how the money flows, and how to set it up.

If you're just getting started, read the Transfers overview and the Quickstart first. If you already know the basics and want to pick the right pattern for your product, keep reading.

📘
Availability by country
Most of the inbound tooling (Account Numbers / CLABEs, verify CLABE, return transfer) is Mexico only. In Chile, inbound transfers land directly on your Account's root_account_number and you reconcile using the transfer's comment and counterparty. See the full capability matrix in the Transfers overview.

Choose the right use cases

Use case	What it does	Best for
Collect payments with dedicated CLABEs	Assign a unique CLABE (or reference) per customer or order to auto-reconcile every inbound transfer.	Lending, insurance, SaaS, marketplaces, any recurring billing.
Send payouts to users or suppliers	Move money from your Fintoc balance to any third-party bank account in real time.	Lending disbursements, marketplace seller payouts, refunds, supplier payments.
Run a wallet or sub-balances for end users	Give each end user a virtual account with its own balance, CLABE, and movements.	Neobanks, fintech apps, marketplaces that hold user balances.
Run payroll or bulk payouts	Upload up to 5,000 transfers in one CSV, authorize with MFA, and track per-row execution.	Payroll, monthly supplier runs, commission payouts.
Verify a CLABE before paying out	Send a 0.01 MXN micro-deposit to confirm the holder name of an account before trusting it.	Any flow where the counterparty enters their own CLABE (P2P, withdrawals, marketplaces).