When I joined my current employer to manage the acquiring switch, I knew payments. What I didn't know was how differently a gift card network behaves compared to traditional card payments. The nuances — the multiple parties, the routing logic, the latency pressure — took months to fully grasp. This article is what I wish I'd had on day one.
What Is an Acquiring Switch?
A payment switch is the routing layer that sits between a merchant (or acquirer) and the issuer of a payment instrument. In the gift card world, the switch receives a transaction request — a purchase, a balance enquiry, or a redemption — and routes it to the right issuer system in milliseconds.
At my current employer, our acquiring switch connects thousands of acquirers (point-of-sale systems, e-commerce platforms, kiosks) to hundreds of issuer brands (retailers, restaurants, entertainment companies). Every time someone buys or redeems a gift card anywhere in APAC, Europe, or the US, there's a good chance that transaction flows through our switch.
The Key Players — And What They Each Want
Understanding who's who is critical before you can manage any payment product. The gift card ecosystem has four core parties:
- The Acquirer: The merchant or platform where the transaction happens. A supermarket POS, an e-commerce checkout, a corporate gifting portal. They want fast, reliable responses and simple integration.
- The Switch (us): We sit in the middle. Our job is to authenticate, route, log, and respond to every transaction — without becoming the bottleneck.
- The Issuer: The brand whose gift card is being purchased or redeemed. They hold the value on their platform. They want accurate, secure transaction processing and reliable settlement data.
- The Cardholder: The end consumer. They want the transaction to just work — instantly, every time.
PM insight: Every decision you make about the switch affects all four parties differently. A change that makes integration easier for acquirers might add latency that issuers notice. Always map your decisions against all stakeholder layers.
How a Gift Card Transaction Actually Flows
Why Latency Is a Product Problem, Not Just an Engineering Problem
At millions of transactions per day, a even a small latency spike at the switch level translates to real money and real customer experience degradation. Retail POS systems often have a hard timeout — if the switch doesn't respond within a tight timeout window, the transaction is declined by default. That's a failed sale, a frustrated customer, and a support call.
As a PM, I own the latency budget — the contractual and experiential ceiling for response times. My job is to understand what each component in the chain contributes to that budget, and make trade-off decisions when a new feature might affect it.
For example: when we added enhanced fraud detection middleware, it added ~40ms per transaction. That was within our budget, but only because I'd audited the existing chain and knew we had headroom. Without that audit, we'd have shipped something that inadvertently caused timeout failures under load.
Partner Onboarding: The Hidden Complexity
Every new acquirer or issuer who connects to our switch needs to be onboarded. This isn't just a technical integration — it's a multi-step process involving legal agreements, security certifications, test environment validation, and production cutover.
Key things I've learned about onboarding at scale:
- Standardise the integration specification early. We built a self-service integration guide that reduced back-and-forth significantly and halved the time to first successful test transaction.
- Sandbox matters more than you think. A robust, production-like sandbox environment means partners can debug independently without blocking your engineering team.
- Certification is a quality gate, not a formality. Every partner goes through a mandatory test suite before production. This has caught misconfigured error handling, wrong currency codes, and security gaps that would have caused live incidents.
Settlement, Reconciliation, and Why Finance Will Test Your Patience
The transaction doesn't end when the authorisation completes. Every gift card transaction needs to settle — the actual movement of funds between acquirers and issuers — and reconcile, matching the switch's records against each party's own ledger.
Settlement files need to go out on schedule, in the right format, for each issuer (many of whom have different requirements). A missed settlement file creates a cascade: the issuer's finance team raises a query, our ops team investigates, and trust in the platform takes a hit.
As PM, I prioritised the settlement module as a tier-one reliability requirement. Downtime in the transaction flow is bad. Downtime in settlement is a financial compliance issue.
What Makes a Good Gift Card Switch PM
After two and a half years managing this platform, here's what I think the role actually requires:
- Systems thinking: You're managing an interconnected network. Every change has downstream effects on multiple parties.
- Latency literacy: Understand your p50, p95, and p99 response times and what they mean for the customer experience.
- Regulatory awareness: Gift card regulations vary by country. What's legal in the US isn't necessarily compliant in the EU or APAC.
- Commercial sensitivity: Partner relationships are also revenue relationships. Technical decisions affect commercial outcomes.
The gift card acquiring space is unglamorous compared to consumer fintech, but it's incredibly complex and consequential. Every millisecond matters. Every integration is a relationship. And the switch is where it all comes together.
