Skip to content
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

Registration PDF does not update to display the payment status correctly #4080

Open
1 of 3 tasks
LaurensBurger opened this issue Mar 29, 2024 · 1 comment · Fixed by #4139
Open
1 of 3 tasks

Registration PDF does not update to display the payment status correctly #4080

LaurensBurger opened this issue Mar 29, 2024 · 1 comment · Fixed by #4139

Comments

@LaurensBurger
Copy link
Collaborator

LaurensBurger commented Mar 29, 2024

Product versie / Product version

2.5.4
Vught 68
RID 195

Omschrijf het probleem / Describe the bug

When the environment is set to: wait_for_payment_to_register=True
The PDF included in the registration should refelct the successes of the payment. But at the moment it can only display the "old" status:
image

since it was generated before the payment status was updated.
image

It should be regenerated at this point to reflect the right payment status.


We're including the user-download PDF here to reflect the same status (so, you download a document that states you paid).

  • Add timestamp to PDF when it is generated: [#4080] Add timestamp to PDF report #4139
  • Handle the case where registration is done before and after payment.
  • The PDF after payment needs to reflect the updated payment status and this updated PDF needs to be sent to the registration backend. Whether the PDF is regenerated always during registration or just after payment, is up to the dev, but I (Joeri) wants that the PDF that the client can download is the same as the one sent to the registration backend (with a preference for the same physical file).
@LaurensBurger LaurensBurger added triage Issue needs to be validated. Remove this label if the issue considered valid. enhancement labels Mar 29, 2024
@joeribekker joeribekker removed the triage Issue needs to be validated. Remove this label if the issue considered valid. label Apr 8, 2024
@joeribekker joeribekker added this to the Release 2.7.0 milestone Apr 8, 2024
Viicos added a commit that referenced this issue Apr 9, 2024
@Viicos Viicos linked a pull request Apr 9, 2024 that will close this issue
Viicos added a commit that referenced this issue Apr 9, 2024
Co-authored-by: Sergei Maertens <sergei-maertens@users.noreply.github.com>
Viicos added a commit that referenced this issue Apr 9, 2024
sergei-maertens added a commit that referenced this issue Apr 9, 2024
@joeribekker
Copy link
Contributor

Refinement: Maybe we should drop support for payment after creating the registration. But, that would make the "betaalstatus" field useless so technically it seems still relevant.

The issue is how to deal with a new version of the PDF that says payment is complete, for all registration backends.

Joeri will ask if the feature "payment after registration" is still needed.

@joeribekker joeribekker self-assigned this Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

4 participants