Why this dispatch exists
Seventh per-archetype RFP template covering Archetype G per the LATAM archetype dispatch.
Section 1: Requirement overview
The requirement is the LATAM CFD broker tech stack for an operator with either local LATAM licensing (Brazil CVM, Mexico CNBV, Argentina CNV, Chile CMF, Colombia SFC) or EU-licensed via non-resident solicitation arrangements serving Brazil + Mexico + Argentina + wider LATAM client geographies.
Section 2: Vendor evaluation categories required
- Brokerage hosting (FR2 if non-resident solicitation; São Paulo + Mexico City if locally licensed)
- Trading platforms (MT5 with Spanish + Brazilian Portuguese distinct localisation tracks + cTrader for differentiation)
- LP procurement (CFD PoPs typical; LATAM currency LPs only for explicit local-currency demand)
- Risk management (per-jurisdiction leverage caps if locally licensed; ESMA-default for non-resident solicitation)
- KYC + AML (Sumsub or Veriff with Brazil CPF + RG + CNH + Mexico CURP + RFC + INE + Argentina DNI + Chile RUT + Colombia cedula support)
- RegTech (Eventus Validus for trade surveillance + Cappitech for EU MiFIR if EU-passported + Behavox or Smarsh with Spanish + Portuguese language detection)
- Broker CRM (B2Core or Match-Trader CRM multi-tenant with distinct Spanish + Brazilian Portuguese tracks)
- Payments (6-12 PSPs covering Pix + boleto Brazil + SPEI + OXXO Mexico + DEBIN Argentina + local rails Chile/Colombia + LATAM specialists EBANX + dLocal + PagBrasil + AstroPay)
- IB management (per-jurisdiction tax disclosure for IB compensation including Brazil-specific)
- Broker analytics (Trading Central + Solitics with explicit Spanish + Brazilian Portuguese content tracks)
- Copy trading (cTrader Copy + ZuluTrade for LATAM IB network depth)
- Crypto exchange WL (Brazil Lei 14.478/22 framework if Brazil crypto authorisation in scope; Mexico Fintech Law restrictive)
Section 3: Universal vendor requirements
Apply the five universal dimensions from the RFP scoring framework opener.
Section 4: Per-pillar requirements
LATAM-specific per-pillar emphasis:
- Spanish + Brazilian Portuguese as distinct localisation requirements (not interchangeable)
- Brazil Pix integration mandatory for any operator with material Brazilian retail client mix
- Per-jurisdiction crypto regulatory regime support (Brazil Lei 14.478/22, Mexico Fintech Law, Argentina less formal)
- FX conversion handling (LATAM retail clients typically trade in USD/EUR not local currency)
- LATAM-specific document support across operator’s jurisdiction set
- Per-jurisdiction IB tax disclosure including Brazil-specific tax handling
- Non-resident-solicitation vs local-licensing decision affects every downstream procurement
Section 5: LATAM archetype customisation (weight multipliers)
Per the Phase 4 opener customisation layer:
- P5 (Spanish + Portuguese distinct) x 1.5
- PMT1 (Pix integration plus LATAM PSPs) x 1.5
- KYC1 (LATAM documents) x 1.3
- IB4 (Brazil tax handling) x 1.5
Section 6: Disqualification thresholds checklist
- ☐ Brazilian Portuguese native localisation depth distinct from Spanish for CRM + KYC + analytics + comms surveillance
- ☐ Pix Cobranca + Pix Saque capability for PSP if Brazilian client mix material
- ☐ Brazil-specific tax disclosure for IB compensation handling if applicable
- ☐ LATAM document verification for KYC vendor (CPF + RG + CURP + INE + DNI minimum)
- ☐ Brazil Lei 14.478/22 framework support for crypto venue if applicable
Section 7: Vendor scoring rubric reference
LATAM-specific demo emphasis:
- Brazilian Portuguese localisation depth distinct from Spanish demonstration
- Pix integration demonstration including Pix Cobranca + Pix Saque + Pix Automatico
- LATAM document verification with operator-provided test documents per jurisdiction
- Brazil-specific IB tax disclosure demonstration if applicable
Section 8: Reference customer validation
- KYC: minimum 2 LATAM operators with Brazil CPF + RG + CNH verification operational tenure
- Payments: minimum 2 LATAM operators with Pix Cobranca + Pix Saque operational tenure
- CRM: minimum 2 LATAM operators with distinct Spanish + Brazilian Portuguese tracks deployment
- IB management: minimum 2 LATAM operators with Brazil-specific tax disclosure operational tenure
Section 9: Integration testing scope
LATAM-specific integration testing:
- Spanish + Brazilian Portuguese client cabinet testing as distinct tracks
- Pix integration end-to-end testing with Brazilian PSP
- LATAM document verification testing with production document samples
- Per-jurisdiction tax disclosure integration testing for IB compensation
Section 10: Decision documentation references
LATAM-specific documentation:
- Non-resident-solicitation vs local-licensing strategic decision rationale
- Brazil CVM enforcement evolution forward-compatibility evaluation
- Pix integration depth procurement rationale
- Spanish + Brazilian Portuguese distinct localisation rationale