DISPATCH ·

APAC CFD broker RFP template (Phase 4 per-archetype artefact)

Forty-seventh dispatch. Sixth per-archetype RFP template covering Archetype F: APAC CFD brokers authorised across MAS, SFC, FSA, ASIC, KFSC.

tags · phase-4 · rfp-template · apac · archetype-f · operational-artefact

Why this dispatch exists

Sixth per-archetype RFP template covering Archetype F per the APAC archetype dispatch.

Section 1: Requirement overview

The requirement is the multi-jurisdiction APAC CFD broker tech stack for an operator authorised across Singapore MAS, Hong Kong SFC, Japan FSA, Australia ASIC, and/or Korea FSC serving sophisticated investor + institutional client segments across Asia-Pacific.

Section 2: Vendor evaluation categories required

  • Brokerage hosting (Equinix SG1 + HK1 + TY3 + SY3 typical for per-jurisdiction data residency)
  • Trading platforms (MT5 with Asian-language localisation + cTrader for differentiation + crypto-CFD on Match-Trader if applicable)
  • LP procurement (tier-1 prime broker with APAC desk + regional Asia PoPs + APAC-specific FX flow specialists)
  • Risk management (per-jurisdiction leverage cap enforcement: MAS 1:20, SFC 1:20, FSA 1:25, ASIC 1:30 majors, Korea 1:10)
  • KYC + AML (Sumsub or Veriff with HK ID Card + Singapore NRIC + Japan My Number + Korea RRN + Australia driver licence + Medicare combinations support)
  • RegTech (Nasdaq SMARTS for trade surveillance + Cappitech for per-jurisdiction reporting + Behavox or Smarsh for comms surveillance including WeChat + LINE)
  • Broker CRM (B2Core or Match-Trader CRM with Mandarin simplified/traditional + Cantonese + Japanese + Korean localisation)
  • Payments (8-12 PSPs covering PayNow + GIRO Singapore + FPS Hong Kong + Zengin + PayPay Japan + PayID + BPay Australia + KFTC Korea)
  • IB management (specialist with per-jurisdiction tax disclosure for IB compensation)
  • Broker analytics (Trading Central + Autochartist + LSEG + Bloomberg Terminal for institutional-leaning APAC operators)
  • Copy trading (cTrader Copy if cTrader)
  • Crypto exchange WL (per-jurisdiction crypto regulatory regimes: MAS DPT, SFC VATP, FSA CAEP, AUSTRAC + ASIC if applicable)

Section 3: Universal vendor requirements

Apply the five universal dimensions from the RFP scoring framework opener.

Section 4: Per-pillar requirements

APAC-specific per-pillar emphasis:

  • Per-regulatory-regime leverage cap configurability (stricter than DMCC permissive defaults)
  • Per-jurisdiction language depth (Mandarin simplified vs traditional distinct; Cantonese, Japanese, Korean, plus regional Southeast Asian languages)
  • Per-jurisdiction payment rail coverage (no APAC SEPA equivalent; jurisdiction-specific rails procurement filter)
  • Per-jurisdiction crypto authorisation if applicable (4 distinct regulatory regimes)
  • WeChat + LINE comms surveillance for HK + Japan operations
  • Per-jurisdiction document support (HK ID Card structure + Singapore NRIC + Japan My Number + Korea RRN + Australia)

Section 5: APAC archetype customisation (weight multipliers)

Per the Phase 4 opener customisation layer:

  • R1 (leverage cap configurability) x 1.5
  • P5 (multi-language) x 1.5 for Mandarin/Cantonese/Japanese/Korean
  • KYC1 (per-APAC documents) x 1.5
  • PMT1 (APAC rail coverage) x 1.5

Section 6: Disqualification thresholds checklist

  • ☐ Per-regulatory-regime leverage cap configurability for risk management vendor
  • ☐ Asian-script document verification for KYC vendor (HK ID Card + NRIC + My Number + RRN)
  • ☐ WeChat + LINE comms capture for comms surveillance vendor
  • ☐ Per-jurisdiction rail coverage for PSP procurement
  • ☐ Per-APAC-jurisdiction authorisation for crypto venue if applicable

Section 7: Vendor scoring rubric reference

APAC-specific demo emphasis:

  • Per-jurisdiction leverage cap configurability demonstration (MAS 1:20 vs SFC 1:20 vs FSA 1:25 vs ASIC 1:30 majors vs Korea 1:10)
  • Asian-script document verification with operator-provided test documents
  • WeChat + LINE comms capture demonstration
  • Per-jurisdiction payment rail demonstration (PayNow, FPS, Zengin, PayID)

Section 8: Reference customer validation

  • Hosting: minimum 2 APAC operators per IBX (SG1, HK1, TY3, SY3 as applicable)
  • KYC: minimum 2 APAC operators with Asian-script document verification operational tenure
  • RegTech: minimum 2 APAC operators with Nasdaq SMARTS deployment + APAC regulator engagement
  • Payments: minimum 2 APAC operators with operator-relevant per-jurisdiction rail coverage

Section 9: Integration testing scope

APAC-specific integration testing:

  • Multi-IBX deployment testing (SG1 + HK1 + TY3 + SY3 as applicable)
  • Per-jurisdiction leverage cap configuration testing
  • Asian-script document verification testing with production document samples
  • Per-jurisdiction rail integration testing across operator’s geography
  • Per-jurisdiction transaction reporting testing for locally-licensed entities

Section 10: Decision documentation references

APAC-specific documentation:

  • Per-jurisdiction procurement extension rationale beyond EU defaults
  • Multi-jurisdiction supervisory examination readiness framework
  • Per-jurisdiction crypto authorisation framework if applicable