Journal · 28 May 2026
Match keys across wallet and card rails
Wallet authorization IDs and card retrieval references rarely share a neat foreign key. Teams invent composite keys, then discover partial captures break them. That is where transaction reconciliation audits for fintech get uncomfortable.
Prefer layered keys
Start with exact merchant order IDs when both rails carry them. Fall back to amount + timestamp window + last-four only with a tolerance policy written down — otherwise analysts “match” by hope.
Document false-positive risk
Every fuzzy rule needs a known failure mode. If two customers can share an amount within the same minute, say so in the control description. Auditors prefer honesty to a 99% match rate that hides collisions.
Lab habit
In our synthetic day files we plant collisions on purpose. Learners who only chase match rate miss them; learners who read the key design notes catch them before Module 2 closes.