Skip to main content
Fintech and remittance services are subject to strict Anti-Money Laundering (AML) and Know Your Customer (KYC) regulations. Regulatory guidelines typically require at least 2 overlapping verification methods for remote account opening.
Regulatory riskFailure to block remittances to UN Security Council sanctioned countries or individuals can result in business suspension and significant fines.

​
Key requirements

ItemRequirement
Key regulationsAML/KYC laws (Anti-Money Laundering)
Required verificationID + selfie liveness
Security levelHighest (financial transaction level)
LivenessActive mode (fraud prevention)
AMLRequired (Sanctions/PEP/Adverse Media)
Data retentionID documents and records for 5+ years

​
Required settings checklist

1

Authentication method settings

Project Management > Policy and Authentication > KYC Process
SettingRecommended valueRationale
ARGOS score threshold70 points (conservative)Apply strict auto-approval criteria
ID recognition guarantee modeONOnly allow OCR-readable IDs
Universal ID supportONSupport various IDs for international customers

Configure KYC process

View detailed settings
2

ID forgery prevention settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > ID-based
SettingRecommended valueRationale
MRZ checkON (name threshold 85)Cross-verify passport MRZ information
ID livenessRetry (screen replay, paper printout)Block forged IDs
Streaming capture onlyONBlock gallery uploads, verify physical possession

Configure anti-fraud settings

View detailed settings
3

Biometric (selfie) settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Face Authentication
SettingRecommended valueRationale
Selfie processON (threshold 85)ID-selfie comparison
Selfie livenessActive mode (≥85)Defend against deepfake/spoofing attacks
Face deduplicationON (reject on duplicate)Prevent same person creating multiple accounts
When using active liveness, the streaming capture only option is enforced.
4

Additional verification settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Additional Auth & Meta Info
SettingRecommended valueRationale
Government data verificationONVerify national ID, driver’s license, passport, residence permit authenticity
Proxy & VPN detectionONBlock suspicious IP connections
Country-specific availability
  • Government data verification: Only South Korea and Mexico IDs supported
If you need government data verification for additional countries, please contact us. Additional support can be arranged upon request.
5

AML settings

Project Management > Policy and Authentication > Anti-Money Laundering (AML)
SettingRecommended valueRationale
AML Watch list filteringON (threshold 90-93)UN, OFAC sanctions list and PEP screening
AML Ongoing MonitoringONImmediate detection when added to sanctions list after signup
Full date of birth matchONPrevent false positives from namesakes
Importance of Ongoing MonitoringThis is a key tool for meeting the strengthened FATF (Financial Action Task Force) recommendations since 2024. It re-scans customer data daily to detect cases where someone was normal at signup but was later added to a sanctions list.

Configure AML settings

View detailed settings
6

Personal data handling settings

Project Management > Policy and Authentication > Authentication Data
SettingRecommended valueRationale
National ID number collectionAllow collectionFinancial companies may need full national ID numbers per tax law
Masking removalON if neededConfigure to receive encrypted original data in backend transmission
Unlike general businesses, financial companies may need to collect full national ID numbers according to credit information and tax laws in certain jurisdictions.
📋 Fintech required checklist

✅ Use ID Document (Liveform) method
✅ Streaming capture only (block gallery uploads)
✅ Selfie liveness - Active mode
✅ Government data verification (South Korea, Mexico supported)
✅ AML Watch list filtering + Ongoing Monitoring
✅ Proxy & VPN detection

​
Webhook integration

Required webhook events
EventAction
submission.approvedApprove account opening
submission.rejectedReject account opening
aml.matchImmediately freeze transaction + alert compliance team
aml.monitor.changedReview account when ongoing changes detected
Build a workflow that immediately freezes transactions when an aml.match event occurs. Real-time response is key to regulatory compliance.

Webhook setup guide

View detailed webhook event settings

KYC process

ARGOS score, age restrictions, country blacklist, and basic settings

Anti-fraud and forgery prevention

Liveness, selfie, Proxy/VPN detection, and security settings

Anti-Money Laundering (AML)

AML screening and Ongoing Monitoring settings

Authentication data

DI generation, deduplication, submission limits, and data management settings