-
Notifications
You must be signed in to change notification settings - Fork 23
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
Allow payment to be disabled for certain users #2617
Closed
LaurensBurger opened this issue
Jan 27, 2023
· 1 comment
· Fixed by open-formulieren/open-forms-sdk#641 or #3841
Closed
Allow payment to be disabled for certain users #2617
LaurensBurger opened this issue
Jan 27, 2023
· 1 comment
· Fixed by open-formulieren/open-forms-sdk#641 or #3841
Comments
LaurensBurger
added
triage
Issue needs to be validated. Remove this label if the issue considered valid.
enhancement
labels
Jan 27, 2023
Refinement: Let's do amount=0 means no payment |
joeribekker
removed
the
triage
Issue needs to be validated. Remove this label if the issue considered valid.
label
Jan 29, 2024
vaszig
added a commit
to open-formulieren/open-forms-sdk
that referenced
this issue
Feb 2, 2024
…ed from submission The way to show the payment step in the progress indicator and to start the payment form was through the form. Since we want to have access to the price rules as well, we had to have access to the submission. So, the submission is now the one which tells us if a form needs payment.
vaszig
added a commit
that referenced
this issue
Feb 2, 2024
With this we evaluate the pricing rules (if they exist) in the submission method in order to see if a payment is still needed to be done, since a rule could result to zero(0) amount and no payment.
vaszig
added a commit
that referenced
this issue
Feb 5, 2024
With this we evaluate the pricing rules (if they exist) in the submission method in order to see if a payment is still needed to be done, since a rule could result to zero(0) amount and no payment.
vaszig
added a commit
that referenced
this issue
Feb 5, 2024
vaszig
added a commit
that referenced
this issue
Feb 5, 2024
With this we evaluate the pricing rules (if they exist) in the submission method in order to see if a payment is still needed to be done, since a rule could result to zero(0) amount and no payment.Additional check that the product has valid price.
vaszig
added a commit
that referenced
this issue
Feb 5, 2024
With this we evaluate the pricing rules (if they exist) in the submission method in order to see if a payment is still needed to be done, since a rule could result to zero(0) amount and no payment.Additional check that the product has valid price.
vaszig
added a commit
that referenced
this issue
Feb 7, 2024
vaszig
added a commit
that referenced
this issue
Feb 7, 2024
vaszig
added a commit
that referenced
this issue
Feb 7, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Feb 7, 2024
With this we evaluate the pricing rules (if they exist) in the submission method in order to see if a payment is still needed to be done, since a rule could result to zero(0) amount and no payment.Additional check that the product has valid price.
sergei-maertens
pushed a commit
that referenced
this issue
Feb 7, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Feb 7, 2024
sergei-maertens
pushed a commit
that referenced
this issue
Feb 7, 2024
sergei-maertens
added a commit
that referenced
this issue
Feb 7, 2024
sergei-maertens
added a commit
that referenced
this issue
Feb 7, 2024
…ment-when-amount-bigger-than-zero [#2617] Disable payment if price is zero
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thema / Theme
Form designer
Omschrijving / Description
internal: utr 39 + lv 70
Utr: As a form designer i want to create forms that (for instance) need to be paid directly when user is auth_bsn, but when the user is auth_kvk we do not require this payment and instead send a invoice. The former is an example, I would like to be able to use logic in order to determine if payment is necessary or not
LV: We would like to skip/disable payment under certain conditions - this condition could be when the form is completed by someone else (like a employee) or when the user has no possibility to pay online.
Added value / Toegevoegde waarde
No response
Aanvullende opmerkingen / Additional context
This could be achieved by creating a condition where if the price = 0, payment gets disabled. At the moment 0 will start a payment request for 0.
The text was updated successfully, but these errors were encountered: