Skydo.
Money crossing a border is a reconciliation problem wearing a product’s clothes.
- Client
- Skydo
- Sector
- Fintech
- Scope
- App + web + admin
- Stack
- React, Node.js, TypeScript
Cross-border payments for exporters. App, web and admin built around a ledger that has to reconcile to the cent.
What made it hard.
Cross-border payments touch multiple providers, currencies and regulators before settling. Every hop can fail, retry or partially succeed, and the customer sees one number that has to be correct regardless.
Onboarding compliance
KYC and AML checks have to satisfy regulation without becoming the reason users abandon signup.
Provider dependency
Payment rails fail in ways you do not control. The system has to degrade without losing money.
Audit expectations
Regulators ask what happened on a specific date to a specific account. The answer has to take minutes.
What we shipped.
A payments platform across mobile, web and an internal admin console, covering onboarding and compliance checks, quoting, transfer initiation and settlement tracking.
How it holds up.
Double-entry accounting from the first commit, idempotency on every money-moving endpoint, and a reconciliation job running independently of anyone watching a dashboard.
The systemThe ledger is the source of truth and everything else reads from it. Provider integrations sit behind a normalisation layer so a rail changing its API is a contained change, and failure paths were designed before the successful ones.
Theirs, from day one.
Repositories, cloud accounts and architecture documentation sat with the client throughout. Senior engineers wrote the production code rather than specifying it.
Ask for the full metrics on a call →More fintech work.
All 42 case studies →Building something like Skydo?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.