Transactions in the QI Account
In the context of prepaid cards, debit or credit situations have an impact on the cardholder's QI Account. These transactions are represented by the Balance Transaction entity. These transactions must obligatorily be executed on the cardholder's QI Account, even if late. Therefore, if a debit cannot be carried out for some reason, the Balance Transaction will remain pending and will be automatically retained by the QI system until the entire amount is debited.
It is important to monitor these transactions and if any Balance Transaction remains pending, the customer must contact the cardholder to ensure that the QI Account is ready and with the necessary balance to cover this pending issue.
Whenever a Balance Transaction is created, a Balance Transaction Event webhook will be sent.
Transaction Event Webhook in Account IQ
{
"key": "cccbd9e9-863f-44b5-aa05-f6afa555bb74",
"date": {
"balance_transaction_key": "cccbd9e9-863f-44b5-aa05-f6afa555bb74",
"transaction_key": "b64c1ca5-095d-4005-a4ed-3be09d7b111f",
"amount": 25.32,
"transacted_at": "2023-07-24T12:00:00.000Z",
"balance_transaction_status": "transacted"
},
"webhook_type": "prepaid_card.balance_transaction_event",
"event_datetime": "2023-07-24T12:00:00.000Z"
}
Details
| Field | Type | Description |
|---|---|---|
balance_transaction_key | string | Authorization Request Unique Identifier |
transaction_key | string | Entity unique identifier Authorization related to this request |
amount | string | The amount transacted on the QI Account in this event |
transacted_at | string | The time the transaction was executed |
balance_transaction_status | string | The state of the Balance Transaction after this event |
The balance_transaction_status describes whether the transaction was executed on the cardholder's QI Account, which may be pending (pending_transaction_execution), partially transacted (partially_transacted) or transacted (transacted)
Os webhooks da QI Tech não devem ser mapeadas de forma restrita. Campos adicionais podem ser incluídos aos payloads dos webhooks retornados em nossas APIs.
A consulta e reenvio de webhooks pode ser feito conforme documentação: Reenvio de webhooks