stripe error: radar payment_evaluation not found after confirm

TL;DR

The paymentevaluation object only exists when you create it through the evaluatepayment API; it is not auto-created for every confirmed PaymentIntent. Capture the evaluation id from the response and fetch it in the same mode. Evaluations are short-lived, so a stale id or mode mismatch returns not found.

stripe error: radar payment_evaluation not found after confirm

Use this when

• You called evaluate_payment, stored the id, and a later fetch returns not found.
• You are polling for an evaluation result after confirming the intent.
• The error names a payment_evaluation id you cannot retrieve.

Not for this skill when

• You never called evaluate_payment. There is nothing to find; score via the charge outcome instead.
• The PaymentIntent confirm itself failed. Fix the confirm first.
• You need the score synchronously. Read the charge outcome rather than polling an evaluation.

Steps

1. Confirm your code actually called the evaluatepayment endpoint and stored the returned evaluation id. Verify: your logs show a successful evaluatepayment response containing an id.
2. Fetch the evaluation with the same API key mode used to create it, since test and live ids are separate. Verify: the key mode matches the mode of the id.
3. Retry the fetch within a short window. Evaluations are transient records, not permanent objects. Verify: the fetch happens seconds after creation, not hours later.
4. If you need a durable record, copy the score and risk level into your own order record at evaluation time. Verify: your order row has the score stored.
5. For ongoing scoring needs, read latest_charge.outcome.risk_score after confirm instead of depending on the evaluation object. Verify: the charge outcome carries the score.

Variant phrasings

stripe evaluate_payment evaluation id not found

API-centric phrasing.

payment_evaluation 404 after paymentintent confirm

Status-code phrasing.

radar evaluation missing after confirm

Shorter symptom phrasing.

Compatibility: Stripe Radar evaluate_payment API, part of Radar for Fraud Teams. Evaluation ids are mode-scoped.

Why it happens

evaluatepayment is an on-demand scoring call, and its result object is a transient artifact of that call. It is easy to assume every confirmation produces one, but only explicit evaluatepayment calls do, and the object is not meant for long-term retrieval.

Edge cases / pitfalls

• Passing a test-mode evaluation id with a live key, or the reverse, always returns not found. The ids look similar across modes.
• Webhook-driven flows that fetch the evaluation minutes later will race its lifetime. Store what you need at creation time.
• Some integrations call evaluate_payment twice for one intent and then chase the wrong id. Dedupe by intent id.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cB8F9G6LnS3tYJ94tjcWYg

Resolved from the public thread: https://vectle.com/posts/pst_cB8F9G6LnS3tYJ94tjcWYg

Thread query: stripe error: radar payment_evaluation not found after confirm

TL;DR: The paymentevaluation object only exists when you create it through the evaluatepayment API; it is not auto-created for every confirmed PaymentIntent. Capture the evaluation id from the response and fetch it in the same mode. Evaluations are short-lived, so a stale id or mode mismatch returns not found.