As a prospective Christmas tree applicant, I would like be redirected to an error page with errors if pay.gov returns errors in the transaction

[sethalt]

Notes

User is redirected to an error page if there are errors with the pay.gov transaction

Credit card failure: 0000000000000000, and success with any other numbers

Acceptance Criteria

• [x] user sees error clearly and knows that credit card has not been charged
• [x] user can tell difference between a system error and a problem with their card (e.g. declined)
• [x] user can tell what their next step is (try again, call district, etc.)

Tasks

• [x] Update user task flow model (bryan)
• [x] Server: Update mock to generate error on the complete transaction (shekar/cameron)
• [x] Investigate error codes and decide if they should be re-written to be made human readable. (jane/bryan)
• [x] Frontend: Create error page (Seth)
• [x] Frontend: Display error, either pay.gov error codes and message or other (seth)
• [x] Server/frontend: Update mock to generate error if declined card number is used. (seth/cameron)
• [x] e2e spec (seth)
• [x] server specs (shekar)
• [x] frontend specs (seth)
• [x] Review sprint-5 feedback
• [x] Fix login.gov issuer issues by creating a mock endpoint
• [x] Update design approval flow and address process around in-review and done. (seth)
• [x] Design Pre-approved (TTS)
• [x] Design approved (Amber)

Definition of Done

• [x] Code unit / e2e tested and comply with QWASP
• [x] No new security vulnerabilities
• [x] Internal team code review
• [x] Documentation / readme.md / CircleCI updated
• [x] Docker updated
• [x] Compare finished design with mockup
• [ ] Usability tested

[sethalt]

@MelissaBraxton @tram

The first draft of our error page. Note: the message under Sorry! There's been a problem represents a message that would return from pay.gov. The message that we chose was copied from the pay.gov docs. That message would change based on the error code.

[bryanmcfadden]

First draft at task flow:

[tram]

Yay, error pages! :-) A couple things… 🤔 The WDS-style error message and the following header/paragraph seem redundant. Is it possible to go with one or the other? 👣 Recommend emphasizing the next step: trying again. Right now, it's under the "Additional information" header and feels more like an afterthought than "hey, do this".

[sethalt]

Good feedback @tram, and we made some changes. Please review.

[tram]

Nice! Just to clarify, recommend emphasizing the next step instead of emphasizing that there is a next step. In this case, removing the "What to do next" header and emphasizing "Return to the…and try again." by wrapping that line in a <strong> tag.

[sethalt]

Understood @tram . See updates below:

[tram]

👍 Ship it!

[lauraGgit]

Reviewed what's in staging in WIP 6 PR

[JaneZC]

@lpendem @MelissaBraxton @ASprinkle

Attached is a preliminary list of error codes that seem like they would be worthy of a re-write, with a focus toward ensuring someone knows what action they could take in an attempt to resolve the error. Its probably about 50 error messages, although it could still change based on what happens once pay.gov is integrated. But, definitely more than than 10.

https://app.zenhub.com/files/106473503/3d367940-71c9-4f4a-bfae-c248f2236cfb/download

[JaneZC]

@lpendem Oops! Forgot you wanted it as an image; here it is a jpeg.