stripe api error: radar payment_evaluation not found

Not specified by the original author.

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.

Not specified by the original author.

TL;DR

Read the error body first. Stripe 400s name the offending parameter, so the fix is usually a single field. Common causes are an unsupported payment method type, an invalid amount or currency, or a missing required field. Validate the payload field by field against the evaluate_payment reference before retrying.

stripe error: radar evaluate_payment returned 400

Use this when

• The evaluate_payment endpoint returns 400.
• The error body names a specific parameter.
• You are integrating evaluate_payment for the first time.

Not for this skill when

• The status is 401. That is an authentication problem with your key.
• The status is 404 on a payment_evaluation id. That is a lookup problem.
• The request succeeds but the score looks wrong. That is a scoring question.

Steps

1. Log the full error response body, including the param field. Verify: you can quote the exact parameter Stripe rejected.
2. Check that the payment method type is one evaluate_payment supports. Verify: the type matches the documented supported list.
3. Validate amount is a positive integer in the smallest currency unit and currency is a supported three-letter code. Verify: no decimals, no symbols.
4. Confirm all required fields for your payment method type are present. Verify: the payload matches the API reference field by field.
5. Retry with the corrected payload. Verify: the response returns a payment_evaluation id.

Variant phrasings

radar evaluate_payment bad request

Shorter phrasing.

stripe evaluate_payment 400 invalid request

Status-focused phrasing.

evaluate_payment api error stripe radar

API-focused phrasing.

Compatibility: Stripe Radar evaluate_payment API, part of Radar for Fraud Teams. Request schema follows the pinned API version.

Why it happens

evaluate_payment validates strictly before scoring. A wrong type string, a malformed amount, or a missing required field fails validation immediately, and the 400 names the culprit. Most 400s are payload-shape mistakes, not Radar problems.

Edge cases / pitfalls

• Error messages reference the parameter path, which may be nested. Read the full path, not just the leaf name.
• API version pinning changes required fields. A payload built for one version can 400 on another.
• Retrying the identical payload will 400 identically. Fix the field first.
• A 400 on the first integration attempt is normal. Treat the error body as the spec and iterate on the payload until it passes.

Provenance

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

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

Thread query: stripe error: radar evaluate_payment returned 400

TL;DR: Read the error body first. Stripe 400s name the offending parameter, so the fix is usually a single field. Common causes are an unsupported payment method type, an invalid amount or currency, or a missing required field. Validate the payload field by field against the evaluate_payment reference before retrying.

Not specified by the original author.

TL;DR

The riskscore does not live on the PaymentIntent. It lives on the charge's outcome object, so read `latestcharge.outcome.risk_score`. The score is null until the payment is confirmed and Radar has evaluated it, and only card payments get scored. If the expanded charge still shows null, the payment probably never went through an evaluation.

"risk_score" is null on stripe payment_intent despite radar enabled

Use this when

• Retrieving a PaymentIntent shows no risk_score at the top level.
• You need the Radar score for a card payment from the API.
• The dashboard shows a risk level your API code cannot see.

Not for this skill when

• The payment method is not a card. Bank debits and similar methods never get a Radar card score.
• You are debugging a Radar rule that did not fire. That is rule evaluation, not scoring.
• The null appears on a refunded or canceled intent where no charge exists.

Steps

1. Retrieve the PaymentIntent with the charge expanded: stripe.PaymentIntent.retrieve("pi_xxx", expand=["latest_charge"]). Verify: the response includes a latest_charge object.
2. Read latest_charge.outcome.risk_score and latest_charge.outcome.risk_level. Verify: risk_level is one of normal, elevated, or highest.
3. Check the PaymentIntent reached post-confirmation; an unconfirmed intent has no evaluation yet. Verify: status reads requires_capture or succeeded.
4. Confirm the payment method is a card via latest_charge.payment_method_details.type. Verify: the type reads card.
5. Confirm Radar is enabled in the same mode you are querying. Verify: the Dashboard Radar overview shows evaluations for that mode.

Variant phrasings

stripe paymentintent risk score empty

Same fix, shorter phrasing.

radar score missing from payment intent api response

Focuses on the API response shape.

stripe outcome risk_score null on charge

Same underlying cause, charge-level phrasing.

Compatibility: Stripe API 2023-10-16 and later. Radar risk scoring applies to card payments; Radar for Fraud Teams unlocks the richer risk_insights signals.

Why it happens

Radar evaluates at confirm time and writes the result onto the charge's outcome. The PaymentIntent never carries the score directly, so code reading a top-level risk_score always sees null. Intents that never reach confirmation never get evaluated.

Edge cases / pitfalls

• In test mode, scores are simulated and some signals are absent. Do not tune production thresholds on test scores.
• A charge created with separate auth and capture still scores at auth time. Null after that points to a non-card method.
• If you use the evaluatepayment API, the score lives on the returned paymentevaluation object, which is separate from both the intent and the charge.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstRv-WrDuHK1gZAsjmqN6nA

Resolved from the public thread: https://vectle.com/posts/pstRv-WrDuHK1gZAsjmqN6nA

Thread query: "riskscore" is null on stripe paymentintent despite radar enabled

TL;DR: The riskscore does not live on the PaymentIntent. It lives on the charge's outcome object, so read `latestcharge.outcome.risk_score`. The score is null until the payment is confirmed and Radar has evaluated it, and only card payments get scored. If the expanded charge still shows null, the payment probably never went through an evaluation.