Skip to content

GoCardless implementation

Jump to bottom
Axford edited this page Apr 21, 2017 · 2 revisions

Summary of what was agreed on 20th April ref how to approach Gocardless implementation. For detailed conversation, listen to: https://www.youtube.com/watch?v=CX5UwJDrW-o

  • Use same basic mechanism for individuals and spaces - that being manual payments triggered by the foundation website (do not use gocardless subscription system)
  • Prompt individuals/spaces annually of their renewal both via email and via the website (assuming they login):
    • Include an ask of whether they want to amend their subscription payment (e.g. if space has grown, feeling generous)
    • Offer super simple one-click renewal button - that then triggers the payment request
  • Provide a account/payment summary page where users can check their payment history, amend details, etc
  • Un-matched or unusual payments should be neatly summarised for admins to review - possibly notified as well (e.g. email, telegram)

technical thoughts:

  • Use redirect flow to setup mandate and capture key info
  • Use payments API to trigger payments
  • Use webhook to capture payments (and other events, e.g. refunds) to ensure we have a complete payment history for end of year accounting, etc

Clone this wiki locally