Multi-source payment fraud checks

The scenario gathers payments from the bank and the payment service, AI scores the fraud risk, sends the suspicious ones for review with an alert in botHelp, and reconciles and stores the rest in Postgres.

  • Payments from all sources in one stream
  • AI scores the risk of each
  • An alert on the suspicious ones in botHelp
  • An audit trail and a final report
Webhook

How it works

To get Postgres notifications in botHelp, you don't need a developer: a ready-made scenario watches events and sends messages for you.

  1. Starts when: Schedule Trigger - Periodic Ingestion
  2. Then: Workflow Configuration
  3. Then: Fetch Bank API Transactions
  4. Check: Merge All Transaction Sources
  5. Then: Normalize Transaction Data
  6. Check: Filter Valid Transactions
  7. Then: Check Idempotency
  8. Then: AI Agent - Fraud Detection
  9. Check: Route by Risk Level
  10. If yes: Flag for Manual Review
  11. Then: Notify Finance Team - High Risk
  12. Then: Send Customer Alert Email
  13. If no: Reconcile with ERP System
  14. Then: Store Transaction Record
  15. Then: Store Audit Trail
  16. Then: Aggregate for Financial Report
  17. Then: Generate Financial Report
  18. Then: Send Financial Report to Slack
  19. Then: Fetch Payment Gateway Transactions
  20. Starts when: Webhook - Real-time Transaction Events
  21. Then: OpenAI Chat Model
  22. Then: Structured Output Parser - Fraud Analysis

You can launch this Postgres + botHelp integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.