Before trying out the demos below, make sure to read 3 - Storing Credentials. You need a wallet app in order to issue credentials properly.
Now that you have created credentials, the next step is to issue credentials to users. There are two steps to issuing a credential type to your users.
See the API documentation for the pairing APIs above or leverage our sample DV workflow below to get started.
After a user has successfully paired a digital wallet, if they meet the Issuance Rule criteria (i.e. Group, Population or SCIM filter) they will automatically see the card in their wallet.
There can be up to a 10-minute wait for the staged credentials to get issued, or you can leverage the API to more quickly issue the credentials to the user's digital wallet ahead of the automated process.
Before trying out the following demo, make sure to read the 3 - Storing Credentials section. You need the Sample Mobile Wallet app in order to issue credentials properly.
Issues either a
VerifiedEmployee credential using a very simple issuance workflow.
Before trying out the following demos, make sure to read the 3 - Storing Credentials section. You need the Sample Mobile Wallet app in order to issue credentials properly.
Issues a BXInsurance Digital Credential into the Sample Mobile Wallet App.
Create BXInsurance Digital ID on the upper right to get started.
Issues a BXGovernment Digital Credential (converts a physical government-based identification) into the
Sample Mobile Wallet App.
Sign up for Digital ID on the upper right to get started.
Issues a BXEducation Student Digital Credential into the Sample Mobile Wallet App.
Sign up for BXEducation Online Access on the upper right to get started.
The following PingOne DaVinci workflows are available for download to get you up and running quickly with PingOne Neo. You will need to modify Flow variables to reference your own PingOne environments. This requires PingOne DaVinci as a service in your PingOne tenant. See more information here.
Two nodes require update after import:
Get Access Token- The client id / secret from a configured P1 Credentials worker application (enabled for
Create User- A population must be selected from the drop-down in the PingOne node; this is no longer a separate variable to define.
See our API documentation if you want to invoke PingOne Credentials directly as a service.