One Engine, Multiple Surfaces
Recurring giving, invoice payment plans, and customer deposits use the same scheduling foundation.
RECURRING PAYMENTS
Set the schedule once. Let the engine run it.
SecureCare’s recurring engine quietly handles donor recurring giving, customer service payment plans, and recurring customer deposits on a nightly schedule — posting each successful charge into the same accounting system as the rest of the platform.
Nightly Processing
The processor runs automatically instead of requiring staff to launch a monthly batch.
Smart Final Payment
Invoice plans cap the final charge at the remaining balance and suspend when the invoice is paid.
Line-Item Allocation
Recurring invoice payments distribute proportionally across lines that still have balance.
Auditable Cancellation
Cancel the schedule and pending future charges while retaining the historical record.
HOW IT WORKS
Set Up Once to Suspend or Cancel.
Staff should not have to rebuild a due-date spreadsheet every month. The engine already knows the payment method, amount, destination, and cadence, so it processes the schedule and records the result automatically.
Set Up Once
Create the recurring schedule from the donation, invoice, or customer-deposit context.
Run Nightly
SecureCare evaluates the schedule and processes due activity.
Post the Charge
Successful activity posts to the ledger and schedules the next run.
Adjust the Final Invoice Charge
Cap invoice-based recurring charges at the amount still owed.
Suspend or Cancel
Stop future charges when the invoice is satisfied or the schedule is deliberately cancelled.
A CLOSER LOOK
The recurring engine is intentionally quiet.
Staff should not have to rebuild a due-date spreadsheet every month. The engine already knows the payment method, amount, destination, and cadence, so it processes the schedule and records the result automatically.
Customer payments/deposits, recurring donations, and anonymous invoice plans process as independent passes.
The processor is designed to avoid double-charging and to recover from a missed nightly run.
Failed runs are retained with their failure reason for staff review.
Invoice final payments are reduced to the remaining balance automatically.
When an invoice reaches zero, the recurring schedule suspends and pending future charges are cancelled.
Anonymous public invoice payment plans can be created without a Patron account; later modifications require staff intervention.
KEY CAPABILITIES
Recurring Payments built around the real workflow.
Recurring Donations
Run donor giving schedules created through the public donation flow.
Service Payment Plans
Run recurring payments against service invoices.
Recurring Customer Deposits
Support patrons pre-loading customer account balances on a schedule.
Nightly Processor
Process due schedules automatically.
Failure History
Retain the reason a scheduled charge failed.
Smart Final Charge
Prevent invoice-plan overpayment at the end of the schedule.
Proportional Distribution
Allocate an invoice payment across remaining line-item balances.
Anonymous Invoice Plans
Support one-time setup from the public Pay Invoice flow.
Cancellation
Suspend the schedule and cancel pending future charges while preserving history.
CONNECTED ACROSS SECURECARE
Part of one connected platform.
Automate the repeatable payment work without losing the accounting history behind every charge.
PEOPLE. PURPOSE. POSSIBILITIES.
Automate the repeatable payment work without losing the accounting history behind every charge.
