I want to see how a payment is collected.
Videos & Demos
See Bonza Payments in Action. One Payment Moment at a Time.
Explore focused walkthroughs across the Bonza Payments suite — from collection and recurring payments to receivables, refunds, customer credits, multiple gateways, Experience Cloud, forecasting and operational payment visibility.
Salesforce-native payment management suite. The Bonza Payments Videos & Demos library provides focused visual walkthroughs of Salesforce-native payment-management capabilities.
Definition
What Are the Bonza Payments Videos & Demos?
The Bonza Payments Videos & Demos library is a visual learning centre for organizations evaluating Salesforce payment management. It provides focused walkthroughs of relevant Bonza capabilities and payment scenarios so buyers can see how payment activity moves through Salesforce, Bonza Payments and configured payment gateways.
The Videos & Demos library differs from the Product Tour: focused demos show individual capabilities or payment scenarios, while the Product Tour shows the connected end-to-end payment lifecycle.
Bonza demo content can cover relevant one-time payments, recurring payments, receivables, due and overdue visibility, refunds, customer credits, multiple configured gateways, customer payment experiences and payment operations where real demo assets exist.
You do not need to watch everything. Start with the payment problem you are trying to understand.
Demo selector
What Do You Want to See Bonza Do?
Twelve payment questions. Pick one and the concept is drawn out below — what it shows, the visual itself, the Product Tour step where you can step through it, and the capability page that explains it.
Demo concept 1 of 12
How does payment management work in Salesforce?
The distinction everything else rests on: which layer holds the customer, which manages the lifecycle, and which actually moves the money.
Salesforce to Bonza to configured gateway
- SalesforceCustomer, account and business context
- Bonza PaymentsThe payment-management lifecycle
- Configured gatewayRelevant transaction processing
What this shows
- Where Salesforce context sits
- What the payment-management layer is responsible for
- What the configured gateway does and does not do
- Why the result has to come back up
Step through it
This is step 4 of the Product Tour, where you can move through it one state at a time.
Open Product Tour step 4The gateway processes the transaction. Bonza manages the payment lifecycle around it.
How these are shown12 of 12 concepts drawn, not filmed
Where they route25 published pages routed to
InventoryVideos presented as published: none
All figures in these visuals are illustrative sample values used to explain the concept. They are not real customer data, a measured Bonza result or a performance claim.
Start from intent
Tell Us What You Came to See.
Eight intents, each routing straight to the pages that answer it. If you want the whole story rather than one moment, the last row is the one to take.
I want to see recurring payments.
I want to see what Finance sees.
I want to see what happens after payment.
I want to see multiple gateways.
I want to see the customer experience.
I want to see what happens next.
I want the full Bonza walkthrough.
By team
Watch the Payment View That Matters to Your Team.
This selector is subtractive on purpose. It shows what a role should watch and what it can reasonably skip, because the point of a focused demo library is not watching all of it.
The shortlist
Read the position, then what needs attention.
What was collected, what remains open and what needs attention?
Worth watching (5)
- Invoice and receivables
- Due and overdue over time
- Refunds and customer credits
- Forward payment visibility
- Signals and the operating view
Can be skipped for this role (7)
- Payment management foundation
- A one-time payment, start to finish
- Recurring continuity
- Multiple configured gateways
- The customer side of the payment
- Experience Cloud payments
- Payment-method expiry timing
5 of 12 concepts selected for this role · you do not need to watch everything
Across the five roles, all 12 concepts are covered — none is orphaned
The categories in full
Every Demo Category and the Questions It Answers.
The same twelve concepts as a readable index, with the questions each one has to answer and where the capability is documented.
Payment management
The foundation the rest of the suite sits on.
- How does payment management work in Salesforce?
- How is Bonza different from the payment gateway?
- What does the wider payment lifecycle look like?
- What happens before and after the transaction?
One-time & ad hoc payments
A single payment, followed through.
- How is an individual payment initiated?
- Where does the customer context come from?
- What happens after the payment is collected?
- Where is payment status visible?
Recurring payments
Continuity between occurrences.
- How do recurring payments remain connected?
- What has already been collected?
- What is expected next?
- What timing signals matter?
Invoice & receivables
What was expected against what is open.
- What was expected?
- What has been collected?
- What remains open?
- Is anything due or overdue?
Due & overdue
The same amount, changing meaning.
- How does an open amount become more operationally relevant over time?
- When is something merely outstanding?
- When does it become due, and then overdue?
Refunds & customer credits
Two directions for returning value.
- Where did the value go after the original payment?
- What does a refund change?
- What does a customer credit change instead?
Multiple payment gateways
Several providers, one process.
- How does Bonza sit above the gateway layer?
- How does a default configured gateway fit?
- How can another configured gateway be selected where relevant?
- How can customer payment journeys remain consistent?
Customer payment experience
The journey around the form.
- What am I paying, and how much?
- What payment option is available?
- What happened after I paid?
- What payment context follows?
Experience Cloud payments
Three layers that are not the same thing.
- What does Experience Cloud provide?
- What does Bonza provide inside it?
- What still belongs to the configured gateway?
Payment forecasting
Three horizons from one record.
- What relevant payment activity is expected next?
- What sits behind the expectation?
- Why is expected not the same as guaranteed?
Payment method expiry
Two dates in relation to each other.
- Why does timing matter before the next payment?
- What does the expiry date mean on its own?
- What does its relationship to the next payment create?
Insights & Command Center
What surfaces, and where.
- How do payment signals become decision support?
- What does a signal say, and what does it not say?
- What does the operating view bring together?
Not shown, not claimedNothing in these categories implies guest checkout, pay-by-link, QR payments or saved cards; subscription plan changes, usage or metered billing, proration or cancellation; smart routing, automatic failover, least-cost routing, cross-gateway retry or success-rate routing; automatic reminders, dunning, debt collection or customer outreach; an automatic card updater or remediation; or that Experience Cloud is the processor. Customer credit is recorded value for future supported payments, not a wallet, stored cash, a bank balance or funds held by Bonza.
How to evaluate what you see
A Good Payment Demo Should Show More Than a Successful Transaction.
Eight things worth checking in any payment demonstration, ours included.
01
Customer context
Who is paying, and where that identity comes from.
02
Payment requirement
What is being paid, and how the amount was established.
03
Processing responsibility
Which configured gateway actually handles the transaction.
04
Payment result
What happened, and where that result is recorded.
05
Current position
What remains outstanding once the payment has cleared.
06
Post-payment context
Refund or customer credit where relevant, and what each does.
07
Future context
What is expected next, and what timing signals sit ahead of it.
08
Operational visibility
What Finance or Operations would actually need to review.
If a demo stops at "payment successful," it has only shown the transaction.
It has not shown the payment operation.
In the Bonza experience specifically
Five Things to Watch for as You Look Through These Concepts.
01
Salesforce context stays central
The customer and business context remains connected throughout, rather than being handed off.
02
Bonza sits above the transaction
Bonza Payments provides the payment-management layer while configured payment gateways perform relevant underlying payment processing.
03
Gateways remain the processing layer
The configured gateway does the relevant transaction processing, and nothing on this page suggests otherwise.
04
The story continues after collection
Receivables, refunds, customer credits and recurring activity may all still be relevant.
05
The operating view extends forward
Forecasting, expiry timing and attention signals add context about what has not happened yet.
Why visual
Why Buyers Often Need to See Payments Instead of Just Reading About Them.
Payment architecture sounds simple written down: Salesforce, then Bonza, then the configured gateway. Three words and an arrow. Evaluation usually gets easier when the same thing is visible instead.
What a buyer actually wants to see is what the customer sees, what Finance sees, what changes after payment, what happens when a payment stays open, how recurring activity continues, where configured gateways fit, how upcoming activity appears, and what an operating view brings together. Those are connections, and connections are hard to read and easy to look at.
Payment management is a connected experience.
Visual material is most useful when it makes those connections visible.
And the ladder from one moment to a conversation
01
Focused concept
One capability, one question, drawn out on this page.
02
Product Tour
The connected end-to-end lifecycle, stepped through.
03
Capability page
The deep explanation of what that capability does.
04
Discussion
Your actual payment use case, with your own environment.
Watch the moment. Then follow the whole lifecycle.
What this page is for
Bonza Is Easier to Evaluate When You Can See the Payment Story.
Stated as what the material is meant to do, not as numbers, because no measured figures exist to quote.
01
Clearer product understanding
See how the payment lifecycle works rather than assembling it from feature descriptions.
02
Faster capability discovery
Jump directly to the payment topic that matters instead of reading everything.
03
Better architecture clarity
See the relationship between Salesforce, Bonza and configured gateways.
04
Clearer customer and business context
Understand both sides of the payment experience, not just the internal one.
05
Better evaluation
See capability behaviour before moving into a deeper product discussion.
06
Connected suite understanding
See how individual capabilities fit into the wider payment lifecycle.
Deliberately not claimedNo faster buying cycle, higher conversion, higher implementation success, reduced implementation time or specific return on investment is claimed, because none has been validated.
The capabilities these concepts draw on
- Payment Management
- One-Time & Ad Hoc Payments
- Recurring Payments
- Invoices
- Receivables
- Due & Overdue Payments
- Refunds
- Credit Management
- Multiple Payment Gateways
- Customer Payment Experience
- Experience Cloud Payments
- Payment Forecasting
- Payment Method Expiry
- AI Payment Insights
- Payment Command Center
And the rest of the Resources set
The demo shows the moment. The Bonza suite connects the moments.
Videos & Demos FAQ
Questions About This Library.
What can I watch on this page right now?
No video or demo recording has been published yet, so there is nothing to play. What is here instead are twelve demo concepts, each drawn as an actual visual with the question it answers, what it shows, and the Product Tour step where you can step through the same thing interactively.
How is Videos & Demos different from the Product Tour?
The Videos & Demos library differs from the Product Tour: focused demos show individual capabilities or payment scenarios, while the Product Tour shows the connected end-to-end payment lifecycle. Use this page when you want one specific answer; use the Tour when you want the whole story.
Are these concepts based on real Bonza capabilities?
Yes. Every concept describes capabilities documented on the Bonza capability pages, and each one links to the relevant page so you can check. The figures inside the visuals are illustrative sample values used to explain the concept, not real customer data.
Can I see the payment management foundation, and how Bonza differs from a gateway?
Yes, as the first concept in the selector. Bonza Payments provides the payment-management layer while configured payment gateways perform relevant underlying payment processing. Stripe, Razorpay and PayU appear only as examples of providers a business might configure.
Can I see one-time and recurring payments?
Yes, as two separate concepts. The one-time concept follows an individual payment from requirement to position; the recurring concept shows how context accumulates across occurrences. Neither implies subscription plan changes, usage or metered billing, proration or cancellation.
Can I see receivables and overdue payments in action?
Yes. The invoice and receivables concept shows an illustrative $10,000 obligation with $6,000 collected and $4,000 outstanding, and the due and overdue concept shows that same amount changing timing state. Nothing sends a reminder, runs dunning or chases a customer.
Can I see refunds and customer credits?
Yes, as a branching concept. A refund returns value outward and reduces the collected figure; a customer credit records value available against future supported payments and leaves the collected figure unchanged. Customer credit is not a wallet, stored cash, a bank balance or funds held by Bonza.
Can I see multiple payment gateways and Experience Cloud payments?
Yes, as two architecture concepts. The multi-gateway concept shows several configured providers beneath one payment process, which does not imply smart routing, automatic failover, least-cost routing or cross-gateway retry. The Experience Cloud concept separates the customer-facing environment, the payment-management capability and the processing layer.
Can I see Payment Forecasting and Payment Method Expiry?
Yes. Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow or treasury forecasting. The expiry concept shows two dates in relation to each other as a timing signal, and does not state that a future payment will fail.
Can I see AI Payment Insights and the Payment Command Center?
Yes, as the final concept. Bonza AI Payment Insights are designed as payment decision support for human review rather than autonomous financial decision-making, and the Command Center is the operating view those signals surface into.
Are there any webinars or recorded events?
No. None has been published, so none is listed. When recordings exist, this page gains a featured demo and a filterable library; until then it carries the concepts and the routes rather than empty shelves.
Can I request a demo based on my own Salesforce payment use case?
Yes, and that is the right next step if a concept here matches your problem. This page and the Product Tour both run on illustrative data; mapping the capability to your own Salesforce, customer payment journey and configured gateway environment is what a conversation is for.
Seen the Capability? Now Map It to Your Payment Process.
If a Bonza concept matches the payment problem you are trying to solve, the next step is to map that capability to your Salesforce, customer payment journey and configured gateway environment.