Customer 360 — Banking ETL Pipeline
A banking integration capstone combining relational customer data with ATM and credit-card files using Informatica Cloud Data Integration.
A question. A process.
Work you can explore.
Follow the decisions behind the implementation, then inspect the original work.
Chapter 1 of 4 · The question
The question behind the build.
Customer information and transaction records arrive from separate systems. Invalid identifiers and account conditions need explicit routing before creating a consolidated customer view.
Follow the implementation.
- 01
Join Oracle banking entities with ATM and credit-card flat-file inputs.
- 02
Normalize customer names and enforce a documented exception matrix.
- 03
Quarantine non-conforming records with descriptive rejection reasons.
- 04
Aggregate customer-level spending and use an upsert delivery pattern.
See the work. Inspect the details.
The mapping and exception documentation make the difference between ingestion and trustworthy integration visible. Review the routing rules and customer-grain output.
Enlarge preview Choose where to look deeper.
Search the linked source inventory or narrow it to the kind of artifact you want to inspect. Files open at their original source.
The source
keeps moving.
Source updated
A production-grade multi-source ETL pipeline that consolidates banking, ATM, and credit card data into a single Customer 360 golden record, enforcing a strict three-rule exception matrix to quarantine non-conforming records before they reach the data warehouse.
Current README excerpt
Informatica Cloud Data Integration (IICS) | Oracle → Data Warehouse
A source excerpt, not an independently verified outcome.