Configure Steps

When you click a step node on the Builder canvas, a side panel opens with that step's configuration. The panel has three tabs: General, Config, and Policy.

At the bottom of the panel, a status indicator shows whether the step has any configuration issues (e.g., "No step issues" with a green checkmark, or a warning count with a link to "Review issues").

General

The General tab contains the step's identity and API credentials.

Step Name (required) – the display name for this step, shown on the canvas and in reporting. You can rename it to something meaningful for your workflow (e.g., "PII Validation," "SMS Link," "Government ID and Selfie Match").

Description – an optional text field for documenting what this step does, which verification methods it uses, or any notes for your team.

API Key (required) – the step's unique API key, used when integrating via the API. The value is masked by default; use the eye icon to reveal it, or the copy icon to copy it to your clipboard.

Shared Secret (required) – the step's shared secret, paired with the API key for authentication. Also masked by default with reveal and copy controls.

Each step has its own API Key and Shared Secret – these are scoped to the step, not the workflow. If you're integrating via the API (rather than Gateway), you'll use these credentials to call the step directly.

Config

The Config tab is where you manage what data the step collects and which verification services it runs. It has two sections: Inputs and Checkers.

User Inputs

Inputs are the data fields collected from the end user (or pre-filled) at this step. The Inputs section shows a count of configured inputs (e.g., "Inputs 1") and lists each one. Required inputs are marked with an asterisk (*).

Viewing input details:

Click the expand arrow (>) on any input to see its sub-fields. For example, expanding "Telephone" reveals its component fields: Dial/Country Code and Telephone Number.

Adding inputs:

Click "+ [X] available inputs" (e.g., "+ 110 available inputs") to open the input selection popover. This presents a searchable list of all available input types, organized alphabetically. Each input has a + button to add it to the step. Available inputs include categories like Aadhar Card/PAN/Passport, Action, Activity Level, Address, and many more.

Use the search bar at the top to find a specific input by name.

Modifying Checkers Within Steps

Checkers are the verification services that run within a step. Each checker connects to a data source or verification provider and performs specific checks against the user's data.

The Checkers section shows a count of configured checkers (e.g., "Checkers 1") and lists each one with a search bar for quick filtering.

Viewing checker details:

Click the expand arrow (>) on a checker to see two sub-sections:

Configured Checks – the individual assertions this checker will evaluate, shown as a count (e.g., "Configured Checks 58"). Expand this to see the full list of active checks, such as Device Local Whitelist Check (6 months), Device Local Whitelist Check, Impossible Travel Check (>= 200 mi/hr), Local Whitelist Check, Multi-Attribute Local Blacklist Check, Multi-Attribute Local Watchlist Check, Browser Anomaly Check, Device and IP Address Reputation Check, and more.
Acquired data – the data points the checker returns after running. Expand this to see the list of acquired attributes, such as Session Risk Rating Verdict, Proxy Score, WebRTC External IP, Session Verdict, Session Processing Verdict, Time Zone Code, Time Zone Name, and others.

Adding a checker:

Click "+ [X] available checkers" (e.g., "+ 56 available checkers") to open the checker selection modal.
The modal shows All checkers in a card-based layout, organized alphabetically.
Use the Filter panel on the left to narrow by checker type:
- Identity checkers – Biometric, Community Affiliation and Licensing, GovID, Knowledge, KYB, PII
- Possession checkers – Email possession, Phone and email Possession, Phone Possession
- Risk checkers – Background Risk, Communication Risk, Communication risk, Device and Network Risk
- Uncategorized checkers
Use the Search bar to find a specific checker by name.
Click a checker card to select it and add it to the step.

After adding a checker, you may be prompted to review and confirm its recommended checks (assertions) before it's finalized. For details on what individual checkers do and which checks they include, see Checkers

Policy

The Policy tab is where you define the rules that determine this step's outcome – whether the transaction is approved, denied, or routed to an additional step for further verification.

The tab shows four collapsible sections:

Default Rule – the fallback behavior when no other rules match. Configure the default action (Deny, Approve, or Obligate), and optionally enable inline retry with a configurable number of attempts and a retry message shown to the user.
Deny Rules – rules that block risky or invalid transactions
Approve Rules – rules that approve transactions meeting your criteria
Obligate Rules – rules that route the user to an additional step

Each section shows the number of configured rules (e.g., "Deny Rules 0," "Approve Rules 1"). Rules use an IF/THEN structure where conditions reference policy groups (reusable bundles of checks) and the THEN action defines the outcome.

For the full guide on building rules, working with policy groups, and understanding the rule evaluation hierarchy, see Policy Manager / Rules Engine