mcpField
T
tw-fintech-compliance

tw-fintech-compliance

github.com/asgard-ai-platformOther24336 installsUpdated 21w ago
Repository

About tw-fintech-compliance

A Taiwan fintech compliance guidance skill for teams assessing financial products before development. It outlines FSC regulatory categories, licensing paths, AML/KYC duties, sandbox conditions, and open banking phases.

Key features

  1. 01FSC service categories and laws
  2. 02License and registration distinctions
  3. 03AML/KYC obligations
  4. 04Regulatory sandbox conditions
  5. 05Open banking phase overview

Use cases

  1. 01Classify a planned Taiwan financial service
  2. 02Identify potential licensing requirements
  3. 03Review AML/KYC duties for a product
  4. 04Assess sandbox or open banking considerations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/asgard-ai-platform/skills --skill tw-fintech-compliance

After installing, type/tw-fintech-compliancein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

examples/
sample_scenario.md
references/
aml-kyc-checklist.md
fsc-licensing.md

Details

From the project README

Taiwan Fintech Compliance

Framework

IRON 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.
FSC Regulatory Framework

金融監督管理委員會 (FSC) oversees all financial services in Taiwan:

CategoryGoverning LawLicense RequiredFSC Division
Electronic payment電子支付機構管理條例電子支付機構許可Banking Bureau
Third-party payment第三方支付服務業管理辦法Registration (lighter)Banking Bureau
P2P lending金融科技發展與創新實驗條例 (sandbox) or crowd-funding rulesCase-by-caseSecurities Bureau
Robo-advisory證券投資信託及顧問法Investment advisory licenseSecurities Bureau
Insurance tech保險法Insurance broker/agent licenseInsurance Bureau
VASP (crypto)虛擬資產服務提供者管理辦法 (2024)VASP registration + AML complianceSecurities Bureau
Open banking金融機構間資料共享指引API partnership with banksBanking Bureau
Electronic Payment vs Third-Party Payment
FeatureElectronic Payment (電子支付)Third-Party Payment (第三方支付)
Stored valueYes (e-wallet)No (pass-through only)
P2P transferYesNo
Capital requirementNT$500M+NT$5M
LicenseFSC approval (12-18 months)Registration (1-3 months)
ExamplesLINE Pay Money, JKoPay, icash Pay綠界 ECPay, 藍新 NewebPay
VASP (Crypto) Regulations (2024+)
RequirementDetail
RegistrationMust register with FSC as VASP
AML/CFTFull compliance with 洗錢防制法
KYCIdentity verification for all users
CustodyCustomer asset segregation required
MarketingRestrictions on advertising (no promises of returns)
ReportingSuspicious transaction reports (STR) to 調查局
AML/KYC Requirements (All Financial Services)
KYC LevelWhen RequiredData Collected
SimplifiedLow-risk, small transactionsName, ID number, DOB
StandardAccount opening, most transactions+ Address, occupation, source of funds
EnhancedHigh-risk customers, PEPs, large transactions+ Detailed source of wealth, ongoing monitoring

Ongoing obligations:

  • Transaction monitoring (unusual patterns)
  • Suspicious Transaction Reports (STR) to 法務部調查局
  • Sanctions screening (OFAC, UN, EU lists)
  • Record keeping: 5+ years after account closure
Regulatory Sandbox (金融科技創新實驗)
AspectDetail
PurposeTest innovative financial services without full licensing
DurationUp to 18 months (extendable to 36)
ApplicationSubmit to FSC with: innovation description, consumer protection plan, risk assessment
Approval time60 business days
Scope limitationMust define user count, transaction limits, geographic scope
Exit planPath to full license or orderly shutdown
Open Banking (Three Phases)
PhaseData SharedStatus
Phase 1Product information (rates, fees)Launched 2019
Phase 2Customer information (with consent)Launched 2021
Phase 3Transaction initiation (payment, transfer)In development

Output Format

# 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 licensing

Gotchas

  • Third-party vs electronic payment: The distinction is stored value. If your app holds customer money (e-wallet), you need the much heavier electronic payment license (NT$500M capital). If you just process payments (pass money from buyer to seller), third-party registration is sufficient.
  • Sandbox is not a shortcut: The sandbox exempts you from licensing temporarily, but you must still comply with AML, consumer protection, and data privacy. And you still need to get a full license to commercialize.
  • VASP regulation is new and evolving: The 2024 VASP rules are Taiwan's first comprehensive crypto regulation. Expect amendments and additional guidance. Build compliance infrastructure that's adaptable.
  • Foreign fintech entering Taiwan: Foreign companies must establish a Taiwan entity and obtain Taiwan-specific licenses. A license in another jurisdiction does not transfer.
  • This is educational guidance, not legal/regulatory advice: Fintech regulation is complex and penalties for non-compliance include criminal charges. Engage a regulatory affairs lawyer specializing in Taiwan financial services.

References

  • For FSC licensing application guides, see references/fsc-licensing.md
  • For AML/KYC implementation checklist, see references/aml-kyc-checklist.md

Comments

Markdown supported