This course provides hands-on training for deploying, configuring, and administering PingOne Verify. Through a live environment, students learn to plan architecture, design verification policies, and implement orchestration patterns. The curriculum covers optimizing user experiences via branding and localization, balancing assurance with compliance, and establishing operational practices—including audit, privacy, and monitoring—to ensure successful production deployments.

Target Audiences

The target audiences for this course include:

• Ping Identity Administrators
• Architects
• Implementation Consultants
• Technical Administrators
• Flow Designers
• Customer Support Teams
• Systems Integrators and Resellers
• Identity Data Administrators

Objectives

Upon completion of this course, you should be able to:

• Plan a PingOne Verify deployment by validating service availability, environment strategy, regional and privacy requirements, administrative access, and the orchestration pattern that best fits the use case
• Design and manage PingOne Verify policies that balance assurance, user experience, and compliance requirements for registration and help desk verification scenarios
• Execute and evaluate verification transactions by interpreting status outcomes and mapping them to orchestration behavior such as allow, retry, deny, or escalation paths
• Optimize the end-user verification experience through branding, custom domains, guidance, localization, and notification design
• Monitor verification activity and apply audit, privacy, consent, retention, and operational readiness practices in production environments

Prerequisites

The following are the prerequisites for successfully completing this course:

• Introduction to PingOne Verify
• Getting Started With PingOne Verify
• PingOne Fundamentals

Duration

3 days

Course Contents

Chapter 1: Planning PingOne Verify Deployments

Deploy PingOne Verify by validating environment readiness, designing administrative access, and selecting the orchestration and integration pattern that best fits the use case.

Lesson 1: Planning and Preparing the Verify Environment

Establish the deployment foundation by confirming service availability, environment strategy, regional and privacy requirements, and baseline readiness for first transaction execution:

• Identify the required starting conditions
• Confirm service availability and environment readiness
• Incorporate privacy and regional design constraints
• Add PingOne Verify and validate baseline readiness

Lesson 2: Designing administrative access and separation of duties

Interpret transaction status outcomes and connect them to the downstream actions that the orchestration flow must take:

• Observe status progression
• Map outcomes to allow, retry, deny, or escalate actions
• Distinguish retry scenarios from fail-fast scenarios
• Design escalation and assisted-verification handoff points

Lesson 3: Selecting the Right Orchestration and Integration Pattern

Compare supported PingOne Verify orchestration methods and align them to the right implementation scenario:

• Compare API, DaVinci, PingFederate, Mobile SDK, and AIC/PingAM
• Match use cases to the right pattern
• Identify prerequisites and architectural constraints for each approach

Chapter 2: Designing Verify Policies and Transaction Behavior

Design PingOne Verify policies, understand transaction outcomes, and align orchestration behavior to business goals.

Lesson 1: Understanding and Designing Verify Policies

Design verify policies by selecting the right verification methods and configuring the policy elements that affect assurance, user friction, operational cost, and compliance posture:

• Explain what a verify policy controls
• Map verification types to business use cases
• Configure timeout, retry, threshold, inspection, and storage settings
• Decide when to enable AAMVA, identity data matching, and verified claims storage

Lesson 2: Managing transaction outcomes and orchestration branching

Interpret transaction status outcomes and connect them to the downstream actions that the orchestration flow must take:

• Observe status progression
• Map outcomes to allow, retry, deny, or escalate actions
• Distinguish retry scenarios from fail-fast scenarios
• Design escalation and assisted-verification handoff points

Chapter 3: Branding, Localization, Notifications, and Trusted User Experience

Optimize the end-user verification experience through supported branding, localization, messaging, and trust-building capabilities.

Lesson 1: Applying Themes and Trusted Domains

Use themes and custom domains to create a more trusted and consistent PingOne Verify experience:

• Apply branding themes
• Explain how custom domains improve trust
• Document DNS, certificate, and rollout prerequisites

Lesson 2: Designing Guidance, Notifications, and Completion Confidence

Improve user guidance and messaging so learners can reduce friction and increase verification completion confidence across self-service and assisted journeys:

• Identify key instructional moments in the journey
• Align guidance and terminology to the use case
• Determine when notification templates are required
• Recommend messaging and delivery-method changes that improve completion confidence

Lesson 3: Supporting Localization and Regional Experience Requirements

Support regional rollout requirements by planning languages, localized pages, and fallback behavior for the verification experience:

• Review localization configuration for Identity Verification pages and keys
• Compare default-language and localized behavior
• Prioritize languages, pages, and rollout decisions

Chapter 4: Operating PingOne Verify, Audit, and Compliance

Operate PingOne Verify after launch by monitoring transactions, interpreting reporting signals, and applying privacy, consent, retention, and compliance controls.

Lesson 1: Monitoring Transactions and Verification Evidence

Review verification activity and evidence so you can support troubleshooting and operational decision-making:

• View verification results by user and transaction
• Use audit reporting to inspect Verify events and transaction details
• Interpret transaction metadata for support and troubleshooting

Lesson 2: Operational Reporting and Webhook-Based Visibility

Use dashboard reporting and webhook-based event visibility to understand operational trends and extend monitoring into external systems:

• Review dashboard filters for time range and verify policy
• Interpret key operational charts and trends
• Explain when audit reporting or webhook visibility is the better tool

Lesson 3: Applying Privacy, Consent, and Retention Controls

Apply privacy and compliance controls that support regional, legal, and operational requirements for PingOne Verify deployments:

• Explain Verify data classes and consent requirements
• Teach data residency and retention concepts
• Document retention, deletion, and compliance decisions