Today. The Binta open-source stack is self-hostable software. For paid production use, operators either (a) run it under a licensed BaaS partner as that partner's agent, or (b) self-host inside their own regulatory perimeter. Neither path makes Binta the money transmitter.
Target state. Over the next 3-4 years we're building out full US send-side licensing (FinCEN MSB + state MTLs in all 49 states that require them) and receive-side licenses in our top corridors (CBN IMTO in Nigeria, Casa de Cambio in Mexico, foreign exchange corp in the Philippines).
| Jurisdiction | Role | Status | Target |
|---|---|---|---|
| US — FinCEN MSB | Send side (federal) | Not registered | Phase 2 (2026) |
| US — Texas MTL | Send side | Not licensed | Phase 2 (2027) |
| US — Georgia MTL | Send side | Not licensed | Phase 2 (2027) |
| US — remaining 47 states | Send side | Not licensed | Phase 3 (2028) |
| Nigeria — CBN IMTO | Receive side | Via partner | Phase 4 (2029) |
| Mexico — Casa de Cambio | Receive side | Via partner | Phase 4 (2029) |
Who holds the license when you send money today
Until Binta's own MTLs are granted, every live transfer runs through a licensed BaaS partner (Rapyd, Thunes, or Nium — comparison doc still in flight). That partner is the money transmitter of record. Binta is their technology provider and, in some configurations, their registered agent.
What happens if a BaaS partner goes down
Our commitment is to maintain a second BaaS adapter live for a different corridor so we can migrate at least one corridor within 72 hours of a partner failure. Transfers in progress at the failed partner would complete through that partner's resolution process; new transfers would route through the backup.