Keep Every Customer Payment Connected Beyond the First Transaction.

By keeping the payment operation in the same environment as the customer relationship. Bonza Payments is Salesforce-native, so one-time and recurring payment activity, receivables, refunds, customer credits and upcoming payment visibility stay associated with the Salesforce customer record rather than living in a gateway portal, a recurring-payment system and a spreadsheet separately.

Yes, and that combination is the common case in technology businesses. A one-time or ad hoc payment and a recurring arrangement can run on the same customer, with both visible in one payment position rather than as two unrelated systems. An outstanding one-time balance does not disappear because the recurring cycles are collecting normally.

They are different capabilities. Recurring payment management covers repeating payment activity, the schedule, the current and next payment, payment history, relevant payment method context and upcoming payment visibility — which is what Bonza does. Subscription billing may additionally cover a product catalog, plans and packages, usage billing and metering, proration, upgrades and downgrades, mid-cycle changes, entitlements, contract amendments, billing rules, complex invoicing logic and revenue recognition, none of which Bonza claims.

No. Bonza supports recurring payment management within the broader customer payment lifecycle and should not be positioned as a full subscription-billing platform. Usage billing, metered billing, plan management, proration and pricing catalogs are not claimed capabilities.

No to both. Bonza is focused on customer payment management rather than the full revenue lifecycle associated with Salesforce revenue products, and it is not CPQ, a pricing engine or a contract-management platform. It also does not provide a general ledger, revenue recognition, tax or accounting functionality.

Yes. Outstanding, due and overdue are distinct states of the same obligation, and timing is what tells a team whether an amount is still expected or needs attention. No automated dunning, automated collections, automatic customer outreach, late-fee automation or debt collection is claimed.

Yes, as forward context: relevant expected and recurring payment activity, and payment-method expiry where it lands before an expected payment. Expected activity is never guaranteed collection, and expiry context is not a prediction that a recurring payment will fail. There is no automatic card updater, credential migration, outreach or remediation.

Bonza Payment Forecasting focuses on relevant expected customer payment activity — upcoming payments and recurring payment activity. It is not ARR forecasting, MRR forecasting, revenue forecasting, sales or pipeline forecasting, or treasury cash-flow forecasting. Expected revenue and expected payment activity are different operational views and treating them as one number leaves neither trusted.

Yes, and both stay connected to the original payment and the customer — including inside a recurring relationship, which is where post-payment change usually becomes hard to follow. Customer credit is value recorded in Bonza Payments, not a wallet, a cash balance or stored money.

Yes. Bonza supports multiple configured gateways, including a configured default and explicit selection where a scenario calls for it, while relevant payment activity stays connected to Salesforce. There is no smart routing, automatic failover, least-cost routing, gateway optimisation, token portability or settlement reconciliation, and provider capabilities are not interchangeable.

Yes, where Experience Cloud is already part of the customer environment. Relevant customer-facing payment activity can remain part of the wider Salesforce environment, so the payment a customer makes is the same payment internal teams see. Bonza is not customer portal software, identity management, account administration, a support portal or a subscription portal.

It surfaces relevant changes for a person to review — that expected recurring payment activity has changed, that relevant payments moved into overdue status, or that payment methods approach expiry before upcoming payment events. There is no churn prediction, renewal prediction, default prediction, customer health scoring, automatic collections, automatic customer contact, automatic subscription changes or revenue optimisation.