Cardholder Verification
Check that the recipient of the payment is the cardholder before sending funds.
We cover Visa and Mastercard cards from any bank
Reducing the likelihood of payments to fraudsters and third parties
Enhanced KYC/AML prior to financial transaction
Support for iGaming, Betting, Lottery, and MFO payout flows
Prevention of risks before payment, not after an incident
Who is this solution suitable for?
MFOs and lending services
For disbursement to the borrower's card. Cardholder Verification reduces the risk of payments to third-party cards (drops), helps control card changes, and detects errors or fraud attempts in the full name before sending funds.
iGaming / Casino / Betting
For withdrawals to the player's card.
The solution reduces the risk of withdrawals to third-party cards, multi-accounting, and payout disputes, and also strengthens KYC/AML and responsible gambling processes through better identification of the recipient.
Lottery and prize payouts
For payout of winnings to a card.
Automatic verification of name and surname minimizes erroneous payments, reduces the number of manual checks, and increases trust in the process on the part of users and regulators.
Other high-risk payout models
For other card payments. Affiliate/CPA, digital goods, financial services with mass payments — any scenarios where it is critically important to confirm that the money is received by the person for whom it is intended.
What is cardholder verification?
Cardholder verification is the process of checking that the recipient's details (full name) obtained during your KYC or onboarding process match those of the payment card holder to whom the payment is to be made.
You transfer:
- Recipient's full name (from the questionnaire, Action, photo of documents, or other KYC source)
- Card identifiers (in a format that matches your process: PAN, token, or other permitted identifiers)
In response, the service returns:
- Match – data matches
- Partial match – partial match (transliteration, abbreviation, typical typing error)
- Not match – data does not match
Important: the service does not make decisions for you. It returns the verification result, and you manage payments through your own risk policy and payout rules.
How Cardholder Verification Works
Step-by-step process
1
The user goes through KYC (questionnaire, photos of documents, etc.) and you receive their full name.
2
The user adds a card for payout or withdrawal.
3
You send a request to the Cardholder Verification API
4
Get the result and apply the Match/Partial match/Not match scenario
Benefits for your business
Less fraud in payments
The solution prevents scenarios where funds are withdrawn to cards belonging to fraudsters or third parties when the recipient's name does not match the cardholder's name.
Lower operating costs
Automating the verification of "is this the same recipient" reduces the number of manual cases, escalations, support requests, and payout disputes.
Prevention instead of investigations
The risk is identified before the funds are sent, not after the payment has already been made and incident management has begun.
The best experience for "white" users
With Match, payments are made quickly and without unnecessary steps – less friction, higher loyalty, lower churn.
Examples of use
MFI: loan repayment to the borrower's card
Betting/Casino: player withdrawals
Lottery: payment of winnings
FAQs
How is this different from 3DS or antifraud?
What does partial match mean?
Can rules be configured for different scenarios and limits?
Why is the verification procedure mandatory for receiving funds from MFOs?
Is it legal to operate a casino without KYC?
What documents are required for KYC?
Ready to reduce the risk of payments to unauthorized cards and strengthen KYC/AML in the payment process?
Get a demo, API access, or compliance consultation right now.