Issuer processing
The real-time engine that authorises, clears and settles card transactions on the issuing side - the system that says yes or no to every payment.
When a card is tapped, the scheme routes the authorisation to the issuer's processor, which checks balance, limits and fraud signals and answers in milliseconds. Modern issuer processors expose this pipeline via APIs and webhooks so programmes can build custom logic.
The processor sees the entire transaction stream - which is why processor jurisdiction and hosting matter as much as the licence. A European processor with EEA hosting keeps that data under GDPR even though the scheme is American.
Primary source: Regulation (EU) 2015/751 (Interchange Fee Regulation) · EMVCo - EMV Payment Tokenisation
In the verified data
- 52 live issuer processors: 28 are EU-core firms and 24 keep data inside the EEA.
- 29 sell processing as software only; 22 also hold a banking, e-money or payment licence of their own.
- 9 are US-controlled (Fiserv, Galileo, Global Payments Europe, Highnote, i2c and 4 more): the processor sees every authorisation, so whoever controls the processor controls the transaction stream.
Recomputed from the catalogue and the official EBA, ESMA and FCA registers on every build — how we verify.
Questions to ask a provider
- Which schemes are you certified with, and what authorisation uptime do you commit to contractually?
- Can I run my own authorisation logic in real time, and what latency budget do I get?
- Where is transaction data processed and stored, and what are the exit terms if I change processor?