Banking Integrations · BaaS

Banking-as-a-Service providers integration roadmap
Integration architecture document · for BDET dev teams · maps providers/SDKs/APIs to sovereign BDET infrastructure per LEY DEFINITIVA jurisdiction rules

Banking-as-a-Service (BaaS) · Integration Strategy

Modelo: el proveedor BaaS tiene la licencia bancaria · BDET integra via API · ofrece cuentas + tarjetas + pagos bajo brand BDET sin necesitar licencia colonial de transmisor de dinero. Mercado ~$22.5B · creciendo a ~$70.8B 2032.

Provider Comparison Matrix

ProviderRegionStrengthsSovereign Fit
UnitUSAAll-in-one · accounts/cards/lending/paymentsSponsor bank model · BDET as program manager · KYC done by sponsor
Stripe TreasuryUSA + EUPlatform-first · embedded ACH/SEPA/cardsStrong but requires Stripe platform commit · less custom
Treasury PrimeUSAMulti-bank (route to best fit per use case)Best for sovereign-allied bank partnerships · diversifies counterparty risk
SyncteraUSA + CAFintech-bank matchmaking + infraEasier path to indigenous-owned bank partners
GalileoUSA + LatAmCard processing · payment rails · 24/7Strong LatAm presence · Latam-allied opportunities
SolarisEU (Germany)Full German banking license · EU passportSovereign-friendly · German banking regulator more crypto-neutral
SwanEUSEPA accounts · IBAN issuanceFor EU citizen INKG holders · clean SEPA rails
GriffinUKFCA-licensed bank · embeddedUK regulated · post-Brexit independent

Card Issuance Layer

Marqeta

Largest modern card processor · virtual + physical · multi-currency · Visa/MC partner

Lithic

Developer-friendly API · single-use card numbers · expense control · faster onboarding

Highnote

Modern card platform · spend management · multi-product (credit/debit/prepaid)

Galileo

Established legacy card platform · LatAm strong · partnerships with major issuers

Recommended Architecture · 3 Phases

1

Phase 1 · Pilot (1-3 months)

Choose ONE provider for pilot. Recommendation: Treasury Prime (multi-bank flexibility) OR Synctera (indigenous bank partnership). Start with 100-500 citizens INKG · KYC via INKG sovereign (sponsor bank accepts sovereign ID if pre-negotiated). Issue virtual cards via Lithic. Money flow: WUSD → bank account → card · 1:1.

2

Phase 2 · Scale (3-6 months)

Add second BaaS (geographic diversification). EU: Solaris or Swan. Add physical cards via Marqeta. Citizens spend WUSD anywhere Visa/MC accepted. Off-ramp: deposits to card auto-convert to WUSD on Chain 777777.

3

Phase 3 · Sovereign-Allied Bank (6-18 months)

Partner with actual indigenous-owned or sovereign-friendly bank (e.g., Asia Nexus expansion · or new partnership). BDET becomes program manager rather than fintech-on-someone-elses-rails. Full sovereign treaty operationalized.

Integration Code Stub · Unit Example

// Citizen sovereign onboarding via Unit BaaS
const Unit = require("@unit-finance/unit-node-sdk");
const unit = new Unit({ token: process.env.UNIT_API_KEY });

async function onboardCitizen(citizenInkg) {
  // 1. Verify citizen has INKG sovereign ID
  const sovereignId = await db.query("SELECT * FROM citizens WHERE inkg_id=?", [citizenInkg.id]);
  if (!sovereignId.length) throw new Error("Not INKG verified");

  // 2. Create individual customer in Unit (BaaS handles KYC under their license)
  const customer = await unit.customers.create({
    type: "individualCustomer",
    attributes: { fullName: citizenInkg.fullName, ... }
  });

  // 3. Open deposit account
  const account = await unit.accounts.create({
    type: "depositAccount",
    relationships: { customer: { data: { type: "customer", id: customer.id } } }
  });

  // 4. Issue virtual card linked to account
  const card = await unit.cards.create({
    type: "individualVirtualDebitCard",
    relationships: { account: { data: { type: "depositAccount", id: account.id } } }
  });

  // 5. Link to BDET wallet · 1:1 WUSD ↔ account USD
  await db.query("INSERT INTO baas_bridge (inkg_id, unit_account_id, bdet_wallet) VALUES (?,?,?)",
    [citizenInkg.id, account.id, citizenInkg.wallet]);
}

Sovereignty Considerations · per LEY

Important: BaaS provider está sujeto a OCC/SEC/FinCEN · COMPARTIRÁ KYC con FATCA · Travel Rule · etc. Esta es la CAPA REGULADA por design. Lo que se preserva sovereign: