If Your Customer Relationship Runs on Salesforce, Your Payment Lifecycle Can Too.

Yes, where the organization's actual payment requirements align with Bonza's supported payment-management capabilities. A business does not need to belong to a specific industry category to evaluate Bonza Payments. The relevant question is whether its payment requirements match Bonza's supported payment-management capabilities — not whether its industry has a page. No claim of universal industry compatibility is made.

Organizations already using Salesforce to manage customer or business relationships, whose payment operation involves some combination of one-time payments, recurring payments, invoice-driven payments, outstanding receivables, due and overdue amounts, refunds, customer credits, multiple configured gateways, customer-facing payment experiences and upcoming payment visibility. The payment pattern is the qualifier, not the sector.

No. Bonza works with the customer and account context an organization already maintains in Salesforce. It does not impose an industry-specific data model, and it does not require the business to restructure its own operational records to fit one.

Yes, and together on the same customer. One-time and ad hoc payments and a recurring arrangement can run in parallel, with both visible in one payment position rather than as two unrelated processes. That combination is where most payment operations end up.

Yes, and it treats them as three different operational states rather than one unpaid figure. Outstanding means still expected, due means the date has arrived, and overdue means past it. The amount need not change for the state to change — timing alone moves it, and that is what tells a team where to look first.

Yes. A refund stays attached to the payment it came from, so the collected figure remains explainable rather than simply lower. Customer credit is recorded and managed within Bonza Payments, available for relevant future payment use where supported. It is not a wallet, a cash balance or stored funds, and Bonza does not hold customer money.

It supports multiple configured gateways and replaces none of them. A relevant default or another configured gateway can be used where appropriate, while payment activity stays connected to Salesforce. Configured gateways perform relevant underlying payment processing. There is no smart routing, automatic failover, least-cost routing, gateway optimisation, token portability or settlement reconciliation.

Where a business already uses Experience Cloud for customer-facing experiences, Bonza can support relevant Salesforce-connected payment journeys within that environment, with payment activity flowing back to Salesforce. No unrelated portal functionality is implied by that.

Yes to both, as forward context. Payment Forecasting covers relevant upcoming, scheduled and recurring customer payment activity, and expected payment activity is not guaranteed collection. Payment Method Expiry surfaces the case where a method expires before a future expected payment — an attention signal, not proof of payment failure, with no automatic card updater, outreach or remediation.

Neither. Bonza focuses on the Salesforce-native payment-management layer. Your industry system manages what makes your business different, Salesforce manages relevant customer context, Bonza manages the payment lifecycle, and configured gateways process the relevant transactions. Bonza should complement rather than replace industry-specific operational systems where those systems perform functions outside payment management.

No. Bonza manages the customer payment lifecycle, not the general ledger or the accounting close, and it is not an ERP, an accounting platform or a revenue-recognition system. There is no bank reconciliation or settlement reconciliation, and no industry-specific billing rules are provided.

Evaluate the organization's actual payment patterns — one-time, recurring, receivables, refunds, credits, gateways, the customer payment journey and future payment visibility — rather than relying only on an industry label. The fifteen-question checklist on this page is a way to do that in a couple of minutes; it is a count of what applies, not a score, and if the payment operation is becoming more complex than the transaction itself, Bonza is worth evaluating.