Education Demo

Debit Card Transaction Processing ETL Flow

Explore how authorization pings, memo records, and merchant data blend into a single enriched transaction event. This guided sandbox walks through the exact data joins, enrichments, and latency metrics modern banking teams rely on.

Authorization → Memo Joining Merchant Enrichment Latency Metrics

What you'll learn

  • • The schema that ties authorization IDs to memo settlements.
  • • How merchant attributes unlock customer-friendly receipts.
  • • Efficiency KPIs: latency windows, enrichment coverage, and throughput.
  • • What the API payload and mobile UI look like before and after enrichment.
Jump to the customer view ↓

Authorization Feed

--

Immediate approve / decline signals that kick off the pipeline.

Memo Transactions

--

Settlement records that land minutes or hours after the auth swipe.

Merchant Directory

--

Logos, contact info, and NAICS categories that enrich the final event.

Lifecycle Timeline

Each transaction walks through three checkpoints. Hover the timeline cards to inspect timestamps and latency deltas.

-- enrichment coverage • -- still awaiting merchant match

Raw Feeds & Unified Event

Study how identifiers and timestamps align across the three datasets. The unified event appears once memo settlement is reconciled against its original authorization.

Authorization: transaction fingerprint captured the moment the card is swiped.

Memo: pending ledger entry that confirms amount and settlement info.

Enrichment: merchant intelligence fused into a customer-friendly event.

Authorization Stream

First signal
Transaction ID Account Amount Status Timestamp Raw Description

Memo Settlements

Reconciliation layer
Transaction ID Posting Date Amount Status Memo Timestamp Merchant Ref

Unified Event Objects

Customer-ready
Transaction ID Lifecycle Merchant Auth → Memo Memo → Enriched Status

Efficiency Dashboard

Track the throughput, latency, and enrichment success metrics that ETL leads report back to stakeholders.

Schema v1.0 • Transaction event spec defined below

Average Auth → Memo

--

Measures switch authorization latency.

Average Memo → Enriched

--

How quickly merchant details land after memo.

Processing Throughput

--

Transactions per minute across the observed window.

Total Enriched

--

Merchant-matched events delivered downstream.

Event Schema

  • Core: transaction_id, account_number_masked, amount, currency, lifecycle_status
  • Auth: auth_status, auth_timestamp, pos_entry_mode, network_reference_id
  • Memo: memo_status, memo_timestamp, posting_date, settlement_channel
  • Merchant: merchant_name, category, logo_url, phone, address, merchant_reference_id
  • Latency: auth_to_memo_ms, memo_to_enriched_ms

Operational Notes

  1. Memo events update the existing authorization record in-place using transaction_id + network_reference_id.
  2. Merchant enrichment uses a resilient lookup that falls back to the raw descriptor when no directory match is found.
  3. Latency metrics are persisted per event and can feed dashboarding tools or alerting thresholds.
  4. API clients receive the newest schema version via the version header (X-Event-Schema: v1.0).

API Playground

Sample response from GET /api/transactions. Use it to prototype downstream experiences or QA field mappings.


            

        


        

            

                

                    
Customer View Comparison

                    
Choose a transaction to compare the raw, unenriched state with the enriched experience your mobile banking app can deliver.

                

                

                    
                    
                

            

            

                

                    

                    Unenriched
                    
--

                    
--

                    

                        

                            Amount
                            --
                        

                        

                            Posted
                            --
                        

                        

                            Contact
                            Not available
                        

                    

                

                

                    

                    Enriched
                    

                        
                        

                            
--

                            
--

                        

                    

                    
--

                    

                        

                            Amount
                            --
                        

                        

                            Status
                            --
                        

                        

                            
--

                            
--

                        

                    

                

            

        


        

            

                
Try this in your workshop

                

                    

                        
Data Practitioners

                        
Duplicate the schema and plug in your own auth + memo feeds to test join logic before production.

                    

                    

                        
Product Managers

                        
Use the customer view comparison to align stakeholders on why enrichment matters.

                    

                    

                        
Engineers

                        
Leverage the API payload sample as a contract for building mock services and integration tests.