Verify a CLABE before payout

🇲🇽
Mexico only.

What you'll build

Before paying a real amount, Fintoc sends a 0.01 MXN micro-deposit to the target CLABE. The receipt returns the holder's real name and RFC — so you can compare it against what the user typed. Catches typos, prevents fraud and satisfies compliance requirements.

When to use it

User-entered CLABEs: withdrawals, P2P, vendor onboarding, marketplace seller setup.
Anywhere the cost of paying the wrong account is high.

How it works

1. Your backend POSTs /v2/account_verifications.
2. Fintoc sends 0.01 MXN to the CLABE.
3. Webhook fires: account_verification.succeeded (with holder_name and holder_id).
4. Your backend compares against what the user typed, and blocks the payout if it doesn't match.

sequenceDiagram
    autonumber
    participant You as Your backend
    participant Fintoc
    participant Dest as Destination bank

    You->>Fintoc: POST /v2/account_verifications (JWS)
    Fintoc->>Dest: 0.01 MXN micro-deposit
    Dest-->>Fintoc: Receipt with holder info
    Fintoc->>You: account_verification.succeeded (holder_id, holder_name)
    You->>You: Compare against what your user typed

Implementation checklist

Create the verification. API details and payload: Verify CLABEs (reference).
Compare holder fields. Use fuzzy matching on holder_name (real-world name variants exist). Use holder_id (RFC) as a stricter signal.
Cache the result. Holder info is stable per CLABE. Many teams verify once at onboarding and skip on subsequent payouts to the same account.