Skip to main content
Attaches a business outcome to an earlier check: the account converted to a paid plan, turned out to be fraud, or caused a chargeback. Outcomes never change the stored recommendation. They show you which recommendations were right, so you can tune your policies. Send them from your systems, for example from your payment provider’s webhooks.

​
Request body

Identify the check with one of run_id, event_id or email.
​
string
The check_id returned by the check.
​
string
The event ID you sent with the check. Use it when you didn’t keep the check ID, for example after a timeout.
​
string
The email of the signup. Matches the earliest signup check for that address before reported_at. If no check matches, the response is 200 with "resolved": false and nothing is stored, because reporting on a user who was never checked is normal.
​
string
required
conversion, fraud or dispute.
​
string
required
Your or your provider’s label for the event, such as approved, chargeback or fraudulent.
​
string
When the event happened, as an RFC 3339 timestamp.
​
object
Where the event came from. Set source (for example stripe) and a stable outcome_id so retries don’t create duplicates: resending the same data with the same outcome_id returns the original outcome.

​
Response

200 with the stored outcome, or {"resolved": false, "reason": "no_matching_check"} when an email matched no check.

​
Errors