How to Verify a Gift Card Supplier Before Buying Wholesale
Short Answer
Before committing capital to a wholesale gift card supplier, verify their legitimacy and reliability through a structured due diligence process. Key checks include: source of codes (authorized distributor vs gray market), invalid code replacement policy (in writing), sandbox/test environment availability, payment terms, and references from existing clients. Suppliers who cannot answer these questions clearly, or who pressure you to prepay large amounts without verification, are high-risk.
Definition: Supplier verification for wholesale gift cards is the process of confirming that a B2B supplier is a legitimate, authorized distributor of the digital goods they sell β with enforceable policies on code validity, pricing, and dispute resolution β before establishing a reseller account.
Key takeaway: The gift card wholesale market includes both reputable API suppliers and gray-market resellers selling codes from questionable sources. Gray-market codes look identical to legitimate codes until a customer tries to redeem one that has already been used, flagged, or was obtained through fraud. Verification upfront is significantly cheaper than dealing with chargebacks, refund losses, and reputation damage later.
Who This Guide Is For
- New resellers evaluating their first digital goods supplier
- Existing resellers considering switching to a new supplier
- Marketplace operators sourcing from multiple suppliers
- Procurement managers adding digital goods vendors to an approved supplier list
Eight Verification Checks
Check 1: Source Confirmation
Ask the supplier where they source their codes.
Acceptable answers:
- "We are an authorized distributor of [brand]"
- "We source directly from the publisher/game developer"
- "We work with licensed distributors in [region]"
Red flags:
- Vague answers ("we have many sources")
- Inability to explain the supply chain
- Codes available for platforms that don't have official B2B programs
Check 2: Invalid Code Policy
Get this in writing before placing any order.
What to ask: "What happens if a buyer receives an invalid or already-redeemed code?"
Acceptable answer: "We replace invalid codes within [X] business days upon receipt of the code, error screenshot, and order reference."
Red flags:
- No written policy
- "All sales final; we do not accept claims"
- Claiming invalid codes are always the buyer's fault
Check 3: Sandbox/Test Environment
For API integration, a sandbox environment is standard practice.
What to ask: "Do you provide a sandbox environment with test codes for integration testing?"
Acceptable answer: Yes, with test credentials and documentation.
Red flag: No sandbox available; you must test with live orders.
Check 4: API Documentation Quality
Review the API documentation before signing any contract.
Look for:
- REST API with clear endpoint descriptions
- Authentication method documented (API key / OAuth)
- Error codes documented with descriptions
- Rate limits documented
- Webhook support documented (if applicable)
Red flags:
- No API documentation available to evaluate pre-contract
- Undocumented error codes
- No versioning or changelog
Check 5: Payment Terms and Prepayment Risk
Ask:
- What are the payment terms? (Prepaid balance vs credit terms)
- What is the minimum deposit to open an account?
- Is the deposit refundable?
Acceptable: Prepaid balance model with reasonable minimums (assess based on your planned order volume). Credit terms for established resellers.
Red flags:
- Requiring very large upfront deposits before you have placed any orders
- Non-refundable deposits with no contract
- Wire transfer only to offshore accounts with no business registration
Check 6: Business Registration and Contact Verification
Verify:
- Company name and registration number
- Registered business address (verify it exists via public records or maps)
- Contact email on a business domain (not Gmail/free email for a supposed B2B company)
- Phone number or video call availability
Red flags:
- No business registration information available
- Contact only via Telegram with no other channels
- No business domain email
Check 7: References from Existing Clients
Ask for references from current resellers using their API.
What to check:
- Are references reachable and willing to speak?
- Do they confirm the supplier's invalid code handling?
- Are there known complaints (search forums, Trustpilot, Telegram groups)?
Red flag: Supplier cannot provide any references.
Check 8: Sample Order Test
Before placing large orders, test with the minimum possible order:
- Place a small test order (1β5 codes)
- Verify code delivery speed
- Attempt to redeem one code (or verify via the platform's code check where available)
- If a code is invalid: submit a claim and observe how the supplier responds
This is the most reliable verification method.
Supplier Evaluation Matrix
Score each check 0 (failed/concerning) to 2 (passed clearly):
| Check | Weight | Max Score |
|---|---|---|
| Source confirmation | High | 2 |
| Invalid code policy (written) | High | 2 |
| Sandbox environment | Medium | 2 |
| API documentation quality | Medium | 2 |
| Payment terms reasonableness | High | 2 |
| Business registration verifiable | High | 2 |
| References available | Medium | 2 |
| Sample order test passed | Very high | 2 |
| Total | 16 |
Score 12+: Proceed with caution; start with small volumes. Score 8β11: Significant gaps; resolve before committing capital. Score below 8: Do not proceed.
Red Flags Summary
| Red Flag | Risk Level | Implication |
|---|---|---|
| No written invalid code policy | High | No recourse for losses |
| No sandbox environment | Medium | Integration errors will cost money |
| Pressure to deposit large amounts upfront | Very high | Potential fraud |
| Free email address as primary contact | High | Not a legitimate business |
| Codes available for non-existent official programs | Very high | Gray market or fake codes |
| No business registration verifiable | Very high | Potentially unregistered |
| Refusal to provide references | High | No track record |
Contract Terms to Require
Before signing any contract or terms of service:
- Invalid code replacement policy: timeframe and process
- Liability for invalid codes above a defined threshold
- Price change notification period (how much notice before wholesale price changes)
- Balance refund policy: can unused prepaid balance be returned?
- Termination clause: how to exit the relationship and recover funds
- Jurisdiction: which country's law governs disputes
Checklist
- Confirm supplier's source for codes (authorized distributor)
- Obtain written invalid code policy
- Request and test sandbox environment
- Review API documentation before contract
- Verify business registration and physical address
- Confirm payment terms and deposit refundability
- Request client references; contact at least one
- Place small test order and redeem/verify at least one code
- Review contract terms: replacement policy, price change notice, balance refund
