Connect What You Sell With What Customers Actually Pay.

It is connecting the payment half of the customer relationship — what was collected, what remains outstanding, what is due or overdue, what recurring or upcoming activity is expected — with the Salesforce customer context the commercial process already created. Bonza Payments gives Revenue Operations teams a Salesforce-native way to do that after the sale.

By keeping the post-sale payment story attached to the customer rather than scattered across gateway portals and spreadsheets. Payment activity, receivables, due and overdue timing, recurring arrangements, refunds, customer credits and upcoming payment activity can be read against the same Salesforce customer, with relevant attention signals surfaced for a person to review.

Yes — that connection is the point. Relevant payment activity stays associated with the Salesforce customer, so Revenue Operations does not have to treat payment data as an anonymous transaction feed or rebuild the link by hand each time.

Sales forecasting and payment forecasting answer different questions. Sales forecasting concerns potential commercial activity — what might close. Bonza Payment Forecasting focuses on relevant customer payment activity expected in the future. A business can have strong pipeline visibility and still have weak payment visibility. Bonza provides the second and does not provide the first.

Yes. Collected and outstanding are distinct operational facts, and keeping them separate is what makes both useful. Closed Won and payment collected are different events, and a commercial event does not automatically equal a completed payment.

Yes. Outstanding describes an unresolved obligation; due means the date has been reached; overdue means it has passed without resolution. Timing is what turns an amount into a priority, and all three can be read alongside upcoming activity.

Yes, as recurring payment management: what happened last cycle, what is happening now, what is expected next and what needs attention. It is not a complete subscription-management or subscription-billing platform, and this page does not claim ARR, NRR or churn analytics.

Where the implementation supports the relevant inputs, yes. Upcoming activity is expected or scheduled payment activity, not collected payment — a schedule says when a payment event is expected, not what its outcome will be.

Where supported, yes — and the useful part is seeing the expiry date next to the relevant upcoming payment date. That is early visibility, not a prediction that the payment will fail, and there is no automatic card updating or automatic customer outreach.

Yes. Payment reality can change after collection, and refund and customer-credit activity stays part of the wider payment story rather than becoming a separate record set. Customer credit is customer value recorded and managed within Bonza Payments — never a wallet, stored cash or a bank balance.

Yes. Different configured gateways can perform the relevant processing while Bonza keeps payment activity connected to the wider Salesforce payment lifecycle. There is no smart routing, automatic gateway optimisation, failover, least-cost routing, automatic retries or settlement reconciliation, and capabilities vary by provider and configuration.

No. Bonza is a Salesforce-native payment management layer that complements the wider Salesforce customer environment. It does not replace CRM, Sales Cloud or Revenue Cloud, does not provide CPQ or subscription management, and does not provide sales or pipeline forecasting.

No. Bonza is not an ERP, a general ledger, an accounting replacement or a revenue-recognition platform. Its focus is Salesforce-native customer payment management and operational payment visibility, and it does not perform bank or settlement reconciliation.

AI payment insights interpret changes in the payment picture — for example that several payments moved into overdue status, or that payment methods are approaching expiry before relevant upcoming payments — and present them with the relevant customer, amount and timing context. AI informs and prioritizes; it does not contact customers, choose collection actions, predict default or churn, score risk, issue refunds, create credits or make financial decisions.

Collected, outstanding, due, overdue, upcoming and recurring payment activity together, with the customer payment position, upcoming payment activity and relevant attention signals alongside. It is deliberately a post-sale payment view rather than a sales pipeline dashboard.