Which fields each institution publishes in transaction.details,
by account type. Generated from the same catalogs the sync writes with,
so this page cannot drift from what the API actually returns.
How to read this
Every field is optional. Which ones appear depends on the movement, not just the institution — a transfer carries counterparty fields that a fee row does not.
Values are verbatim. Formats are whatever the institution reports, and can differ between two keys on the same transaction. Where a format matters it is stated in the description.
Keys are derived from the institution's own labels. Stable in practice, best-effort by contract: if an institution renames a label, its key changes with it.
An institution absent from this page publishes no details yet, and its transactions return details: null.
cl_banco_bci_pyme
Checking accounts
Key
Type
Description
fecha_de_transaccion
date
Date the movement was executed, on incoming payments. Format DD/MM/YYYY.
fecha_de_transferencia
date
Date the transfer was executed, on outgoing transfers. Format DD/MM/YYYY. BCI uses this label instead of "Fecha de transacción" for transfers, so check both keys.
hora_de_transaccion
time
Time of day the movement was executed, bank local time. Format HH:MM.
hora_de_transferencia
time
Time of day the transfer was executed, bank local time. Format HH:MM.
fecha_contable
date
Date the movement posted to the ledger. Format DD/MM/YYYY. This is the date `transactionDate` reflects, and it can differ from the date the movement was executed.
codigo_transaccion
string
BCI's internal reference for the movement.
rut_origen
string
RUT of the sending party, on incoming payments. Personal data.
razon_social
string
Registered name of the sending party. Personal data.
cuenta_origen
string
Account number the funds were sent from. Personal data.
banco_origen
string
Bank the funds were sent from.
numero_operacion
string
Operation number assigned by the originating bank.
tipo_pago
string
Payment scheme behind the movement, e.g. a Transbank card settlement.
nombre_destinatario
string
Name of the receiving party, on outgoing transfers. Personal data.
rut_destinatario
string
RUT of the receiving party. Personal data.
n_de_cuenta_de_destino
string
Account number the funds were sent to. Personal data.
banco_de_destino
string
Bank the funds were sent to.
codigo_transferencia
string
Transfer reference shown on the comprobante.
categoria
string
BCI's own classification of the movement, e.g. Pagos, Transferencias. Independent of the API `category` field.
mnemonico
string
BCI's internal movement-type code, e.g. 4K, 93, 1116. Opaque, but stable for a given kind of movement.
descripcion_movimiento
string
Explanatory text the bank attaches to certain movements, e.g. the terms behind an automatic credit-card payment. Present on a minority of rows.
Credit cards
Key
Type
Description
codigo_de_referencia
string
Card network reference for the purchase.
ciudad
string
Merchant city as reported by the acquirer. Often truncated or blank.
cantidad_de_cuotas
number
Total instalments the purchase was split into. 0 on unbilled purchases, where BCI has not assigned instalments yet.
numero_de_cuota
number
Which instalment this charge represents.
monto_total
number
Full purchase amount. On an instalment purchase this differs from the transaction's `amount`, which carries only the cuota being charged.