We have broadened our payments function to include recurring payments. There are some rather sophisticated ideas implemented herein:
- Validates the card information immediately
- Shows you all the unpaid items for a selected family
- Drag and drop(!) the order in which you’d like to pay the outstanding items (thus establishing a waterfall).
- Select a payment frequency and amount
- Optionally declare a maximum number of payments.
From there, the magic unfolds. As each payment date arrives, the card is charged, of course. Then, the payment is automatically applied to the outstanding items that you specified in step 3 above.
The system applies periodic payments until either (a) the maximum number of payments is reached, or (b) all outstanding items declared in the waterfall reach a $0 balance. At that point, the program applies any remaining monies to credit on file, and sends an email to your office personnel to cancel the recurring payment.
As a synagogue back office, you would accomplish all of the above within ShalomCloud. The actual card activity occurs within Stripe , but ShalomCloud handles the “conversation” with Stripe.
Many systems offer a recurring payment feature–however, you would typically find yourself making decisions on each individual payment as it arrives (“Here’s $100–let me look over the ledger–hmm, what should I apply it to??”). Not the case here–when you set up the recurring payment, you’d make those decisions during setup. The activity flows automatically from there.
If we’ve piqued your interest in this capability, please consider subscribing to this blog, by entering your email into the area at the top of the beige-colored box.
