What is recurring payment management?
Recurring payment management is the process of organizing, collecting, tracking and reviewing customer payments that are expected to repeat over time. It covers the payment schedule itself and the operational context around it: what was collected, what is expected next, what is outstanding and what needs attention.
How can I manage recurring payments in Salesforce?
With Bonza Payments, the recurring payment arrangement, its schedule and the resulting payment activity live inside Salesforce and stay attached to the customer record. Teams can see payment status, upcoming activity, receivables context and relevant attention items without moving between separate systems.
Can Bonza Payments manage recurring customer payments?
Yes. Bonza Payments is a Salesforce-native payment management suite with recurring-payment capability: schedules, repeated payment activity, payment status and the wider payment context around each arrangement.
What is the difference between recurring payments and subscription billing?
Recurring payment management focuses on repeated payment activity, payment schedules, status and operational visibility. Full subscription billing platforms may additionally include plan management, usage billing, proration, subscription changes and accounting-specific billing capabilities. Bonza is positioned as Salesforce-native payment management, not a complete subscription billing platform.
Can I see upcoming recurring payments?
Yes. Recurring schedules create a forward view of expected payment activity, which appears alongside the rest of the payment picture and in payment forecasting. Expected activity is a forecast of what is scheduled, not a guarantee of collection.
Can recurring payments be connected with Salesforce customer records?
Yes. That connection is the point of a Salesforce-native approach: each payment cycle stays associated with the customer, alongside invoices, receivables, refunds, credits and payment methods.
Can Bonza show recurring payments that become overdue?
Yes. Where a relevant expected payment remains outstanding, it stays visible in the due and overdue view and in the broader receivables picture. Follow-up is a decision your team makes — Bonza does not run automated dunning or send automated customer chasing.
Can Bonza show payment methods approaching expiry?
Yes. Payment method expiry provides visibility when a payment method approaches expiry before future payment activity, so the timing can be reviewed early. An expiry does not itself mean a future payment will fail.
Can Bonza forecast upcoming recurring payments?
Payment forecasting provides forward visibility into relevant expected payment activity, while Recurring Payments manages the repeated payment relationship itself. Figures shown are expected and scheduled amounts rather than guaranteed collections.
Can Bonza work with multiple payment gateways for recurring payments?
Bonza can manage payments across multiple configured gateways. Available recurring behavior depends on the gateway and the implementation — a recurring arrangement does not switch gateways by itself, and stored payment credentials are not portable between providers.
Can customers manage their recurring payments themselves?
Customer-facing payment capability depends on what has been configured, including Experience Cloud payments. This page does not claim customer self-service for pausing, cancelling, skipping, rescheduling or changing the amount or payment method of a recurring payment.
Can Bonza automatically update expired cards?
No. Bonza surfaces payment methods approaching expiry in the context of upcoming payment activity so a person can review them. It does not include an automatic card updater.
Does Bonza automatically retry failed recurring payments through another gateway?
No. Bonza does not perform automatic gateway failover or smart routing between providers. Payment activity runs through the gateway configured for that arrangement.
How do refunds and customer credits relate to recurring payments?
Refunds and customer credits stay connected to the same customer relationship as the recurring activity, so post-payment changes remain visible in context. How an available credit is applied to future payment activity depends on your configuration.