Every Payment Story Starts With a Business Problem.

No. The scenarios on this page illustrate common payment-management situations and how Bonza capabilities can fit into those journeys. They should not be interpreted as named customer case studies unless explicitly identified as such. No verified Bonza Payments customer story has been published on this site, so this page contains no customer name, logo, quotation, metric or case-study result. When an approved customer story exists, it will appear in its own section and be labelled as a verified customer story.

Bonza supports relevant payment-management scenarios across one-time and recurring payments, invoices, receivables, due and overdue activity, refunds, customer credits, multiple configured payment gateways, customer payment experiences and forward payment visibility. Bonza Payments is a Salesforce-native payment-management suite for organizations that need customer payment activity connected to Salesforce.

Yes. One-time, ad hoc, recurring and invoice-related payment activity are distinct payment models that sit in one payment-management model, so the customer payment story stays connected across them. Recurring payment management is not full subscription billing and does not include pricing plans, usage, metering, proration or product catalogs.

An invoice records what was billed or expected. A receivable is the amount still outstanding against it. Bonza keeps expected, collected and outstanding readable together in customer context, so Finance can interpret the payment position rather than reconstructing it from disconnected records.

Yes, and the distinction matters. An amount may remain outstanding before its relevant due date, become due when that date arrives and become overdue only after it passes. Bonza keeps those states distinct so a team can tell open payment activity from payment activity that now deserves attention. Bonza does not chase customers, run dunning sequences, apply late fees or escalate anything on its own.

A refund is treated as a change to an existing payment position rather than a separate finance event. The refund stays attached to the payment it relates to, so the customer payment history continues through the change instead of restarting after it.

Bonza customer credit refers to relevant credit recorded and managed within Bonza for future supported payment use, kept connected to the Salesforce customer. It should not be interpreted as a digital wallet or bank balance, and it is not cash, stored money, a stored-value account or funds held by Bonza.

Yes. Multiple configured gateway options can sit beneath one Bonza payment-management experience, and a relevant default or alternative gateway may be configured where applicable. The business configures which gateway applies. Bonza does not perform smart routing, least-cost routing, automatic failover, cross-gateway retry or AI gateway selection. Stripe, Razorpay and PayU are named only as examples of configured options and imply no partnership or endorsement.

Relevant payment experiences can be presented inside Salesforce Experience Cloud, so paying becomes part of the customer journey customers already use. Experience Cloud is the customer-facing environment and does not itself process the payment. The configured payment gateway performs the relevant underlying processing.

Bonza Payment Forecasting provides forward visibility into relevant expected customer payment activity rather than treasury or corporate cash-flow forecasting. It covers upcoming, scheduled, recurring and expected customer payment activity. Expected payment activity is useful context and is not guaranteed collection.

Bonza AI Payment Insights are designed to surface relevant payment context for human review rather than autonomously making financial decisions. A payment moving into overdue status, a payment method expiring before upcoming payment activity, or a payment position changing after a refund or credit are the kinds of situations that can be surfaced. The AI does not collect payments, contact customers, approve refunds, create credits, write off receivables, change schedules, choose gateways or predict payment failure or default.

The Payment Command Center is an operating view across connected Bonza payment activity, covering collected, outstanding, due, overdue and upcoming alongside receivables, forecast, recurring activity, payment method expiry, insights and recent payment, refund and credit activity. It is an operating view rather than the entire product.

No. Configured payment gateways perform relevant underlying payment processing, while Bonza manages the wider payment lifecycle and Salesforce context around that activity. Bonza is not a payment gateway, is not the processor, and does not hold customer money.

No. Bonza Payments is not an accounting system, a general ledger, an ERP or a treasury platform, and it does not perform bank reconciliation. It manages the customer payment lifecycle in Salesforce and is designed to sit alongside those systems rather than replace them.

Salesforce provides relevant customer and business context and remains the system of record for the relationship. Bonza provides the Salesforce-native payment-management layer around that relationship. Configured payment gateways perform relevant underlying payment processing. Bonza Customer Stories illustrate how payment requirements can move from an isolated transaction model toward a connected customer payment lifecycle.