Skip to content

Architecture

Qbank Connect integrates API technologies with legacy batch systems, resulting in a "hybrid" architecture.

1. The mETL Engine

In QBank systems, all large data exchanges are handled by the mETL Engine, a legacy batch ETL system. It performs nightly scheduled data syncs between the bank's internal databases and the Fiserv CoreAdvance core banking system. 1 2 3 Due to this technical constraint, certain API endpoint DBs get refreshed only once a day.

2. Hybrid Data Flow (API to Core)

This diagram illustrates the hybrid data flow between third-party Transaction Management Platforms (“Platforms”), QBank Connect, the mETL Engine, and Fiserv.

graph TD
A[Platform]-->|"Real-Time: GET /balances, POST /transfers"|B["QBank Connect API Gateway"]
A-->|"Asynchronous: POST /payments/ach"|B
B-->C{"QBank<br>Connect Service<br>& POS"}
C-->|"Immediate Write"|D["QBank Connect DB"]
D-->|"Polls every 15 min"| E["mETL Engine"]
E-->|"Extract & Transform - Fiserv Format"|F["Data Processing"]
F-->|"Fiserv Batch Processing - CoreAdvance"|G["Fiserv CoreAdvance Core"]
G-->|"Nightly EOD File - End of Day"|F
F-->|"mETL EOD Job - 1:00 am"|E
E-->|"Load - Daily Sync"|D
D-->|"GET /transactions, /accounts"|C

3. Data Latency

The hybrid approach used by this application results in all API requests being categorized into one of two main types of latency:

Category Example Endpoints Source Description
Real-Time Synchronous /balances , /transfers , /payments/wire A direct call to the Fiserv API Less than 1 second. 56
Batch-Latent Asynchronous /accounts , /transactions , /reports/nsf , /reports/chargebacks metL import from Fiserv loader Data is current as of the previous business day. 7

4. The Three Required Transaction Dates

For both reconciliation and treasury reporting purposes, there are three different date fields contained in the Transaction resource. To meet cash position requirements and other regulatory needs, all platform developers should be aware of the background for each date field. 4

Field Name Purpose Source
transaction_date Initiated: The date and time when the customer/ERP initiated the transaction. The client's core system/request
value_date Interest/Funds: The date upon which funds are actually credited/debited to compute interest accrual. 4 Fiserv CoreAdvance
posting_date Available/Posted: The date and time the transaction record was inserted into the QBank Connect DB through the mETL engine and made available through the API. 89 Fiserv CoreAdvance

5. Documents Cited

  1. Fiserv CoreAdvance SFTP Specification, "Batch Communication Protocol." ↩

  2. QBank mETL Engine Design Document, "Asynchronous Data Integration." ↩

  3. QBank Connect SLA, "API Latency and Data Freshness Profiles." ↩

  4. QBank Whitepaper, "Transaction Date Standards and Compliance," v1.1. ↩↩

  5. QBank Performance Testing Report, "Real-Time Endpoint Benchmarks." ↩

  6. Fiserv CoreAdvance API Integration Guide, "Direct Connect Latency." ↩

  7. QBank mETL Operational Handbook, "Daily Sync and EOD Cutoff." ↩

  8. QBank Connect Integration Guide, "Transaction Query Best Practices." ↩

  9. QBank Accounting Compliance Memo, "Posting Date Audit Requirement." ↩