Skip to main content

Why you’d use it

Catches double payments, sanctioned payees and changed bank accounts while you can still stop them. The single highest-value use case in the API.

How it behaves

Asynchronous: POST the batch, then poll the warnings endpoint until AnalyzeStatus is Done. 31 indication rules run per transaction. No webhook — polling only.

Use cases

Screen Supplier Payments

FraudScreen supplier payment batches prepared to be sent by the ERP. Fetch a list of warnings connected to the payments. Hold the risky ones, and release the rest.

Warning lifecycle