Condor OTC, cross-border payments and exchange

Condor OTC moves and converts value across currencies, rails and providers for cross-border operations, and gives the desk the tooling to run it day to day.

I am the CTO and technical lead.

This case study contains no proprietary code or confidential data. It describes the product, my role and how it is designed.

What I built

• Financial provider integrations for payments and exchange, each isolated behind a common internal interface, so a provider can be added or swapped without touching core logic.
• Multi-currency, multi-rail flows across several corridors, including instant local rails and US, EU and UK payment methods.
• Beneficiary verification for regulated corridors, with explicit match and mismatch handling.
• Compliance gating on regulated rails: where the regulation requires it, the operation does not go out without the endorsement.
• Revenue and business-metrics tooling: fee, margin and volume reporting for the desk.
• Internal tooling the operations team uses every day.

How it is designed

It is an integration-heavy architecture, with every provider behind the same internal interface.

On anything that touches money, correctness comes first. Fees, netting and settlement are reconciled against real provider behaviour before shipping.

The operations tooling is built for a real desk workload: fast and with no room for error.

Status

Live in production, supporting real international operations across several currency corridors.