Know who is behind the payment.
When a customer says "that wasn't me," you need more than a transaction log. VerifiNow Payments verifies the customer before the payment completes, and keeps the payment and the identity evidence together in one record you can export as a PDF.
The dedicated product site at verifinowpayments.com has the full detail: pricing, security, FAQ, and partners.
- Government ID
- US driver's license. AAMVA data validated.
- Face match
- Live face matches the ID photo.
- Liveness
- Live person present.
- Location
- GPS 34.1478° N, 118.1445° W, Pasadena, CA
- Bound to
- Payment authorization, order 55120, $2,480.00
- Recorded
- Sep 21, 2026, 10:42:18 AM PT
Every system in your stack answers a different question. Only one is about the person.
Each of these does its own job well. None of them was built to tell you who was actually there when the money moved.
Payment processor
"Can this payment be authorized?"
Authorizes, captures and settles the card payment.
Doesn't establish who paid
Fraud platform
"Does this transaction look risky?"
Scores transaction, device and behavioral signals.
Returns a score, not an identity
Identity verification
"Who is this person?"
Establishes identity at some point in time, usually at signup.
Not built around the payment event
VerifiNow Payments
"Who is behind this payment?"
Binds a verified person's fresh authentication to the specific transaction.
One record, tied to the payment
Bank-approved. Customer-verified.
The card is authorized first. The payment completes only after the identity check passes. A transaction that meets your rules and clears both is what we call a Protected Transaction.
Your rules decide
A customer starts a payment on web, mobile, by phone or in person. Your configured rules decide whether this one needs identity assurance. Everything else checks out as usual.
The bank authorizes the card
Card authorization runs first, so you know the payment instrument is good before you ask the customer for anything.
The customer proves they're there
A government ID scan and a live selfie. VerifiNow authenticates the document, including AAMVA validation where available, matches the face to the ID photo, and runs liveness, deepfake and anti-spoof checks.
The payment completes, with evidence attached
The result returns in under 5 seconds and binds to that specific transaction. The payment completes and the record is yours to keep.
Applies to transactions that meet your configured rules. Card processing runs through CardConnect, or an alternate processing partner for online gaming and adult merchants.
The evidence is ready before the dispute arrives.
A chargeback can cost you the sale, the goods and a fee, on top of the hours spent assembling a response. On a Protected Transaction, none of that assembly happens after the fact, because the evidence was gathered at checkout.
A dispute arrives
The cardholder's bank reports a chargeback saying the purchase wasn't authorized.
Open the record
The payment, the verified identity and the selfie result for that payment are already in one place.
Export the PDF
One report with the transaction details, the identity verification details, and GPS location where it was captured, ready to attach to your dispute response.
What the report contains
- Payment transaction details, with timestamp
- Document authentication result
- Face match and liveness results
- Device, network and time of the check
- GPS location, where it was captured
Built for "I didn't authorize this" disputes. It is less relevant where identity isn't the question, such as disputes about delivery or product quality. VerifiNow strengthens your dispute documentation. It does not guarantee chargeback outcomes.
Verified once. Authenticated when it matters.
The objection to identity checks at checkout is friction. This is how that stays small: a customer proves who they are one time, and after that a protected payment only needs a fresh selfie.
First-time customer once
Full identity verification. Scan a government ID, checked for authenticity, document liveness and AAMVA data where available. Take a selfie, matched to the ID with liveness, deepfake and anti-spoof checks. The result binds to the payment.
About 20 to 25 seconds to scan and take the selfie, plus a result in under 5 seconds: up to roughly 30 seconds end to end. Times vary by customer and device.
Returning customer selfie only
Step-up selfie authentication. No ID scan. A fresh selfie is matched to the identity already verified, with liveness, deepfake and anti-spoof checks, then bound to the payment along with device, network, time, and GPS where enabled.
Returning customers never rescan an ID.
Protect the transactions that matter.
Add identity assurance where the risk justifies it, and let everyone else pay the way they always have. The rules stay yours.
High value
Orders above a threshold you set, where a single disputed transaction is expensive.
New account
A new customer's first purchase, or a first purchase from a new device.
Account changes
A new card on file, or changed payout details.
Phone and contact center
Send the caller a step-up request on their own phone before the payment completes.
Pickup and delivery
The payer and the person collecting the goods may not be the same.
Your existing risk rules
Orders your fraud platform already flags, or in-store pickup verified at the counter with LiveVerifi.
How this fits with 3-D Secure
3-D Secure lets the card issuer authenticate the cardholder, and when a payment is successfully authenticated, liability for fraud chargebacks generally shifts from the merchant to the issuer.4 That is valuable, and it stays in place. It also has limits, and they all follow from one fact: 3-D Secure is the issuer's check, run for the issuer's purposes.
Where 3-D Secure stops
- The liability shift doesn't apply to recurring transactions.4
- The issuer chooses how to authenticate, which may be a password or a one-time code.5
- You receive an authentication result, not your own evidence of who was present.
You only pay for the orders you choose to protect.
Verification is charged per protected transaction, not per order. A customer's first protected order carries the full verification. Every protected order after that is a selfie-only step-up, at a fraction of it. Orders that fall outside your rules are neither verified nor billed.
One customer, four orders
The rule in this example: verify orders of $500 or more.
| Order | Amount | What happened | Verification charge |
|---|---|---|---|
| Order 51877 | $640.00 | First-time verification. ID scan and selfie. Creates the verified identity record. | Full verification |
| Order 53302 | $1,150.00 | Selfie-only step-up. Matched to the verified identity and bound to this payment. | Cents |
| Order 55120 | $2,480.00 | Selfie-only step-up. A larger order, the same quick selfie. No ID rescan. | Cents |
| Order 58841 | $95.00 | Below your rule. Normal checkout, no added step. | No charge |
| Four orders worth $4,365, one full verification and two selfie step-ups | One verification, then cents | ||
An illustrative example to show how charging works, not a quote. Verification is billed only on transactions you choose to protect, and a monthly platform fee applies. Payment processing is quoted separately. Talk to us about pricing for your business.
Payment, identity and records in one platform.
Payment processing
- Card processing through CardConnect, or an alternate partner for online gaming and adult merchants
- Rules engine you configure for when identity assurance applies
- Real-time webhook notifications
- One dashboard for payments and verification
Identity verification
- Government ID authentication, with AAMVA data validation for US licenses
- Document liveness and presentation attack detection
- Face match with confidence thresholds you configure
- Liveness against photos, video replays, masks and deepfakes
Records and reporting
- Exportable PDF dispute report for each protected transaction
- Tamper-evident record, so later changes are detectable
- KYC and AML screening through the Trust & Compliance Suite
- Fraud and risk reporting in the dashboard
Security and data handling
Encryption and testing
TLS 1.3 in transit and AES-256 at rest. Annual third-party penetration testing and 24/7 security monitoring.
Compliance
- KYC and AML screening through the Trust & Compliance Suite
VerifiNow Payments questions
What is a Protected Transaction?
A payment that met your configured rules, was authorized by the bank, and passed an identity check before completing. Each one produces a record tying the verified person to that specific payment, exportable as a PDF.
How long does verification take?
A customer's first verification takes about 20 to 25 seconds to scan an ID and take a selfie, plus a result in under 5 seconds, so up to roughly 30 seconds end to end. It happens once per customer. Protected payments after that need a selfie only. Times vary by customer and device.
Does every customer have to verify at checkout?
No. You set the rules, for example orders above a threshold, a new account's first purchase, a new card on file, changed payout details, phone payments, or orders your fraud rules already flag. Everyone else checks out as usual.
What does it cost?
Verification is charged per protected transaction. A customer's first protected order carries the full verification, and every protected order after that is a selfie-only step-up at a fraction of it. Orders outside your rules are neither verified nor billed. A monthly platform fee applies, and payment processing is quoted separately. We quote rates for your business, so talk to us or book a demo.
Who processes the card payment?
Card processing runs through CardConnect, or an alternate processing partner for online gaming and adult merchants.
How does this work with 3-D Secure?
Payment card issuers use 3-D Secure to authenticate the cardholder, and when a payment is successfully authenticated, liability for fraud chargebacks generally shifts to the issuer. VerifiNow adds your own record of who was present, including where the 3-D Secure liability shift does not apply, such as recurring transactions.
What is in the record for a payment?
The payment transaction details, the document authentication result, the face match and liveness results, a timestamp, the device, network and time of the check, and the GPS location if location capture was enabled. The record is bound to that payment and tamper-evident, and exports as a PDF for a dispute response.
Is GPS location required?
No. Location capture is a setting you control. You can leave it off, ask for location but let customers continue without it, or require it. For customers in California, sharing location is always optional. When it is on, the customer's device asks their permission before sharing location.
How do we integrate it?
Through a REST API and web and mobile SDKs, with real-time webhook notifications. Deployments can go live in as little as one week.
Sources
- Mastercard dispute data, as reported in chargeback.io, "Chargeback Statistics 2026."
- Visa Acquirer Monitoring Program fact sheet, as cited in Redo, "Chargeback statistics for 2026." Threshold applies in the US, Canada, Europe, and Asia Pacific.
- Sumsub, "Synthetic Identity Document Fraud Surges 300% in the U.S.," June 12, 2025. Figure reflects Sumsub platform data.
- Adyen Help Center, "What is the 3D Secure liability shift?"
- Corefy, "Liability shift," payments glossary.
See a Protected Transaction end to end.
30 minutes, from checkout through to the exported dispute report, built around a transaction from your business.
