Skip to main content
Fraud Solutions

Alerts and Decisioning

Receive and decision payment holds, programmatically within your enterprise systems
  • Integrate payment hold management with your existing enterprise systems
  • Receive near-real time visibility into fraud screening and payment holds
  • Act on holds directly from your existing workflows and tools
  • Automate notifications and decisioning to improve operational efficiency

Overview

The Alerts and Decisioning API helps you automate payment hold management within your existing fraud and operations workflows. Receive notifications when payments are placed on hold, retrieve hold details, and submit decisions programmatically to help reduce manual effort and accelerate resolution.

How it works

What you can build with Payment Control Center

Payment hold and decisioning

  1. Client initiates payment: The client starts a payment using channels such as SWIFT, JPM Access, Host-to-Host or API.

  2. Payment sent for fraud screening: The payment is automatically sent to the Fraud Screening Engine for evaluation.

  3. Fraud screening decision: The fraud screening engine checks for possible fraud:

    • If no fraud is detected, the payment continues processing.
    • If possible fraud is detected, the payment is flagged and held.
  4. Alerts and Decisioning API notification: When a payment is held, the API receives the fraud alert.

  5. Hold notification delivered: The API sends a hold notification to the client’s application.

  6. Client decision on hold: The client reviews the notification and decisions on the held transaction.

  7. Act on client decision: The API acts based on the client’s decision.

  8. Approve or reject payment: Based on the client decision provided on Step 7, following actions are taken:

    • 8a: No (reject): The payment is canceled.
    • 8b: Yes (approve): The payment is released.
  9. Hold expiry and notifications: Both of the below actions will occur:

    • 9a: The payment is canceled.
    • 9b: The client application receives a notification about the updated status through a payment hold closed event.

Capabilities

Detect potential high‑risk payments, hold suspicious items and enable rapid decisions to cut engagement while improving cut‑off adherence and strengthening fraud controls.

Get near real-time notifications via webhook when the bank puts a payment on hold. Send these holds into the systems you already use. Your team can review and act right away, with key payment details.

Use the REST APIs to approve or reject held payments from the systems you already use. This helps you clear held payments faster, reduce manual work, and maintain strong fraud and payment controls. 

Benefits

Manage payment holds in near real time, integrated with your enterprise systems.

  • Faster resolution on payments holds: Reduce calls, emails, and manual follow-ups for payments held due to suspected fraud.
  • Near real-time notifications: Receive near real-time holds when action is needed via webhook.
  • Works with your current systems: Integrate holds and decisions using the tools you already use 
  • One API across payment types: Use the same API for different payment types such as wires, ACH and RTP (U.S.).
  • Troubleshooting-friendly: Clear error codes and guidance help teams resolve issues quickly.
  • Hold payments visibility: Programmatically retrieve details and decision status for any held payment

Scope

The Alerts and Decisioning functionality is part of the Bank Control feature, which supports payment types including Wires, ACH (outbound) and RTP (U.S.). Bank Control, offered as a complimentary service, enables streamlined investigation and decision-making for payments flagged by J.P. Morgan's fraud screening program. With near real-time digital alerts, this feature enhances security and helps minimize processing delays.

Availability

Alerts and Decisioning is available in the following regions and markets:

Alerts and Decisioning is available in the following regions and markets:
Regions Market/Scheme
North America (NAMR)
  • United States
  • Canada
Europe, Middle East, and Africa (EMEA)
  • Belgium 
  • France 
  • Germany 
  • Ireland 
  • Italy 
  • Luxembourg 
  • Netherlands 
  • South Africa 
  • Spain 
  • Switzerland 
  • Turkey 
  • United Kingdom
Asia-Pacific (APAC)
  • Australia 
  • Hong Kong 
  • India 
  • Indonesia 
  • Japan 
  • Malaysia 
  • New Zealand 
  • Philippines 
  • Singapore 
  • South Korea 
  • Taiwan 
  • Thailand 
  • Vietnam
Latin America (LATAM)
  • Argentina
  • Chile
  • Colombia
  • Mexico (Note: Wires, ACH, H2H and APIs are not supported.)

How to

Learn how to handle webhook notifications when a payment is placed on hold and when that payment hold is updated.

Learn how to approve or reject payment holds to release or cancel payments, individually or in bulk.

Next steps

Complete the onboarding process to ensure you have everything that you need.

Learn more about our Payment Hold.