Do standalone (non-event) forms ever need payment collection?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- payments
Research direction
Start by reviewing PR #2588 and the standalone form flow at /f/:slug, then inspect how payment_method, someone_else_will_pay, and additional_forms currently attach to EventRegistration. The next step is stakeholder confirmation of whether standalone payments are needed and, if so, what they charge and where their records belong; otherwise, mark these fields as event-only on the Smart field settings page.
Written by the indexing model from the issue text.
Description
🤖 From Claude: Filed on behalf of the team while working on the standalone-form smart-field parity work (PR #2588).
The question
Do we need standalone forms (collab / agreement forms filled out at /f/:slug, not attached to an event) to collect payment?
Why it's blocked
We made person and organization smart fields behave the same on standalone forms as on event registration forms (PR #2588). The one group we could not bring over is payment — payment_method, someone_else_will_pay, and additional_forms (Invoice / W-9):
- Those fields all write to an
EventRegistration, and the pay-now flow starts a Stripe checkout using the event's cost. - A standalone form has no event and no registration, so there is nothing to attach a payment to and no cost to charge.
So "handle payment on standalone forms the same as event forms" isn't implementable without deciding what a payment on an event-less form even means.
What we need from stakeholders
- Is there a real need to take payment on a form that isn't tied to an event? If so, for what (a flat fee? a donation? a membership)?
- If yes, what should it charge against, and where should the money/record land (no
EventRegistrationexists today)? - If no, we'll leave payment as event-only and mark those payment smart fields as event-only on the Smart field settings page.
Until we hear back, payment stays event-only.
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 28
- Avg merge
- 14h 29m
- Merged PRs (30d)
- 292
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rubyforgood/awbw
-
blocked
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rubyforgood/awbw#2824 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rubyforgood/awbw#2822 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rubyforgood/awbw#2160 ·
Maintainers usually reply within 1 day
-
Update callout faq defualt text when the new person subscription launchesPossibly taken @maebeale claimed this 98 days ago. Openblocked
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubyforgood/awbw#2095 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rubyforgood/awbw#2088 ·
Maintainers usually reply within 1 day
All issues in rubyforgood/awbw
Similar issues
-
Bug Ruby
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/sentry-ruby#3211 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
internetee/registry#2984 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ecosyste-ms/issues#862 ·
Maintainers usually reply within 1 day
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredPossibly taken @mimosa claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
riscv/riscv-unified-db#2829 ·
Maintainers usually reply within 1 day