Loading...
Loading...
Navigate Taiwan fintech regulations including FSC oversight, electronic payment laws, VASP rules, AML/KYC requirements, and the regulatory sandbox. Use this skill when the user is building a fintech product in Taiwan, needs to understand licensing requirements, assess crypto/VASP compliance, or apply for the regulatory sandbox — even if they say 'do we need a license', 'crypto regulation in Taiwan', 'KYC requirements', or 'fintech sandbox application'.
npx skill4agent add asgard-ai-platform/skills tw-fintech-complianceIRON LAW: In Fintech, Regulation Comes BEFORE Product
Unlike most tech products where you can launch and iterate, financial
services in Taiwan require LICENSING FIRST. Operating without the proper
license is a criminal offense (not just a fine). Determine your regulatory
category and licensing requirements BEFORE writing code.| Category | Governing Law | License Required | FSC Division |
|---|---|---|---|
| Electronic payment | 電子支付機構管理條例 | 電子支付機構許可 | Banking Bureau |
| Third-party payment | 第三方支付服務業管理辦法 | Registration (lighter) | Banking Bureau |
| P2P lending | 金融科技發展與創新實驗條例 (sandbox) or crowd-funding rules | Case-by-case | Securities Bureau |
| Robo-advisory | 證券投資信託及顧問法 | Investment advisory license | Securities Bureau |
| Insurance tech | 保險法 | Insurance broker/agent license | Insurance Bureau |
| VASP (crypto) | 虛擬資產服務提供者管理辦法 (2024) | VASP registration + AML compliance | Securities Bureau |
| Open banking | 金融機構間資料共享指引 | API partnership with banks | Banking Bureau |
| Feature | Electronic Payment (電子支付) | Third-Party Payment (第三方支付) |
|---|---|---|
| Stored value | Yes (e-wallet) | No (pass-through only) |
| P2P transfer | Yes | No |
| Capital requirement | NT$500M+ | NT$5M |
| License | FSC approval (12-18 months) | Registration (1-3 months) |
| Examples | LINE Pay Money, JKoPay, icash Pay | 綠界 ECPay, 藍新 NewebPay |
| Requirement | Detail |
|---|---|
| Registration | Must register with FSC as VASP |
| AML/CFT | Full compliance with 洗錢防制法 |
| KYC | Identity verification for all users |
| Custody | Customer asset segregation required |
| Marketing | Restrictions on advertising (no promises of returns) |
| Reporting | Suspicious transaction reports (STR) to 調查局 |
| KYC Level | When Required | Data Collected |
|---|---|---|
| Simplified | Low-risk, small transactions | Name, ID number, DOB |
| Standard | Account opening, most transactions | + Address, occupation, source of funds |
| Enhanced | High-risk customers, PEPs, large transactions | + Detailed source of wealth, ongoing monitoring |
| Aspect | Detail |
|---|---|
| Purpose | Test innovative financial services without full licensing |
| Duration | Up to 18 months (extendable to 36) |
| Application | Submit to FSC with: innovation description, consumer protection plan, risk assessment |
| Approval time | 60 business days |
| Scope limitation | Must define user count, transaction limits, geographic scope |
| Exit plan | Path to full license or orderly shutdown |
| Phase | Data Shared | Status |
|---|---|---|
| Phase 1 | Product information (rates, fees) | Launched 2019 |
| Phase 2 | Customer information (with consent) | Launched 2021 |
| Phase 3 | Transaction initiation (payment, transfer) | In development |
# Fintech Compliance Assessment: {Product}
## Product Classification
- Service type: {payment / lending / advisory / crypto / insurance}
- Regulatory category: {electronic payment / third-party / VASP / etc.}
- License required: {specific license name}
## Licensing Pathway
| Step | Action | Timeline | Cost |
|------|--------|----------|------|
| 1 | {step} | {months} | NT${X} |
## AML/KYC Requirements
- KYC level: {simplified / standard / enhanced}
- Transaction monitoring: {required / not required}
- STR reporting: {required / not required}
## Key Risks
| Risk | Impact | Mitigation |
|------|--------|-----------|
| {regulatory risk} | H/M/L | {action} |
## Recommendation
- Proceed with licensing / Use sandbox / Restructure product to avoid licensingreferences/fsc-licensing.mdreferences/aml-kyc-checklist.md