Keys and EMV cryptography
Card key derivation, CVV and PVV generation, and EMV cryptogram validation at authorisation time — every operation executed inside FIPS 140-2 Level 3 certified payment HSMs, with keys segregated per issuer.
EMV cryptography
M-EMVThe chip’s cryptographic primitives, executed inside certified payment HSMs. Available on its own.
ARQC and ARPC
Chip application cryptogram validation and issuer response generation at authorisation time.
PIN and PIN translation
PIN validation with PVV, static and dynamic CVV, and native PIN translation for fleet scenarios (card in the vehicle, driver’s PIN) and corporate expense (one card, many employees).
Data Preparation
Automated assembly and delivery of personalisation files to the bureau chosen by the issuer, with keys protected by KEK end to end. Direct integration, with no manual handling of sensitive material.
Multi-product cards
Multiple payment products on the same physical card — benefits, fleet, corporate — each with its own AID, PAN, profile and keys, and per-product block and unblock after issuance.
Dynamic CVV
Virtual cards with a code that renews on every use or expires in minutes, for online purchases.
Validation
Validated in real production: cards personalised by the platform transacted with approval on market capture terminals, in the real acquirer authorisation flow.
Where this connects
Technical material →Issuer stack
UNCHANGEDCard core and customer records
Accounts, limits, billing and records stay with the issuer.
Processor / switch
The issuer’s own system keeps authorising the transaction.
Risk & fraud
Fraud tooling stays. We supply the primitive, not the risk decision.
Personalisation bureau
Physical cards keep being produced by the issuer’s bureau.
Portals and channels
The issuer’s app, portal and support are untouched.
Legacy databases
No database migration is required to start.