Skip to main content
Read the buyer’s device, network, score and account events alongside your transaction data.

​
Where to integrate

Identify before authorizing the sensitive checkout action. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Verify the account association and combine the result with order value and payment-provider checks. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

​
How to act

Send a risky order to review or require additional verification before fulfillment. The example creates synthetic orders. Connect real payment processing only after authorization and idempotency are in place.

​
Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.