Identity verification
Documents, personal data, date of birth, citizenship, expiry date and authenticity indicators.
API Integration / KYC
KYC API Integration
APIACE helps connect player identity verification: documents, biometrics, address, AML, PEP, sanctions lists, risk assessment and manual review.
ID
documents and data
Face
selfie and liveness
AML
risks and restrictions
Launch
scenario testing
Verification scope
From application to decision
Player verification
Player, country, required verification level, documents, current status and decision history.
Documents
Passport, ID card or driver licence, data extraction and authenticity checks.
Biometrics
Selfie, face-to-document matching and liveness verification.
Risk checks
PEP, sanctions lists, open sources, risk assessment and additional checks.
Player decision
Approval, rejection or manual review with a reason and an update to the player profile.
Linked to player management and security
Identity verification is linked to the player profile, back office, security and integration resources.
Overview
Identity verification within the platform
KYC integration brings together the player profile, document upload, biometrics, risk assessment, manual review and account restrictions.
The platform receives clear statuses, retains verification history and applies the final decision to the player profile.
Biometric verification
Face matching, liveness verification, image-quality checks and protection against reuse of submitted materials.
Risks and requirements
PEP, sanctions, open sources, risk assessment, manual review and required restrictions.
Integration scope
What KYC integration includes
The integration covers document and identity checks, receipt of decisions, manual handling of disputed cases and application of restrictions.
Connection and data
Service access and secure data exchange.
Create a verification for a specific player based on country and required level.
Upload documents, selfies, proof of address and additional data.
Receive statuses, handle repeated requests and errors, and update the player profile.
Working with players
Age and identity checks during registration, deposits, withdrawals or when a limit is reached.
Different verification levels for countries, products, amounts and risk categories.
Manual review, rejection reasons, requests for additional documents and reverification.
Reports on results, rejection reasons, verification times and staff actions.
How verification works
How player verification works
The process includes starting verification, collecting documents, analysing data and applying the final decision.
01
Start verification
The platform sends player data, country, language and required verification level.
02
Documents and selfie
The player uploads a document, takes a selfie and provides proof of address if required.
03
Data verification
The provider checks document authenticity, face match, restrictions and potential risks.
04
Player decision
The platform receives the result and updates KYC status, limits and operations available to the player.
Verification types
Core KYC checks
The verification scope depends on country, risk level, payment activity, regulatory requirements and operator rules.
Document verification
Data extraction, expiry date, document type, machine-readable zone and signs of alteration.
Selfie and liveness
Matching the selfie to the document and verifying the presence of a live person.
Proof of address
Bills, bank documents, government correspondence, issue date and data matching.
PEP and sanctions
Checks against sanctions lists, PEP records, related parties and additional sources.
Risk assessment
Country, age, documents, behaviour, payment data and results of additional checks.
Manual review
Review queue, staff permissions, requests for additional data, decisions and comments.
Verification statuses
Pending, processing, approved, rejected, manual review, expired and reverification.
Verification history
Documents, statuses, decisions, staff actions and reasons for changes.
Testing
What must be tested before launch
Before launch, test different documents, image quality, repeated requests, manual decisions and history retention.
Problem documents
Expired document, cropped image, glare, poor quality and mismatched data.
Selfie and face
Face mismatch, reused photo, screen image, mask, poor lighting and interrupted verification.
Reverification
Repeated verification creation, already completed requests and moving a player to a new KYC level.
Status change
Incorrect approval, delayed or repeated status and a decision change after manual review.
Manual review
Escalation to staff, request for a new document, decision and application of required restrictions.
History and reports
Status history, rejection reasons, staff actions, verification time and data export.
Documentation
KYC integration resources
Related sections help prepare integration, data protection, status receipt, error handling and pre-launch testing.
FAQ
Questions about KYC API integration
What is KYC API integration?
It connects a platform to an identity-verification service for documents, biometrics, risk assessment, statuses, manual review and decision history.
Can multiple KYC providers be connected?
Yes. The platform can select a service by country, verification type or availability and receive results in one consistent format.
Is manual review supported?
Yes. Disputed verifications can be assigned to staff, additional documents can be requested and the decision can be recorded.
Can KYC be connected to an existing iGaming platform?
Yes. KYC can be connected to registration, player profiles, payments, limits, withdrawals and back office.
Related pages
Related player-management capabilities
Need to connect a KYC API?
Tell us about the KYC provider, target countries, verification levels, documents, biometrics, AML and status-handling rules. APIACE will help define the integration scope and launch sequence.