DocsWatchTowerAdapter API Ingestion

Adapter API Ingestion

How to integrate institutions whose upstream payloads do not match the native WatchTower transaction contract.

Section

Why adapters exist

Not every institution can emit the native WatchTower transaction shape. Some institutions expose bank-transfer payloads, some emit bill-payment events, some emit airtime or merchant-payment payloads, and some use a proprietary core-banking event contract.

The adapter layer lets WatchTower receive those customer-specific payloads, normalize them into the canonical model, and then pass them through the same rule engine and persistence flow.

Section

What adapters make possible

  • institution-specific onboarding without changing the rule engine
  • support for transfers, bill payments, airtime, merchant payments, wallet transfers, and similar flows
  • clear customer-specific integration contracts without fragmenting WatchTower itself