Wholesale Gift Cards: How to Choose a B2B Supplier

Short Answer

Choosing a wholesale gift card supplier means evaluating eight factors: product catalog coverage, stock stability, region accuracy, API quality, wholesale pricing, payment terms, refund and dispute policy, and support responsiveness. The cheapest wholesale price is rarely the best choice if the supplier has poor stock reliability, incorrect region labeling or slow support. A wrong region card delivered to a customer is more expensive than a slightly higher wholesale price for the correct one.

Definition: A wholesale gift card supplier is a B2B company that sells digital codes — gift cards, game top-ups, digital goods — at prices below retail, with an API or bulk delivery mechanism, for resellers to sell on to end customers.

Key takeaway: For a reseller, the cheapest wholesale price is not always the best option. Stable stock, correct activation regions, fast delivery and clear reconciliation often matter more than a 1–2% price difference. Evaluate suppliers on all eight factors before connecting.

Who This Guide Is For

This guide is for:

• Resellers looking for their first or a second wholesale gift card supplier
• Store owners evaluating multiple supplier options before integration
• Marketplace operators due diligence-checking a potential digital goods supplier
• Telegram bot operators who need a reliable automated fulfillment source
• Fintech and loyalty platforms evaluating B2B digital goods partners

Why Supplier Choice Is a Critical Decision

Your choice of wholesale supplier determines:

• What products you can sell (catalog coverage)
• Whether your orders consistently succeed (stock stability and API uptime)
• Whether your customers get codes that actually work (region accuracy)
• How much your operations cost (pricing, payment terms, support overhead)
• How you resolve problems (refund policy, dispute resolution)

Switching suppliers mid-operation is expensive: you must rebuild the API integration, migrate product listings, retrain support staff and manage any in-flight orders. Getting the supplier selection right at the start saves significant cost.

The Eight Evaluation Factors

Factor 1: Product Catalog Coverage

Why it matters: You can only sell what your supplier has. A supplier with 50 SKUs limits your catalog. A supplier with 500 SKUs allows you to test what sells and expand.

What to check:

• Total number of SKUs (brands × denominations × regions)
• Coverage of your primary target market (gaming vs. retail gift cards vs. top-ups)
• Regional availability (US, EU, UK, MENA, APAC cards)
• Top-up products availability (PUBG UC, Roblox Robux, ML Diamonds, etc.)
• How frequently new products are added to the catalog

Questions to ask:

• "Do you have Steam, PSN, Xbox, Google Play and Apple in multiple regions?"
• "Do you support game top-ups for [specific games in your market]?"

Factor 2: Stock Stability and Availability

Why it matters: A product listed on your store that is frequently out of stock leads to failed orders, customer complaints and manual work to issue refunds.

What to check:

• Does the API provide real-time stock status per SKU?
• What is the typical in-stock rate for your key SKUs?
• Are there peak periods when stock drops (holidays, game releases)?
• How are out-of-stock situations communicated — by API or only by email?

Red flags:

• Stock status not available via API (you only find out when an order fails)
• Frequent out-of-stock on top-20 products
• No notification system for stock changes

Factor 3: Region Accuracy

Why it matters: A US Steam card cannot be redeemed by a customer in the UK. A PSN card for the European account does not work on a US PSN account. Wrong-region delivery is the most common source of refund requests and customer disputes in digital goods.

What to check:

• Are regions explicitly labeled in the catalog (e.g., "US", "EU", "TR", "GLOBAL")?
• Is there a single SKU covering multiple regions, or separate SKUs per region?
• Does the API return region information in the catalog response?
• What is the supplier's refund policy for wrong-region deliveries?

Correct catalog structure example:

Problematic catalog structure:

• "Steam Gift Card $10" without region label — unusable for reseller catalog

Factor 4: API Quality

Why it matters: Poor API documentation means slow integration. Unstable API means failed orders. Missing endpoints (no stock check, no balance API) means more operational risk.

What to check:

Questions to ask:

• "Is there a sandbox for testing before going live?"
• "What is your API uptime target?"
• "Do you provide a status page?"
• "How do you notify resellers of planned downtime?"

Factor 5: Wholesale Pricing and Volume Tiers

Why it matters: Margin is a function of the gap between wholesale cost and retail price. Pricing terms determine whether a product category is viable.

What to check:

• Is a price list available without signing an NDA first?
• Are there volume tiers (higher discount at higher monthly GMV)?
• Are prices fixed or do they change with FX rates?
• Is pricing per denomination consistent within a product (e.g., is a $50 card the same % discount as a $10 card)?

What to calculate before committing: Use the margin formula to model each key SKU at current pricing. If the net margin after your payment fees and platform commission is below 2%, that SKU is not viable unless pricing improves with volume. See How to Calculate Gift Card Margins.

Factor 6: Payment Terms and Minimum Order

Why it matters: Prepaid balance requirements affect your working capital. Net payment terms affect cash flow. Minimum order size affects whether the supplier is accessible to your volume.

What to check:

• Is the model prepaid balance, net-30 or net-60?
• Is there a minimum balance requirement to activate an account?
• Is there a minimum order amount per transaction?
• Are there fees for topping up the balance (bank transfer fees, etc.)?

Factor 7: Refund and Dispute Policy

Why it matters: Invalid codes, wrong-region deliveries and duplicate orders happen. Your customer will want a resolution. If the supplier won't refund you, you absorb the cost.

What to check:

• What events qualify for a refund claim (invalid code, wrong region, duplicate delivery)?
• What is the refund claim window (e.g., 24 hours, 7 days)?
• What evidence is required for a refund claim?
• Is the refund process manual or automated via API?
• What is the average refund resolution time?

Important: Do not assume a supplier offers refunds for scenarios they have not explicitly stated. Confirm refund policy in writing before signing any agreement.

Factor 8: Support Quality and Response Time

Why it matters: When an order fails at 11pm on a Friday, you need a response before your customer escalates. Support quality directly affects how quickly you resolve problems and how much operational overhead you carry.

What to check:

• What support channels are available (email, Telegram, phone)?
• What are the stated response time commitments?
• Is support available 24/7 or business hours only?
• Is there a dedicated account manager for B2B clients?

Questions to ask:

• "What is your average response time for urgent order issues?"
• "Do you have a dedicated channel for API integration support?"

Supplier Evaluation Summary Table

Shortlist Process: How to Evaluate Multiple Suppliers

1. Request a product catalog and price list from each supplier. If a supplier won't share pricing without a signed agreement, that is a signal.

2. Compare catalog coverage against your target product list. Count how many of your must-have SKUs each supplier covers.

3. Test the API in sandbox for each supplier. Check endpoint availability, response time and documentation quality. This reveals integration complexity.

4. Model net margins for your top 10 SKUs at each supplier's pricing. A 2% price difference may be worth it for better stock reliability.

5. Ask about refund policy and support explicitly. Request written answers, not verbal.

6. Start with a small live test before committing your full catalog. Place 20–50 real orders and observe fulfillment speed, stock accuracy and any issues.

Common Mistakes When Choosing a Supplier

1. Choosing on price alone — a 1% price advantage does not compensate for a 10% order failure rate

2. Not testing region accuracy — order one card per region in your top SKUs and verify it activates correctly before going live

3. Not reading the refund policy — discovering the policy after your first refund dispute is too late

4. Not evaluating API quality — a supplier without a sandbox or webhooks means slower integration and higher operational risk

5. Signing a long-term contract without a test period — test first, commit second

6. Assuming one supplier can cover all your needs — most stores use a primary supplier and a backup

Supplier Readiness Checklist

• Product catalog covers your top 20 target SKUs
• All SKUs have explicit region labels
• Real-time stock check available via API
• API documentation is complete with request/response examples
• Sandbox environment available for testing
• Webhooks supported
• Balance API available
• Reconciliation export in machine-readable format
• Price list provided before commitment
• Refund policy stated in writing
• Support channel and response time confirmed
• Test period negotiated before full commitment
• Net margin calculated for your top SKUs at current pricing