Featured

How to Choose a Gift Card API: A Vendor Evaluation Guide

A vendor evaluation guide for product managers and developers integrating a gift card API.

by 
Jen Hoffman
•
November 9, 2026
Share this article

The global digital gift card market reached $513.79 billion in 2025 according to IMARC Group. Most rewards providers now offer an API, and the core capabilities are broadly similar: catalogue access, ordering, delivery, and tracking. The differences that matter for your integration are more specific. How deep is the catalogue in the markets your recipients actually sit in? How does the fulfilment chain behave under failure conditions? Does the delivery model give your product control over the recipient experience? 

This guide covers the evaluation criteria for a production-grade gift card API, where programmes break once they're live, and the questions your team should ask every vendor before committing engineering time.

What Makes Gift Card APIs Different to Evaluate

If your team has integrated payment processors, identity providers, or communication APIs, the mechanics are familiar. Authenticate, call an endpoint, handle the response, listen for webhooks. 

What's specific to this category is the supply chain sitting behind the endpoint. A gift card API isn't serving data from a database. It's triggering a transaction across a network of brand suppliers, each with their own inventory, activation rules, denomination constraints, and regional availability. The API abstracts that complexity, but the quality of the abstraction varies enormously between vendors.

Three things matter more here than in most API evaluations: the real catalogue depth behind the advertised number, the reliability of the fulfilment chain under failure conditions, and whether the vendor's delivery model gives your product control over the recipient experience or forces you into their flow.

Evaluation Criteria

Catalogue Depth Per Country

Total brand count gives you a starting point, but the number that matters for your integration is how many locally redeemable brands are available in each specific country your recipients sit across.

When evaluating, request the catalogue for your three largest recipient markets individually. Check that the brands returned are ones people in those markets recognise and more importantly, use. A strong global catalogue and strong local catalogues are two different things, and your programme needs both if you're serving recipients across multiple regions.

Look for a catalogue query endpoint that filters by country and currency so your product can surface the right options dynamically per recipient. This saves your team from building and maintaining market-level filtering logic on your side.

Integration Quality

Sandbox access is worth prioritising early in the evaluation. Some vendors offer instant access, others require a conversation first. Either approach works, but factor the access timeline into your integration schedule.

Documentation that your team can ship from. Endpoint references, authentication guides, error code definitions, and code samples. Searchable, versioned, and maintained. Documentation quality remains the most reliable predictor of integration speed across any API category.

Webhooks across the full order lifecycle: placed, delivered, opened, redeemed, failed. Without granular state webhooks, your product either polls for status or operates blind between the order call and an eventual confirmation.

Idempotency on order endpoints. A network timeout that triggers a retry should not produce a duplicate order and a duplicate charge. If the vendor doesn't handle this at their layer, your team absorbs that engineering cost.

Production Readiness

The gap between a successful demo and a reliable production integration is where most evaluations fall short.

Batch and high-volume ordering. How does the API handle a thousand orders triggered simultaneously? Is there a rate limit? Does the vendor support concurrent requests without queuing delays?

Reconciliation. Your finance team needs to match every order to a spend line. The API should expose transaction-level data: order ID, amount, brand, recipient, status, and timestamp. If reconciliation requires exporting reports from a separate dashboard rather than querying the API directly, that's a manual process your team will resent by month three.

Delivery speed. Digital gift cards should arrive within seconds of the API call, not in batched processing windows. Rewards lose behavioural impact proportionally to how long they take to reach the recipient.

Controls and Compliance

Controls are imperative when you’re moving real money through the API.

Budget thresholds that prevent overspend. Fraud monitoring that flags unusual ordering patterns. Spend limits per recipient, per campaign, or per time period.

Security attestations: ISO 27001, GDPR compliance, CCPA compliance. 

For a detailed breakdown of compliance considerations by market, see our compliance guide.

Pricing Transparency

Most gift card API providers charge face value for the cards with their margin built into brand commissions, platform fees on certain catalogue items, or FX spread on international payouts. Ask whether there are API usage fees, per-transaction fees, or minimum spend requirements. Ask whether international orders carry additional FX charges. You want to track the total cost per delivered reward, including FX fees, transaction fees, etc. 

Evaluation Criteria at a Glance

Gift card API evaluation criteria

Criteria What to look for Questions to ask
Catalogue depth Locally relevant brands in your top recipient markets, filtered by country and currency Can I query the catalogue for a specific country? How many active brands will my users in [market] see?
Sandbox access Available early in the evaluation process so your team can test before committing How quickly can my engineering team access the sandbox? What's included in the test environment?
Documentation Searchable, versioned, with endpoint references, authentication guides, and code samples Is the documentation publicly available? When was it last updated?
Webhooks Real-time notifications across the full order lifecycle: placed, delivered, opened, redeemed, failed Which order states trigger webhooks? What's the retry mechanism for missed events?
Idempotency Idempotency keys on order endpoints to prevent duplicate orders on retry How does the API handle duplicate requests from network timeouts?
High-volume ordering Supports concurrent requests at scale without queuing delays What are the rate limits? How does the API handle a thousand simultaneous orders?
Error handling Clear error codes, retry guidance, and documented failure states What does the error response structure look like? Are failure states documented?
Delivery speed Digital cards delivered in seconds of the API call What's the average delivery time? Is delivery real-time or batched?
Security Named certifications: ISO 27001, GDPR, CCPA or equivalent Which specific security certifications does the platform hold?
Pricing Transparent fee schedule available before integration begins Are there API usage fees, per-transaction charges, or FX surcharges? Can I see the fee schedule in writing?

Use these criteria and questions with any vendor you're evaluating. The answers will surface the differences that matter for your specific integration.

Where Programmes Begin To Break

Most teams spend their evaluation time on the catalogue and the initial send mechanics. The catalogue definitely matters, but overall it’s simply table stakes. Where you want to focus your evaluation is on order fulfillment. 

Activation failures. A card is ordered and a code is generated, but the card doesn't activate. The recipient tries to redeem it and it doesn't work. Your support team gets the ticket. How does the vendor handle reactivation or reissuing? Is it automated or does it require a manual support request?

Failed deliveries. An email bounces. A recipient's inbox is full. A spam filter catches the delivery. How does the vendor surface failed deliveries? Is there a webhook for failures? Can your system automatically retry with a corrected email address, or does it require a manual resubmission?

Duplicate orders. A network timeout causes your system to retry an order. Without idempotency keys, the recipient gets two gift cards and your budget absorbs the duplicate. How does the vendor prevent this? Ask for specifics, not assurances.

Reconciliation gaps. Your finance team needs to match every order to a spend line. The vendor's reporting shows 500 orders. Your system logged 502 API calls. Two of those were retries that produced duplicates. Or two were failures that were never fulfilled. Without clear reconciliation endpoints and audit trails, finding the discrepancy is manual detective work.

Webhook reliability. Your product relies on a webhook to confirm delivery before showing the reward in the user's dashboard. The webhook doesn't fire. The user sees nothing. Your system thinks the order is still pending. How does the vendor handle missed webhooks? Is there a retry mechanism? Can you query order status independently as a fallback?

These scenarios sound edge-case until they happen at volume. At 10,000 orders a month, a 0.5% activation failure rate is 50 support tickets. A 1% webhook failure rate is 100 orders where your product doesn't know what happened. The vendor's reliability on these details matters more than its brand count.

Eight Questions to Ask Every Gift Card API Vendor

Eight questions to ask every gift card API vendor

Question Why it matters Totally's answer
Can I access the sandbox today without a sales call? Determines whether your engineering team can start evaluating immediately or waits for access. Yes. Sandbox environment available with publicly accessible API documentation. Your team can start testing immediately.
How is authentication handled? Security model determines integration complexity and ongoing key management. HMAC-SHA256 signed headers on every request. Documented authentication flow with code samples.
Do you support webhooks for the full order lifecycle? Without lifecycle webhooks, your product either polls for status or operates without real-time confirmation. Yes. Real-time webhooks for delivery, opens, and redemptions. Status syncs to your systems automatically.
How are duplicate orders prevented on retries? Network timeouts happen. Without idempotency, retries produce duplicate orders that cost real money. Idempotent request handling. Retries do not produce duplicate orders.
Can the API return a voucher code to my backend without auto-emailing the recipient? Essential for embedded experiences where your product controls the delivery UI and recipient journey. Yes. The API returns reward data to your backend. You control when and how the reward reaches the user.
What does the catalogue look like in my specific markets? Local catalogue depth determines whether the API serves your actual recipients, not just a headline number. 3,000+ brands across 50+ countries. Catalogue query endpoints return locally relevant brands filtered by country and currency.
What are the fees? Hidden per-call charges, FX spreads, and minimum commitments change the programme economics after integration. No API usage fees. No platform fees. No subscriptions. Face value pricing with transparent commercial terms.
What is the published uptime? Reward delivery that goes down during a campaign or high-volume send damages user trust and programme credibility. 99% published uptime.

These questions work with any vendor you're evaluating. Totally's answers are included to give you a benchmark for comparison.

How Totally's API Works

Totally is a RESTful gift card API for ordering, delivering, and tracking digital gift cards, prepaid cards, and incentives programmatically.

3,000+ brands across 50+ countries. Local brand gift cards, Multi-Choice Cards, global prepaid Visa and Mastercard, and payouts. The catalogue query endpoint returns locally relevant brands filtered by country and currency, so your product surfaces the right options for each recipient's market.

No fees beyond the card value. No API usage fees. No platform fees. No subscriptions. No per-transaction charges. The commercial model is transparent and documented before integration begins.

HMAC-SHA256 authentication. Every request is authenticated using signed headers. The authentication flow is documented with code samples in the API documentation.

Real-time webhooks. Instant notifications on delivery, opens, and redemptions. Status syncs to your systems automatically, so your product can reflect the current state of every reward without polling.

Event-based triggers. Define triggers within your product for any qualifying action: milestone reached, survey completed, referral converted, transaction processed. The API handles fulfilment automatically when the event fires.

Sandbox and documentation. A full sandbox environment for testing against live catalogue data without spending real balance. Publicly available API documentation covering endpoints, authentication, catalogue queries, order management, and status tracking.

99% uptime. Published availability with monitoring across all endpoints.

ISO 27001 certified. GDPR and CCPA compliant. Information security, data protection, and privacy requirements managed within the platform infrastructure.

Getting Started

Three steps from evaluation to live integration.

Step 1: Access the sandbox. Visit the API documentation, review the authentication flow, and place a test order against the sandbox. No sales call required.

Step 2: Validate your markets. Query the catalogue endpoint for each country your recipients sit in. Confirm the brands, denominations, and card types available in those specific markets.

Step 3: Build and test. Implement the order flow, configure webhooks, test error handling and retry logic. Most engineering teams move from sandbox access to production readiness within four to eight weeks.

Ready to evaluate Totally's API? Request sandbox access or talk to the team. 

Frequently Asked Questions

What is a gift card API?
A programmatic interface that lets your software order, deliver, and track digital gift cards automatically. Your system sends an API request with the brand, amount, and recipient, and the provider delivers the card by email, SMS, or a claim link, typically within seconds.

How does a gift card API work?
Authenticate with an API key. Query the catalogue for available brands and denominations. Place an order (single or batch). The provider delivers the card and sends webhooks confirming each state change: delivered, opened, redeemed.

How much does a gift card API cost?
Most providers charge face value with margin built into brand commissions or FX spread. Totally charges no API usage fees, no platform fees, and no subscriptions. Always request a fee schedule in writing and compare total cost per delivered reward.

Do I need a sandbox before integrating?
Yes. A sandbox lets your engineering team test ordering, webhooks, and error handling without spending real balance. Totally provides instant sandbox access with publicly available documentation.

How fast are gift cards delivered through an API?
Digital gift cards are typically delivered within seconds of the API call. Totally publishes 99% uptime across all endpoints. Delays usually come from fraud review on unusual orders, not the delivery pipeline.

What is the difference between a gift card API and a payouts API?
A gift card API sends branded cards from a catalogue. A payouts API moves cash through bank, wallet, or prepaid card rails. Some vendors offer both. Most lean toward one. Totally supports digital gift cards, Multi-Choice Cards, and prepaid Visa and Mastercard through a single API.

What is the difference between open-loop and closed-loop gift cards?
Closed-loop cards work at one brand or group of brands. Open-loop cards (Visa, Mastercard) run on a card network and work almost anywhere. IMARC Group reports closed-loop cards hold 57.3% of the digital gift card market.

How long does a gift card API integration take?
Most engineering teams move from sandbox access to production readiness within four to eight weeks, depending on the complexity of the front-end experience and the number of systems being connected.

Let’s build something great

See how Totally’s API can support your reward and payout workflows. Talk to our team to explore your use case, or access our documentation when you’re ready to get started.
Book a Demo
Gradient arc shape blending blue, cyan, and magenta colors on a transparent background.Gradient arc shape blending blue, cyan, and magenta colors on a transparent background.Hand holding smartphone showing a balance of £130.00 and a catalogue with gift card options including Uber Eats, Starbucks, Adidas, Airbnb, Sephora, and Netflix.