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

GoCardless Membership payments #572

Open
dpslwk opened this issue Aug 13, 2023 · 1 comment
Open

GoCardless Membership payments #572

dpslwk opened this issue Aug 13, 2023 · 1 comment

Comments

@dpslwk
Copy link
Member

dpslwk commented Aug 13, 2023

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

@dpslwk
Copy link
Member Author

dpslwk commented Aug 13, 2023

huh nice

day_of_month
As per RFC 2445. The day of the month to charge customers on. 1-28 or -1 to indicate the last day of the month.

If end_date is blank and count is not specified, the subscription will continue forever.

metadata
Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.

pause subscription??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant