Onboarding and identity
Document capture, liveness and identity verification through pluggable providers, with data-source cross-checks, re-verification triggers and a full evidence trail attached to every customer record.
Corridor
Corridor is the operating system for a cross-border money transfer business. Customer onboarding, identity verification, sanctions and PEP screening, risk scoring, transaction limits, multi-provider payout routing, treasury and reconciliation — designed as one system, because in payments they are one system.
Live in production In production today, clearing roughly £2 million per month.
£2M/month
settled through the platform in live production
190migrations
of modelled financial and compliance domain
15countries
live destination corridors from a GBP base
24/7
operation with automated monitoring and alerting
01 / The problem
Anyone can move a balance from A to B. The hard part is everything wrapped around it: proving who the sender is, screening them and their beneficiary against sanctions and PEP lists, applying the right limits for their risk profile, choosing a payout route that is actually up right now, holding enough float in the right currency, and reconstructing all of it two years later when someone asks.
Most operators assemble that from a patchwork — a KYC vendor here, a spreadsheet there, a payout partner portal in another tab. The gaps between those tools are exactly where losses and compliance failures live.
Corridor closes the gaps by making the whole lifecycle one modelled system, with one ledger, one audit trail, and one place where a compliance officer can answer any question about any transaction.
02 / In operation
The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.
Illustrative interface with sample data — no customer records are shown.
03 / Capabilities
9 capability areas, each built because the operation breaks without it.
Document capture, liveness and identity verification through pluggable providers, with data-source cross-checks, re-verification triggers and a full evidence trail attached to every customer record.
Sanctions, PEP and adverse-media screening run through an orchestration layer that consults multiple providers and reconciles their verdicts, so a single provider outage or false negative does not become your compliance failure.
A configurable rules engine scores senders and transactions on behaviour, velocity, corridor, counterparty and linked-account signals. Hard rules block; soft rules queue for review. Every decision records the inputs that produced it.
Per-customer, per-corridor and per-period limits derived from verification tier and risk band, enforced at the point of transaction rather than discovered in a monthly report.
Transactions are routed across multiple payout partners by corridor, cost, availability and live provider health. When a route degrades, traffic moves without an operator noticing.
A rate engine that pulls from multiple providers, applies your margin policy per corridor and product, and calculates fees transparently — with the exact rate and fee that applied stored against the transaction forever.
A purpose-built investigation surface: search across senders, recipients, devices, cards and transactions; follow linked accounts; reconstruct a customer’s entire history in one view for a SAR or a regulator request.
Float positions per provider and currency, settlement files, partner statements and automated reconciliation that surfaces breaks the same day rather than at month-end.
Native mobile apps for senders with device binding and mobile security controls, plus branch and agent tooling for assisted transactions — all against the same core.
04 / Surface area
Breadth is only an asset when the parts share a data model. Every module here reads and writes the same records — there is no export step between them.
05 / Architecture
A modular monolith on a mature PHP/Laravel core with a strongly-modelled financial domain, background workers for everything that must not block a customer, and provider adapters isolated behind stable internal contracts so a partner can be swapped without touching the transaction lifecycle.
06 / Integrations
Third parties are first-class parts of the architecture, isolated behind stable internal contracts so any one of them can be replaced without touching the core.
Document, biometric and data-source verification providers behind one adapter interface.
Sanctions, PEP and adverse-media providers, orchestrated and reconciled rather than trusted singly.
PCI-scoped card collection with tokenisation and 3-D Secure.
Bank, mobile money and cash-collection partners across multiple corridors.
Transactional SMS, push notification and email delivery with per-channel fallback.
Real-time alerts to the operations team the moment a route, provider or threshold moves.
Cross-border payments
We can walk you through the live platform, talk about how it maps onto how you work today, and be honest about where it does not fit.