{
"id": "mov_BO381oEATXonG6bj",
"object": "movement",
"amount": 59400,
"post_date": "2020-04-17T00:00:00.000Z",
"description": "Traspaso de:Fintoc SpA",
"transaction_date": "2020-04-16T11:31:12.000Z",
"currency": "CLP",
"reference_id": "123740123",
"type": "transfer",
"pending": false,
"recipient_account": null,
"sender_account": {
"holder_id": "771806538",
"holder_name": "Comercial y Producción SpA",
"number": "1530108000",
"institution": {
"id": "cl_banco_de_chile",
"name": "Banco de Chile",
"country": "cl"
}
},
"comment": "Pago factura 198"
}
| Attribute | Type | Description |
|---|---|---|
id | string | Unique identifier for the Movement |
object | string | Identifier for the type of object. Its value for Movements will always correspond to movement |
amount | integer | Amount of the movement, represented as an integer. This number is positive when money enters the bank account and negative when money leaves the bank account. For example, buying something will be reflected as a movement with a negative amount attribute, while receiving a transfer will be reflected as a movement with a positive amount attribute |
post_date | string | Movement's accounting date, using ISO 8601 |
description | string | Description for the movement, retrieved from the institution |
transaction_date | string | Date and time in which the Movement was made, using ISO 8601. It can be null |
currency | string | Currency ISO code |
reference_id | string | Movement's identifier retrieved from the institution. It can be null.If the Movement is a transfer, it represents the operation number or transaction id. Also, if the transaction idis not given by the bank, sometimes we will use the document number. If the Movement is a check, it represents the document number. |
type | string | Type of movement. Its values can be transfer, check or other |
pending | boolean | If the movement is a check, this field indicates whether confirmation by the bank is pending. If the movement isn't a check, this attribute is false |
recipient_account | object | If the movement is a transfer, this attribute indicates the account to which the transfer was made. It can be null. Take a look at the Transfer Acccount object table below to learn more |
sender_account | object | If the movement is a transfer, this attribute indicates the account that made the transfer. It can be null. Take a look at the Transfer Acccount object table below to learn more |
comment | string | If the movement is a transfer, this attribute indicates the transfer comment. It can be null |
Post date and transaction date
As you probably noticed, each movement includes two different dates: a
post_dateand atransaction_date🧐. This is because the bank uses accounting dates internally. Some bank even create movements in the future. For example, if you make a transaction on a Saturday, this transaction will appear to have Monday as its date. In this example, Saturday corresponds to thetransaction_date, and Monday corresponds to thepost_date.
Pending checks
Checks take some time to be confirmed by the bank. This can take as long as 48 business hours. Pending checks can be reversed for several reasons (for example, lack of funds). Fintoc marks pending checks with the
pendingflag so you know that the movement isn't yet confirmed by the bank.
Transfer Account Object
| Attribute | Type | Description |
|---|---|---|
holder_id | string | Identifier of the owner of the account. In Chile, it corresponds to a RUT |
holder_name | string | Name of the owner of the account |
number | string | Account number. Does not include hyphens nor prefixed zeros. It can be null |
institution | object | Institution to which the account belongs. It can be null |