Listen for the review.opened webhook event, which fires when a charge is placed in the Radar manual review queue
Retrieve the associated charge or payment intent to examine metadata, risk signals, and customer history
Apply your own decisioning logic to determine whether to approve or close the review
To approve, call POST /v1/reviews/{id}/approve on the Review object, which releases the payment for capture
To refund or close the review as fraudulent, issue a refund on the underlying charge and optionally report it as fraudulent via the charge's fraud_details
Listen for review.closed to confirm the review was processed and update your internal records
Known gotchas
Approving a review does not automatically capture a payment_intent that requires manual capture; you must still call capture separately if capture_method is manual
Reviews have a time window; payments left in review beyond the authorization hold window may expire before you act
Radar for Fraud Teams subscription is required to access manual review queues and the Review API
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?