Pick your use case
Learn how to configure Fintoc Transfers for the most common business scenarios.
These guides describe the pattern for each common scenario — when to use it, what it looks like, and which reference pages to read. The actual API payloads live in Receive transfers and Send transfers.
| I want to… | Pattern | Best for |
|---|---|---|
| Receive transfers and know who paid, automatically | Payins on dedicated CLABEs | Lending, insurance, SaaS, marketplaces |
| Send money from my Fintoc balance | Payouts to users or suppliers | Loan disbursements, refunds, vendor payments |
| Give every end user their own balance | Wallet for end users | Neobanks, gig platforms, B2B marketplaces |
| Pay a list of 10 – 5,000 people in one go | Payroll or bulk payouts | Monthly payroll, supplier runs |
| Check who owns a CLABE before paying them | Verify a CLABE before payout | User-entered destinations, P2P, onboarding |
A note on Chile
Some reconciliation tooling (dedicated Account Numbers per customer, options.min_amount / max_amount, CLABE verification, inbound transfer returns) is Mexico only. In Chile, inbound transfers land on the Account's single default Account Number and you reconcile by reading counterparty.holder_id and comment.
Each use-case page calls out exactly which steps apply per country.
Updated 20 days ago