WatchTower for Core-Banking and Payment Infrastructure Providers
What core-banking platforms and payment infrastructure providers typically need from WatchTower when routing risk decisions for the institutions they serve, and where to find the details for each.
Pre-posting decisions
Get an immediate allow, pause, or cancel signal before a transaction settles on your ledger.
Organization-isolated routing
Route each institution you serve into its own separate WatchTower organization.
Reliable follow-up
Receive a signed callback with the final release or cancel outcome once a paused transaction is resolved.
What matters most to an infrastructure provider
If you operate a core-banking platform or shared payment infrastructure, you are usually integrating WatchTower on behalf of the institutions you serve, not for a single organization. That changes what you need most: a synchronous decision your own transaction pipeline can act on before posting, a reliable way to route each institution to its own isolated WatchTower organization, and a dependable follow-up when a paused transaction is later resolved by a human.
What you will typically care about first
- requesting an immediate decision before a transaction posts, so you can allow, pause, or cancel it inline
- routing each institution you serve into its own separate WatchTower organization
- a reliable callback once a paused transaction is resolved, so you are not left polling for status
- idempotent retries, since real-time systems retry when a network is slow or a response is unclear
- a clear timeout and reconciliation plan for when no response arrives in time
Where to start
- Read Inline Decisioning for the full request and response flow, including retries, idempotency, and timeout planning.
- Read Decisions and Risk Outcomes, specifically "Held transactions and the review outcome," for how a paused transaction is released or cancelled after analyst review.
- Read Organizations to understand how organization isolation works across the institutions you route.
- Read Retry and Idempotency for how WatchTower treats duplicate requests safely.
- Read Latency and Reliability for what to expect from response times and how to plan around them.
The pause and release pattern
When your platform can hold a transaction before it posts, WatchTower can return a decision that tells you to pause it. That pause is not the end of the story. Once an analyst investigates and records a final outcome, either release or cancel, WatchTower sends that outcome back to you as a signed callback, so your pipeline can act on it automatically instead of waiting for someone to check back manually.
The initial inline response only tells you a transaction is paused. Build your integration around receiving and acting on the follow-up callback as a first-class part of the flow.