We Built Bonza to Make Customer Payments Make Sense Inside Salesforce.

Bonza Payments is a Salesforce-native payment management suite designed to connect customer payment activity with relevant Salesforce customer and business context. It manages the wider payment lifecycle around a transaction — what was expected, what was collected, what remains outstanding, due or overdue, what changed through refund or recorded customer credit, and what payment activity is expected next.

Because payment operations rarely stay simple. A business connects a gateway to take a payment, then adds recurring payments, then reporting for what is outstanding, then refunds, then customer credits, then a second gateway, then customer-facing payments, then forward visibility, then a dashboard. No one designs that shape deliberately; it accumulates one reasonable requirement at a time. Bonza exists to connect those payment moments into one Salesforce-native payment-management model instead.

That the payment lifecycle is managed where the customer and business context already lives, rather than in an unrelated transaction system that has to be cross-referenced every time someone needs an answer. Salesforce provides the relevant customer and business context, Bonza manages the payment lifecycle, and configured payment gateways perform the relevant underlying processing. This page makes no claim about package architecture, hosting, data residency or the Salesforce security model, as none has been established here.

No. Bonza is not a payment gateway, not a processor, not a bank and not a merchant acquirer, and it does not hold customer money. Configured payment gateways perform the relevant underlying payment processing. Bonza manages the payment lifecycle around that transaction, which is a different job from performing it.

No. Those are examples of configured gateway options that can sit beneath the Bonza payment-management experience, and Bonza does not replace any of them. Naming them is an example of the gateway layer, not a statement of partnership; no partnership has been established. The business configures which gateway applies, and Bonza does not select one automatically.

Payment processing answers one question: can this transaction be authorised and completed? Payment management answers the questions around it — who the customer is, what was expected, what was collected, what remains open, whether it is outstanding, due or overdue, what changed through a refund or a credit, and what is expected next. A gateway response answers the first well and is not designed to answer the second.

Relevant one-time and ad hoc payments, recurring payments, invoice-related payments, receivables, due and overdue activity, refunds, recorded customer credits, customer-facing payment experiences including Experience Cloud, and forward payment visibility across upcoming and recurring activity. All of it stays attached to the Salesforce customer it belongs to.

Yes, as part of the same payment-management model rather than as a separate process. Recurring payment management in Bonza is not full subscription billing: it does not include usage billing, metered billing or proration, and it does not perform automatic dunning, automatic retry or an automatic card updater.

Yes, and keeping them distinct is one of the points of the product. Outstanding is what is still open, due is what has reached its date, and overdue is what has passed it. Collapsing the three into a single open figure is common and it removes the information that decides whether anyone needs to act today.

Yes, and both stay attached to the payment they came from rather than being filed as unrelated events. A refund returns value to the customer. A recorded customer credit retains relevant value within the payment lifecycle for supported future payment use; it is not stored cash, not a bank balance and not a digital wallet, and Bonza does not hold customer money.

Yes. Multiple configured gateway options can sit beneath one wider payment-management model, so a second provider does not require a second operating model. Relevant default or alternative configured gateway selection may be supported depending on the payment context, with the business deciding what applies. Bonza does not perform smart routing, least-cost routing, automatic failover, cross-gateway retry or gateway optimization, and claims no universal gateway support.

Yes, Experience Cloud payments are part of the customer payment experience layer. Experience Cloud is the customer-facing environment; it does not itself process the payment, which remains the configured gateway's role. The point of connecting it is that what the customer sees and what Finance sees stay attached to the same underlying payment story.

The operational view across relevant connected payment activity — collected, outstanding, due, overdue and upcoming at the top, with receivables, forecast, recurring activity, attention, insights and payment-method timing beneath. It is not the entire Bonza product, and it is only useful because the payment lifecycle underneath it is connected in the first place. Every figure shown on this page's Command Center visual is illustrative sample data.

Decision support. Insights are designed to observe, surface, explain and prioritise relevant payment situations — a payment that moved into overdue, a payment method expiring before relevant future activity, a position that changed after a refund or credit — and then hand them to a person. Bonza AI does not collect payments, contact customers, approve refunds, create customer credit, select gateways, write off receivables, change recurring schedules, predict default or predict payment failure.

Bonza Payment Forecasting focuses on relevant expected customer payment activity, made visible before the date arrives. It is not corporate cash-flow forecasting, revenue forecasting, treasury forecasting or bank-balance forecasting, and it is not a guarantee that any expected payment will be collected.

No. Bonza supports recurring payment management as part of the payment lifecycle, which is narrower than full subscription billing. Usage billing, metered billing and proration are not part of the model, and recurring payment management should not be read as a substitute for a billing platform where one is genuinely needed.

No. Bonza is not an accounting system, a general ledger, an ERP or a treasury platform, and it does not perform bank reconciliation or universal settlement reconciliation. Receivable visibility inside the payment lifecycle is a different thing from general accounting, and the boundary is deliberate: Bonza does not need to replace every financial system to connect the payment experience.

No founding year, founder names or leadership information has been established for publication on this site, so none appears here and none should be inferred from the absence. There is no company timeline, no team section and no customer proof on this page for the same reason. What the product does and does not do is the trust mechanism used instead, and the company section above lists exactly what is not established rather than leaving it to silence.