The Payment May Happen Once. The Customer Relationship Doesn't.

A one-time payment is an individual customer payment that does not itself operate on a recurring schedule. It is collected once, for a relevant payment requirement, rather than repeating according to an arrangement. Being one-time describes the payment's frequency and says nothing about whether the payment record should be isolated from the customer's wider context.

One-time payments and recurring payments describe different payment patterns. One-time payments occur individually, while recurring payments repeat according to a relevant schedule or arrangement. A one-time payment runs payment need → payment → status; a recurring arrangement runs schedule → payment → status → next payment. Neither is better — the question is which matches the payment requirement.

Bonza Payments is Salesforce-native, so the payment requirement, the payment activity, its status and its history stay connected to the Salesforce customer record. The journey is select the customer or context, define the payment and amount, choose the relevant configured payment route, collect, record and track, then manage what happens next — payment history, receivables, a refund, customer credit or another future payment where relevant.

No to both. Bonza Payments does not replace the underlying payment gateway. Configured gateways perform relevant payment processing, while Bonza manages the wider Salesforce payment lifecycle. Provider names are used only as configured-gateway examples and imply no endorsement or partnership. Salesforce does not process the payment either.

Yes. Bonza supports multiple configured payment gateways, with a relevant default that can be configured and another configured gateway selected where appropriate. There is no automatic intelligent routing, least-cost routing, failover, cascading, automatic retries through another gateway, AI gateway selection, authorisation optimisation or universal gateway compatibility.

Where the business already uses Salesforce Experience Cloud for a customer-facing journey, Bonza can support relevant connected payment experiences inside that environment, with payment activity flowing back to Bonza and Salesforce. Experience Cloud itself does not process the payment — the configured gateway does.

Where receivables are relevant, yes. The payment transaction is only one part of the picture: Bonza's wider suite can provide context around what has been collected and what remains outstanding, including due and overdue states. No partial payment support, payment plans or installment plans are claimed.

A one-time payment can still have a post-payment lifecycle. Depending on the supported use case, relevant payment value may later be managed through a refund via the relevant configured refund process, or recorded as customer credit. Customer credit is recorded and managed within Bonza Payments and is available for relevant future payment use. Bonza does not store customer money — there is no wallet, cash balance or stored-value account, and no instant or guaranteed refund timing is claimed.

Yes, and that is the point of keeping the first one connected. A second independent payment requirement is simply another one-time payment on the same customer, and because the first is part of the customer's payment history rather than a standalone record, the second arrives with context rather than starting from nothing.

No — that is the most common misreading. A payment can occur once while still being connected to the customer, the account, an invoice or relevant payment obligation, receivables, a refund, a customer credit, the configured gateway that handled it, payment history and future payment activity. One-time describes frequency, not isolation.

Yes. Businesses can use both one-time and recurring payment models, and Bonza Payments is designed to keep relevant payment activity connected within a wider Salesforce-native payment-management suite. Both can run on the same customer without either becoming the other.

No. Bonza manages the customer payment lifecycle, not the general ledger or the accounting close. It does not produce accounting entries, revenue recognition, automatic reconciliation, bank reconciliation or settlement reconciliation, and it is not a bank and does not hold customer funds.