One product layer. One ledger. Provider adapters underneath.
FYNIX is the product, orchestration, and support layer around regulated partner infrastructure. This is what actually lives inside the platform — and why we built it this way.
A single backend. Adapters, not microservices.
Our Express backend is the integration host. Mock providers get replaced by real provider adapters for card top-ups, virtual accounts, payouts, KYC and email — but everything runs against one database, one audit log, and one route layer. That keeps the pilot debuggable, portable, and easy to onboard engineers into.
What lives inside FYNIX
Onboarding & KYC
Student and worker signup, sponsor / parent KYC, institution linking, agent vetting workflow with FYNIX admin clearance.
Wallets & ledger
Internal ledger as the canonical record of every transaction — even when balance or status updates come from partner providers. Reconciliation-first.
Named funding accounts
vIBAN issuance and funding-reference generation for USD, EUR, GBP and AED through our banking partners — with capacity to extend to SGD, MYR and INR.
Payouts & FX
Outbound payouts through our global payout partner, corridor-tailored FX pricing, and last-mile local rails through our APAC partner for MYR / SGD / INR / LKR.
Compliance & MLRO
Role-aware admin, MLRO, support, agent, super-agent and student consoles. AML report catalog, audit trails, and SAR workflows.
Support & operations
Dispute, refund, exception, reversal and reconciliation workflows. Human-readable dropdowns and reports on top of raw database keys.
Country channels, built into the platform.
Country super-agents control geographies, appoint agents, view the students and workers brought in by their network, and escalate onboarding issues to FYNIX admin. Commission splits are configurable by geography, volume, and subscription plan — with a formal vetting path before any agent is activated.
- ✓ Super-agent geography control and sub-agent appointment
- ✓ KYC + vetting checklist + FYNIX admin clearance for every agent
- ✓ Configurable commission splits by geography, volume, plan
- ✓ Auditable approval path — no uncontrolled channel onboarding
100K to 500K
Year-1 end clients via partner channels, with a ~70/30 student/worker split across launch corridors.
Backend cleanup before backend growth
Our next engineering hire is a Backend Platform Engineer whose mandate is cleanup, standardization and stabilization — not senior ownership of banking architecture, compliance interpretation, settlement design, or partner relationships. That mandate is exactly what a maintainable MVP needs.
Clean service boundaries
Onboarding, auth, wallet, KYC, transactions, notifications and admin operations — separated so future integrations don't compound technical debt.
Reusable conventions
API design, config, logging, tracing, error handling, retries, service templates and internal libraries. Provider integrations reuse patterns instead of inventing them.
Metrics, alerts, repo hygiene
Dashboards on critical flows, structured debugging paths, branching discipline, PR quality, documentation standards, CI basics. Safer to scale, easier to operate.