Summary #
Card networks solved one of the hardest problems in commerce: moving money between people, banks and merchants who do not know each other. For moving money, the issuer-acquirer model is the right architecture, and this paper does not argue otherwise.
Organisations now distribute value that is not simply money, through parties that are not banks. A health fund issues care. An employer issues wellness benefits. A brand sponsors experiences. The organisations that accept this value are clinics, spas, car washes and schools, and many of them issue value of their own.
This paper introduces the issuceptor: an entity, whether an organisation or an individual, that holds both capabilities on one network. It can issue value and it can accept value, and each programme decides which role it plays. The paper sets out how an issuceptor network differs from a card network, where each is the better fit, and how Tiports PromoCore runs one in production today.
It builds on Research 01, Digital Value, which defines the value object this network carries.
The issuer-acquirer architecture #
A card payment involves five parties. The issuing bank gives a customer a card and stands behind their spending. The cardholder presents the card. The merchant accepts it. The acquiring bank signs up the merchant and receives the payment for them. The card network connects issuers and acquirers, routes each authorisation and runs clearing and settlement between them.
Figure 1. The issuer-acquirer model. Roles are fixed by institution type: banks issue, merchants accept.
The flow is well known: the cardholder pays, the acquirer sends the request through the network, the issuer approves or declines, and the network clears the transaction so the issuer pays the acquirer and the acquirer pays the merchant.
The model works because it solves trust at global scale. A merchant in Lagos can accept a card issued in London without either party knowing the other. Acceptance is near universal, settlement is guaranteed by rules every member signs, and fraud controls sit at every step. Card programmes can also restrict spending, usually by merchant category, which is how fleet, benefit and health-account cards work.
For moving money between strangers, the issuer-acquirer model is hard to improve on.
Where the abstraction stops fitting #
The model assumes the value is money, the issuer is a bank, and acceptance is a commercial contract between a merchant and its bank. Many value programmes break all three assumptions.
| Programme | Who issues | What is issued | Who accepts |
|---|---|---|---|
| Healthcare | Health fund | Consultations and treatment value | Approved clinics, labs, pharmacies |
| Employee benefits | Employer | Wellness and transport value | Named gyms, spas, transport operators |
| Humanitarian | NGO | Food and essentials value | Verified local traders |
| Sponsorship | Brand | Sponsored experiences | Participating restaurants and venues |
| Education | Institution | Meals, access, exam entitlement | Campus services and partners |
In each case the issuer is not a bank and does not want to become one. The value may be a consultation or an admission rather than an amount. The issuer wants to approve specific organisations, not every merchant in a category. And the organisations taking part change roles: a clinic that accepts a fund's healthcare value may want to issue its own wellness credit next month.
Card rails can carry the money inside these programmes. They were not designed to represent the programme itself.
The issuceptor #
The capability is the point, not constant use of both roles. Most entities will issue in some programmes and accept in others. What matters is that they are onboarded once, hold one identity and one settlement relationship, and can take either role without a new integration.
- A clinic issues a wellness credit to its patients, and accepts a health fund's treatment value.
- A spa issues gift experiences, and accepts an employer's wellness benefit.
- A car wash issues vehicle-care credits to its customers, and accepts credits sponsored by employers, brands or partner businesses.
- A school issues meal and exam entitlements to students, and accepts a sponsor's scholarship value.
- A creator issues community credits to followers for events and merchandise, and accepts a brand's sponsored credits.
An issuceptor is not defined by what it sells. It is defined by what it is authorised to do with value on the network.
In the card model these organisations would sit on one side only. As merchants, they accept. To issue anything, they would need a bank, a programme manager and a separate system.
Isn't this just a merchant? #
No, and the difference is worth stating precisely, because two familiar things look similar and are not.
| What it does | Issuceptor? | |
|---|---|---|
| Merchant | Accepts payment or value issued by others | No: accepts only |
| Closed-loop gift card or store credit | Issues value that only it accepts | No: issues and accepts, but only its own |
| Issuceptor | Issues value that other organisations accept under its rules, and accepts value others issue | Yes |
The closed loop is the important distinction. A shop that sells its own gift cards and takes them at its tills is doing both jobs, but inside one organisation. That is the model Research 01 argues against. An issuceptor's value leaves its walls, and other organisations' value comes in, on the same network and under each issuer's rules.
Card networks and issuceptor networks compared #
| Dimension | Issuer-acquirer card network | Issuceptor network on PromoCore |
|---|---|---|
| Who issues | Licensed banks, and fintechs through sponsor banks | Organisations authorised on the network, of any type |
| Who accepts | Merchants with an acquiring relationship | Organisations each issuer approves |
| Roles | Fixed by institution type | Set per programme; one organisation can hold both |
| Unit of value | Money | Issuer-defined units, monetary or not |
| Restrictions | Available, usually by merchant category | Named acceptors, identity, time, place and limits |
| Credential | Card or tokenised card | QR, NFC, wearable, code, web link or API |
| Settlement | Clearing and net settlement between member banks | Per transaction over licensed payment service providers |
| Reach | Near-universal acceptance | Acceptors approved within each programme |
The last row matters. A card works almost everywhere; an issuceptor network works where its participants have joined. That is the trade: card networks optimise for reach, issuceptor networks for control over purpose and participation. They are different tools, and a programme may use both, with card and payment-provider rails carrying the money that settles issuceptor value.
The issuceptor network #
In an issuceptor network the organisations sit around a shared value layer rather than on two sides of a bank relationship.
Figure 2. An issuceptor network. Each organisation joins once; each programme decides whether it issues, accepts or both.
Participation is controlled. An organisation joins the network once, but it can only accept a given issuer's value if that issuer has approved it. Being on the network is not the same as being able to accept everything on it.
Network effects can run in both directions. In a three-party model, each new acceptor adds places to use value. In an issuceptor network, each new organisation is also a potential issuer, bringing its own customers, patients, staff or members. Every participant can add supply of value and demand for it.
Why Digital Value makes it possible #
The issuceptor model needs value that is not tied to the system that created it, which is the subject of Research 01. Four properties from that paper do the work:
- Issuer-defined units. A clinic's consultation credit and a brand's experience credit can live on the same network because PromoCore does not force every value into one currency.
- Acceptor lists on the value. Each value object carries the organisations allowed to accept it, so approval is set by the issuer, value by value.
- Separation of concerns. Identity, credential, channel and settlement are separate, so an organisation's role can change without its integration changing.
- Access connected to settlement. Every accepted value creates a recorded obligation that the network resolves, so acceptors know they will be paid.
Settlement in an issuceptor network #
When value is accessed at an acceptor, the issuer owes the acceptor. PromoCore records that obligation and settles it per transaction, under one of two models described in Research 01.
Model A, prefunded. The issuer prefunds the programme into a Tiports settlement account with a licensed payment service provider. When value is accessed, PromoCore records the obligation and disburses to the acceptor through that provider.
Model B, configurable settlement. PromoCore's orchestration is built on payment-provider APIs, so funds can instead stay in the issuer's own account until value is accessed. PromoCore then instructs settlement to the acceptor.
PromoCore does not currently net obligations between organisations. Multilateral netting, where an issuceptor's amounts owed and owed to it are offset before settlement, is a future direction for networks where organisations regularly hold both roles.
In production #
The issuceptor model runs today through Pandley Limited, a consumer and programme brand built on PromoCore.
- Pandley as issuer. Pandley issues its own credits to consumers. Partner organisations across cinema, dining, spa, events and leisure accept them.
- Pandley as acceptor. At Pandley Shop, Pandley accepts credits at checkout, including sponsored credits funded by third-party sponsors.
- Partners across roles. Organisations can issue value that other partners accept, for example a clinic issuing a credit that a spa and a car wash accept.
Each organisation is onboarded to PromoCore once. Whether it issues, accepts or does both is configured per programme.
Governance: the questions every issuceptor network must answer #
Letting organisations both issue and accept raises questions that a card network answers with bank regulation and scheme rules. An issuceptor network has to answer them explicitly.
| Question | How PromoCore answers it |
|---|---|
| Who may accept an issuer's value? | Only organisations that issuer approves, value by value |
| Who defines the rules? | The issuer: acceptors, limits, validity, channels, identity binding |
| Who funds the value? | The issuer, or a sponsor on the issuer's behalf |
| Who owes whom? | The issuer owes the acceptor when value is accessed; PromoCore records the obligation |
| Who settles? | PromoCore, through licensed payment service providers, under Model A or B |
| What happens at expiry? | Value lapses at the end of its validity, as the issuer configured |
| Who can stop value? | The issuer can suspend or retire value it issued |
One question needs particular care as networks grow: what happens to outstanding value and unsettled obligations when an organisation leaves. The principle is simple, that obligations are settled before exit and holders are protected. Each programme's terms must make it concrete.
Conclusion #
The issuer-acquirer model organised the world's payments around one question: which bank stands behind the payer, and which bank stands behind the payee. That question fits money.
Programmable value asks different questions: who created this value, what is it for, and which organisations are allowed to accept it. Answering them needs a network organised around organisations, not banks, in which any participant can issue, accept, or both.
Different value systems need different network abstractions. The issuceptor model provides one for programmable Digital Value.
Glossary #
| Term | Meaning |
|---|---|
| Acceptor | An organisation where value can be used |
| Card network | Infrastructure connecting issuing and acquiring banks for card payments |
| Closed loop | Value that only its issuer accepts |
| Issuceptor | An entity, organisation or individual, that can both issue and accept value on one network, with its role set per programme |
| Issuer | The organisation that creates and funds value and sets its rules |
| Model A | Settlement from issuer prefunds held in a Tiports settlement account with a licensed payment service provider |
| Model B | Settlement instructed by PromoCore from the issuer's own payment-provider account |
Cite and share #
Mekwuye, S. (2026). Beyond Issuer-Acquirer: The Issuceptor Model for Digital Value Networks. PromoCore Research 02, version 1.0. Tiports Limited. https://promocore.tiports.com/research/issuceptor
Start with Research 01, Digital Value, which defines the value this network carries.
About this paper
This paper sets out Tiports' thesis on value networks. Section 9 describes capabilities in production. Examples elsewhere illustrate how the model applies and are not claims that each is deployed. Netting is described as a future direction.
The description of card networks is a general summary of the issuer-acquirer model for comparison. Visa and Mastercard are trademarks of their respective owners. Tiports is not affiliated with or endorsed by any card network.
Tiports Limited (RC 7772829) builds and operates PromoCore. Pandley Limited (RC 7210243) is a separate company that operates programmes on PromoCore.
This edition replaces the earlier note "Visa Issuer-Acquirer Model vs Tiports PromoCore Issuceptor Model".
© 2026 Tiports Limited. This paper may be shared and redistributed in unmodified form with attribution. All other rights reserved.