Cosmo: The Foundational Infrastructure for Loyalty Ecosystems
Where banks, fintechs and consumer loyalty programs meet, the infrastructure between them decides what is possible. Most of that infrastructure is still built one partnership at a time: a custom integration, a custom contract and a custom reconciliation for each airline or hotel a bank wants to work with. This article describes a different model, a neutral base layer underneath the loyalty stack, and explains how Cosmo plays that role.
What does the loyalty stack look like today?
Loyalty programs began in travel. Airlines and hotels used miles and points to influence where customers flew and stayed, and banks followed by letting cardholders earn those currencies on everyday spend. That made bank cards a major source of new miles for many programs, and made travel currencies one of the most valuable rewards a bank can offer.
The stack that grew up around this has three layers. At the top sits the customer experience: the app, the card, the redemption flow. In the middle sit the loyalty programs themselves, each with its own ledger, rules and API. At the bottom sits whatever moves value between them, and that bottom layer is where the problems live.
Because every program exposes a different interface, a bank integrates with each one separately. Each integration has its own endpoints, authentication, data formats and failure modes. Each partnership has its own contract and its own invoice. Reconciliation means matching issuance records across currencies, exchange rates and program-specific rules, partner by partner. Development cost and operational load grow with every program added, which is why most institutions add very few.
What is a base layer in loyalty infrastructure?
A base layer is a shared, neutral platform that sits beneath all the programs and all the issuers and handles the work they would otherwise each repeat. It does three things:
- Normalises the many program APIs into one interface, so an issuer integrates once.
- Routes and validates each transaction: checks the member, applies the agreed ratio, credits the right program and confirms the result.
- Clears and settles what moved, producing one reconciled position across every partnership on a fixed cycle.
The defining property of a base layer is that it has no opinion about the product built on top. Point exchange, co-branded cards, multi-program earning and embedded rewards all run on the same rails. Payment networks work the same way: they move value between any bank and any merchant without prescribing what is sold.
How does Cosmo work as the base layer?
Cosmo is a loyalty network for banks, fintechs and card issuers. It sits between the issuers of rewards and the programs that accept them, and provides the three layers every partnership needs: the partner contracts, the integration and the settlement.
Technically, an issuer integrates with one REST API. The same call issues into any program on the network; only the program identifier changes. Every transaction carries a reference number, so a retried request is never processed twice, and webhooks report outcomes back to the issuer in real time. A sandbox mirrors production so that the full flow can be tested before go-live. The developer guide documents each step.
Commercially, the issuer signs one agreement that covers the programs on the network, and can keep a direct agreement with any partner where one already exists. Markups are disclosed to both the issuer and the program, and there are no setup or management fees.
Financially, Cosmo acts as the clearing house. Transactions are processed in real time, and one monthly settlement produces a single invoice covering every partner, currency and jurisdiction, in place of a separate reconciliation per partnership.
What does a transaction look like from start to finish?
A cardholder in a bank's app chooses to move 10,000 points into an airline program. The bank calls the Cosmo API with the member's program number, the amount and a reference. Cosmo validates the member with the airline, applies the conversion ratio the bank has agreed with that airline, instructs the airline to credit the miles, and returns a confirmation. The bank debits its own points ledger. At month end the transaction appears on one statement alongside every other transfer the bank made that month, to every partner, netted into a single amount owed.
Nothing in that flow is specific to the airline. Swap in a hotel group or a retailer and the bank's code does not change.
What are the benefits in practice?
- For banks and fintechs: faster time to market for point exchange, co-branded cards and multi-program earning; fewer contracts to manage; one monthly statement instead of many.
- For loyalty programs: distribution to financial institutions through one integration instead of a separate build per bank, with standardized terms and one counterparty for settlement.
- For members: more places to earn and more ways to redeem, because adding a partner no longer takes a quarter.
The base layer also travels beyond travel. As banks extend rewards into retail, telecoms and fintech apps, the same rails carry those partnerships, because the layer never depended on what the program sells.
Why neutrality matters
A base layer only works if every program on it can trust it. Cosmo does not run a loyalty program, does not own members or points, and does not sell to the issuer's customers. It does not compete with the platforms that run a program; it works alongside them. That neutrality is what lets competing airlines, hotel groups and banks share one piece of infrastructure without handing any of them an advantage. The About page sets out those boundaries in full.
Summary
The loyalty industry still builds its plumbing one partnership at a time, and that is the main reason rewards catalogues stay narrow. A neutral base layer that normalises program APIs, routes and validates transactions, and clears and settles across every partner removes that constraint. Cosmo provides that layer for banks, fintechs and card issuers, so new partnerships become a setting rather than a project.
Read the full guide to loyalty program infrastructure for banks.