- Home
- Resources
Bonza Payments Resources
Understand the Payment Lifecycle. Solve the Right Payment Problem.
Explore practical guidance on payment management in Salesforce, including one-time and recurring payments, invoices, receivables, due and overdue payments, refunds, customer credits, multiple payment gateways, customer payment experiences, forecasting and payment operations.
Resources for Salesforce-native payment managementAn interactive map of the customer payment lifecycle in six stages: collect, track, change, connect, anticipate and operate. Selecting a stage shows the core question it answers, a short explanation, and the relevant Bonza pages for that stage, each labelled by whether it sits in Platform, Solutions or Industries. Every destination is a published page on this site. Use the arrow keys to move between stages.
What needs to be collected, and in which payment model?
Before anything else, a payment has a shape: once, repeating, or driven by an invoice or obligation. Choosing the wrong model early is what produces a second payment process later.
Collect. The question is what needs to be collected and in which payment model.
Intent-led discovery
What Are You Trying to Understand?
Seven questions people actually arrive with, each routed to the pages that answer it. Not “blog”, “guides” or “videos” — nobody has a format problem.
Start with the question you are trying to answer — not the feature name you think you need.
Definition
What Is the Bonza Payments Resources Hub?
And, just as usefully, what it is not yet.
The Bonza Payments Resources Hub provides educational content for organizations that want to understand customer payment management in Salesforce.
It brings together guidance across payment collection, receivables, recurring payments, refunds, customer credits, payment gateways, customer payment experiences, forecasting and payment operations, so buyers can understand the problem before evaluating the relevant Bonza capability.
Signature · from question to the right next step
The Resource Hub Should Help You Move From Learning to the Right Next Step.
Six questions, each routed through what to understand first, the capability that answers it, the operating model around it, and where to go next. Every destination is a page published here.
“What remains outstanding?”
The most common finance question on this site, and the one most often answered with a single number that cannot explain itself.
An amount may be outstanding before it is due, become due when the relevant date arrives, and become overdue once it passes. The amount can be identical in all three.
What remains unresolved, and which timing state it sits in today.
How the same open balance can mean completely different things depending on what it is made of.
Two Solutions pages approach this from the problem side rather than the capability side.
Question: what remains outstanding? Understand first that outstanding, due and overdue are three states rather than one.
The resource hub should not end at content consumption. It should help the visitor find the next relevant payment answer.
The learning path
Learn Payment Management in the Same Order the Payment Lifecycle Happens.
Bonza Payments covers a connected payment lifecycle that includes relevant one-time payments, recurring payments, invoices, receivables, due and overdue payment visibility, refunds, customer credits, configured payment gateways, customer payment experiences and forward payment visibility.
Payment requirement
What actually needs to be collected?
Everything downstream depends on this being stated plainly, including whether a payment is tied to an obligation or simply needs to happen once.
Payment model
Once, repeating, or invoice-driven?
Three models, and a customer can hold more than one at a time. Picking by habit rather than by requirement is how a second payment process gets built.
Payment activity
What actually happened?
A configured gateway performs the relevant processing. What matters next is that the result is recorded against the customer rather than living only in a provider portal.
Current position
What was collected, and what is still open?
Collected, outstanding, due and overdue. The last three are timing states, and collapsing them is the most common way a receivables figure stops being useful.
Post-payment change
What happens when the value changes after collection?
A refund returns the value; customer credit keeps it in the relationship. Both belong to the payment that created them.
Future payment activity
What is expected next?
Upcoming and recurring activity, with payment-method timing as an internal signal. Expected is not the same as guaranteed.
Customer experience
How does the customer understand and complete the payment?
The same obligation looks entirely different from the payer's side, and giving them context is what removes the phone call.
Payment operations
What needs attention, and who decides?
The operating layer, where signals are surfaced with context and a person makes the call.
The payment lifecycle is connected. The learning experience should be too.
The first concept
The First Concept Every Buyer Should Understand
Payment processing and payment management are different. Configured payment gateways handle relevant transaction processing, while Bonza manages the wider Salesforce customer payment lifecycle.
- Did this transaction process?
Answered by the configured payment gateway. One question, answered well.
- Who is the customer?
- What was expected?
- What was collected?
- What remains outstanding?
- Is it due or overdue?
- Was anything refunded?
- Does customer credit exist?
- What is expected next?
- Which gateway was relevant?
- What needs attention?
A gateway explains the transaction. Payment management explains the customer payment lifecycle around the transaction.
Three time horizons
A Better Payment Question Has Three Time Horizons.
Most payment reporting answers the first one thoroughly and the other two by inference.
- Outstanding
- Due
- Overdue
- Current payment status
- Recurring payment
- Upcoming payment
- Payment forecast
- Payment method expiry
Across all three: AI Payment Insights and the Payment Command Center, which surface what changed for a person to review.
A transaction report explains the past. A payment operating model should also explain the present and help teams understand the future.
Topic zones
Explore by Payment Topic
Twelve topics, each stated as the questions it answers rather than as a feature summary.
- What is payment management?
- How is it different from payment processing?
- Why connect payment activity with Salesforce?
- When should a payment be treated as one-time?
- Why does one-time not mean disconnected?
- How should an individual payment stay connected to customer context?
- What is recurring payment management?
- How is it different from subscription billing?
- How should current and next payments stay connected?
- What is the difference between an invoice and a receivable?
- What has been collected?
- What remains open?
- What is outstanding?
- What is due, and what is overdue?
- What deserves attention now?
- What is the difference between a refund and customer credit?
- How does post-payment activity change the payment position?
- Why separate payment management from the processing provider?
- How should multiple configured gateways fit within one payment operation?
- What does the customer need to understand before paying?
- What is the difference between checkout and self-service?
- How does Experience Cloud fit into the payment journey?
- What payment activity is expected next?
- How is it different from revenue or cash-flow forecasting?
- Why does payment-method timing matter?
- When is expiry an attention signal rather than a failure?
- How can AI help surface payment signals?
- What should remain under human control?
- Which questions does each team actually ask?
- How do they read the same payment lifecycle differently?
Quick answers
Payment Management Questions, Answered Clearly
Seven answers written to stand on their own, each with somewhere to go if it raises the next question.
What is payment management in Salesforce?
Bonza Payments provides a Salesforce-native payment-management layer that connects relevant customer payment activity with the customer and business context already managed in Salesforce. It covers the lifecycle around a transaction rather than the transaction alone.
What is the difference between payment processing and payment management?
Payment processing focuses on executing a relevant transaction through a configured payment gateway. Payment management covers the wider payment lifecycle around that transaction, including customer context, receivables, recurring activity, refunds, credits and relevant future payment visibility.
What is the difference between outstanding, due and overdue?
An outstanding payment is not necessarily overdue. A payment may remain outstanding before its relevant due date, become due when that date arrives and become overdue after the date passes. The amount can be identical in all three states; only the timing differs.
What is the difference between a refund and customer credit?
A refund and customer credit are different post-payment paths. A refund returns relevant value through the applicable refund process, while customer credit records value in Bonza Payments for future supported payment use. Customer credit is not a wallet, stored cash or a bank balance.
Is recurring payment the same as subscription billing?
No. Recurring payment management focuses on repeating payment events. Subscription billing may also involve pricing plans, usage, metering, proration, product catalogs and other billing logic that should not automatically be attributed to Bonza.
Does Bonza replace payment gateways?
No. Configured payment gateways perform relevant underlying payment processing. Bonza manages the broader Salesforce-native payment lifecycle. Providers such as Stripe, Razorpay or PayU are examples of the kind of gateway that can be configured, and naming them implies no partnership.
Does Bonza replace accounting or ERP?
No. Bonza Payments is not a payment gateway, accounting system, general ledger or ERP. It provides a Salesforce-native payment-management layer around relevant customer payment activity. Bonza Payment Forecasting focuses on expected customer payment activity rather than corporate revenue, treasury or bank-balance forecasting.
Guided navigation
Not Sure Where to Start? Follow the Payment Question.
Twelve yes-or-no questions, each pointing at one capability. This is deterministic navigation, not a recommendation engine and not AI.
Distinctions
Understand the Differences That Matter
Ten distinctions that decide whether a payment project is scoped correctly. Each one links to where it is worked through properly.
One executes a transaction through a provider. The other explains the customer lifecycle around it.
A frequency difference, not a connectedness difference. Both need the same payment context afterwards.
Repeating payment events, versus plans, usage, metering, proration and catalogs that are not attributed to Bonza.
One states what was expected. The other states what remains unresolved after payment activity.
Three timing states that can carry an identical amount. Collapsing them removes the reason to act.
Where the value goes, versus how it may be used later. Both belong to the original payment.
Completing a transaction, versus understanding the payment before and after it.
Expected customer payment activity, which is not corporate revenue, treasury or bank-balance forecasting.
What happened once, versus where the customer payment relationship stands now.
A provider's transactions, versus one operating view across the whole payment lifecycle.
Architecture
Understand Where Each Part of the Payment Stack Belongs.
Different systems have different responsibilities. Most payment confusion is really a boundary question wearing a feature question's clothes.
The relevant business-specific process. Bonza does not replace it.
Customer, account and business context. Bonza does not replace it.
The customer payment lifecycle, inside Salesforce.
Relevant transaction processing. Bonza does not replace it and is not one.
By team
Explore Payment Management Through the Questions Your Team Asks.
Five teams reading one lifecycle. The questions differ; the underlying record should not.
Finance & Accounts Receivable 5 questions
- What has been collected?
- What remains outstanding?
- What is due?
- What is overdue?
- What is expected next?
Revenue Operations 3 questions
- What happened after the commercial event?
- What payment activity is open?
- What comes next?
Business Operations 4 questions
- What is open?
- What changed?
- What needs attention?
- How do multiple payment processes stay connected?
Customer Service 4 questions
- Did the customer pay?
- What remains open?
- Was there a refund?
- Does customer credit exist?
Salesforce Teams 4 questions
- How should payment capability fit into Salesforce?
- What belongs in Bonza versus the gateway?
- How should Experience Cloud payments work?
- How can multiple gateways remain manageable?
By industry
See How Payment Patterns Change by Industry—Without Changing the Core Payment Lifecycle.
Each entry is the educational question that sector arrives with, rather than a logo wall.
Education
“How can relevant payer payment activity remain connected through the wider Salesforce payment lifecycle?”
Technology & SaaS
“How is recurring payment management different from subscription billing?”
Membership & Associations
“How is recurring payment different from membership renewal?”
Real Estate & Property
“How can property-related customer payments move from collected to outstanding to upcoming without turning Bonza into property management software?”
Nonprofits
“How can relevant payment activity remain connected without confusing payment management with fundraising or donor management?”
Financial & Professional Services
“How can client payment activity stay connected across invoices, receivables, payment events and post-payment changes?”
Other Salesforce-powered businesses
“Does the payment model fit Bonza even when the industry does not have a dedicated category?”
Healthcare Page not yet published
“How can relevant customer payment activity remain connected without confusing payment management with healthcare billing?”
A dedicated Healthcare page has not been published on this site yet, so this entry links to the nearest published guidance rather than to a page that does not exist. The payment pattern itself is the same one described under invoice-based payments and customer self-service payments, and Bonza operates on the customer payment side only: no medical billing, claims, patient accounting or insurance adjudication.
Starting points
Where Is Your Payment Operation Today?
Four descriptions rather than a score. Find the one that sounds like your week.
We can process payments, but most context lives in gateway portals.
We can see payment activity, but outstanding and overdue context is fragmented.
Payments, refunds, credits and customer context are increasingly connected.
We need to understand upcoming payment activity and what deserves attention.
Planned, not published
The Editorial Library This Hub Is Built to Hold
These six explainers are the recommended starting set for a payment knowledge library. None of them has been written yet, so none is presented as a published resource.
Each concept below is a slot in the planned library, with the question it would answer and the page that answers as much of it as exists today. Until a resource is written, the link goes to the real page rather than to a placeholder.
What does payment management include beyond transaction processing?
What should the gateway own, and what should the payment-management layer own?
Which payment model matches the business requirement?
How should Finance interpret open customer payments?
What happens when payment value changes after collection?
What happened, what is open and what is expected next?
A filterable knowledge library, curated collections and a latest-resources feed are all designed for in this hub's structure. They are deliberately absent until there is real content to put in them, because an empty archive and an invented one are both worse than a clear route to the pages that exist.
Why this shape
Payment Management Makes More Sense When You See the Whole Lifecycle.
Bonza Payments is designed as a connected Salesforce-native payment management suite, and this hub is organised the same way for the same reason.
Payments are not isolated transactions. They form a lifecycle — and this hub teaches the same thing the product is designed around.
FAQ
Resources Hub Questions.
Twelve questions about this hub and the payment concepts it organises.
What can I learn in the Bonza Payments Resources Hub?
The Bonza Payments Resources Hub provides educational content for organizations that want to understand customer payment management in Salesforce. It is organised around the payment lifecycle and around the questions buyers arrive with, covering collection, receivables, recurring payments, refunds, customer credits, gateways, customer payment experiences, forecasting and payment operations.
Does this hub contain downloadable guides, articles or case studies?
Not yet. No editorial library has been published on this site, so this hub does not present articles, guides, ebooks, webinars, videos or case studies as if they existed. It is built as question-led navigation into the capability, solution and industry pages that are published, and the planned editorial architecture is shown separately and marked as not yet published.
What is payment management in Salesforce?
Bonza Payments provides a Salesforce-native payment-management layer that connects relevant customer payment activity with the customer and business context already managed in Salesforce. It covers the wider lifecycle around a transaction rather than the transaction alone.
What is the difference between payment management and payment processing?
Payment processing and payment management are different. Configured payment gateways handle relevant transaction processing, while Bonza manages the wider Salesforce customer payment lifecycle, including customer context, receivables, recurring activity, refunds, credits and relevant future payment visibility.
How do I know whether I need one-time or recurring payments?
One-time describes a payment that happens once; recurring describes payment activity that repeats on a relevant cycle. A customer can hold both at the same time. One-time does not mean disconnected, and both models need the same payment context after collection.
What is the difference between an invoice and a receivable?
An invoice establishes a relevant payment obligation and states what was expected. A receivable describes what remains unresolved after payment activity has been recorded. A third question sits alongside them, which is what actually happened, and that is the payment activity itself.
What is the difference between outstanding, due and overdue payments?
An outstanding payment is not necessarily overdue. A payment may remain outstanding before its relevant due date, become due when that date arrives and become overdue after the date passes. The amount can be identical in all three states; what differs is the timing.
What is the difference between a refund and customer credit?
A refund and customer credit are different post-payment paths. A refund returns relevant value through the applicable refund process, while customer credit records value in Bonza Payments for future supported payment use. Customer credit is not a wallet, stored cash or a bank balance, and Bonza does not hold customer funds.
How do multiple payment gateways work with Bonza Payments, and can customers pay through Experience Cloud?
Bonza can support multiple configured payment gateways with the payment-management layer sitting above all of them, so the payment view is not split by provider. Where Salesforce Experience Cloud is already used for customer-facing journeys, relevant payment activity can stay connected to that Salesforce environment; Experience Cloud does not process the payment and Bonza does not provide the portal.
What does Payment Forecasting show, and how does Payment Method Expiry relate to future payments?
Bonza Payment Forecasting focuses on expected customer payment activity rather than corporate revenue, treasury or bank-balance forecasting, and expected activity is not guaranteed cash. Payment Method Expiry is an internal attention signal when a payment method expires before a relevant upcoming payment; it does not say the payment will fail.
What do AI Payment Insights and the Payment Command Center do?
AI Payment Insights surface relevant changes in payment context, such as an amount moving into overdue status or an upcoming position changing, for a person to review. The Payment Command Center is the operating view across the payment lifecycle. Neither approves anything, moves value or contacts customers, and no autonomous financial decision is made.
Does Bonza replace payment gateways, accounting or ERP software?
No. Bonza Payments is not a payment gateway, accounting system, general ledger or ERP. Configured payment gateways perform relevant underlying payment processing, and Bonza provides a Salesforce-native payment-management layer around relevant customer payment activity rather than the general ledger or the accounting close.
Resources
Have a Payment Question You Haven't Found the Answer To?
Explore Bonza's connected payment capabilities, or discuss how your current Salesforce payment process works across collection, receivables, recurring payments, refunds, credits, gateways and customer experiences.