Fraud prevention
Fingerprint in a decision flow.
A Connection node calls Fingerprint mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.
- Category
- Fraud prevention
- Type
- Integration
- Authentication
- api_key
- Test environment
- Production host only
What a flow can call
2 operations, each one a step you can place on the canvas.
- GET
/v4/events/$data.fingerprint_event_idRead device-intelligence event
Retrieves the full server-side event emitted by the Fingerprint client agent.
- PATCH
/v4/events/$data.fingerprint_event_idFlag a device event as suspicious
Adds a stable application link, tags, or a suspicious flag after a human review.
Provider documentation: https://docs.fingerprint.com/reference/server-api-v4-get-event
Where it sits in the decision
A provider call is a node, not a side effect.
The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.
Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Fingerprint returned at the time is in the trace, not re-fetched from a service whose answer has since changed.
- 01Add Fingerprint as a connection, with your credentials.
- 02Place a Connection node and choose the operation.
- 03Read the response in the rules, tables and branches that follow.
- 04Test the whole path in Sandbox before it carries live traffic.
Ready when you are
Wire Fingerprint into a real decision.
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.