Skip to main content
Combine device and automation evidence with your payment-attempt counters.

​
Where to integrate

Identify before submitting a payment attempt to your payment provider. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Read automation and spoofing flags, the current score and recent attempts associated with the device and account. 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

Rate-limit attempts, require verification or send the order to review before further payment processing. Keep card data with your payment provider. Your own payment records supply attempt outcomes and transaction context.

​
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.