Know What Happened. What's Open. What's Next. And What Needs Attention.

Payment operations management is the work of understanding and coordinating customer payment activity across the wider lifecycle, not only processing individual transactions. The relevant questions include what was expected, what was collected, what remains open, what is due or overdue, what changed after payment and what activity is expected next. It is an operating problem rather than a reporting problem: the records usually exist, and the work is assembling them into something a team can act on.

Bonza Payments connects relevant payment activity with Salesforce customer and business context. Its established capabilities span one-time and recurring payments, receivables, due and overdue activity, refunds, customer credits, configured gateways, forecasting, payment-method expiry visibility, AI Payment Insights and the Payment Command Center. For operations specifically, the point is that those are one connected lifecycle rather than a set of separate processes that have to be cross-referenced.

No. Payment processing focuses on whether a relevant transaction can be processed, and a configured gateway answers that well. Payment operations deals with the wider operational context around customer payments before, during and after that transaction. A gateway response is not designed to tell an operations team what remains open, what changed afterwards or what is expected next.

Payment status describes what happened to a particular payment. Payment position provides wider context about where the customer currently stands — whether relevant amounts remain open, are due or overdue, whether value was later refunded or recorded as credit, and whether future payment activity is expected. A payment can be collected and the customer still be unsettled; the status alone does not say so.

Yes. Receivables and Due & Overdue Payments are established Bonza capabilities designed to provide relevant payment visibility in Salesforce. Keeping the three states distinct is deliberate: outstanding is what is still open, due is what has reached its date, and overdue is what has passed it. Collapsing them into one open figure removes the information that decides whether anyone needs to act today.

Bonza includes Payment Forecasting, which provides forward visibility into relevant upcoming, scheduled or recurring customer payment activity. This is payment-operations forecasting. It is not treasury, cash-flow, bank-balance, liquidity, revenue or FP&A forecasting, and expected payment activity is not the same as guaranteed collection.

Refunds and customer credits are treated as part of the wider payment lifecycle rather than as separate side processes. A refund returns relevant value through the applicable refund process, while recorded customer credit keeps relevant value available for supported future payment use. Customer credit should not be understood as stored cash, a bank balance or a digital wallet, and Bonza does not hold customer money.

Yes. Multiple Payment Gateways is an established Bonza capability. Relevant configured gateways can be managed within the Bonza payment model, including a default or another configured gateway where appropriate, with the business deciding what applies. Bonza does not perform smart routing, least-cost routing, AI gateway selection, automatic failover, cross-gateway retries or success-rate optimization, and claims no universal gateway support.

The Payment Command Center is the operational visibility layer across relevant Bonza payment activity. It is intended to help teams see areas such as collections, receivables, due and overdue activity, recurring payments, refunds, credits, upcoming activity and payment insights in a connected Salesforce-native view. It is one capability within the payment operations story rather than the whole of it, and it is only useful because the lifecycle underneath it is connected first.

Bonza AI Payment Insights are positioned to help surface and interpret relevant payment signals and indicate where attention may be useful. The model keeps financial decisions under human review rather than positioning AI as an autonomous financial decision-maker. Bonza AI does not collect payments, contact customers, approve refunds, create customer credit, select gateways, write off receivables, predict default or predict payment failure.

No. Bonza surfaces payment activity that may deserve review and stops there. It is not a debt-collection agency, performs no autonomous collections or customer outreach, applies no automatic late fees, runs no automatic dunning and records no promises to pay. Not every overdue payment follows the same resolution path, and deciding what to do about one is a person's job.

No. Bonza is a Salesforce-native payment-management suite. It should not be positioned as a general ledger, an ERP, a treasury platform or a full accounting system, and it does not perform bank reconciliation or universal settlement reconciliation. Receivable visibility inside the payment lifecycle is a different thing from general accounting.

No. Bonza provides the payment-management layer around the customer payment lifecycle. Relevant configured gateways perform the underlying transaction processing. Bonza is not a gateway, not a processor, not a bank and not a merchant acquirer, and gateway providers named on this page are examples of configured options only, implying no partnership.