Customer payment experience
Give customers a clear, connected way to understand and complete payments — while keeping payment activity tied to Salesforce and the wider Bonza payment lifecycle.
Part of the Salesforce-native Bonza Payments suiteWhat the customer sees is connected with what the business sees. Interfaces shown are illustrative representations; amounts, references and dates are sample values, and the options a customer is offered depend on your configuration.
Plain definition
A customer payment experience is the customer-facing journey through which a customer understands a payment obligation, selects an available payment option and completes the relevant payment.
Bonza Payments provides a Salesforce-native customer payment experience that connects that journey with the relevant Salesforce customer and payment context, so the payment remains associated with the customer and the wider payment lifecycle.
Bonza Payments is not a payment gateway. It provides the Salesforce-native payment-management layer around customer payment activity, while configured gateways handle the relevant payment-processing functions.
The real problem
The payment experience should translate internal payment complexity into a clear customer journey.
Before the pay button
Checkout is one screen. The experience is everything around it — and it can go wrong before payment processing begins at all.
A payment experience becomes confusing when the customer lacks context about the amount, the obligation or the options available. The mature approach is to connect the transaction with the customer and payment context surrounding it.
A payment link is not the same as a payment experience. This comparison is educational — it does not describe pay-by-link functionality in Bonza.
Core capability
Present the relevant customer and payment information inside the supported payment journey, so the customer understands what the payment relates to before being asked to act.
The amount requiring payment is prominent and easy to read — the primary action isn't buried inside operational detail.
Where supported, the relevant payment options are presented within the same journey, working with Bonza's broader multi-gateway architecture.
Where the configured workflow supports it, relevant customer credit is visible within the payment journey so existing value can take part in the payment.
Once payment activity occurs, the transaction stays associated with the wider Salesforce customer and payment lifecycle.
Two views
Work the customer side below — apply the credit, pick an option, pay. Watch the business record on the right keep up.
CUSTOMER VIEW
Payment submitted. Your payment status will be reflected in the payment journey.
BONZA / SALESFORCE VIEW
Illustrative interfaces. The customer-side action and the business-side record describe the same payment — how and when payment activity is reflected in Salesforce follows your integration rather than a promise of instant synchronisation made here.
How it works
The first four steps are the customer's. The last three are your payment operation's. Bonza is what makes them one sequence rather than two.
Clarity before action
A payment summary that states the obligation, the adjustment and the amount leaves nothing for the customer to work out — and nothing for your team to explain afterwards.
Summary content reflects the relevant payment information supported by your configuration. It does not describe invoice line-item functionality.
Options and credit
Bonza can support multiple configured payment gateways while keeping one connected customer payment experience. Where configured, the customer selects from the relevant options made available to them.
No smart routing, automatic gateway selection, lowest-cost routing, failover, automatic retries or universal payment methods — the customer picks from what has been configured for them.
Customer credit managed within Bonza can be available for relevant future payment use, according to the supported payment workflow. The customer chooses to use it — nothing is applied automatically.
Credit is a balance recorded and managed within Bonza. It is not a wallet, a cash balance or stored funds.
Different payment moments
A one-time payment doesn't need to become an isolated transaction simply because it happens once.
Explore One-Time Payments →The customer shouldn't have to mentally reconnect an invoice from one system with a payment form from another.
Explore Invoices →The obligation and the action should both be understandable. Bonza does not send automated reminders or run collections.
Explore Due & Overdue Payments →Recurring payment activity can be part of the customer's connected payment context.
This is payment context, not subscription self-service. This page does not describe customers pausing, cancelling or modifying a recurring arrangement, changing frequency or amount, updating a saved card, or managing autopay. [Confirm which customer-facing recurring capabilities are in scope before launch.]
Explore Recurring Payments →For organisations using Salesforce Experience Cloud, Bonza can support customer-facing payment journeys that keep relevant payment activity connected with the Salesforce environment.
The journey
Six stages, read from both sides at once. Select a stage to see what each side is doing.
Roles, not overlap
Bonza manages the broader Salesforce-connected payment journey and the payment context around it — the customer relationship, the obligation, the record and the lifecycle that follows.
The gateway handles the relevant underlying payment-processing functions according to its own capabilities and configuration.
The payment stays connected to the customer it belongs to, in the environment your teams already work in.
The customer's checklist
The payment obligation should carry clear context.
The relevant payment amount should be prominent.
The available configured payment options should be understandable.
Where relevant, available customer credit should be visible in the supported flow.
The customer should receive the relevant payment outcome or status the experience supports.
That's the question a customer never asks and a finance team always does. Bonza connects it to the customer journey rather than answering it afterwards.
Use cases
Both sides gain
Connected suite
The customer sees a payment journey. The business manages the wider lifecycle behind it — and both are looking at the same payment.
What changes
These describe the connected experience itself. We don't claim higher conversion, faster payment, lower abandonment, higher satisfaction scores, reduced DSO, increased revenue, reduced churn, fewer support tickets or higher collection rates.
Why Bonza
Customer payment activity connects with the wider Salesforce relationship rather than arriving as an orphaned transaction.
The customer-facing experience connects with invoices, payments, receivables, refunds and credits.
Support relevant configured payment choices without making each gateway a separate customer journey.
Bring available customer credit into relevant future payment scenarios where supported.
Extend customer payment journeys into Salesforce Experience Cloud scenarios.
Keep relevant customer payment activity connected with Bonza's wider payment-management environment.
FAQ
It is the customer-facing journey through which a customer understands a payment obligation, selects an available payment option and completes the relevant payment — including the context, amount and status around the transaction, not only the payment form itself.
By connecting the journey with the relevant Salesforce customer and payment context. The customer sees what the payment relates to, how much is owed, which configured options are available and — where supported — any available credit, while the resulting payment activity stays associated with the customer record.
Salesforce itself does not process payments. Bonza Payments provides a Salesforce-native payment experience where the customer-facing journey and the resulting payment activity stay connected to Salesforce, with a configured gateway performing the relevant processing.
Yes. Bonza supports customer-facing payment experiences including Salesforce Experience Cloud scenarios, keeping the relevant payment activity connected with the Salesforce environment.
Where configured and supported, the relevant payment options can be presented within the payment journey. Not every customer necessarily sees every configured gateway — what appears depends on how the experience has been configured.
Where the configured payment workflow supports it, available customer credit can be surfaced in the payment journey and used toward the payment. It is selected rather than applied automatically, and credit is a balance recorded and managed within Bonza — not a wallet or stored funds.
Yes. An invoice payment experience can carry the invoice reference, the amount due and the relevant status into the payment journey, so the customer doesn't have to reconnect an invoice from one system with a payment form in another.
Yes. A one-time or ad hoc payment can be completed within the same connected experience and stays associated with the relevant customer context rather than becoming an isolated transaction.
The payment is created and managed within the Salesforce-native Bonza payment layer, so the customer, the obligation and the resulting payment activity share one record. How and when the payment result is reflected follows your integration rather than any promise of instant synchronisation.
No. Bonza Payments is a Salesforce-native payment-management suite that works with configured payment gateways for the relevant payment-processing functions. It is not a gateway, a processor or a bank.
Bonza can be configured with supported payment gateways; examples discussed for the platform include Stripe, Razorpay and PayU. That list is not exhaustive, and available integrations and capabilities depend on the implementation.
This page does not describe customer self-service subscription management. Recurring payment activity can appear as part of the customer's payment context, but pausing, cancelling or modifying a recurring arrangement, changing frequency or amount, updating a saved card and managing autopay are not capabilities claimed here — confirm what is in scope for your implementation.
No self-service refund initiation is claimed. Refunds are managed by your team within Bonza, where the refund stays connected to the original payment and the customer record. Whether any customer-facing refund request step exists in your implementation is worth confirming separately.
See how Bonza Payments connects customer-facing payment journeys with Salesforce, configured payment options and the wider payment lifecycle.