API work needs to be done for storing the TOS details
Acceptance Criteria
Scenario: User accepts TOS
GIVEN the user has a premium account
AND they have a default payment method
AND they have the appropriate account privileges
WHEN they have accept the TOS
THEN they are allowed to create an API KEY
AND have access to BCRegistry API services
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Do you know a possible contact person to reach out (from the other team)?
UI design: https://preview.uxpin.com/bec3f8d14073ab230b4cf9026aefe303972f8fe7#/pages/131944592/simulate/sitemap
API work needs to be done for storing the TOS details
Acceptance Criteria
Scenario: User accepts TOS
GIVEN the user has a premium account AND they have a default payment method AND they have the appropriate account privileges WHEN they have accept the TOS THEN they are allowed to create an API KEY AND have access to BCRegistry API services
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design @xxx - please link the Design here
Link to DoR for a US/ Feature https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Relationships.md https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Entity.md
Link to the DoD for a US/ Feature https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Relationships.md https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Entity.md