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

As survey owner I want to require payment from respondee #519

Open
japsu opened this issue Sep 27, 2024 · 0 comments
Open

As survey owner I want to require payment from respondee #519

japsu opened this issue Sep 27, 2024 · 0 comments

Comments

@japsu
Copy link
Contributor

japsu commented Sep 27, 2024

This could support a variety of ad-hoc payment cases, such as

  • accommodation signup,
  • partly subsidized products for event organizers (eg. organizer hoodies),
  • partly subsidized tickets to an event for organizers (eg. TSH coniteanäytäntö),
  • catch-all ”the financeperson said I need to pay XX € to the event, so please take my money” form
  • etc.

Would require that the organization has a payment method configured.

When payments are configured for a Survey, it could automatically add a dimension for payment status (unpaid, paid, refunded).

Need to design how the price is calculated for a survey response:

  • Easiest way would be to specify a fixed price per response. However, this would already fail to serve most obvious cases such as multiple products (better served by ticket shop?), several instances on one form submission etc.
  • We could also assign prices to dimension values. This would, however, fail to serve multiple instances of a product.
  • We could embed a custom LISP dialect or even WASM runtime for which we could compile pricing logic functions with Rust…
    • …but let's not :)
  • We could have a field type for product selection. Products and their prices would be configured via the configuration of that field type.

Slack discussion (lippukauppa2025 private channel, ask Japsu)

@japsu japsu added this to Surveys v2 Sep 27, 2024
@japsu japsu converted this from a draft issue Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant