We'd like to accept direct debits as membership payments using GoCardless in order to remove the unreliability of standing orders and make it easier to set up a payment.
We should do this using GoCardless's pre-authorisation/billing flow, which does not set a fixed payment amount per month, so members can easily change their membership payment on our site without cancelling and re-creating the payment plan. It also allows us to potentially charge for consumables or other services using the same method in the future.
This will mean we need to initiate the bill from our system for every member each month.
We will need to move the logic used to subscribe members and send new-member and expiry emails out of the existing ruby reconciliation system and into PHP, so we can share this code between bank transfer and direct debit payments.
General consensus seems to be that we should do this in the new python framework rather than sticking with PHP. So, this depends on #115. See how deep that rabbit hole goes.
We'd like to accept direct debits as membership payments using GoCardless in order to remove the unreliability of standing orders and make it easier to set up a payment.
We should do this using GoCardless's pre-authorisation/billing flow, which does not set a fixed payment amount per month, so members can easily change their membership payment on our site without cancelling and re-creating the payment plan. It also allows us to potentially charge for consumables or other services using the same method in the future.
This will mean we need to initiate the bill from our system for every member each month.
We will need to move the logic used to subscribe members and send new-member and expiry emails out of the existing ruby reconciliation system and into PHP, so we can share this code between bank transfer and direct debit payments.