Jump to content

Module for Recurring Payments / Subscriptions


Recommended Posts

Did anybody here developed a ProcessWire Site with Recurring Payments / Subscriptions?

I have an idea for an B2B service where companies can register themselves and if they have an active subscription they can access some specific content. They can also cancel the subscription every month.

I looked and SnipWire/FormBuilder but found nothing about Recurring Payments.

Link to comment
Share on other sites

  • 8 months later...

I have experiences with connecting to various payment gateways and done that with custom developments (modules).
Here is important that the payment gateway returns the result of the transaction to a specific url (PW side) where you can do what you need (e.g. write desired values in member page).
Also, if necessary, you can create additional cron job/scheduled task procedures for automation (e.g. member notification...).
In this particular case (member subscription), you can use "expiration date" field on the member page and check that on the front (allowed/permitted to ...).

  • Like 1
Link to comment
Share on other sites

On 9/20/2020 at 2:39 PM, markus_blue_tomato said:

I looked and SnipWire/FormBuilder but found nothing about Recurring Payments.

I remember Snipcart does have recurring payments but not on their latest API 😞

My first idea would be to look into the actual payment gateway provider, in my case my first option is Stripe which I've used their Checkout API and it's pretty straighforward, very well documented and saves a lot of development time by basically letting stripe do a lot of the heavy lifting including the actual subscription management. But I haven't actually done a subscription site! So this is all wishful thinking haha.


EDIT: Just realized this is a very old topic 🙃

Link to comment
Share on other sites

I have a membership site with recurring payments. It uses GoCardless (direct debits) - not sure what their coverage is for Austria. The API is excellent. It is cheaper than credit cards and arguably more secure. The way I do it is for the member to authorise a mandate. My site then collects on the due dates using that mandate, so this is technically a series of one-off payments, but I think you can also set it up so that GoCardless will charge automatically on a recurring basis. 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By Pete Jones
      We are currently looking at building a custom administration area with the basic outlined functionality. Users will be able to login and see their horses, their events and their payments. Admins will be able to login and see all users, horses, events, payments. Data structure below.
      1) Would this make sense to build as a single frontend with different 'admin' levels' rather than customising the backend of PW? Ultimately the PW install will be running a full frontend website (showing Horses for Sale, Events and other misc content) so users will need to login to update content.
      2) How does PW handle database relationships? Could this structure be built?
      Horses - one user can own many horses
      Membership Level (payment)
      Events - one horse can enter many events
      Required Membership Level
      Payment Items - one payment can have many payment items
      Order Type - Horse Registration/Donation/Event
      ItemID - HorseID, DonationID, EventID
      Many thanks
  • Create New...