Cross Border Payments

The compliance service runs as an independent microservice within the transaction flow, with sanctions lists cached in Redis rather than fetched from an external API on every transaction. This means screening happens against a current local copy of the list, which is refreshed on a defined schedule, rather than making a live API call that adds variable latency to every transfer. When a transaction matches a sanctions entry, it is flagged and held for review rather than silently failed, giving the compliance team a clear audit trail for each flagged case.

It means the core infrastructure — compliance screening, FX rate management, transfer orchestration, beneficiary management — is already built and operating in production. A white-label partner deploys their own branding, configures their banking partner connections for the target corridor, and sets their fee and FX margin parameters. They do not rebuild the compliance framework or the transfer logic from scratch. For regulated market entry, this is the difference between a multi-month build and a weeks-long configuration and licensing process.

FX rates are fetched from the rate source on a defined refresh cycle and cached in Redis, so the rate a user sees is current without a live API call on every page load. When a user initiates a transfer, the displayed rate is locked for a defined window — typically sufficient to complete the confirmation flow — after which the rate refreshes if the transaction has not been submitted. The fee breakdown displayed alongside the rate is calculated in real time based on the transfer amount, corridor, and applicable fee structure, with no hidden charges applied at settlement.

The platform has live implementations covering OFAC screening, active sanctions list compliance, and velocity limit enforcement. KYC integration is handled at the onboarding layer and varies by jurisdiction — connecting to local identity verification providers as required by the regulatory environment in each market. For new corridors, we assess the specific compliance requirements during the discovery phase and configure the compliance service accordingly before go-live.

Each microservice — auth, transfer, compliance, FX, beneficiary, notifications — has its own deployment pipeline. A change to the compliance service does not require a full platform release and does not risk regression in the transfer or FX services. This is particularly relevant in regulated environments where compliance rule changes need to be deployed quickly, tested in isolation, and audited independently. The mono-repo structure keeps shared code consistent across services while preserving independent deployability.

For a market where banking partner APIs are accessible and regulatory requirements are scoped, adding a new country corridor typically takes six to ten weeks from partner onboarding to live transactions. The compliance service configuration, FX rate integration for the new corridor, and UI localization are the primary variables. Markets with more complex regulatory onboarding — requiring new licensing or novel KYC integrations — add time at the pre-build discovery and licensing phase, not in the technical build itself.

It means the platform is operating at roughly half its current infrastructure capacity under live daily transaction volumes. When transaction volume grows — through organic user growth or new country additions — the existing infrastructure absorbs that growth without requiring an immediate re-architecture. AWS ECS scales horizontally when utilization thresholds are breached, so the scaling is automatic rather than requiring manual intervention. The 58% figure comes from post-optimization production monitoring, not a load test projection.

The platform is handed over production-ready, load-tested across target corridors, and documented at the service and API level. Your team can operate and extend it independently. We do not build on proprietary frameworks that require ongoing GeekyAnts involvement to run. If a formal support or retainer arrangement post-launch makes sense for your team, that is a separate conversation we are happy to have.