-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Pay and Invite to Pay docs #2444
Conversation
Removed vultr server and associated DNS entries |
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.
Prioritising docs over refactor makes sense ahead of audit, thanks for getting these through!
@@ -82,7 +84,14 @@ export async function fetchPaymentRequestDetails( | |||
next(); | |||
} | |||
|
|||
// middleware used by /payment-request/:paymentRequest/pay?returnURL=... | |||
// https://docs.payments.service.gov.uk/api_reference/create_a_payment_reference/#json-body-parameters-for-39-create-a-payment-39 |
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.
appreciate these comments 👍
5fac00f
to
a059c37
Compare
What does this PR do?
I had initially split this into two "Pay" and "Invite to Pay" PRs but as they're quite tightly coupled it proved pretty tricky - the total lines of code changed in two PRs (even with one branching over the other) was significantly higher than a single PR.
Regression tests passing against this branch https://github.com/theopensystemslab/planx-new/actions/runs/6912983715 ✅