Bulk Gift Card API for Business — Buy Gift Cards in Bulk at Scale

Buying gift cards in bulk as a business is a different transaction from buying one at a supermarket rack. A consumer buys a card, pays with a personal card, and gets a code. A business needs an invoice in its own currency, a VAT or sales-tax treatment its finance team can defend, a record of who received what, and a supplier that can repeat the whole thing next quarter without a new procurement cycle. That is the difference between a retail purchase and a corporate gift card program, and it is why a gift card API for business exists at all.

What a bulk gift card order actually looks like

1. Open a business account. Every B2B account goes through KYB — legal entity, beneficial owners, signed MSA, sanctions screening. Our brand partners require it before the catalog can be switched on, so it is not optional at any supplier that carries first-party stock.
2. Choose brands and denominations. Nine high-demand brands sit behind the main endpoint, and the full 5,000+ brand catalog is reachable the same way. Most programs settle on two or three brands plus a universal default.
3. Send the recipient list. Either upload a CSV in the dashboard or POST the same payload to the API. Each row carries a recipient, a country, a brand, and an amount.
4. Delivery happens automatically. Each recipient gets their code or top-up, region-matched to their country. Failures surface immediately rather than silently.
5. Reconcile from one invoice. One MSA, one monthly invoice in your base currency, one audit trail — instead of per-brand reseller paperwork and per-region tax documents.

Buying in bulk without writing any code

The no-code path is a form. You upload a CSV of recipients in the dashboard, click Send, and the same delivery pipeline, the same volume tier, and the same audit log apply as they would for an API order — the dashboard calls the API under the hood. Teams routinely start on CSV uploads, prove the program internally, and only wire up the REST endpoint once the sends become recurring enough that a human should not be doing them. Neither route is a downgrade: the discount tier is earned on volume, not on which surface you ordered from.

Who buys gift cards in bulk, and what for

• HR and people ops — service anniversaries, spot recognition, referral bonuses, onboarding gifts. See the procurement buyer’s guide to bulk gift cards for employees.
• Finance and procurement — a single supplier and a single invoice line in place of dozens of expensed retail purchases, with cost-center rollups in the analytics dashboard.
• Marketing and sales — research incentives, webinar rewards, channel-partner spiffs, customer win-backs.
• Support and CX — goodwill gestures and service-recovery credits that are faster to issue than a refund.

Tax treatment is part of the buying decision

Gift cards given to employees are taxable in most jurisdictions, and the thresholds differ sharply by country — which is exactly the detail that derails a rollout after the cards have already gone out. Before you size a program, check the rules where your people actually are: Germany, Canada, Australia, and Poland each treat the same card differently.

Brand-by-brand bulk buying guides

If you already know which brand you need, these walk through the purchase channels, regional availability, and delivery options for each one: Amazon, Steam, Apple, PlayStation, Xbox, Google Play, and Visa.

How the discount actually applies

When you create an order via the API, the response includes a unit_price for each line item. That price is the discounted price for your current tier — not the list price. If you cross into a higher tier mid-month, the next order automatically uses the new tier’s pricing. You never negotiate the discount; you simply earn it as your volume grows. The dashboard always shows your current tier, the next tier’s threshold, and how many cards you need to clear it.

Locking rates for predictable budgeting

For finance teams that don’t want surprise cost variance on a quarterly accrual, Enterprise customers can lock their per-card rate forward by quarter. The rate you see at the moment of lock is the rate you pay on every order for the next 90 days, regardless of tier drift. This is standard for our Enterprise rollouts running a $50K+ monthly volume.

How regional catalog selection works

When you submit a recipient with a country, the API selects the correct regional catalog for that country and brand. A brand: "amazon" + country: "DE" produces an Amazon.de balance; the same brand with country: "JP" produces an Amazon.co.jp balance. You do not have to manage region codes yourself; we do it server-side. The full list of supported (brand, country) pairs is published in the OpenAPI spec and updated whenever we add a new region.

Edge cases we handle for you

• Country not in the brand’s catalog? We surface a clear 422 with a hint to the closest supported region
• Currency mismatch? We convert at mid-market FX at the moment of order creation
• Recipient email invalid? We fail-fast on validation, not 6 hours later after the brand rejects the code
• Recipient wants a different brand? They can self-serve swap via a hosted picker, on your branded domain

For non-developers or one-off projects, the dashboard no-code form calls the same API under the hood — you upload a CSV of recipients, click Send, and the same webhooks fire. For SaaS, HR-tech, and loyalty platforms, the REST API + webhooks is the right path. For most teams, the bulk of the integration work is mapping your internal event to our recipient schema; the actual API call is one HTTP request. The procurement buyer’s guide walks through a typical rollout timeline in detail.