Who Paymentology is
Paymentology is an issuer processor that began in the UK, where in 2014 it built what it describes as one of the first cloud-native processing platforms in Europe, and merged in 2021 with Tutuka, a processor from South Africa. In 2026 it raised new investment co-led by Apis Partners and Aspirity Partners.
Its platform runs debit, credit, prepaid, virtual and crypto or stablecoin card programmes for clients in many countries, with BIN sponsors from its partner network. That reach, and an interface that lets the programme decide each authorisation itself, is why it is one of the issuer processors our card issuing module connects to.
What it does in your platform
Card issuing
Processes your cards and, in active mode, sends each authorisation to the module, so the answer comes from your ledger, the customer's limits and your fraud rules. In the crypto card app, that is the moment the customer's stablecoin balance is converted to the card currency, through the FX module.
How the connection works
The card issuing module manages cards through Paymentology's API and answers its FAST messages, card transactions in the ISO 8583 format carried as JSON. Notifications that need no answer arrive by remote messaging.
A card is issued
When a customer passes KYC, the module issues the card on your Paymentology programme: virtual at once, physical to follow.
Into the wallet
From your app, the customer adds the card to Apple Pay or Google Pay, with push provisioning through MeaWallet's SDK.
Paymentology asks
When the customer pays, the authorisation reaches Paymentology over the network, and FAST passes it to the module for a decision.
The module decides
It checks the ledger, the limits and your rules and answers. If no answer comes in time, stand-in applies: a decline, or your own approval rules with enhanced stand-in.
Settlement follows
Settlement comes over FAST, card status and token events by remote messaging, and the module posts each one to the ledger.
Next to other processors
Paymentology is one of several issuer processors in the card issuing module. The card screens, the controls and the ledger belong to the module, so customers see the same app whichever processor runs their card.
Paymentology brings BIN sponsors from its partner network. Moving a programme to another processor later is a migration you plan with your sponsor and the network, but your apps stay the same and past transactions stay in your ledger.
When Paymentology fits best
A strong fit when
- You launch cards in several regions and want one processor across them.
- You run a crypto card and want a processor that supports stablecoin card programmes.
- You want to choose between deciding every authorisation yourself and letting the processor decide.
Also worth a look
- A processor that is also your BIN sponsor, if you want one contract for both.
- A processor you already have a contract with: it becomes a connector too.
How we get you live
The contract
We help you get your Paymentology account and contract in place, with a BIN sponsor from its network for your markets.
The card programme
We set up the programme with you: card types and designs, active or passive FAST, stand-in rules, limits and controls, and wallet provisioning.
The keys
Paymentology's API keys go into your platform's secrets and nowhere else, and your apps never see them.
A full test run
The whole flow runs in Paymentology's UAT environment, where its card test simulator plays network traffic, authorisations included, before your first real card.
