Skip to content
Help Center

Removing a verification from an Inquiry template

Last updated on .

View Markdown Contact support Contact support 8 min read
On this page

Overview

Removing a verification from an Inquiry template is more than deleting a single step. Each verification module inserts a cluster of related steps into your flow like collection screens, a verification step, a retry screen, an action sequence, a branching step, and outcome routes, and all of them need to be removed together for the flow to remain valid.

This article walks you through identifying the full set of steps that belong to a verification and removing them cleanly, even when your template contains multiple verifications.

What gets added when you insert a verification module?

When you insert a verification module, Persona adds a pre-built group of steps to your flow. Knowing what’s in that group makes it easier to identify what to remove.

Government ID Verification module

RemoveVerification002Full

Inserting a Government ID Verification module adds:

  • A Country select screen. Module versions that classify the ID type automatically do not add this screen.
  • A Government ID verification step. This one step contains the pages where the user selects the ID type and captures the front and back of the ID.
  • An ID retry screen
  • An action sequence that runs the Government ID verification and updates the Inquiry fields from the result
  • A branching step named Conditional Step, with three routes: Passed, Retry, and Failed. The Passed route also contains an action that updates the Account fields.

The Retry route sends the user to the ID retry screen, which leads back to the verification step for another attempt. The number of attempts allowed is set in the Retry route’s condition.

Selfie Verification module

Inserting a Selfie Verification module adds:

  • A Selfie verification step
  • A retry screen
  • An action sequence that runs the Selfie verification
  • A branching step named Conditional Step, with three routes: Passed, Retry, and Failed

Database Verification module

Inserting a Database Verification module adds:

  • A data collection form screen (collects name, birthdate, address, SSN)
  • A retry screen
  • An action sequence that runs the Database verification and updates the Inquiry fields from the result
  • A branching step named Conditional Step, with three routes: Passed, Retry, and Failed. The Passed route also contains an action that updates the Account.

After inserting a Database Verification module, you add the Success and Fail screens separately (with the Standard success step and Standard failed step modules). If you remove the module, you’ll also need to check whether those screens should be removed or re-connected to the remaining flow.

Other verification modules

Other verifications (AAMVA, Email, Phone Number, Document AI, etc.) follow the same pattern: one or more collection screens, a verification step, and a branching step with outcome routes.

How to identify which steps belong to a specific verification

Templates with multiple verifications can have closely spaced branching paths and outcome screens that are difficult to distinguish at a glance. Use the following approaches to identify which steps belong to which verification.

Method 1: Trace from the verification step outward

  1. In the Flow Editor, locate the verification step. These appear as named nodes such as Government ID verification or Selfie verification, or as the data collection form for a Database verification.
  2. Trace backward from the verification step to find the collection screens that feed into it.
  3. Trace forward from the verification step to find the action sequence that runs the verification, the Conditional Step after it, and each of its outcome routes (Passed, Retry, Failed).

All of these steps, the collection screens, the verification step itself, the retry screen, the action sequence, the Conditional Step, and the outcome routes, are the complete set for that verification.

Method 2: Check the action before the branching step

Branching steps inserted by a verification module are all named Conditional Step, so the name does not tell you which verification a branching step belongs to. Look at the action sequence immediately before the Conditional Step. Its action (for example, an action that runs the Government ID verification) identifies the verification.

Method 3: Use step display names

Steps inserted by a module get display names from the module (for example, Country select, Government ID verification, and ID retry). If you’ve renamed steps manually, double-click a step to open it and check what it collects.

Distinguishing between two verifications of the same type

If your template has two Government ID Verification steps (for example, a primary path and a step-up path), look at the flow structure:

  • The branching step immediately downstream of a verification step belongs to that verification.
  • The collection screens immediately upstream of a verification step belong to that verification.
  • Follow each route to its next significant step (a screen, a Success or Fail screen, or a transition) to understand where one verification’s scope ends and the next begins.

When in doubt, give each verification’s steps distinct display names in the Flow Editor before editing, so they’re easier to track.

You do not need to create a draft before you make changes. When you click Save on a published version, Persona creates a new draft version automatically. Nothing goes live until you publish the draft, so you can preview and validate the updated flow first.

Once you’ve identified the steps that belong to the verification you want to remove, delete them in the following order to avoid leaving broken references in the flow.

To delete any step in the Flow Editor, hover over the step and click the trash (Delete) icon. Steps do not have an options menu.

Step 1: Check the outcome routes

Before deleting any steps, look at the downstream connections from the Conditional Step’s outcome routes (Passed, Retry, Failed). Some of these routes may connect to steps that are shared with the rest of the flow (for example, a common Success screen used by multiple verifications).

  • If a route leads to a shared step you want to keep, note the connection. You’ll need to re-wire the upstream step after the removal.
  • If a route leads to a step that only belongs to this verification (for example, the verification’s retry screen), that step is part of the set to remove.

Step 2: Remove the branching step

Hover over the Conditional Step and click the trash (Delete) icon.

When you delete a Conditional Step, Persona deletes the Retry and Failed routes and the steps in them. Persona keeps the steps in the first route (Passed) and moves them up one level in the flow.

For verifications like Government ID and Database, the Passed route includes an action that updates the Account. Persona does not delete this action when you delete the Conditional Step. The action moves up one level. If you do not need it, delete it separately.

Step 3: Remove the verification step and its action sequence

Hover over the verification step and click the trash (Delete) icon. Then delete the action sequence that runs the verification, if it is still in the flow.

Step 4: Remove the collection and retry screens

Remove each screen that was collecting information for this verification, for example the Country select screen, the data collection form, and the retry screen. For each screen, hover over it and click the trash (Delete) icon.

Step 5: Re-connect the flow

After removing the verification cluster, the step upstream of where the verification started may have a broken connection. Clicking a screen on the canvas does not open a settings panel, so use one of these methods to re-connect it to the appropriate next step:

  • Double-click the screen immediately before the deleted cluster to open it in the Screen Editor. Select its button and update the button’s Transition to point to the correct next step in your flow.
  • Add a Connector step after that screen and select the correct next screen.

If that step uses an action sequence to route to the next screen, update the action sequence to remove or replace any routing logic that referenced the deleted verification steps.

Step 6: Validate and save

  1. Review the updated flow to confirm there are no broken connections (steps with no outgoing transition or dangling paths).
  2. Click Save in the top right.
  3. Publish the new version when the updated flow is ready.

Things to watch out for

Shared outcome screens. A single Success or Fail screen is sometimes used as the destination for multiple verifications. Deleting it as part of one verification removal will break the other. Always check whether an outcome screen is referenced by more than one branching step before deleting it.

Action sequences that reference deleted steps. If your flow uses an action sequence to route between verifications (for example, a shared routing action that evaluates multiple verification results), removing one verification’s steps may leave stale references in the action sequence. Review the action sequence logic and remove or update any references to the deleted steps.

Actions kept from the Passed route. Deleting a Conditional Step keeps the actions in its Passed route, such as the action that updates the Account. Check whether you still need them.

Retry loops. The Retry route sends users to the verification’s retry screen, which leads back to the verification step. Delete the retry screen together with the verification. If you keep it, update its Transition so that it does not point to a deleted step.

Multiple verifications of the same type in one template. If you have two Government ID Verification steps (for example, a primary flow and a step-up path), make sure you’re deleting the correct cluster. Use the identification methods above to confirm which steps belong to the verification you want to remove before making any changes.

Was this page helpful?If something is missing, let us know and we will take a look.
Thanks for the feedback. It helps us improve these docs.