Verify the customer before the server goes live
ID document, selfie and liveness for new hosting, VPS and cloud customers, and a face blocklist so a customer you banned for abuse cannot sign up again.
What goes wrong without it
-
Orders paid with stolen cards
The server is running long before the chargeback arrives.
-
Abuse from throwaway accounts
Phishing, spam, scanning and mining, each time from a new email, and the abuse reports land on you.
-
Manual ID checks hold good customers
Scans sent by email, reviewed by staff, orders on hold for hours.
-
Banned customers sign up again
A new email, a new card, the same person.
Who uses it
- VPS, cloud and dedicated server providers
- Verify a new customer before the first deploy, or only the orders your fraud screening holds.
- Free tiers and trials
- One person, one free trial. A selfie catches the same face behind a new account, whatever email or card they use.
- Shared hosting and resellers
- Verify high-risk orders, or the customer behind a suspended account before you reactivate it. The flow carries your brand.
How it works
-
Step 1
Create a verification
Your billing or order system calls the API, or an SDK, when an order comes in or is held. You get a link for the customer.
-
Step 2
The customer completes it
In the hosted widget: a photo of their ID and a selfie with a liveness check, on a phone or a computer.
-
Step 3
The result arrives
By signed webhook, with any blocklist or duplicate match. Provision the server, keep the order on hold or cancel it.
End to end, at the 95th percentile, Identity verification (KYC) finishes in under 10 s. ID documents from 190+ countries.
Which check to use
| Situation | Check | Price per verification |
|---|---|---|
| A new customer before the first server, or a held order | Identity verification (KYC) | $0.30 |
| One free trial per person | Facial age estimation with duplicate detection | From $0.05 |
| Keep customers banned for abuse out | Block repeat accounts | Included |
Banned customers stay out
ProofAge can remember faces and devices, so a ban sticks. It works with face, ID and KYC checks and is included in the price. How Block repeat accounts works.
Face blocklist
Ban a customer once, and a later verification with the same face is caught, whatever email, card or document they use.
Device blocklist
Block the device a banned customer verified from, so a new account from that device is caught too.
Duplicate detection
See when the same person verifies for several accounts, without waiting for an abuse report.
What happens to your customers' data
- Kept only as long as bans need it
- Photos, video and verification data are kept for 30 days. A face template and a device fingerprint hash are kept for 12 months, so blocklists and duplicate detection work.
- Hosted in the EU
- Google Cloud EU regions by default. US regions on request, agreed in writing.
- Encrypted in transit and at rest
- TLS 1.2 or higher for all traffic, AES-256 at rest. We act as your data processor under a Data Processing Agreement.
Pricing
$0.30 for Identity verification (KYC), from $0.05 for Facial age estimation. Blocklists and duplicate detection are included. A verification is billed once, when it reaches a decision; abandoned verifications are free.
-
Free to try
500 live verifications, no time limit, no card.
-
Monthly minimum
$30 a month after the trial. Your usage counts toward it.
-
Money back
30-day money-back guarantee on the first payment.
Billing rules are on the pricing page. Higher volume or a competing quote? Talk to us.
Hosting customer verification: FAQ
Should we verify every customer, or only risky orders?
Either. Some providers verify every new customer before the first server; others verify only the orders their fraud screening holds. Each verification is billed once, when it reaches a decision.
Does this replace our payment fraud screening?
No. It works alongside it. Card screening tells you about the card; ProofAge tells you who the person is and whether you banned them before.
Can we connect it to our billing or order system?
Yes, through the REST API and signed webhooks: create a verification when an order comes in, and let the webhook release or cancel it. SDKs for Laravel/PHP, Node.js and Python. We help you integrate: ready SDKs, an MCP server and an integration prompt for AI coding agents, and direct help from the developers who built it.
Can we compare the ID with the billing details?
Yes. Identity verification (KYC) returns the data from the document by API, including the name and date of birth, so you can compare it with the name on the order.
Do you verify companies?
ProofAge verifies people: the customer, or the person who signs up for a company account. Need to check the company too? Talk to us: we will help you find a solution, or build one for your case.
A direct line to the developers who built it
Write to us on LinkedIn, by email or in the dashboard chat. The developers who built ProofAge answer themselves, weekends included.