Manage Every Payment. Without Losing Sight of What Happens Next.

Payment management is the process of managing customer payment activity across collection, status, receivables, recurring payments, refunds, customer credits and relevant future payment activity. In Salesforce, it means keeping that activity connected to the customer record that explains who the payer is, rather than holding it in a gateway dashboard or a spreadsheet beside Salesforce.

A gateway answers one question: can this transaction be processed? Payment management answers a different one: what is happening across this customer’s payment activity? The gateway handles authorization, provider-specific processing and the transaction response. Payment management handles what the payment was for, what remains open, what was returned, what is recorded and what is expected next.

No. Configured payment gateways perform the relevant payment processing. Bonza is the Salesforce-native payment-management layer above them, and is not positioned as a payment gateway, a bank, an acquirer, an accounting platform or an ERP. Bonza does not hold customer money.

Yes. One-time and ad hoc payment scenarios are supported, and the resulting activity stays connected with the Salesforce customer and with the wider payment lifecycle rather than existing only as a standalone transaction.

Yes. Recurring payment management covers what has been collected, what is current, what is expected next and what may need attention. It is not full subscription billing: there are no pricing plans, usage or metered billing, proration or product catalogs.

Yes, and the distinction between the three matters. Outstanding describes unresolved value regardless of timing. Due means the relevant date has arrived. Overdue means it has passed. Attention adds operational priority on top. An amount can be outstanding without being due, and the amount does not change when the timing does.

Yes, and both stay attached to the payment story. A refund remains connected to the customer, the original payment, the relevant history and the updated position. Customer credit is recorded and managed within Bonza for supported future payment use. Refund timing depends on the configured gateway and the customer’s own provider, so no instant, same-day or guaranteed timing is promised.

Yes. Bonza can support multiple configured payment gateways, including examples such as Stripe, Razorpay and PayU, without positioning gateway selection as autonomous smart routing. Businesses configure the gateways they use and select a relevant default or another configured option where supported. Those names are examples of configured options and imply no partnership.

No. There is no smart routing, no least-cost routing, no automatic failover, no cascading and no automatic retry through another gateway. Gateway selection is configured by the business. What Bonza provides is one payment-management experience regardless of which configured gateway performed the processing.

Relevant payment journeys can operate through Salesforce Experience Cloud. Experience Cloud provides the customer-facing Salesforce environment, Bonza provides the payment-management capability, and a configured gateway performs the processing. Salesforce itself does not process the payment, and Bonza does not provide identity management or the entire portal.

Yes. Bonza Payment Forecasting focuses on relevant upcoming customer payment activity rather than treasury or bank-balance forecasting. Expected, scheduled and upcoming activity become visible before their dates. Expected activity is not guaranteed collection, and it is not described as certain or committed cash.

No. Overdue payments can be surfaced for attention with the context behind them, and the next step is a person’s decision. There is no automatic dunning, no autonomous collections and no automatic customer outreach.

It is the operational view across the connected payment layer — collected, outstanding, due, overdue, upcoming activity and what needs attention, in one place. It is a view over payment management rather than the product itself: the capabilities it reads from are what actually manage the lifecycle.

Bonza AI Payment Insights support human review and payment decision-making rather than autonomous financial action. Payment activity, customer context, receivables, due and overdue state, recurring activity, upcoming payments and payment-method timing are used to surface a signal with its context and a priority. The decision stays with a person. Nothing scores customers, predicts default, approves refunds or creates credits on its own.

No. Bonza does not perform general ledger accounting, revenue recognition, tax accounting, bank reconciliation or universal settlement reconciliation, and it does not replace an accounting system or ERP. Receivables in Bonza are about the visibility of the customer payment position, not about how that position is represented in an organisation’s accounting process.

No. Recurring payment management covers payments that repeat on a schedule and the operational context around them. Full subscription billing adds pricing plans, product catalogs, usage and metered billing, proration and plan changes, none of which Bonza is positioned as providing.

No. Payment Method Expiry is a timing signal: it shows that a stored method expires before an expected payment date, while there is still time to do something about it. It does not predict failure, it does not update cards automatically, and it does not contact anyone automatically.