Experience Cloud payments
Enable connected customer payment journeys through Salesforce Experience Cloud while keeping payment activity tied to customer context and the wider Bonza payment lifecycle.
Part of the Salesforce-native Bonza Payments suiteHOME / MY PAYMENTS
HOME / MY PAYMENTS / INV-10482
HOME / MY PAYMENTS / INV-10482
The relevant payment outcome is reflected in the payment journey, and the payment activity returns to your Salesforce payment context according to the integration.
The customer stays inside their Salesforce experience; the business keeps connected payment context. Interfaces shown are illustrative representations — the exact components, fields and options depend on your configured Experience Cloud implementation. [Confirm the supported Experience Cloud payment components before launch.]
Plain definition
Experience Cloud payments are customer-facing payment journeys delivered through a Salesforce Experience Cloud experience.
Bonza Payments supports relevant payment journeys through Experience Cloud while keeping customer payment activity connected with Salesforce and the wider Bonza payment lifecycle. Configured payment gateways handle the relevant underlying payment processing.
Salesforce Experience Cloud provides the customer-facing environment; Bonza Payments provides the Salesforce-native payment-management layer around the payment journey.
The real problem
Your customer is already interacting with you through Salesforce. Then a payment becomes due — and, without a connected experience, the journey breaks exactly where it matters most.
The issue isn't simply that another screen exists. It's that customer context and payment context can become disconnected at the exact moment money changes hands — and someone has to put them back together afterwards.
The better question: how do we make payment part of the customer's existing Salesforce relationship?
What a portal owes the customer
A mature Experience Cloud payment model answers six questions in one continuous thread: who is the customer, what payment needs attention, what amount is relevant, what options are available, what happened when they paid, and how that activity returns to the business.
The model
Experience Cloud provides the environment your customers already interact with you through.
Bonza provides the Salesforce-native payment-management layer that carries the journey between the portal and the processor.
The configured gateway handles the relevant underlying payment processing according to its own capabilities. Gateway names are examples of configured providers, not partnerships or endorsements.
Core capability
The payment journey stays associated with the customer interacting through Salesforce Experience Cloud — rather than becoming an anonymous transaction the moment it leaves the customer-facing experience.
Where supported, the relevant payment context appears inside the experience so customers understand what they're being asked to pay.
Where supported by the configured experience, relevant payment options can participate in the customer journey — so Experience Cloud stays the customer-facing environment even with several providers behind the payment layer.
Where the supported Bonza workflow allows it, relevant available customer credit becomes part of the future payment journey — selected by the customer, never applied automatically.
Relevant payment activity stays connected with the broader Bonza and Salesforce payment operation, according to the configured integration.
The full path
Most payment stories stop at “payment successful.” This one has a return path. Step through it.
THE RETURN PATH
Someone who already has a relationship with you — and, right now, a payment to make.
Customer sideThe journey does not end at “payment successful.” It ends with connected payment activity — and how and when that activity is reflected in Salesforce follows your integration.
How it works
Inside the experience
The invoice obligation and the resulting payment activity stay part of one connected Salesforce payment journey, rather than two records someone reconciles later.
Explore Invoice Payments →Where configured and supported, customer credit managed within Bonza can be made available as part of the relevant future payment journey. It is a balance recorded and managed within Bonza — not a wallet, cash balance or stored funds — and it is never applied automatically.
Options behind the experience
Bonza's multi-gateway capability can support relevant configured payment options inside the customer experience — without turning each provider into a separate customer journey.
The business keeps its configured default as the normal starting point in the supported customer flow.
Relevant alternatives can be made available in supported customer-facing payment scenarios.
Not all configured gateways are necessarily exposed to every customer, and Bonza does not choose a “best” gateway on anyone's behalf — no automatic routing, failover, cost optimisation, AI selection or universal payment methods, and gateways differ in what they support.
Payment moments in the portal
Relevant one-time and ad hoc payment scenarios can be connected to the customer's Salesforce-facing journey where supported.
Explore One-Time & Ad Hoc Payments →Recurring payment information can be part of the customer's broader payment relationship. This is context, not self-service control — pausing, cancelling, skipping, changing amount or frequency, updating a card or switching gateway are not claimed here.
Explore Recurring Payments →When a payment is due or overdue, a connected experience makes both the obligation and the next action clearer. Bonza does not send automated reminders or run collections.
Explore Due & Overdue Payments →Same payment, two vantage points
One customer action. One connected payment context.
Two journeys
External payment experiences are appropriate in some architectures — this isn't an argument that the disconnected model is always wrong. The Bonza model is relevant when an organisation wants payment to stay closely connected with its Salesforce customer experience.
Two related ideas
The customer-facing Salesforce environment your customers already use to deal with you.
The journey itself — context, amount, options, action and status — wherever the customer meets it.
The provider that performs the relevant underlying payment processing.
Where the payment continues to mean something after it completes.
These two pages describe different things. This one is about the environment: how a payment journey can exist inside the customer's Salesforce Experience Cloud relationship, and how the architecture holds together around it.
The customer payment experience is about the journey: what a customer sees, understands, chooses and does when it's time to pay — wherever that journey is presented. An organisation can care about the journey without using Experience Cloud at all.
Payment Command Center
A payment made in Experience Cloud is part of the same operation as every other payment — visible where your team already reads the payment picture.
Payments made through a customer-facing experience appear in the same operational view as the rest of the payment operation. This page doesn't claim a dedicated Experience Cloud analytics dashboard.
Use cases
Connected suite
Experience Cloud is a customer-facing entry point. Bonza manages everything that happens around the payment once the customer has acted.
What changes
These describe the connected architecture. We don't claim higher portal adoption, higher payment conversion, faster collections, lower DSO, higher satisfaction, fewer support tickets, reduced abandonment, increased revenue or specific ROI.
Why Bonza
Payment activity connects with Salesforce customer and business context by design, not by integration afterwards.
Support relevant customer-facing payment scenarios through Salesforce Experience Cloud.
Connect Experience Cloud payment activity with invoices, receivables, recurring payments, refunds and credits.
Work with relevant configured gateways without turning each one into a separate customer relationship.
Bring relevant customer credit into supported future payment journeys.
Keep customer-facing payment activity connected with Bonza's wider payment-management environment.
FAQ
They are customer-facing payment journeys delivered through a Salesforce Experience Cloud experience. With Bonza Payments, the relevant payment activity stays connected with Salesforce customer and payment context while a configured gateway handles the applicable processing.
Yes — where the payment experience has been configured for that Experience Cloud environment. Bonza supports relevant customer-facing payment journeys there, with payment activity connected back to the Salesforce payment context.
Experience Cloud provides the customer-facing environment, Bonza provides the Salesforce-native payment-management layer around the payment journey, and the configured gateway performs the relevant payment processing. Bonza connects the payment to the customer, the obligation and the wider lifecycle.
Yes. Bonza Payments is a Salesforce-native payment management suite, which is why payment activity can stay associated with the Salesforce customer relationship rather than living in an external system.
No. Experience Cloud provides the customer-facing Salesforce environment. The relevant payment processing is handled through your configured payment setup and gateway.
Bonza can be configured with supported payment gateways; examples discussed for the platform include Stripe, Razorpay and PayU. That list is not exhaustive, and the available integrations and capabilities depend on the implementation.
Where the configured experience supports it, relevant payment options can be presented within the customer journey. Not all configured gateways are necessarily exposed to every customer — what appears depends on your configuration.
Where configured, yes. The invoice context — reference, amount, status — can carry into the payment journey so the customer isn't reconnecting an invoice from one place with a payment form in another.
Where configured and supported, customer credit managed within Bonza can be made available as part of the relevant payment journey, and the customer chooses to use it. Credit is a balance recorded within Bonza, not a wallet or stored funds, and it is never applied automatically.
Relevant one-time and ad hoc payment scenarios can be connected to the customer's Salesforce-facing journey where supported by the configured experience.
Recurring payment information can form part of the customer's payment context, but this page does not claim customer self-service controls. Pausing, cancelling, skipping, changing the amount, frequency, card or gateway are not described here — confirm what is in scope for your implementation.
The payment is managed within the Salesforce-native Bonza layer, so the customer, the obligation and the payment activity share the same context. How and when the payment result is reflected follows your configured integration rather than a promise of instant synchronisation.
No. Bonza Payments is the Salesforce-native payment-management layer that works with configured payment gateways for the relevant payment-processing functions.
That depends on your implementation. The payment journey is presented within the Experience Cloud experience, and the relevant processing is performed by the configured gateway — whether any step of that processing is presented outside the experience depends on the gateway and how the flow has been configured. We'd rather confirm that against your setup than assume embedded processing here.
See how Bonza Payments can connect customer-facing payment journeys through Salesforce Experience Cloud with payment context, configured payment options and your wider Salesforce payment operation.