CTO, Product Architect and ISMS Manager, Cede Technologies
Voye
Cross-border remittance and peer-to-peer FX for diaspora communities, on top of a B2B payments and treasury platform.
# voye.yaml
project: Voye
org: Cede Technologies
role: "CTO, Product Architect and ISMS Manager"
domain: [payments]
ships_to: [iOS, Android, Web, B2B API]
stack:
- Flutter
- Dart
- Go
- Node.js
- PostgreSQL
- AWS RDS
- AWS WAF
- GuardDuty
- CloudWatch
- UnleashContext
Cede is a financial infrastructure company covering global payments and settlement, treasury, risk and working capital. Voye is its consumer product: a multi-currency wallet for sending GBP and CAD to Nigeria and Kenya, plus a P2P community that brings informal diaspora currency exchange into a regulated, visible channel.
I led product and engineering across both sides of the business, the retail app and the institutional platform behind it, while also carrying security, DevOps and compliance.
What I owned
- Led a cross-functional team of about ten across mobile, backend, product and QA, plus an external development team working alongside it.
- Designed and shipped the production transaction-monitoring system: velocity rules, cross-platform tracking, geo-fencing and device-change detection.
- Inherited a React Native contractor codebase, kept it alive for two months, then led the migration to Flutter as a platform decision.
- Designed the B2B partner auth layer: HMAC-SHA256 request signing in middleware with a shadow-user model, so no existing handler had to change.
- Set trunk-based development with Unleash feature flags as the branching strategy.
- Served as ISMS Manager and owned the compliance programme end to end: SOC 2, PCI-DSS v4.0.1, ISO 27001 and 22301, KYC and AML.
- Wrote and delivered the secure-coding training for engineering and product (July 2026): a threat model for FX, NDPA 2023 and CBN cybersecurity duties, PCI-DSS and the OWASP Top 10:2025 mapped to our Flutter, Node, React and AWS stack, ending in a live find-the-vuln exercise.
- Moved the edge to AWS WAF after a ModSecurity and OWASP CRS incident, exported RDS logs to CloudWatch and fixed security headers on the public site.
- Built the product analytics model: KYC funnel, cohort retention and corridor-level conversion.
- Researched and compared UK and Canada payment rails (open banking, card acquiring, Interac) for corridor expansion.
Decisions
Fraud signals inside the payment path
A cross-border platform can't wait for a nightly review to spot fraud. I designed and shipped a transaction-monitoring system that raises fraud signals in real time: velocity rules, tracking across platforms, geo-fencing and device-change detection. It is one of the things I am proudest of at Cede.
Flutter over keeping React Native
The inherited app worked, but every new corridor meant new KYC and payout screens in two codebases of mixed quality. One Flutter codebase with a shared design system made each new market a configuration task instead of a rewrite.
Partner auth without touching handlers
Institutional partners needed signed requests. Putting HMAC verification and a shadow user in middleware meant the existing business logic saw a normal authenticated user, so the change shipped without touching existing endpoints.
Flags before branches
With a small team shipping into regulated corridors, long-lived branches were the biggest source of risk. Trunk-based development with Unleash let us merge daily and release by market.
Results
Highlighted figures are results from my role. The rest are public context about the product, with sources.