Skip to main content
POST
Create a transfer
v2 · Base URL https://api.fintoc.com/v2

Authorizations

Authorization
string
header
required

Headers

Fintoc-JWS-Signature
string
required

JWS signature of the request body. See Generate JWS keys to set up request signing.

Body

application/json
account_id
string
required

Identifier of the account the transfer is sent from.

Example:

"acc_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

amount
integer
required

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

Example:

50000

currency
enum<string>
required

Currency of the transfer. One of CLP, MXN.

Available options:
CLP,
MXN
Example:

"MXN"

counterparty
object
required

Recipient of the transfer.

comment
string

Comment shown to the counterparty.

Example:

"Payout March"

reference_id
string

Numeric reference shown in the counterparty statement in Mexico. Up to 7 digits, with no leading zeros.

Example:

"1234567"

metadata
object

Set of key-value pairs you can attach to the transfer for storing additional structured information.

Example:

Response

The created 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
required

Unique identifier of the transfer.

Example:

"tr_2daFu0zqqDtZGJaSi2TGI2Mm1nN"

object
any
required

Type of the object. Always transfer.

account_number
object
required
amount
integer
required

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

Example:

50000

comment
string | null
required

Comment shown to the counterparty, or null.

Example:

"Payout March"

counterparty
object
required

Details of the counterparty of the transfer.

currency
enum<string>
required

Currency of the transfer. One of CLP, MXN.

Available options:
CLP,
MXN
Example:

"MXN"

direction
enum<string>
required

Whether the transfer is inbound or outbound.

Available options:
inbound,
outbound
Example:

"outbound"

entity
object
required

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
required

Set of key-value pairs attached to the transfer.

Example:
mode
enum<string>
required

Whether the transfer is live or test data.

Available options:
live,
test
Example:

"test"

post_date
string<date-time> | null
required

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

Example:

null

receipt_url
string | null
required

URL of the transfer receipt, or null.

Example:

null

reference_id
string | null
required

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

Example:

null

return_reason
string | null
required

Reason code when the transfer was returned, or null.

Example:

null

status
enum<string>
required

Lifecycle status of the transfer. One of pending (being processed), succeeded (settled), rejected (rejected before settling), failed (could not be processed), returned (settled, then returned to the sender), return_pending (a return is in progress), or reject_failed (the rejection could not be completed).

Available options:
succeeded,
rejected,
failed,
pending,
returned,
return_pending,
reject_failed
Example:

"succeeded"

tracking_key
string | null
required

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

Example:

null

transaction_date
string<date-time> | null
required

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

Example:

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