Why cross-border payment infrastructure is uniquely demanding
Cross-border payments combine three workloads that are individually demanding and become extreme when combined: low-latency transactional processing, cryptographic key management for signing, and jurisdiction-aware compliance routing. Single-cloud single-region deployment often introduces latency on intra-corridor flows, exposes signing infrastructure to upstream provider availability, and forces compliance posture to match the cloud provider's geographic footprint rather than the operator's. We architect deployments that decouple these concerns: latency-sensitive flows on the lowest-latency network path, signing infrastructure on isolated bare-metal, compliance posture aligned to the operator's licensing footprint.
Architecture for payment platforms
A standard payment platform deployment runs application logic across active-active regions in Alibaba Cloud Singapore and Tencent Cloud Hong Kong, with origin protection at Cloudflare edge. Signing and key-management runs on dedicated bare-metal HSMs with multi-sig key shards distributed across geographically separated DCs (Singapore, Hong Kong, Tokyo). Compliance routing — sanctions screening, jurisdiction-of-origin validation, BSA/AML triggering — runs as a separate service tier with its own audit log and immutable storage. Settlement reconciliation runs on a delayed batch tier to avoid coupling to live transaction throughput.
Settlement flexibility
We support multiple settlement rails based on the operator's licensing and counterparty profile: SWIFT MT103 for traditional bank-to-bank, regional fast-payment rails (FAST in Singapore, FPS in Hong Kong, PayNet in Malaysia), and stablecoin (USDT TRC20/ERC20, USDC ERC20) where commercially appropriate. Stablecoin settlement specifically aggregates the operator's cloud bills across providers (AWS, Alibaba, Tencent, BytePlus, Cloudflare) into a single monthly invoice settled on-chain, with our broker fee at +1% of provider list price — fully transparent, no hidden markup on provider invoices.
Compliance posture
We work with operators that maintain appropriate corporate registration and visible compliance posture in their operating jurisdictions. We screen all stablecoin receiving addresses against OFAC SDN, EU/UK consolidated sanctions lists, and known mixer-exposure profiles via Chainalysis-supported tooling. We do not accept payment from sanctioned jurisdictions, OFAC SDN-listed entities, or addresses with direct sanctioned-entity exposure. We do not advise on regulatory arbitrage; we do help operators build infrastructure that meets their existing licensing obligations across multiple jurisdictions.
Anonymized case outline — A regional payment platform with USD $34,000/month cloud spend across AWS Singapore, Cloudflare, and BytePlus had its traditional banking relationship strained by the volume and pattern of cloud-related international wires. After migrating to a consolidated stablecoin invoicing model with our broker, the monthly settlement cycle compressed from 9 days (waiting for SWIFT) to 12 minutes (on-chain confirmation). Effective infrastructure cost increased only 1% from broker fee. Operational continuity improved measurably and the platform regained banking-relationship stability for its non-cloud operations.
FAQ
How does the +1% broker fee compare to typical reseller markups?
Typical APAC resellers mark up provider list price by 5–15%, or sell at list price without migration support. We pass through provider list price with a transparent +1% fee. Our economics come from cross-customer volume aggregation, not per-customer markup.
Can settlement be split across rails?
Yes. Some operators settle 80% via stablecoin for cloud bills and 20% via wire for support hours and one-time engagement fees.
How is stablecoin/USD price exposure handled?
We use the CoinMarketCap median USDT/USD or USDC/USD price at month-end UTC 00:00. Historical deviation is within ±0.3%. Deviations under 0.5% are absorbed; above 0.5% triggers re-quote.
Which stablecoins are supported?
USDT TRC20, USDT ERC20, USDC ERC20. We do not accept algorithmic or non-fully-fiat-backed stablecoins.
Talk to our infrastructure team
MNDA standard. Multi-channel: email, scheduled call, or Telegram. We respond within 4 business hours.