Skip to main content
Mexico only.

​
What you’ll build

Before sending a payout, Fintoc sends a 0.01 MXN micro-deposit to the target standardized Mexican bank account number (CLABE). The receipt returns the holder’s name and Mexican tax ID (RFC). You can compare these values with the information your user entered. This check helps you catch typos and evaluate the destination holder against your compliance rules.

​
When to use it

Use this verification in these flows:
  • Withdrawals to a user-entered CLABE.
  • Peer-to-peer transfers to a user-entered CLABE.
  • Vendor onboarding and marketplace seller setup.
  • Any payout where a misdirected transfer is hard to reverse, such as a vendor settlement or a one-time withdrawal.

​
How it works

The verification runs in five steps and uses a JSON Web Signature (JWS):

​
Implementation checklist

  1. Create the verification. See Verify CLABEs for the API details and request body.
  2. Compare holder fields. Use fuzzy matching on holder_name to account for name variants. Use holder_id (RFC) as a stricter signal.
  3. Cache the result. Holder information is stable for each CLABE. You can verify the CLABE during onboarding and reuse the result for subsequent payouts to the same account.

​
Test the integration

In test mode, verify a published test CLABE and confirm that the webhook includes the holder fields:
  • Use your test secret key (sk_test_...) and the test CLABE 000000000000000000.
  • Expect an account_verification object in pending status on the initial response, with holder_name and holder_id still null.
  • Expect an account_verification.succeeded webhook with populated holder_name and holder_id fields in counterparty. See Verify CLABEs for the full payload. See Test your integration for the available test CLABEs.