How to Verify GPU Providers Before You Pay Them
When to ask for an ID, what to collect, and how a risk flag pauses one payout without pausing the platform.
Compute marketplaces have a strange supply side. Some providers are data centres with a legal team. Some are one person with four cards in a garage in Lisbon. Both are valuable, and both will ask you the same question on day one: when do I get paid?
Verification is how you answer that question without exposing your platform. Here is the approach we recommend, and what NVDA Protocol does for you along the way.
Do not verify everyone up front
Asking for a passport before a provider has earned a dollar is the fastest way to lose the garage in Lisbon. Onboard with the minimum: a name, an email, a country and a wallet. Let them list hardware and start earning.
Verify on signals, not on schedules
Set rules that trip on behaviour. The ones that catch the most with the least friction:
- Volume. More than $1,000 in a calendar month, or a single payout above $500.
- Shared wallets. One wallet address across several accounts is the single strongest fraud signal on a compute marketplace.
- Country changes. A provider whose declared country and connecting region disagree.
- Chargeback-adjacent jobs. Workloads bought with a card that later disputes.
Pause the payout, not the account
When a rule trips, the account moves to Restricted. The provider keeps their dashboard, keeps their job history and sees exactly what is due: usually one document. Their pending balance sits safely on the platform wallet until the review closes.
This matters because the provider's compute is still running. A restricted account that still serves jobs is a good provider having a bad week; an account that vanishes when asked for ID told you what you needed to know.
What to collect
For individuals: a government ID and a selfie. For companies: a registration number, a director, and the ID of that director. Store the outcome, not the document. NVDA Protocol keeps the verification state on the account and hands you a webhook when it changes.
Closing the loop
When the review passes, payouts resume automatically and the held balance settles in seconds. When it fails, you have the job history to make a fair call. Either way the rest of your providers were never touched, which is the whole point.