APIs to digital wallet
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Once I've agreed I want the credentials sent to the digital wallet, generate a QR code.
Once user confirms their VP on the phone, then send the VO, VR credentials to the digital wallet
Create a callback hook (we provide verified person credential service with a callback URL & we need a listener for when the service changes
Deploy in Openshift or GCP
GIVEN the user is a director of an entity with a sole director
When they indicate they want digital credentials sent to their wallet
THEN generate a QR code in the UI
GIVEN the user has set up a digital wallet
AND the user takes a photo of the QR code on their phone
WHEN the user confirms they are the verified person on their phone
THEN Issue a Verified Organization credential (VO) to their digital wallet using the established connection
AND issue a Verified Relationship credential (VR) to their digital wallet using the established connection
GIVEN the user confirms they are the verified person on their phone
WHEN we issue the VO & VR credentials
THEN also send a callback hook
GIVEN there is a digital wallet for a person and organization
WHEN the service changes and the digital wallet is updated by a third party (ie name changes on BC Services Card)
THEN listen for these messages
AND determine if any action needed (this might be out of scope)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the UI flow for requesting digital-wallet credentials and the existing verified-person service connection, then trace where a callback listener could fit. Done would require the QR-code flow, VO and VR issuance, callback notification, and a decision on handling third-party wallet updates, with deployment in OpenShift or GCP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, javascript
- Domain
- api, cloud, frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100