Integration Options
Integration Guides
Choose an ingestion path, connect your transaction data, and decide how your application handles WatchTower decisions.
Choose how to send transactions
Use the API for ongoing transaction evaluation. Use file import for transaction records held in a CSV or Excel workbook. Historical uploads are a separate workflow from live decisioning.
- Canonical API Ingestion: send transactions in the WatchTower payload format.
- Adapter API Ingestion: use a configured adapter to translate your institution’s payload.
- CSV and Excel Import: map file columns, review validation findings, and handle duplicate records.
- Historical Backfill: choose context-only ingestion or historical replay and understand their limits.
Connect and handle the result
- Follow the Implementation Guide to prepare credentials, payloads, and decision handling.
- Read Inline Decisioning if your application calls WatchTower before executing a payment. Your application is responsible for enforcing the returned decision.
- Configure Signed Callbacks when using callback delivery, and verify messages before processing them.
Test failure handling before launch
Test a valid request, invalid input, a repeated request, and a temporary service failure. Check both the API response and how your application behaves.
- Retry and Idempotency: avoid duplicate evaluation when retrying requests.
- Error Handling: distinguish requests that need correction from failures that may be retried.
- Go-Live Checklist: review configuration and operational readiness before production use.
- Troubleshooting: investigate integration problems.