Loyalty Program Infrastructure for Banks: A Guide

Every bank card rewards program depends on partnerships: airlines that accept miles, hotel groups that accept points, retailers that accept vouchers. Each partnership has three parts, a contract, a technical integration and a settlement process, and in most banks each part is rebuilt from scratch for every partner. This guide explains what loyalty program infrastructure is, which layers it covers, how a loyalty network changes the economics, and what to check when evaluating a provider.

What is loyalty program infrastructure?

Loyalty program infrastructure is the set of systems and agreements that let one organisation issue, convert or redeem rewards in another organisation's loyalty program. For a bank, that means the plumbing between the card program and the airline, hotel and retail programs its customers want to earn in. It sits below the customer experience, which the bank owns, and above the partner programs, which the partners own.

The infrastructure has three layers that must all be in place before a single point moves:

Commercial layer: the contract that sets the price of a point or mile, who is liable for it, how volumes are reported and how disputes are handled.
Technical layer: the API integration that validates a member, issues or converts the reward, confirms the result and keeps both ledgers in agreement.
Financial layer: the settlement process that reconciles what was issued, nets it against what is owed, and produces an invoice in the right currency and tax regime.

Why do bilateral partnerships stop scaling?

A bank building these layers directly with each partner pays the full cost every time. The second airline is as expensive as the first. Ten partners means ten negotiations, ten integrations and ten monthly reconciliations, and the operational load grows with every program the bank adds. In practice most institutions stop at a handful of partners, and the rewards catalogue stays narrow.

The pattern is familiar from other parts of financial services. Payments once ran on bilateral bank-to-merchant relationships until card networks standardised them. Account access ran on bespoke screen scraping until open banking standardised it. Loyalty is still largely bilateral, which is why the same program integration gets built hundreds of times across the industry.

How does a loyalty network change the model?

A loyalty network puts a neutral party between the issuers of rewards (banks, fintechs, wallets, card issuers) and the programs that accept them (airlines, hotels, retailers). Each side integrates with the network once and reaches everyone else on it. The three layers are provided once and reused:

One contract covers the programs on the network, with the option to keep a direct agreement where one already exists.
One integration issues into any program through the same API call; only the program identifier changes.
One settlement runs on a fixed cycle and produces a single statement across every partnership.

Cosmo is built on this model. Banks, fintechs and card issuers integrate once and issue points and miles into airline, hotel and retail programs such as Miles&Smiles, Privilege Club, AlFursan, ALL Accor and Radisson Rewards. Transactions are processed in real time, and one monthly settlement produces a single invoice covering every partner. The layers are modular: a client can use Cosmo's partner contracts or bring its own, and Cosmo can run settlement for either.

What products run on the same integration?

Once the infrastructure exists, several customer-facing products become configuration rather than new projects:

Point exchange: customers convert bank, wallet or program rewards into airline, hotel and retail programs in real time. The client sets its own conversion ratio, subject to partner approval.
Co-branded cards: a card tied to one loyalty partner, where the issuer keeps its processor and customer relationship and the network supplies the partner contract, issuance and settlement. New co-brands are added on the same integration.
Multibrand: one card that earns across several loyalty programs at once, with each cardholder choosing a single program or a split. Cosmo holds a US patent on this model (US 12,597,048 B2).
Direct reward issuance: issuing points or miles from the bank's own systems for campaigns, service recovery or account milestones, without a card transaction behind it.

What does the integration look like for a developer?

A well-designed loyalty API is small. The Cosmo integration comes down to five steps, four of them API calls, and clients typically complete it in about a week:

Authenticate with OAuth 2.0 client credentials, using a separate secret for sandbox and production.
Retrieve partnerships to list the programs the client is linked to, with the agreed conversion ratio and transfer limits for each.
Validate the member against the partner program before issuing, so a mistyped membership number fails fast.
Issue the reward with a single call that carries a reference number, so a retried request is never processed twice.
Receive webhooks for transaction outcomes, authenticated with Basic, OAuth or signature schemes.

The developer guide walks through each call with request and response examples, including sandbox behaviour and error handling.

How does settlement work on a network?

Settlement is where bilateral partnerships hurt most, because every partner has its own invoice format, currency, tax treatment and payment terms. On a network the cycle is standardised:

Each transaction is recorded at the agreed price at the moment it is issued.
At month end, issuance is aggregated per partner and netted against anything owed in the other direction.
One statement covers every partnership, with the detail available per program in the portal or over the API.
Currency conversion and tax are handled once, centrally, rather than per invoice.

For finance teams this replaces a stack of partner invoices with one position to reconcile. For the partner programs it means they are paid on a predictable schedule by one counterparty, which is part of why programs join a network in the first place.

What should a bank check before choosing a provider?

The questions below separate infrastructure from a redemption catalogue with an API attached:

Modularity: can the bank use its own partner contracts and still use the integration and settlement? Or is it all or nothing?
Transparency: is the markup on each program disclosed to the bank and to the program? Are there setup or management fees?
Ownership: who owns the member relationship and the card? Infrastructure should sit underneath the bank's product, not between the bank and its customers.
Multi-program support: can one card earn in several programs, or is each co-brand a separate build?
Compliance: SOC 2 Type II and ISO/IEC 27001 are the baseline for a vendor that touches customer data. Ask for the report and the data-residency details.
Time to value: how long is the technical integration, and how long does it take to add the second and third partner after the first?

The comparison page applies these questions to Cosmo, Ascenda, Points.com and Currency Alliance, and the trust and security page covers Cosmo's certifications, hosting and data protection.

What do loyalty programs get from a network?

The same infrastructure works in the other direction. An airline or hotel program that wants distribution through banks faces the mirror image of the bank's problem: one contract, one integration and one reconciliation per financial institution. Joining a network gives the program one integration that reaches every issuer on it, standardised commercial terms, and a single monthly settlement from one counterparty instead of a payment run per bank. Programs typically complete onboarding in two to four weeks, after which each new issuer is a commercial decision rather than a technical project.

Frequently asked questions

Is a loyalty network the same as a rewards catalogue?

No. A rewards catalogue is a redemption storefront: the bank buys inventory such as gift cards or hotel nights and shows it to members. A loyalty network moves value between programs. It issues points and miles directly into the partner's ledger, so the member earns in the program they already belong to. Some providers bundle both; the distinction matters when evaluating what is being bought.

Who owns the customer when a bank uses a network?

The bank does. Infrastructure sits beneath the bank's product: the card, the app and the member relationship stay with the issuer, and the network is invisible to the cardholder. Any provider that inserts its own brand or storefront between the bank and its customers is a marketplace, not infrastructure.

How is a loyalty network paid?

Models vary. The questions to ask are whether there are setup fees, management fees or monthly minimums, and whether the markup on each program is disclosed to both the bank and the program. Cosmo charges no setup or management fees and discloses markups to both sides, so the price of a point is known before the first transaction.

How long does it take to add a second partner?

On a bilateral model, roughly as long as the first: a new contract, a new integration, a new reconciliation. On a network, a partner that is already live can be enabled from the portal without a new integration, which turns partner expansion from a quarterly project into an operational setting.

Summary

Loyalty program infrastructure is the contract, integration and settlement behind every rewards partnership. Built bilaterally, it is rebuilt for every partner and caps how many programs a bank can offer. Built once on a network, it turns new partners into a setting. Cosmo provides that network for banks, fintechs and card issuers, with the partner contracts, integration and settlement supplied together or in whichever combination the client needs.