Do standalone (non-event) forms ever need payment collection?

Open
#2,590 0 comments 0 reactions 0 assignees View on GitHub

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

blocked stakeholder-question

🤖 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

  1. 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)?
  2. If yes, what should it charge against, and where should the money/record land (no EventRegistration exists today)?
  3. 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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rubyforgood/awbw

All issues in rubyforgood/awbw

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.