Every Payment Question This Site Answers, and the Page That Answers It.

Bonza Payments is a Salesforce-native payment management suite. It manages the customer payment lifecycle around a transaction — what a customer was expected to pay, what was collected, what remains outstanding, what is due or overdue, what changed through a refund or recorded credit, and what payment activity is expected next — all connected to the Salesforce customer and business context it belongs to. Configured payment gateways perform the relevant underlying processing. Bonza is not a gateway, not a processor, not a bank and not an acquirer, and it does not hold customer money.

Because an absent fact and an unlisted one look identical to a reader, and the difference matters when someone is evaluating a product. Several pages here carry things that would normally be filled with placeholder content — customer proof, a partner programme, company history, contact details, a guide library — and each states what is not established rather than showing a blurred logo, an invented milestone or a “coming soon”. The same applies to product boundaries: saying what Bonza is not is more useful to an evaluation than another adjective about what it is. No single page owns that decision, so it is explained here.

Bonza Payments is not a payment gateway, a processor, a bank, a merchant acquirer, an accounting system, a general ledger, an ERP, a treasury platform, a full subscription-billing platform, a debt-collection agency, a customer wallet or a stored-value platform, and it does not hold customer money. Recurring payment management is not full subscription billing and does not include usage billing, metered billing or proration. Recorded customer credit is value retained for supported future payment use, not stored cash, a bank balance or a wallet. Payment Forecasting covers relevant expected customer payment activity and is not cash-flow, treasury, revenue, liquidity or bank-balance forecasting.

Bonza does not perform smart gateway routing, least-cost routing, AI gateway selection, automatic gateway failover, cross-gateway retry or success-rate optimization, and claims no universal gateway support. It runs no automatic dunning, no autonomous collections or customer outreach, no automatic late fees and no promise-to-pay recording, and it operates no automatic card updater. Bonza AI Payment Insights observe, surface, explain and prioritise payment situations and then hand them to a person; they do not collect payments, contact customers, approve refunds, create customer credit, select gateways, write off receivables, change recurring schedules, or predict default or payment failure.

No pricing is published on this site. There is no price list, no plan comparison, no calculator and no pricing-request workflow anywhere on it, and none should be inferred from the absence. Commercials can be raised inside a conversation about the requirement; nothing on this site implies a hidden pricing mechanism or a published figure held back.

Through the contact page. No email address, phone number, office address or working hours has been established for publication, so none appears on this site. The contact form sends what you enter, including the payment context you describe, to the Bonza team by email, so they can reply to the address you provide.

No. No customer logo, customer statement, case study, usage figure or adoption figure has been approved for publication, so none appears anywhere on this site — not as a placeholder, not blurred, and not as an unattributed quote. The Customer Stories page explains this directly and uses representative payment scenarios instead, each labelled as such. Product specificity is used as the trust mechanism rather than proof that does not exist.

Because several questions matter in more than one context, and the useful answer differs by context. “Can Bonza work with multiple payment gateways?” is answered one way on the gateway capability page and another way inside a design discussion or an operations story. The index above shows every page that answers a given question, so you can choose the framing that fits what you are trying to decide rather than being sent to a single canonical copy.

It is complete with respect to this site: it contains every question answered in an FAQ section on any page here, extracted when the site is built rather than maintained by hand. It is not a complete list of payment questions in general, and a question that does not appear is one the site does not currently answer rather than one being withheld. If you have a payment question this site does not cover, asking it directly is the faster route.

No. No security documentation, compliance certification, audit report, data-residency statement, uptime figure or service level agreement has been published on this site, and this page makes no claim about any of them. Those questions are legitimate and usually decisive in an evaluation; they simply have to be answered in a direct conversation rather than read off a marketing page.