If you run a business with POS terminals - a retail chain, a string of agent locations, a payments business with terminals in the field, you know the evening ritual. Transactions came in all day. Now you need to know which ones actually settled, which are still pending, and whether the money that hit your account matches what your terminals reported.
This guide does that. We'll build an automated settlement monitor using the ) purchases are not currently covered by Transaction Search. If you're verifying IPG web checkout payments, that's a different flow. Transaction Search is built for transactions that flow through the switch: POS, ATM, cash withdrawal, transfers.
What We're Building
A settlement monitor that does three things:
Authenticates against Interswitch Passport for an access token
Searches each terminal's transactions for a given day
Pulls full settlement details for each transaction and flags anything not yet settled
By the end you'll have a function you can drop into a cron job that runs every evening and emails you a settlement report.
Step 1 - Setup Your Project
Get your credentials first:
Create an account on the . Build that into your notFound handling rather than letting it break the run.
Wrapping Up
We took three API calls: authenticate, search by terminal, get settlement details, and turned them into an automated settlement monitor for a POS business.
The key isn't any single call. It's the insight that transaction status and settlement status are different questions, and that the gap between them is exactly what reconciliation is about.
Resources:
Running POS terminals and building reconciliation tooling? Join our community on Slack and share what you're building.
↗ Original-Artikel auf dev.to lesenVollständiger Original-BerichtAusführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
SOCIAL SHARE CARD GENERATOR