Fintech (remittance) KYC setup guide

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

Item	Requirement
Key regulations	AML/KYC laws (Anti-Money Laundering)
Required verification	ID + selfie liveness
Security level	Highest (financial transaction level)
Liveness	Active mode (fraud prevention)
AML	Required (Sanctions/PEP/Adverse Media)
Data retention	ID documents and records for 5+ years

Required settings checklist

Authentication method settings

Project Management > Policy and Authentication > KYC Process

Setting	Recommended value	Rationale
ARGOS score threshold	70 points (conservative)	Apply strict auto-approval criteria
ID recognition guarantee mode	ON	Only allow OCR-readable IDs
Universal ID support	ON	Support various IDs for international customers

Configure KYC process

View detailed settings

ID forgery prevention settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > ID-based

Setting	Recommended value	Rationale
MRZ check	ON (name threshold 85)	Cross-verify passport MRZ information
ID liveness	Retry (screen replay, paper printout)	Block forged IDs
Streaming capture only	ON	Block gallery uploads, verify physical possession

Configure anti-fraud settings

View detailed settings

Biometric (selfie) settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Face Authentication

Setting	Recommended value	Rationale
Selfie process	ON (threshold 85)	ID-selfie comparison
Selfie liveness	Active mode (≥85)	Defend against deepfake/spoofing attacks
Face deduplication	ON (reject on duplicate)	Prevent same person creating multiple accounts

When using active liveness, the streaming capture only option is enforced.

Additional verification settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Additional Auth & Meta Info

Setting	Recommended value	Rationale
Government data verification	ON	Verify national ID, driver’s license, passport, residence permit authenticity
Proxy & VPN detection	ON	Block 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.

AML settings

Project Management > Policy and Authentication > Anti-Money Laundering (AML)

Setting	Recommended value	Rationale
AML Watch list filtering	ON (threshold 90-93)	UN, OFAC sanctions list and PEP screening
AML Ongoing Monitoring	ON	Immediate detection when added to sanctions list after signup
Full date of birth match	ON	Prevent 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

Personal data handling settings

Project Management > Policy and Authentication > Authentication Data

Setting	Recommended value	Rationale
National ID number collection	Allow collection	Financial companies may need full national ID numbers per tax law
Masking removal	ON if needed	Configure 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.

Recommended settings summary

📋 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

Event	Action
`submission.approved`	Approve account opening
`submission.rejected`	Reject account opening
`aml.match`	Immediately freeze transaction + alert compliance team
`aml.monitor.changed`	Review 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

Dashboard Overview

Statistics

Pre-verification List

User Submissions

Session Journey

AML Data

Event Log

Add-on

Project Management

Profile Options

Industry KYC Setup Guide

Fintech (remittance) KYC setup guide

Key requirements

Required settings checklist

Configure KYC process

Configure anti-fraud settings

Configure AML settings

Recommended settings summary

Webhook integration

Webhook setup guide

KYC process

Anti-fraud and forgery prevention

Anti-Money Laundering (AML)

Authentication data

​Key requirements

​Required settings checklist

Configure KYC process

Configure anti-fraud settings

Configure AML settings

​Recommended settings summary

​Webhook integration

Webhook setup guide

​Related documentation

KYC process

Anti-fraud and forgery prevention

Anti-Money Laundering (AML)

Authentication data

Key requirements

Required settings checklist

Recommended settings summary

Webhook integration

Related documentation