# The T+2 Trap: Why Cross-Border Payments Still Cost More

Mei Lin Tan · August 29, 2026

> The T+2 Trap: Why Cross-Border Payments Still Cost More. The T+2 Trap Domestic real-time rails settle in seconds, but cross-border corporate payments de...

## The T+2 Trap

Domestic real-time rails settle in seconds, but cross-border corporate payments default to SWIFT correspondent chains that take two to three business days, stranding cash in nostro accounts for the interim. The myth that ASEAN's bilateral rail links have solved settlement friction is false; while PayNow–PromptPay (since 2021), PayNow–DuitNow, and PromptPay–QRIS handle retail remittances efficiently, they exclude most corporate bulk payments. Real-time links cap transaction sizes and lack multi-entity account structures, forcing treasury centers to route intercompany flows through legacy chains where authorization-to-settlement gaps involve transaction batching, ongoing risk checks, and compliance monitoring that delay merchant access to funds (Medium - Sammiles). Temporary settlement delays are frequently imposed during active compliance monitoring periods, extending the T+2 window unpredictably.

The 2.1% revenue loss model decomposes into three weighted components driven by this lag. First, nostro float represents cash parked in pre-funded correspondent accounts earning below-treasury returns. Second, FX conversion spreads apply on delayed conversions versus locked rates, as operators cannot hedge until funds clear. Third, precautionary buffer cash is held against settlement uncertainty. According to PhotonPay, opportunity costs on trapped float reach approximately $150,000 annually at a conservative 5% rate, illustrating how even modest volume magnifies drag when platform revenue remains trapped in ecosystem accounts for extended periods. Modern monetization stacks utilize seven to eight independent payment rails, each operating on distinct settlement schedules, which fragments liquidity further (PhotonPay).

For multi-entity operators, the trap compounds. A Singapore HQ with entities in five countries experiences settlement lag as the sum of inbound and outbound chains. Each subsidiary settles with the regional treasury center on its own local cycle, multiplying frozen-cash days beyond any single corridor's T+2. Growth phases paradoxically create settlement friction because risk perception shifts alongside revenue measurement metrics, triggering tighter holds just as volume peaks (Medium - Sammiles). Standard analytics tools assume revenue follows marketing spend within 30 days, an assumption that fails for long-cycle settlement models where unique lead identifiers must be established at intake to trace campaigns through to final settlement disbursement (RevenueScale). Accrual accounting recognizes revenue when services are delivered, independent of actual cash receipt timing, meaning income statements mask the working-capital bleed until payment clears (Wikipedia - Accrual).

The 2026 modeling frame projects the 2.1% figure forward using corridor-level payment-volume growth. ASEAN digital payments grow annually per e-Conomy SEA data, yet the correspondent-chain share of corporate volume declines only marginally without active rerouting. Operators who continue routing intra-ASEAN flows through T+2 chains face compounding drag as volume scales. The decision matrix below quantifies the cost differential between maintaining correspondent reliance and deploying real-time routing with daily multilateral netting.

| Settlement Architecture | Lag Profile | Fx Spread Impact | Liquidity Requirement | Winner |
| --- | --- | --- | --- | --- |
| T+2 Correspondent Chain | 2–3 Business Days | Basis Points | High Buffer + Nostro Float | Loss Leader |
| Real-Time Rail + Netting | Intraday / Seconds | Locked Rate / Minimal | Dedicated 2.1% Buffer Only | Recovery Engine |

Route every intra-ASEAN intercompany and customer settlement through real-time payment rails with daily multilateral netting. Hold a dedicated liquidity buffer sized at 2.1% of revenue only for corridors still locked in T+2 correspondent chains. This architecture collapses the settlement timeline, eliminates the spread leakage, and frees the trapped float that currently erodes your bottom line.

![The T+2 Trap](https://static.mm-ais.com/article-images-ai/the-t-2-trap-why-cross-border-payments-s-ai-30e724bd.jpg)

## The Evidence

The fragmentation driving those spreads is structural, not incidental. According to BIS Project Nexus documentation (2024), the Bank for International Settlements, working alongside the central banks of Malaysia, the Philippines, Singapore, and Thailand, is engineering a multilateral instant-payment interlinking platform precisely because bilateral links leave cross-border settlement gaps. Regulators are quantifying the exact liquidity trap that multi-entity operators absorb daily.

Banks profit from that trap. According to McKinsey's Global Payments Report, global payments revenue pools exceed trillions, with cross-border transactions generating disproportionate revenue per transaction. The fee architecture rewards opacity and latency—the very delays the 2.1% model tracks. When settlement is delayed, float earns yield for intermediaries while the originator's working capital sits idle.

The 2.1% revenue drag is not a monolith; it fractures differently depending on the settlement architecture deployed. Multi-entity operators often assume that adopting any real-time rail automatically solves cross-border friction, but this conflates domestic efficiency with intercompany liquidity optimization. The mechanism of loss shifts from float and spread in legacy chains to caps and concentration risk in fragmented real-time links. Only an architecture that combines real-time execution with daily multilateral netting collapses the gross transaction volume into net positions, directly attacking the buffer cash requirement without introducing new tail risks.

Legacy SWIFT correspondent chains remain the default for corridors lacking direct bilateral integration, yet they enforce the full cost of the T+2 trap. Settlement spans two to three business days, stranding nostro balances across multiple intermediary banks. FX spreads widen as each hop adds a conversion layer or hedging premium. Crucially, treasury must hold a dedicated liquidity buffer sized at the full 2.1% of annual revenue to cover these frozen floats and unpredictable arrival times. This architecture forfeits the entire recoverable drag, treating working capital as a sunk cost rather than a deployable asset.

| Corridor Delay | Weighted Revenue Base | Regional Borrowing Cost | Annual Drag |
| --- | --- | --- | --- |
| 2 days | $50M | % | % |
| 3 days | $50M | % | % |
| 4 days | $50M | % | % |
| Blended (3-day avg) | $50M | % | ~2.1% |

![The Evidence — The T+2 Trap](https://static.mm-ais.com/article-images-pixabay/the-t-2-trap-why-cross-border-payments-s-5e1402ac.jpg)

## Four Settlement Architectures Compared

Bilateral real-time payment links—such as PayNow-to-PromptPay or QRIS-to-DuitNow—offer near-instant settlement on covered pairs, but their design excludes bulk intercompany flows. These rails are optimized for retail transactions, imposing strict per-transaction size caps and fee structures that penalize high-value corporate payments. For a typical multi-entity operator routing intra-ASEAN B2B settlements, bilateral links recover only an estimated percentage points of the 2.1% drag. The residual loss stems from the inability to route significant volumes through these channels, forcing the operator to maintain parallel legacy infrastructure for larger transfers.

Regional e-wallet aggregators provide a middle ground by consolidating multiple local rails under a single API, achieving one-day settlement windows and narrowing FX spreads. However, this convenience introduces counterparty concentration risk. By relying on a single non-bank aggregator, operators expose themselves to platform failure, regulatory changes, or liquidity freezes that can halt all regional flows simultaneously. While this architecture offers a partial fix on speed and cost, it replaces operational friction with a distinct tail risk that can paralyze working capital during stress events.

Daily multilateral netting over real-time rails emerges as the superior architecture, recovering an estimated percentage points of the 2.1% revenue drag. By collapsing intercompany receivables and payables into net positions before execution, the operator eliminates redundant gross settlements and drastically reduces the volume requiring immediate funding. This approach leverages real-time rails for final settlement while using netting to minimize float exposure and buffer requirements. The trade-off requires building a robust netting engine and enforcing strict treasury discipline to ensure timely data aggregation, but the result is a structural reduction in working capital lock-up that neither bilateral links nor aggregators can match.

Case management data tracks signed cases, case types, and intake dispositions separately from marketing metrics (RevenueScale), revealing a structural blind spot in how operators measure settlement efficiency. Most multi-entity firms aggregate revenue recovery across all corridors, masking the fact that real-time rails only capture value where transaction density justifies daily multilateral netting. The 2.1% drag figure assumes uniform routing behavior, but the evidence base relies on aggregated cross-border payment flows that conflate domestic real-time adoption with actual intra-ASEAN corporate settlement paths. This aggregation inflates the perceived efficacy of rail adoption because it counts successful domestic PayNow or PromptPay transactions as proof of cross-border capability, when in reality, the average corporate payment still traverses a 2–3 day correspondent chain for intercompany transfers.

Variance across cases emerges not from currency pairs but from entity topology. Operators with hub-and-spoke structures involving Singapore, Malaysia, and Thailand show tighter convergence to the recovery model because their internal liquidity pools can be swept into DuitNow and PayNow accounts with predictable timing. Conversely, fragmented operators maintaining standalone legal entities in Vietnam and Indonesia exhibit higher variance; their settlement flows lack the critical mass required for effective netting, causing the realized recovery to drift significantly below the benchmark. The mechanism fails to scale linearly with volume when entity count exceeds the operational capacity of a single treasury desk to reconcile daily nets against T+2 incoming wires. In these high-variance cases, the cost of managing multiple real-time accounts often erodes the FX spread savings, turning the theoretical recovery into a net negative unless automated reconciliation is deployed.

| Architecture | Settlement Days | FX Spread | Buffer Cash Req. | Per-Transaction Cost | Recovery vs. Baseline |
| --- | --- | --- | --- | --- | --- |
| (1) Legacy SWIFT Correspondent Chains | 2–3 days | bps | Full 2.1% of revenue | High (intermediary fees + FX) | Baseline (0% recovery) |
| (2) Bilateral Real-Time Rail Links | Near-instant (caps apply) | Low on covered pairs | Reduced on capped flows | Variable (retail pricing) | pp recovered |
| (3) Regional E-Wallet/Aggregator Routing | 1 day | bps | Moderate reduction | Medium (aggregator markup) | Partial fix; tail risk added |
| (4) Daily Multilateral Netting over Real-Time Rails | T+0 (netted) | Minimized via netting | Significantly reduced | Engine cost + rail fees | pp recovered |

![Four Settlement Architectures Compared — The T+2 Trap](https://static.mm-ais.com/article-images-pixabay/the-t-2-trap-why-cross-border-payments-s-b39c828c.jpg)

## What the Data Doesn't Tell You

The canonical rule breaks under three specific conditions where the decision matrix must invert. First, when dealing with regulated sectors such as healthcare or defense procurement in ASEAN jurisdictions, contractual payment terms may mandate SWIFT MT103 delivery regardless of rail availability; here, the 2.1% buffer remains mandatory even if real-time options exist, because counterparty risk dictates the architecture, not efficiency. Second, the rule fractures for micro-transactions below the minimum threshold of local real-time schemes; QRIS and InstaPay impose floor limits that make per-transaction routing economically unviable compared to batched correspondent processing. Third, during periods of extreme liquidity stress in peripheral ASEAN currencies, central banks may impose temporary capital controls or widen intraday spreads beyond standard models; in these windows, holding cash in nostro accounts becomes a hedge rather than a drag, and the netting advantage vanishes until stability returns. Operators must monitor regulatory filings from the Monetary Authority of Singapore, Bank Negara Malaysia, and the Bangko Sentral ng Pilipinas for early signals of these regime shifts.

The 2.1% headline is a volume-weighted aggregate that obscures the structural variance defining your actual working-capital drag. The model assumes a uniform settlement architecture, but ASEAN's payment landscape fractures along corridor lines. According to the Article Headline/Model, revenue loss attribution is calculated at a fixed percentage threshold of 2.1%, serving as the baseline metric for operational efficiency tracking in the 2026 framework. However, this average masks extreme heterogeneity. Singapore–Malaysia corridors, saturated with PayNow-DuitNow integration, may run at %. Conversely, Cambodia, Laos, and Myanmar corridors, lacking real-time rail links entirely, can exceed %. Your entity footprint dictates your exposure; a company concentrated in CLMV markets faces double the drag of a Singapore-centric operator, regardless of netting adoption.

FX volatility further confounds the signal. In 2026, when the baht or rupiah moves %, hedging outcomes swamp the 2.1% settlement drag, making it methodologically hard to isolate settlement delay as the causal variable in any single year's P&L. Operators often misattribute FX translation losses to settlement inefficiency. The mechanism requires separating currency risk from liquidity friction. Sales dashboards reflect top-line performance while settlement timelines dictate actual cash reality for scaling merchants, yet without isolating the FX component, you cannot validate whether your treasury function is optimizing rails or merely absorbing currency noise.

| Condition | Routing Action | Liquidity Implication |
| --- | --- | --- |
| Regulated sector contracts mandating SWIFT | Maintain T+2 correspondent chain | Hold 2.1% buffer; no recovery |
| Micro-transactions below scheme floors | Batch via correspondent | Buffer sized by batch frequency |
| Central bank capital controls / spread spikes | Prioritize nostro liquidity | Buffer expands temporarily |
| Fragmented entity topology (no netting mass) | Hybrid routing with auto-recon | Recovery drops below % |

![What the Data Doesn't Tell You — The T+2 Trap](https://static.mm-ais.com/article-images-pixabay/the-t-2-trap-why-cross-border-payments-s-35a0590b.jpg)

## What the 2.1% Model Hides

Data vintage poses a forward-looking risk. The model extrapolates from 2023–2024 corridor data, and if BIS Project Nexus reaches production by 2026–2027 as planned, the correspondent-chain share could collapse faster than the model assumes, shrinking the recoverable pool. Settlement timing depends on backend rules, risk assessments, and payment infrastructure rather than instantaneous processing. If Nexus interoperability accelerates, the T+2 chains may vanish sooner than projected, meaning the 2.1% buffer could become obsolete capital allocation too quickly. You must stress-test your liquidity buffers against an accelerated migration timeline.

Finally, counterparty-behavior variance inflates the perceived impact of settlement architecture. The model assumes counterparties pay on invoice terms, but in practice % of ASEAN B2B invoices settle late for relationship reasons unrelated to rails. That late-payment cost is real but is not settlement-architecture cost, and conflating the two inflates the headline. Payment approval does not equate to settled revenue; authorization is only the beginning of the money's journey before actual settlement occurs. Merchants planning cash flow based on approvals instead of actual settlements face unexpected liquidity constraints when reserves are applied. You must decouple commercial dispute delays from routing latency to avoid over-investing in rails to solve behavioral credit issues.

A Singapore-headquartered electronics distributor with $120 million in ASEAN revenue operates a five-entity structure across Indonesia, Thailand, the Philippines, and Vietnam. In 2026, this operator's working capital is trapped by a legacy settlement architecture: all intercompany flows route through SWIFT correspondent chains via a single regional bank. This creates a compounding drag on liquidity that standard treasury dashboards often obscure because they track gross inflows rather than net settlement velocity. The baseline friction manifests as frozen nostro float, excessive FX conversion spreads, and buffer cash held against T+2 chains. Applying the model's components to the $120M revenue base reveals a total drag of $2.5 million, or exactly 2.1% of annual revenue. This comprises approximately $1.1 million in nostro float and buffer cash carrying costs (calculated at 7% regional funding rates), $0.9 million in FX conversion spreads across four currency pairs, and $0.5 million in late-settlement financing costs.

The 2.1% revenue drag is not a static tax; it is a function of corridor architecture and netting geometry. Operators who treat settlement as a treasury afterthought rather than a routing decision will bleed working capital even when domestic rails settle in seconds. The cross-border reality remains that average corporate payments traverse 2–3 day correspondent chains, stranding nostro float and inflating FX conversion spreads. Your job is to isolate where that drag lives and apply the canonical rule: real-time routing with daily multilateral netting for viable corridors, and a hard liquidity buffer only for those still trapped in T+2 chains.

Rule 1 demands a corridor-level inventory before any modeling begins. You must map every intercompany and customer flow by rail type—real-time (PayNow, PromptPay, QRIS, InstaPay, DuitNow), bilateral link, or correspondent chain—and compute the drag per corridor. If no single corridor exceeds a 1.5% drag threshold, the fixed costs of deploying a netting engine fail the payback test. In these low-friction environments, the investment yields negative returns against the recoverable pool. Rule 2 flips the migration instinct: implement multilateral netting first. Netting recovers the largest share of the loss, roughly 1.4 to 1.6 percentage points, and functions on corridors where real-time links do not yet exist. By netting obligations daily across entities, you reduce gross settlement volumes, which compresses the absolute cost of the remaining correspondent-chain flows. Rail migration becomes a secondary optimization once the netting layer is live.

| Distortion Factor | Mechanism Impact | Actionable Threshold |
| --- | --- | --- |
| Corridor Heterogeneity | SG-MY: 0.8% vs CLMV: >4% | Map entity footprint; apply corridor-specific buffers |
| FX Volatility | Baht/Rupiah 5-8% moves swamp 2.1% drag | Isolate FX P&L from settlement cash-flow analysis |
| SME Scale | Fixed netting costs exceed drag for | Defer netting engine until revenue inflection point |
| Data Vintage | Nexus 2026-27 could collapse T+2 share faster | Stress-test buffers against accelerated migration |
| Counterparty Variance | 30-40% late B2B due to relationships, not rails | Segregate commercial disputes from routing latency |

![What the 2.1% Model Hides — The T+2 Trap](https://static.mm-ais.com/article-images-pixabay/the-t-2-trap-why-cross-border-payments-s-2fa3df52.jpg)

## Worked Case

Shared cost allocation methods are required to distribute brand campaigns, SEO investments, and website expenses across multiple locations, but settlement drag follows a stricter mechanical logic. Unlike marketing overhead, settlement costs compound through nostro float and FX spreads. A common belief that real-time payment adoption has solved settlement friction is false cross-border; domestic rails settle instantly, but intercompany flows often default to SWIFT chains. The myth persists because domestic dashboards show green lights while cross-border nostro accounts remain red. Only by mapping corridors, netting first, and sizing buffers to rail type can operators recover two-thirds of the 2.1% loss before the next Project Nexus expansion erodes the remaining opportunity.

| Drag Component | Mechanism | Annual Cost ($M) | Revenue Impact |
| --- | --- | --- | --- |
| Nostro Float & Buffer Cash | Frozen liquidity in correspondent accounts; buffer sized for T+2 variance | $1.1 | 0.92% |
| FX Conversion Spreads | Multi-leg routing across four currency pairs incurs cumulative spread markup | $0.9 | 0.75% |
| Late-Settlement Financing | Bridge financing required to cover gaps between invoice date and value date | $0.5 | 0.42% |
| Total Baseline Drag | Aggregate loss from current SWIFT-only architecture | $2.5 | 2.1% |

The intervention requires collapsing the gross payment volume into net positions before execution. By implementing daily multilateral netting across the five entities, the operator reduces roughly 70% of gross intercompany volume to net settlements. This structural change eliminates the need for full-value gross transfers on the majority of flows. The residual flows are then migrated to bilateral real-time rail links where corporate limits permit, specifically targeting corridors with established PayNow-PromptPay or QRIS-DuitNow bridges. Netting alone eliminates $1.2 million of float and spread cost by removing the gross exposure that triggers nostro holds and multi-leg FX markups. Rail migration on the Singapore–Malaysia and Singapore–Thailand corridors recovers an additional $0.5 million by bypassing correspondent chains entirely. The result is a recovered figure of $1.7 million, leaving only $0.8 million of residual drag concentrated in the Vietnam and Philippines corridors where real-time rails remain fragmented or lack sufficient corporate liquidity limits. This represents a 68% recovery, consistent with the model's 1.4–1.6 point estimate for operators who successfully hybridize netting with rail migration.

| Intervention Layer | Action | Recovered Value ($M) | Corridor Focus |
| --- | --- | --- | --- |
| Daily Multilateral Netting | Collapse 70% gross volume to net positions; eliminate gross nostro requirements | $1.2 | All intra-ASEAN entities |
| Rail Migration | Route residual flows via real-time bilateral links; bypass SWIFT chains | $0.5 | SG-MY, SG-TH |
| Residual Drag | Unrecoverable cost due to rail fragmentation or limit constraints | $0.8 | VN, PH |
| Total Recovery | Net benefit from combined architecture shift | $1.7 | 68% of baseline drag |

Implementation costs must be weighed against the speed of recovery. Building the netting engine, onboarding banks for direct rail access, and restructuring treasury processes require an estimated $250,000 to $350,000 in year one. These are sunk costs that enable the recurring yield. With a first-year net benefit of roughly $1.4 million after accounting for implementation expenses, the payback period falls under three months. The canonical decision rule dictates that operators hold a dedicated liquidity buffer sized at 2.1% of revenue only for corridors still locked in T+2 correspondent chains—in this case, the Vietnam and Philippines legs. For all other flows, the buffer should be reduced to near zero, as real-time rails with daily netting eliminate the settlement variance that necessitates large cash buffers. This approach converts trapped working capital into deployable liquidity while neutralizing the 2.1% revenue leak.

## Five Rules for Deciding Where Your 2.1% Lives

The 2.1% revenue drag is not a static tax; it is a function of corridor architecture and netting geometry. Operators who treat settlement as a treasury afterthought rather than a routing decision will bleed working capital even when domestic rails settle in seconds. The cross-border reality remains that average corporate payments traverse 2–3 day correspondent chains, stranding nostro float and inflating FX conversion spreads. Your job is to isolate where that drag lives and apply the canonical rule: real-time routing with daily multilateral netting for viable corridors, and a hard liquidity buffer only for those s

## Frequently Asked Questions

**Why do ASEAN's real-time bilateral payment links fail to solve corporate settlement friction?**

While PayNow–PromptPay and similar retail remittance corridors handle consumer transfers efficiently, they exclude most corporate bulk payments because they cap transaction sizes and lack multi-entity account structures.

**What specific financial components make up the 2.1% revenue loss model?**

The 2.1% revenue loss decomposes into three weighted components: cash parked in pre-funded correspondent accounts earning below-treasury returns, FX conversion spreads on delayed conversions versus locked rates, and precautionary buffer cash held against settlement uncertainty.

**How much annual opportunity cost does PhotonPay attribute to trapped float at a conservative yield rate?**

According to PhotonPay, opportunity costs on trapped float reach approximately $150,000 annually at a conservative 5% rate.

**What structural limitation prevents multi-entity operators from simply adopting any real-time rail to fix cross-border friction?**

Multi-entity operators often assume that adopting any real-time rail automatically solves cross-border friction, but this conflates domestic efficiency with intercompany liquidity optimization.

**How does accrual accounting impact treasury visibility into working capital bleed during T+2 delays?**

Accrual accounting recognizes revenue when services are delivered independent of actual cash receipt timing, meaning income statements mask the working-capital bleed until payment clears.

**Which settlement architecture recovers an estimated percentage points of the 2.1% revenue drag by collapsing gross transaction volume into net positions?**

Daily multilateral netting over real-time rails emerges as the superior architecture, recovering an estimated percentage points of the 2.1% revenue drag by eliminating redundant gross settlements and drastically reducing immediate funding requirements.

## Quick answers

| Why do cross-border corporate payments default to SWIFT correspondent chains? | They take two to three business days, stranding cash in nostro accounts for the interim. |
| --- | --- |
| Do ASEAN's bilateral real-time rail links solve settlement friction for all payment types? | No; while they handle retail remittances efficiently, they exclude most corporate bulk payments because they cap transaction sizes and lack multi-entity account structures. |
| What are the three weighted components of the 2.1% revenue loss model? | Nostro float (cash parked in pre-funded correspondent accounts earning below-treasury returns), FX conversion spreads on delayed conversions versus locked rates, and precautionary buffer cash held against settlement uncertainty. |
| How does accrual accounting impact the visibility of working-capital bleed from settlement delays? | It recognizes revenue when services are delivered independent of actual cash receipt timing, meaning income statements mask the working-capital bleed until payment clears. |
| Why is the Bank for International Settlements engineering a multilateral instant-payment interlinking platform? | Because bilateral links leave cross-border settlement gaps, and regulators are quantifying the exact liquidity trap that multi-entity operators absorb daily. |

Also worth reading: **ASEAN Cash Reserves: Why Not Centralizing Hits 18% ROI in 2026**: [ASEAN Cash Reserves: Why Not](https://cashwise.asia/blog/asean-cash-reserves-why-not-centralizing-hits-18-roi-in-2026.php) · **AI Cuts APAC DSO by 12 Days: McKinsey Evidence and Framework**: [AI Cuts APAC DSO by](https://cashwise.asia/blog/ai-cuts-apac-dso-by-12-days-mckinsey-evidence-and-framework.php)

### Related reading

- [Fix Data Plumbing, Not AI Models, To Close APAC Logistics Cash Gaps](https://cashwise.asia/blog/fix-data-plumbing-not-ai-models-to-close-apac-logistics-cash-gaps.php)
- [AI Cuts APAC DSO by 12 Days: McKinsey Evidence and Framework](https://cashwise.asia/blog/ai-cuts-apac-dso-by-12-days-mckinsey-evidence-and-framework.php)
- [Hybrid AI Cuts Reconciliation to 3 Days, Payouts in

Canonical: https://cashwise.asia/blog/the-t2-trap-why-cross-border-payments-still-cost-more.php
Markdown: https://cashwise.asia/blog/the-t2-trap-why-cross-border-payments-still-cost-more.php/index.md