CROSS-BORDER PAYMENTS DEVELOPMENT
PROPELOO engineers cross-border payment systems — multi-currency ledger, FX rate management, stablecoin-based settlement rails, correspondent banking integration, SWIFT/SEPA/SWIFT GPI connectivity, compliance-aware payment routing, and the reconciliation layer that tracks every dollar across currencies and jurisdictions. Cross-border payments fail at compliance bottlenecks or FX opacity — not at technical complexity.
Cross-border payments involve at least two currencies, two banking systems, correspondent banking relationships, FX conversion at some point in the payment chain, and compliance checks at every jurisdiction the payment passes through. The technical complexity is manageable. The operational complexity — correspondent banking relationships, FX rate management, compliance across jurisdictions, reconciliation across multiple rails — is where most cross-border payment projects underestimate scope. PROPELOO builds cross-border payment infrastructure with the full operational complexity accounted for: multi-currency ledger that tracks balances by currency and jurisdiction, transparent FX rate management with rate lock for the user, compliance-aware routing that selects payment rails based on the sender/recipient jurisdictions and currencies, and stablecoin settlement rails as an alternative to correspondent banking for supported corridors.
Multi-currency ledger, FX management, payment rails, and compliance are each distinct problems.
Double-entry ledger with currency denomination on every entry. Customer balances in each currency. FX conversion creates a buy entry in one currency and a sell entry in another. P&L tracking for FX spread earned. Nostro/vostro position tracking per correspondent bank per currency.
Real-time FX rate sourcing from multiple providers (Open Exchange Rates, XE, OANDA, bank feeds). Mid-market rate with configurable spread markup. Rate lock for time-sensitive transactions (rate guaranteed for N seconds). FX rate audit trail — every rate applied to a transaction logged.
Corridor-optimised routing: SWIFT for G10 currencies institutional, SEPA for EUR intra-EU, ACH for USD domestic, Faster Payments for GBP, local schemes for emerging market corridors. Stablecoin (USDC/USDT) for corridors where traditional banking is slow or expensive.
Stablecoin-based cross-border settlement: sender converts to USDC, transfers on-chain (Polygon/Stellar), recipient converts USDC to local currency. 24/7 settlement, transparent on-chain trail, competitive rates for supported corridors.
FATF Travel Rule: transmit sender/recipient information for transactions above threshold. Sanctions screening on both sender and recipient. OFAC screening for USD-touching transactions. Correspondent bank due diligence. Currency controls for restricted destinations.
Daily reconciliation across all payment rails: SWIFT MT940 statement matching, SEPA CAMT reconciliation, stablecoin on-chain transaction matching. Nostro account balance reconciliation against internal ledger. Break investigation workflow.
Cross-border payments are a compliance problem with a payments wrapper. The technical implementation is the easy part.
There is no single cross-border payment solution. Each currency corridor (USD-INR, EUR-NGN, GBP-MXN) has different optimal rails, different compliance requirements, different settlement times, and different FX cost structures. A system that routes all corridors through the same path will be suboptimal for most of them. Corridor-specific routing logic is the correct architecture.
Axiom: OPTIMISE PER CORRIDOR
The opacity of traditional cross-border FX pricing (mid-market rate buried in fees, recipient gets less than sender thinks) is the primary user complaint about legacy systems. A cross-border payment product that shows the exact exchange rate, the exact fee, and the exact recipient amount before the sender commits — and locks that rate — differentiates on transparency.
Axiom: RATE TRANSPARENCY IS THE PRODUCT
For corridors where correspondent banking is expensive (multiple intermediary banks), slow (2-5 business days) or unreliable (funds stuck in correspondent bank queue), stablecoin settlement offers competitive economics: on-chain settlement in minutes, transparent trail, competitive FX conversion at each end. Not every corridor benefits — but for remittance corridors to emerging markets, stablecoin rails can reduce cost by 50-70%.
Axiom: STABLECOIN FOR HIGH-COST CORRIDORS
These choices define your corridor economics, compliance posture and settlement speed.
Impact: Hybrid: local payment schemes for supported corridors (USD-to-USD, EUR-to-EUR), stablecoin for emerging market corridors where correspondent banking is expensive, SWIFT as fallback for unsupported corridors.
Impact: FX provider API (Currency Cloud, Wise) for launch. Transition to in-house or bank partner FX when volume justifies the margin improvement.
Impact: TRISA or OpenVASP for crypto-native platforms. Manual bilateral for initial compliance if transaction volume is low. TRUST for US-regulated entities.
Impact: Single ledger with currency denomination is the correct accounting model for multi-currency platforms. Account-per-currency is simpler initially but creates reconciliation complexity when FX conversion is frequent.
Consumer remittance service — multi-corridor support, transparent FX, stablecoin settlement for emerging markets, mobile UX.
Business payment platform — multi-currency accounts, SWIFT integration, bulk payment upload, FX rate management, invoice matching.
Stablecoin-based cross-border — receive in crypto, settle in fiat at destination, KYC/AML on both ends.
Multi-currency capability for an existing FinTech — currency wallet, FX conversion, international transfers.
International contractor/employee payroll — multi-currency payroll calculation, local currency payout, FX optimisation.
Multi-rail connectivity with multi-currency accounting.
Stack: SWIFT GPI API, SEPA CAMT/PAIN XML, Currencycloud / Wise API, Stellar / Polygon (stablecoin), Local scheme connectors
Stack: Open Exchange Rates API, OANDA institutional feed, Rate lock engine (Redis TTL), FX spread configuration, Rate audit log
Stack: PostgreSQL (multi-currency), Double-entry with FX entries, Nostro position tracking, Reconciliation job, FX gain/loss reporting
Stack: Comply Advantage (sanctions), Travel Rule (TRISA), AML transaction monitoring, Currency control rules, OFAC screening
A sanctions screening miss on a cross-border payment creates regulatory liability in multiple jurisdictions simultaneously.
A USD-touching transaction is subject to OFAC requirements regardless of the originating jurisdiction. All cross-border payments must be screened against OFAC in addition to local sanctions lists.
A compromised FX rate data source can cause the system to offer rates that are unprofitable or that the institution cannot hedge. Rate anomaly detection (reject rates more than X% from market mid) and multiple rate source validation protect against this.
Nostro/vostro account credentials used for SWIFT connectivity must be secured equivalently to customer fund accounts. Multi-factor authentication on all correspondent banking portals. Payment instruction verification procedures.
Authorised Push Payment (APP) fraud is the primary fraud vector for cross-border payments. Beneficiary name verification, payment delay for first-time beneficiaries, large payment confirmation callbacks, and beneficiary pattern analysis reduce APP fraud exposure.
Target corridors, rail selection per corridor, FX provider selection, compliance requirements per jurisdiction.
Ledger design, currency entries, nostro tracking, FX accounting.
Rate sourcing, spread configuration, rate lock, FX audit trail.
SWIFT connectivity, local scheme connectors, stablecoin settlement setup.
Sanctions screening, AML monitoring, Travel Rule, currency control rules.
Multi-rail reconciliation, nostro account matching, discrepancy workflow.
Pilot corridor go-live, monitoring, FX exposure management, additional corridors.
The primary FX exposure management approach: rate-lock for customer transactions (we buy FX from the provider at the moment the customer locks the rate, eliminating exposure between quote and settlement). For higher-volume operations, natural hedging (matching buy and sell flows in the same currency pair) reduces the FX purchased. Institutional FX forwards for known future exposures.
In most jurisdictions, yes — transmitting money requires a licence (MSB registration in the US, EMI licence in the UK/EU, etc.). We build the technical infrastructure. Your legal team handles the licensing. We can share which licensing framework applies to your product model, but we are engineers, not regulatory advisors.
Sender converts fiat to USDC (via an on-ramp partner like MoonPay or directly via exchange). USDC transferred on-chain (Polygon or Stellar for low fees) to a wallet at the destination. Destination wallet converts USDC to local currency via an off-ramp partner or local exchange. The sender sees a fiat-to-fiat flow; the stablecoin is infrastructure.
The Travel Rule requires VASPs (Virtual Asset Service Providers) to transmit sender and recipient information alongside crypto transactions above a threshold ($1000 in the US, CHF 1000 in Switzerland). If your platform transfers crypto on behalf of customers, you are likely a VASP and subject to Travel Rule. We implement Travel Rule compliance using TRISA or OpenVASP protocols.
We construct two-way translation engines between ISO 20022 financial message standards (pacs.008 credit transfers, pacs.002 payment status reports) and public/private blockchain transactions. This enables core banking systems to communicate seamlessly with smart contract settlement ledgers without disrupting legacy reporting.
Traditional correspondent banking via SWIFT takes 1–5 business days, incurs multiple intermediary fee deductions ($25–$75 per transfer), and has limited weekend availability. Stablecoin settlement over networks like Polygon, Solana, or Stellar completes within seconds for fractions of a cent, enabling continuous 24/7 liquidity.
Our automated treasury rebalancing module continuously monitors balance thresholds across local payout bank accounts and crypto exchange liquidity pools. Algorithmic liquidity sweeps automatically convert and route capital to high-demand corridors just-in-time, minimizing trapped idle float.
Every transaction is routed through pre-execution compliance pipelines that screen remitter and beneficiary identities against global watchlists (OFAC, PEP, UN, EU sanctions). On-chain addresses are verified via blockchain intelligence APIs to intercept tainted funds before settlement.