DocsWatchTowerWatchTower for Cross-Border and Multi-Currency Platforms

WatchTower for Cross-Border and Multi-Currency Platforms

What cross-border payment platforms, remittance providers, and treasury desks typically need from WatchTower, and where to find the details for each.

Multi-currency by design

Source, destination, settlement, and fee amounts stay distinct, evaluated in your own base currency.

Full payment lifecycle

Initiation, completion, reversal, refund, and chargeback are all tracked against the original payment.

Step-up before block

A risky-but-not-blocked payment can go through a proportionate challenge instead of an outright block.

What matters most to a cross-border platform

Cross-border and multi-currency platforms deal with money that moves between currencies, corridors, and jurisdictions, often through several lifecycle steps rather than a single instant transfer. WatchTower is built to keep source, destination, and settlement amounts distinct, evaluate risk in your own base currency, and follow a payment through its full lifecycle instead of only its first hop.

What you will typically care about first

  • sending source, destination, settlement, and fee amounts without WatchTower inventing or guessing an exchange rate
  • corridor-aware risk signals, such as unusual corridor concentration or exposure to a higher-risk geography
  • reporting the full payment lifecycle, including completion, reversal, refund, and chargeback, without those being mistaken for new activity
  • a step-up friction option for a risky-but-not-blocked payment, instead of only allow or block
  • a way to release or cancel a held payment automatically once an analyst has reviewed it

Where to start

  1. Read Decisions and Risk Outcomes, including the challenge outcome and the held-transaction pattern for a review decision.
  2. Read Canonical API Ingestion to see the full multi-currency payload shape, including source, destination, settlement, fees, and the exchange rate you executed.
  3. Read Inline Decisioning if your payment flow can pause for an immediate decision before the payment completes.
  4. Read Monitoring Rules to see the corridor, geography, and value-based control families relevant to cross-border movement.
  5. Read Watchlist Screening for how sanctions and PEP checks apply to cross-border counterparties.

A note on exchange rates

WatchTower never fetches a market rate on your behalf and never invents one. You send the rate you actually executed or quoted for the payment, and WatchTower uses exactly that rate for risk evaluation. If a rate is missing, only the amount-based checks are skipped, and this is reported back as a data-quality warning rather than a false block.

Your rate is the rate that gets evaluated

This keeps the risk evaluation consistent with what your customer actually saw and agreed to, which matters when a decision needs to be explained later.