A gift card aggregator is a company that gathers gift card and game code catalogues from many issuers and suppliers into one commercial contract and one API. A platform signs a single agreement and gets catalogue data, ordering and code delivery for hundreds of brands through one integration, instead of negotiating with each brand separately.
Nearly every page ranking for this term was written by an aggregator selling its own API, so the definitions drift towards product copy. This is the neutral version: what the role covers, how it differs from the roles next to it, and what the API model looks like from the buying side.
The four roles in gift card commerce
Four roles recur in this market, and the labels overlap because many companies play two of them at once. The reliable way to tell them apart is to ask who they contract with, what they hold, and where their income comes from.
| Role | Contracts with | What they hold | How they earn |
|---|---|---|---|
| Issuer | Nobody upstream; it creates the product | The redemption liability behind every code it sells | Sells its own goods and services when the card is redeemed |
| Aggregator | Issuers and distributors on the supply side, platforms on the demand side | Contracts and connectivity, often little or no stock | Per-order fees, or a small spread on each product |
| Distributor | Issuers or aggregators | Stock, or the right to draw codes on demand | The spread between trade price and selling price |
| Reseller | Distributors or aggregators | Inventory briefly, plus the end-customer relationship | The gap between trade price and retail price |
The issuer is the only party that owes anyone anything at redemption; everyone downstream trades access to that promise. An aggregator’s product is connectivity: it does the contracting, compliance and integration work once, then rents the result out many times over.
The line between an aggregator and a distributor is blurry in practice, and plenty of firms are both. A workable buyer’s test: a distributor takes commercial responsibility for stock and replacements, while a pure aggregator passes your order through to whoever holds the product. Ask who answers when a code fails to redeem, and you will find out which one you are dealing with.
How a catalogue API works
Most catalogue APIs reduce to three moving parts.
- Catalogue. An endpoint listing products with denominations, currencies, regions and availability, each carrying a face value and a trade price. The gap between those two prices is where everyone downstream earns, and it moves, so buyers sync the catalogue on a schedule rather than caching it once.
- Order. Your system posts a purchase request, normally with an idempotency key, so a request that times out and gets retried cannot buy the same code twice.
- Delivery. The code comes back in the API response or arrives moments later through a webhook, and your storefront passes it to the customer.
That is the whole mechanism. The engineering around it, sandbox testing, price sync, secure code storage, daily reconciliation, is where integrations succeed or fail; our gift card API integration guide walks through it end to end.
Why platforms sign one contract instead of dozens
Each direct brand relationship carries fixed overhead: a commercial negotiation, a compliance review, an integration where the brand offers an API at all, and ongoing account management. At five brands that is tolerable. At fifty it is a department.
An aggregator collapses the overhead to one instance of each: one onboarding, one API, one invoice, one settlement flow. Volume pools as well, since orders across the whole catalogue count towards a single commercial relationship. That suits businesses whose volume is real but spread thin across many brands, which describes most storefronts.
The price of convenience is the extra layer. Every intermediary earns something, so a platform doing heavy volume in one brand will get sharper terms by going direct for that brand and keeping the aggregator for the long tail. Mature storefronts often run exactly that hybrid.
Frequently asked questions
What does a gift card aggregator do?
It signs supply agreements with issuers and distributors, connects their catalogues into one API, and sells that access to platforms, storefronts and rewards programmes. Day to day it handles product data, pricing updates, order routing, code delivery and settlement, so its clients integrate once instead of once per brand.
What is the difference between an aggregator and a distributor?
An aggregator concentrates on connectivity: many catalogues, one feed, often without holding stock. A distributor holds commercial relationships and stock, and takes responsibility for delivery and replacements. Many companies do both, so ask a practical question instead of a taxonomic one: who is contractually liable when a delivered code does not redeem?
How many brands does a typical catalogue cover?
Hundreds is the norm for an established aggregator, spread across gaming, entertainment, shopping and telecom brands, with coverage varying by region. The gaming slice alone usually runs to dozens of brands, each with multiple denominations, currencies and regional variants, which is why a catalogue can list thousands of individual products.
How do gift card aggregators make money?
Mostly through per-order fees or a small spread on each product: the aggregator buys access at one set of terms and resells it at slightly narrower ones. Its real asset is the contracting, compliance and integration work done once and rented out many times, so income scales with order flow across the whole client base rather than with stock held. Pure aggregators often hold little or no inventory at all.
When should a platform go direct to a brand instead of using an aggregator?
When volume in one brand is heavy enough to justify its own contract. A direct agreement beats aggregator terms on that single brand, at the price of separate onboarding, compliance and integration. Mature storefronts often run a hybrid: direct deals for the two or three brands that dominate their volume, and the aggregator for the long tail, where breadth matters more than the last fraction of discount.