-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPP-113 Gov pay integration #88
base: master
Are you sure you want to change the base?
Conversation
# Conflicts: # apps/epp-new/translations/src/en/pages.json
# Conflicts: # apps/epp-new/translations/src/en/pages.json
…o EPP-113-gov-pay-integration
# Conflicts: # apps/epp-new/translations/src/en/pages.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good, I've not paid too much attention to the templates, css and tests. Just had a couple of small questions, and the concern we spoke on the phone where the payment pages have a 90 mins session, and our pages have a 30 mins session, so there is a possibility that the user could have completed the payment, but the form is not submitted
# Conflicts: # apps/epp-new/index.js
# Conflicts: # apps/epp-new/index.js
What?
EPP-113 - GOV Pay Integration
This task involves implementing the payment flow for the for new, renew and replace flows. The payment flow involves generating a random ID, creating an HMAC, initiating the request payment request, retrieving payment details, and error handling.
Why?
For new, renew and replace journeys, users need to pay the required amount.
How?
Utils
behaviours
Testing?
Screenshots (optional)
Anything Else? (optional)
Check list
here is an example commit