Handling the response
Route the checkout based on suggestedAction.
Each /v1/risk response carries a suggestedAction — allow or deny — that tells you how to route the checkout. You decide the mechanism.
allow
Commit the reservation. No extra steps.
deny
Stop the checkout and surface a neutral error to the user. Don't spell out the reason — a generic "we couldn't process this booking" message is enough.
Test the deny path
To test your deny branch, send a risk request with this booker email:
staysignals-deny-test@example.comStaySignals returns a normal decision with suggestedAction: "deny". The fixture itself does not affect future decisions for your project.
Store the decision ID
For every decision — regardless of action — store decisionId on the order record:
POST /orders
{
...,
"staysignalsDecisionId": "dec_8f2a1c7b2e8d"
}The decision ID is your entry point for looking up the full decision in the Dashboard later — helpful when a customer pushes back on a denial, when operations wants to audit a batch, or when you're tuning your routing logic.