GoCardless Membership payments

for MakerSpace Ashfield

need to wrap some existing sanding order bits in a new feature flag
we word "Standing Order" to "Membership Payments" where needed

new feature flag to warp GC bits

Looks like will need 4 new entities to track things
Client
Mandate
Subscriptions
Payments

should likely tie all of the above to each other and then back to Account not User since we need to keep joint account options

hope full can use "Instant First Payment + Direct Debit mandate creation" to setup things
that way firstpayments can be confirmed in either rite away or in next day

Mandate Setup Notification
Payment Notification (advance notice)
these need to go to the email of the person paying the bill not just the member, hoping we can pull and keep this on either the Mandate or Client Entity

default notification is 10 working days, hmm one of the guide below show 3 days as example for payment notifications?
working days fubar do we need to actual count / skip bank holidays? most people likely won't care,

Can we allow date change?
maybe
Can we pick a date during setup?
Request changes of amounts
sure but if within x days of next payment collection will have to be after that (10 working days?)
both above will need a new advance notice once change confirmed on GC

https://gocardless.com/direct-debit/notifications/
https://gocardless.com/guides/posts/advance-notice/
https://hub.gocardless.com/s/article/Notifications-overview?language=en_GB

Start by reviewing the existing sanding-order implementation and the linked GoCardless notification and advance-notice guidance. Define the feature-flag boundary and how Client, Mandate, Subscriptions, and Payments relate to Account. Done requires agreed behavior for first payments, payer notifications, payment dates, amount changes, and advance-notice timing.