QFD can integrate either via REST or SOAP API real time calls to the system of record in order to search for retain useful transaction information.
Please note: QFD only supports looking up a list of transactions by the unique account id typically along with a date range.
In order for QFD to display search results, and to retain other needed transaction information, we will need as many of the following data points as possible to be made available from the API response:
Field | Required? | Comment |
|---|---|---|
Acquirer Reference Number | Yes | This value will be needed to improve automation capabilities when interacting with the associations (Visa and MC) and their APIs. |
Card Number | Yes | This value must be the full card PAN unmasked, and is needed to improve automation capabilities when interacting with the associations (Visa and MC) and their APIs. |
Credit/Debit Indicator | Yes | We need an indication for whether the transaction is a debit or credit against the account. |
Date Posted | Yes | The date the transaction was posted into the system of record. |
Description | Yes | A description of the transaction that was transacted. |
Posted Amount | Yes | The amount that was transacted. |
Transaction Date | Yes | The date the transaction occurred, should be before or same day as posted date. |
Transaction ID | Yes | This value must be a unique identifier for a specific transaction. This value should not occur on any other transactions for the same account number, or any other account numbers. |
Transaction Code*** | Yes | |
Transaction Type | Yes | |
Authorization Amount | No | If the transaction is pending, this is the amount of the transaction that was transacted. |
Authorization Code | No | |
Mail Telephone Indicator | No | |
Merchant Category Code | No | |
POS Entry Mode | No | |
Sequence Number | No | |
Trace Number | No | |
Retrieval Reference Number | No | This can be used in place of the ARN if needed. |
Teller ID | No | |
Teller Name | No | |
Acquirer Network | No |
*** Please provide a list of all the transaction codes in the system of record and which of the below QFD transaction types they should map to.
QFD supported transaction types:
Transaction Type | Description | Additional Comment(s) |
|---|---|---|
ACH | An electronic fund transfer made between Financial Institutions across the Automated Clearing House network | |
ATMDEP | A cash or check deposit made at an ATM | |
ATMWD | A withdrawal made at an ATM | |
BalanceTransfer | The transferring of some funds from one creditor to another. | |
BillPay | An online electronic fund transfer to a service provider | |
CardPinless | A card transaction initiated without the PIN being entered | |
CardPinned | A card transaction initiated with the PIN being entered | |
Check | A written, dated, and signed draft that directs a bank to pay a specific sum of money to the bearer from a checking or savings account | |
ConvenienceCheck | A written, dated, and signed draft that directs a bank to pay a specific sum of money to the bearer from a Credit Card account. | |
Fee | A charge applied to an account, that may or may not relate to a transaction, for various circumstances like account overdraft, balance transfer, late payment, etc. | Please provide examples of how the fee description will appear from the API (ex: “Overdraft Fee XYZ”, “Foreign Transaction Fee XYZ”) |
P2P | A peer-to-peer fund transfer between two parties with separate bank accounts, mediated by a third-party website or mobile app | |
RTP | A Real-Time Payment processed over the NACHA network used to send money electronically between banks in the United States. | |
Wire | An electronic transfer of funds via a network that is administered by banks and transfer service agencies around the world. | |
Zelle | A P2P transfer completed over the Zelle digital payments network. |