Phase 1 MVP - Self-serve Digital Business Card

## Description (Hypothesis):

As a Registries Account user
I want a self-serve option where I can get a digital credential which shows I am related to a company attached to my account
so that I can present it to obtain other services instead of sending personal information in an unsecure fashion

* What are the most critical features being built as part of this Epic
- [ ] issuing a credential which includes information about a person and a business they are authorized to represent
- [ ] revoke a credential
- [ ]

* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.
Based on meetings with several ministries, City of Vancouver and TD Bank, they have existing processes which requires their customers to email/fax/drop off documents with personal information (driver's licences, etc.) and/or company documentation which proves the company exists and information about that company.
There is a demand to reduce the disclosure of personal information in an unsecure way and to streamline Know Your Business / Know Your Client processes so a service could be delivered more efficiently.

----
## Acceptance Criteria
* Used to determine whether the implementation is correct and delivers the business benefits
### Scenario 1 - Authenticated with BC Services Card App options
**GIVEN** I have a Registries Account
**AND** authenticated with my BC Services App (card, non-card, or token)
**AND** I have any role type (Account Administration, Account Coordinator, User)
**WHEN** I have logged into my account
**THEN** I can request a Digital Business Card
**AND** it will be added to my BC Wallet

### Scenario 2 - Authenticated with BCeID, 2FA and affidavit
**GIVEN** I have a Registries Account
**AND** authenticated with a BCeID, 2FA and affidavit
**AND** I have the Account Administrator role type
**WHEN** I have logged into my account
**THEN** I can request a Digital Business Card
**AND** it will be added to my BC Wallet

### Scenario 3 - Authenticated with BCeID ONLY (invited by an Account Administrator who authenticated with an affidavit)
**GIVEN** I have a Registries Account
**AND** authenticated with a BCeID only (no affidavit)
**AND** I have any role type (Account Administrator, Account Coordinator or User)
**WHEN** I have logged into my account
**THEN** I **cannot** request a Digital Business Card*
_*this decision has not been made yet_

----
## Additional Information
* Start date when team will start to work on: This is visible in ZenHub under "Roadmap" - June
* End date Epic will be delivered: This is visible in ZenHub under "Roadmap" - August
* T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints). Story points needs to be updated in Epic. This can be decided by team.
* Process Flow (if applicable)
* CM considerations?
* Possible dependencies or blockers foreseen right now? - Please create a story and block this epic by the dependency story.

----
Enabler Epics:
* action
* result
* object

The issue names no files, tests, or code entry points. Start by reviewing the three acceptance scenarios and resolving the undecided BCeID-only behavior; done means the agreed eligibility rules support requesting, adding, and revoking a Digital Business Card.

Written by the indexing model from the issue text.