Remove "Other" payment method from registration forms#1706
Merged
Conversation
jmilljr24
approved these changes
Jun 17, 2026
jmilljr24
left a comment
jmilljr24
left a comment
Collaborator
There was a problem hiding this comment.
If you think this is the direction it needs to go that is fine.
My understand from the conversation was to remove "other" completely. They will get user feedback on any confusion regarding scholarships and payments.
One down side to this is we now have another option of a hardcoded value with extra logic around it. I don't love having the stripe checkout dependent on a string (we already saw the issue of checkouts not working with this). My vote it so just remove other. One less thing to deal with right now.
maebeale
changed the title
The "Other" option offered no clear meaning to registrants and added noise to the payment choice. Keep it in code and form data — the scholarship flow still relies on it as the stored payment method — but filter it out of the options surfaced on the public registration and bulk payment forms, preserving it only when it's already the selected value (e.g. the scholarship preset). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
maebeale
force-pushed
the
maebeale/hide-other-payment-type
branch
from
89af800 to
957fe77
Compare
The "Other" option offered no clear meaning to registrants and added noise to the payment choice, so drop it from the form builder's payment method options. New registration and bulk payment forms no longer offer it; existing forms are left as-is. Scholarship applicants previously had "Other" preselected; they now see the same default as everyone else, and are still never charged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
maebeale
force-pushed
the
maebeale/hide-other-payment-type
branch
from
957fe77 to
091beb5
Compare
Collaborator
Author
|
ok updated to just remove |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR and why is this important?
How did you approach the change?
FormBuilderService::PAYMENT_METHOD_OPTIONS, so newly built registration and bulk payment forms no longer offer it. Existing forms are left as-is (no data migration).UI Testing Checklist
Anything else to add?