Skip to main content
POST
Simulate receiving a transfer

Autorizaciones

Authorization
string
header
requerido

Cuerpo

application/json
account_number_id
string
requerido

Account number that receives the simulated transfer.

Ejemplo:

"acno_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

amount
integer
requerido

Amount to receive, in the smallest currency unit. For MXN this is centavos; CLP has no minor unit. The minimum is 1.

Ejemplo:

1500

currency
enum<string>
requerido

Currency of the transfer. One of CLP, MXN.

Opciones disponibles:
CLP,
MXN
Ejemplo:

"CLP"

comment
string

Comment to attach to the simulated transfer.

Ejemplo:

"Test deposit"

reference_id
string

Numeric reference shown in the counterparty statement in Mexico. Up to 7 digits.

Ejemplo:

"1234567"

counterparty_account_number
string

Account number of the simulated sender. In Mexico, Fintoc derives the sender's account type and institution from this value. Use a standardized Mexican bank account number (CLABE), debit card number, mobile phone number, or a Chilean bank account number; defaults to a Fintoc test counterparty when omitted.

Ejemplo:

"646180111800000004"

counterparty_account_type
string

Type of the simulated sender account, used in Chile. One of checking_account, sight_account, or savings_account.

Ejemplo:

"checking_account"

counterparty_institution_id
string

Identifier of the simulated sender's financial institution, used in Chile. Use a bank public ID such as cl_banco_santander. In Mexico, Fintoc ignores this value and derives the institution from counterparty_account_number.

Ejemplo:

"cl_banco_santander"

counterparty_holder_id
string

Tax ID of the simulated sender. Use a Chilean tax ID (RUT) in Chile, or a Mexican tax ID (RFC) in Mexico.

Ejemplo:

"11.111.111-1"

counterparty_holder_name
string

Name of the simulated sender account holder.

Ejemplo:

"Test Customer 1"

Respuesta

The simulated inbound transfer.

A movement of money between one of your accounts and a counterparty. A transfer is outbound when you send money to a counterparty, or inbound when money arrives in one of your account numbers. Fintoc settles transfers over local payment rails in Chile and Mexico.

id
string
requerido

Unique identifier of the transfer.

Ejemplo:

"tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

object
any
requerido

Type of the object. Always transfer.

account_number
object
requerido
amount
integer
requerido

Amount of the transfer, in the smallest currency unit. For MXN this is centavos; CLP has no minor unit.

Ejemplo:

50000

comment
string | null
requerido

Comment shown to the counterparty, or null.

Ejemplo:

"Payout March"

counterparty
object
requerido

Details of the counterparty of the transfer.

currency
enum<string>
requerido

Currency of the transfer. One of CLP, MXN.

Opciones disponibles:
CLP,
MXN
Ejemplo:

"MXN"

direction
enum<string>
requerido

Whether the transfer is inbound or outbound.

Opciones disponibles:
inbound,
outbound
Ejemplo:

"outbound"

entity
object
requerido

Entity that owns the account involved in the transfer. For an inbound transfer this is the entity that received the money; for an outbound transfer, the entity that sent it.

metadata
object
requerido

Set of key-value pairs attached to the transfer.

Ejemplo:
error_reason
enum<string> | null
requerido

Reason code for a failed transfer, or null. This field is available for Chilean transfers only. One of recipient_account_disabled_for_tef, recipient_institution_timeout, recipient_institution_unavailable, invalid_recipient_account, recipient_account_closed, invalid_recipient_holder_id, invalid_holder_id_account_relationship, account_type_not_enabled, recipient_account_not_found, product_account_not_enabled, recipient_account_credit_restricted, recipient_institution_amount_limit_exceeded, system_amount_limit_exceeded, and unknown.

Opciones disponibles:
recipient_account_disabled_for_tef,
recipient_institution_timeout,
recipient_institution_unavailable,
invalid_recipient_account,
recipient_account_closed,
invalid_recipient_holder_id,
invalid_holder_id_account_relationship,
account_type_not_enabled,
recipient_account_not_found,
product_account_not_enabled,
recipient_account_credit_restricted,
recipient_institution_amount_limit_exceeded,
system_amount_limit_exceeded,
unknown,
null
Ejemplo:

null

mode
enum<string>
requerido

Whether the transfer is live or test data.

Opciones disponibles:
live,
test
Ejemplo:

"test"

post_date
string<date-time> | null
requerido

Time the transfer was posted, as an ISO 8601 datetime in UTC, or null.

Ejemplo:

null

receipt_url
string | null
requerido

URL of the transfer receipt, or null.

Ejemplo:

null

reject_reason
enum<string> | null
requerido

Reason code for a rejected transfer, or null. This field is available for Chilean transfers only. One of recipient_account_closed, recipient_account_credit_restricted, and unknown.

Opciones disponibles:
recipient_account_closed,
recipient_account_credit_restricted,
unknown,
null
Ejemplo:

null

reference_id
string | null
requerido

Numeric reference shown in the counterparty statement in Mexico, or null.

Ejemplo:

null

return_reason
string | null
requerido

Reason code when the transfer was returned, or null.

Ejemplo:

null

reversed_at
string<date-time> | null
requerido

Time the transfer was reversed, as an ISO 8601 datetime in UTC, or null. This field is available for Chilean transfers only.

Ejemplo:

null

failed_at
string<date-time> | null
requerido

Time the transfer failed, as an ISO 8601 datetime in UTC, or null. This field is available for Chilean transfers only.

Ejemplo:

null

rejected_at
string<date-time> | null
requerido

Time the transfer was rejected, as an ISO 8601 datetime in UTC, or null. This field is available for Chilean transfers only.

Ejemplo:

null

status
enum<string>
requerido

Lifecycle status of the transfer. One of pending (being processed), succeeded (settled), partially_succeeded (only part of the amount settled), rejected (rejected before settling), failed (could not be processed), returned (settled, then returned to the sender), return_pending (a return is in progress), reject_failed (the rejection could not be completed), reverse_pending (a reversal is in progress), or reversed (settled, then reversed). A Chilean transfer can move from succeeded to reverse_pending and then reversed when a payment network issue requires a reversal. partially_succeeded, reverse_pending, and reversed occur for Chilean transfers only.

Opciones disponibles:
pending,
succeeded,
failed,
returned,
return_pending,
rejected,
reject_failed,
partially_succeeded,
reverse_pending,
reversed
Ejemplo:

"succeeded"

tracking_key
string | null
requerido

Interbank tracking key (clave de rastreo) of the transfer, or null.

Ejemplo:

null

transaction_date
string<date-time> | null
requerido

Time the transfer occurred, as an ISO 8601 datetime in UTC, or null.

Ejemplo:

"2026-03-01T12:00:00.000Z"