UX/UI - [Pay Fees] - Payment Failure

mbertucci commented 2 months ago

📖 User Story

As a host, when my payment fails I want to know that it has failed and be able to resubmit payment on the application confirmation page and on my dashboard So that I can resubmit the payment

Context:

If payment fails we need to provide them with the message that it failed and to also flag the application as payment failed.

Payment fail status is "Payment Due" see: https://app.zenhub.com/workspaces/strr-65b2a7146835aa0cdf315b79/issues/gh/bcgov/entity/21374

Unknown: what happens when payment fails on Pay API. Is it an endless loop? Is the user stuck in the Pay API?

Is there an opportunity to tell the Pay API if payment fails to 3 times then go to the confirmation page.

🎨 UX/UI Link: need design work

📏 Business Rules

[x] When a payment fails, and the host clicks "Go Back" on Pay API then take host to "Confirmation Page". Message on confirmation page states payment is still due.
- [ ] Provide url to Pay API
- [ ] Provide link to Dashboard
- [ ] see video https://bcgov.sharepoint.com/:v:/r/teams/09399/Shared%20Documents/Product%20Team%20Chat/Testing%20videos/Microsoft%20Teams%20Meeting%20_%20Microsoft%20Teams%202024-08-06%2011-21-10.mp4?csf=1&web=1&e=s1wPec
[x] Application Details Page - needs to let applicant know the "Payment Due" status and an option to pay again
[x] Dashboard status to say "Payment Due"
[x] On Host Detail View Page DO NOT include the filing status of "Registration Submitted" see image below
[x] On Examiner Detail View page include filing status "Registration Submitted"
[x] An application with failed payment will be flagged as "Payment Due" in the Examiner dashboard
[ ] An application with failed payment and flagged as "Payment Due" should not go through the automatic approval process
[ ] When host re-attempts to make payment and the transaction is success, the application should go through the automatic approval process
[ ] When host clicks to repay. the system should pull the fee from the application and pass it to the Pay API

Roadmap and Storymap links

Roadmap: https://app.mural.co/t/citzservicebcbcros0435/m/citzservicebcbcros0435/1708551828009/76eaa2c92258b0bde76157b3dd6e37220967e91a?wid=0-1708639933585 Story Board: https://app.mural.co/t/citzservicebcbcros0435/m/citzservicebcbcros0435/1706554024951/153dc4e4f3fbbd7cfc1352e0c804cb105960321e?sender=u919d7a4924c2e37e12b55343

🎭 Story Scenarios

Scenario 1: Payment fails

Given the host has attempted to make payment for the registration application
When the payment transaction fails for whatever reasons
Then the host should be notified on the application confirmation page and host dashboard
and "Then host should be able to see a link that takes them to re-attempt to complete the payment again

Scenario 2: Payment Re-attempts and successes

Given the host has re-attempted to make payment for the registration application
When the payment transaction goes through successfully
Then the host should be notified on the application confirmation page (TBD) and host dashboard
and "Then the application will go through the automatic approval process
🌐 Accessibility Scenarios

Keyboard Users

Scenario: Comprehensive Keyboard Navigation Given I am a keyboard user on the website When I use the Tab key to navigate through the website Then all interactive elements should be accessible and highlighted And I should be able to activate these elements using the Enter or Space key

Scenario: Full Content Accessibility via Keyboard Given I am a keyboard user navigating the website When I traverse through different pages and sections Then all content should be fully accessible using the keyboard alone And there should be no traps that prevent me from navigating away using the keyboard

Screen Reader Users

Scenario: Accessible Image Descriptions Given I am using a screen reader on the website When I encounter images Then each image should have descriptive alt text that conveys the same message as the image

Scenario: Structured Navigation for Screen Readers Given I am navigating the website using a screen reader When I move through different page elements Then the content should be structured with proper headings And the reading order should be logical and sequential

Scenario: Descriptive Form Fields Given I am filling out a form using a screen reader When I navigate through the form fields Then each field should be clearly labeled with descriptive text And instructions should be directly associated with their respective inputs

Low Vision Users

Scenario: Effective High Contrast Mode Given I am a user with low vision on the website When I enable high contrast mode Then all content should display with high color contrast suitable for low vision And the layout should remain coherent and unchanged

Scenario: Text Resizing Accommodation Given I am a user with low vision on the website When I increase the text size Then the text should resize without loss of information or functionality And the page layout should adapt accordingly without disrupting the user experience

Scenario: Personalized Styling Preferences Given I am a user with low vision adjusting settings on the website When I customize my styling preferences, including colors, fonts, and spacing Then these adjustments should be applied consistently across all pages And the changes should persist during my entire session or until altered by me

##

🌍 Global Scenarios

## Data Validation # Mikaela to confirm: Do we need to do these for MVP - data validation required for inputing data in the right format - as defined by business rules. ### Internet Connection #### Standard Internet Connection Given I am accessing the website from a standard internet connection When I navigate to any page on the site Then the page should load completely within 2 seconds, ensuring a fast and efficient user experience. #### Low-Speed Internet Given a user accesses "Application Details View" with a low-speed internet connection defined as under [specific speed] Mbps When the user attempts to load and interact with the dashboard page Then the "Application Details View" should prioritize critical content and functionality, loading essential elements first to ensure usability. #### Mobile Responsiveness Given I am accessing "Application Details View" on a mobile device When I click on the "any" link Then "_____ " should display correctly and be easily editable on my device, ensuring a responsive design.