How to Vet a Game-Key Supplier Before Funding Your Balance
Digital distribution is structured so that you pay first — which means you are extending credit to your supplier. From the moment you fund the balance, your money sits with a counterparty, and your only leverage is whatever you built in before the transfer. Below is the due-diligence process worth running in full before a first deposit.
Why verification has to happen before the money
Digital goods deliver instantly and never return to stock. From the supplier's side, payment terms would be unsecured credit, so the deposit model is the industry standard: you fund a balance, each order draws against it.
The consequence matters: once funded, you have almost no negotiating position. Every lever — contract, documents, reputational channels, balance size — must be built beforehand. Verification after the first problem order arrives exactly one deposit too late.
Step 1. Verify the legal entity
Half an hour of work that filters out most problem counterparties.
- Find the registration details. Company name, registration number, jurisdiction and address should appear on the site or in the offer. Missing details alone are sufficient reason not to transfer money.
- Check the public registry. The jurisdiction of registration almost always has a public company register. Confirm the company exists, is active and is not in liquidation.
- Match against the payment details. The bank account must belong to the same company named in the contract. A request to pay a third party or an individual is a stop signal.
- Check age and history. A company registered last month asking for a large deposit calls for a fundamentally different level of caution.
Step 2. Read the contract properly
Do not read "in general" — read for specific clauses.
What must be present:
- The funding procedure and terms for returning an unspent balance if you stop working together.
- Replacement or refund for revoked and non-working codes, with an explicitly stated response window.
- Dispute-resolution procedure and governing law.
- Terms for changing pricing and the notice period.
What should worry you:
- The right to change any term unilaterally without notice.
- A blanket disclaimer of responsibility for code quality and functionality.
- A non-refundable deposit under any wording.
- Vague phrases in place of deadlines — "within a reasonable time", "where possible".
A separate breakdown of what documentation a supplier should provide is collected in supplier documents for game keys.
Step 3. Technical audit before integration
Request documentation before funding, and check it for:
- Whether there is a sandbox or the option to place one real minimum-value order.
- How you learn the final order status — by polling or callback. Do not assume webhooks or idempotency keys exist; ask directly whether that specific supplier implements them, and design against what is genuinely documented.
- Whether the SKU issuing region is exposed in the catalogue in machine-readable form.
- How the supplier communicates stockouts and outages — the standard mechanics are covered in supplier stockout recovery.
If the documentation exists only as a messenger thread, you will not be able to automate against it. A correct order lifecycle is laid out in the API order flow explained.
Step 4. The test order
A minimum purchase verifies what a contract cannot show you.
- Run one order end to end — from creation to code delivery.
- Activate the code yourself. Do not hand the first order to a customer.
- Measure actual delivery time, not the advertised figure.
- Create a problem case deliberately — request a replacement on a faulty code, or ask support a question that requires investigation. You are testing response time and completeness, not politeness.
- Request closing documents for that purchase. A company that cannot issue paperwork for 50 dollars will not issue it for 5,000.
Step 5. Stage the deposit
Do not fund a large sum up front. A sensible schedule looks like this:
| Stage | What you do | What you verify |
|---|---|---|
| Test | Minimum amount, one or two orders | Delivery, documents, support speed |
| Pilot | A few days of turnover | Stability, stockout behaviour |
| Working | A comfortable working balance | Incident response, balance return |
The rule is simple: never hold more on a balance than you could lose without it affecting operations. Parking a month of turnover with a new counterparty is not optimisation, it is risk concentration.
Step 6. References
Testimonials on the supplier's own site carry no information. What works instead:
- Direct contact with current clients of comparable size. Ask the supplier for introductions and do not accept an unexplained refusal.
- Specific questions rather than general ones. Not "are you happy" but: what happened at the last batch revocation, how fast did support respond during the incident, was the remaining balance returned on exit, were there unilateral pricing changes.
- Industry communities. Look for incident write-ups, not star ratings.
Red flags
None of these is disqualifying on its own, but two or more together is a reason to stop:
- Crypto only and no paperwork. Crypto as a payment method is ordinary industry practice. Crypto with no legal entity, no contract and no closing documents means no recourse of any kind.
- No legal entity. By definition there is nobody to bring a claim against.
- Pressure to deposit big and fast. "Today only", "the lot is nearly gone" — a standard technique that works specifically against your verification process.
- Refusal of a test order. A legitimate supplier wants you to be satisfied.
- A price noticeably below market with no explanation. A discount is always paid for by something: code provenance, absent replacement terms, or missing documents.
- Communication only through a personal messenger account, with no corporate channels or email on the company domain.
- No answer on their buying tier. The tiers are explained in where to source game keys for resale.
Where to buy once you have vetted
The point of the whole exercise is to end up with a supplier that has a legal entity, a coherent offer, real documents and predictable incident behaviour. FoxReload operates as a wholesale supplier with a 900+ SKU catalogue — game keys, gift cards, top-ups, eSIM and software licences — through a single REST API with auto-delivery and multi-region SKUs, meaning one contract and one balance instead of a set of fragmented counterparties each requiring its own vetting.
Pre-deposit checklist
- Legal entity details found and matched against a public registry.
- Payment details belong to the same company named in the contract.
- The offer contains a revoked-code replacement clause with a response window.
- The procedure for returning an unspent balance is written down.
- Received technical documentation, not a chat thread.
- Ran a test order and activated the code yourself.
- Deliberately created a problem case and measured the support response.
- Received closing documents for the test purchase.
- Agreed a staged deposit schedule.
- Spoke to one or two current clients with specific questions.
Related reading: how to verify a gift-card supplier.