Inbound transfers in Mexico
Complete the setup guide first. To receive inbound transfers, follow these steps:- Create an
account_number, a standardized Mexican bank account number (CLABE) used by the Sistema de Pagos Electrónicos Interbancarios (SPEI) rail, with your secret key. - Create a webhook endpoint to handle inbound transfer events.
- Receive a transfer at the account number and get notified by webhook.

Step 1: Create an account number (CLABE)
AnAccountNumber represents a CLABE. You can think of the account number as a reference that you assign to a customer or order to reconcile your incoming payments. Assign one account number per customer, so a transfer to that account number identifies the customer it came from. To learn more about account numbers, see the data model.
Attach arbitrary key-value data to your account number
When you create an account number, attach arbitrary key-value data to themetadata object. Use metadata to store your unique identifier for that account number, such as your internal customer ID. When you receive an inbound transfer, Fintoc attaches the metadata object so you can reconcile the transfer against your internal records.
Example
Using your test secret key and your account ID, create anAccountNumber from your backend, attaching an internal customer ID id_cliente:
Node
Python
Step 2: Create a webhook endpoint to handle inbound transfer events
Whenever you receive an inbound transfer, Fintoc sends atransfer.inbound.succeeded event. Follow the webhook guide to learn how to create a webhook endpoint to receive these events and run actions.
The transfer.inbound.succeeded event looks like this:
Step 3: Receive a transfer at the account number
Now that you have created an account number and added a webhook endpoint to handle notifications, you can transfer to it and start reconciling your payments.Test the integration
Intest mode, use the /v2/simulate/receive-transfer endpoint to simulate an inbound transfer. The behavior is identical to a real transfer sent to the same account number. Pass your test secret key, the account_number_id you created, an amount in the smallest currency unit, and the lowercase ISO 4217 currency code:
Node
Python
Response
transfer.inbound.succeeded event to your webhook endpoint with the payload shown above. Receiving that event confirms your integration is working. For the full set of test values, see Test your integration.
Inbound transfers in Chile
Complete the setup guide first. To receive inbound transfers, follow these steps:- Identify your account and its
root_account_number, the account number that receives the transfer. See the account data model to learn how it is provisioned. - Create a webhook endpoint to handle inbound transfer events.
- Receive a transfer at your account and get notified by webhook.

Step 1: Identify your account
Each Chilean account has aroot_account_number, the account number that receives inbound transfers. This is the account_number that appears in the transfer.inbound.succeeded payload below. See the account data model to learn how it is provisioned.
Step 2: Create a webhook endpoint to handle inbound transfer events
Whenever you receive an inbound transfer, Fintoc sends atransfer.inbound.succeeded event. Follow the webhook guide to learn how to create a webhook endpoint to receive these events and run actions.
The transfer.inbound.succeeded event looks like this:
Step 3: Receive a transfer at your account
Now that you have identified your account and itsroot_account_number and added a webhook endpoint to handle notifications, you can transfer to it and start reconciling your payments.
Test the integration
Intest mode, use the /v2/simulate/receive-transfer endpoint to simulate an inbound transfer. The behavior is identical to a real transfer sent to the same account number. Pass your test secret key, the account_number_id for your account, an amount in the smallest currency unit, and the lowercase ISO 4217 currency code:
Node
Python
Response
transfer.inbound.succeeded event to your webhook endpoint with the payload shown above. Receiving that event confirms your integration is working. For the full set of test values, see Test your integration.