Healthcare - Pair A Digital Wallet - Subflow

The Healthcare - Pair A Digital Wallet - Subflow lets users pair a new digital wallet.

Purpose

The Healthcare - Pair A Digital Wallet - Subflow checks if the user has a verified mobile number.

If the user does have a verified mobile number, the flow lets them pair a digital wallet using their mobile device, with a QR code as an alternate option.
If the user doesn’t have a verified mobile number, the flow lets them pair a digital wallet using a QR code.

Structure

This flow is divided into sections using teleport nodes:

Choose QR Path Or SMS: Uses a PingOne node to retrieve the user’s devices. The flow then progresses to the Deliver Wallet Pairing Request via Trusted Mobile Channel section if the user has a verified mobile number, and to the Pair Wallet using QR Code section if the user does not have a verified mobile number.
Deliver Wallet Pairing Request via Trusted Mobile Channel: Uses a PingOne Credentials node to create a pairing request. Function nodes then retrieve the pairing notification information and verify the notification was sent.

An HTML node directs the user to follow the instructions on their mobile device, providing the option of using a QR code instead.

If the user selects the QR code option, the flow checks the user’s device. If the user is using a mobile or laptop, a pairing QR code is displayed, and the flow progresses to the Process Pairing Status section.

If the user has not selected the QR code option, the flow progresses to the Process Pairing Status section.
Pair Wallet using QR Code: Uses a PingOne Credentials node to create a pairing request. The flow then checks the user’s device. If the user is using a mobile or laptop, a pairing QR code is displayed, and the flow progresses to the Process Pairing Status section.
Process Pairing Status: Uses a PingOne node to check the wallet pairing status. If pairing is complete, the flow sends a success JSON response indicating that the flow completed successfully. If pairing is incomplete, the flow continues polling.
Return Error: Uses a function node to enrich the error details, then sends an error JSON response indicating that the flow completed unsuccessfully.

Input schema

This flow has the following inputs:

Input name Required Description

Input name	Required	Description
`p1UserId`	Yes	The user ID of the current user.
`companyLogo`	No	The company logo. Used only when the main flow was launched using a redirect.

p1UserId

Yes

The user ID of the current user.

companyLogo

The company logo.

Used only when the main flow was launched using a redirect.

Output schema

This flow has the following outputs:

Output name Description

Output name	Description
`digitalWalletPairingStatus`	The user’s wallet pairing status.
`digitalWalletId`	The ID of the user’s paired wallet.
`digitalWalletDeviceData`	The device data associated with the user’s wallet.
`errorMessage`	The error message to display in the parent flow.
`errorDetails`	The details of the error that occurred in this flow.

digitalWalletPairingStatus

The user’s wallet pairing status.

digitalWalletId

The ID of the user’s paired wallet.

digitalWalletDeviceData

The device data associated with the user’s wallet.

errorMessage

The error message to display in the parent flow.

errorDetails

The details of the error that occurred in this flow.

Variables and parameters

This flow uses the following variable or parameter values:

Variable name Description

Variable name	Description
`canEnrollOnlyEmail`	A Boolean indicating whether email should be the only permitted MFA device.
`resendOtpAttempts`	The number of times the user has resent the OTP.
`p1MFADeviceId`	The device ID for the device being registered.

canEnrollOnlyEmail

A Boolean indicating whether email should be the only permitted MFA device.

resendOtpAttempts

The number of times the user has resent the OTP.

p1MFADeviceId

The device ID for the device being registered.

PingOne Solution Packs