Skip to main content

Risk & Radar

Risk & Radar helps protect payments and merchant accounts from unusual behavior, disputes, and abuse.

What This Section Covers​

  • understanding merchant-visible risk signals;
  • knowing why a payment may require review or additional action;
  • reducing false positives with clean payment data;
  • following dispute or review statuses when they are exposed in the dashboard.

Data That Helps Reduce Risk​

When creating a payment, provide consistent data:

  • correct transaction_country;
  • realistic currency and amount;
  • customer, email, or phone when available;
  • clear business metadata such as order_id or checkout_session_id;
  • configured webhooks to track status changes.

Possible States​

StateMeaning
requires_actionCustomer or merchant action may be required.
review_holdThe payment is temporarily held for review.
payment_failedThe payment failed or was declined.
succeededThe payment is confirmed.

Best Practices​

  • Do not store sensitive information in metadata.
  • Keep stable business identifiers to reconcile payments, orders, and webhooks.
  • Use webhooks to react to status changes instead of relying only on customer redirects.
  • Show clear customer messages when a payment requires action.