Bonza Payments Documentation
Everything You Need to Understand and Work With Bonza Payments.
Explore Bonza Payments by task, capability and payment lifecycle area — from payment management and recurring payments to receivables, refunds, customer credits, configured gateways, customer experiences, forecasting and operational visibility.
Documentation status
What Exists Today, and What Does Not.
Bonza Payments documentation provides guidance for understanding and working with Bonza's Salesforce-native payment-management capabilities. This page is the documentation information architecture, published ahead of the documentation itself.
No documentation article has been written yet. That means there are no installation procedures, no Salesforce object or field references, no permission sets, no package or release versions, no API or endpoint reference, no error codes and no developer material anywhere on this site — and none is implied below. What does exist is a capability page for each part of the suite, and those are what the navigation routes to.
Why this matters more here than elsewhere
Documentation is the one place where an invented detail causes real damage: someone follows a fabricated step, looks for a field that does not exist, or builds against an API that was never published. So this page states availability explicitly for every area rather than leaving you to discover the gap.
| Area | Available today | Not yet written |
|---|---|---|
| Getting started | Payment Management |
|
| Collect & bill | One-Time & Ad Hoc Payments |
|
| Manage & recover | Receivables |
|
| Connect & experience | Multiple Payment Gateways |
|
| Understand & optimise | Payment Command Center |
|
| Administration & configuration | Nothing published yet |
|
| Troubleshooting | Nothing published yet |
|
| Technical and developer | Nothing published yet |
|
1 · Getting started
New to Bonza Payments? Start With the Payment Model.
Before configuring any individual capability, it helps to know where that capability sits in the payment lifecycle. Bonza Payments manages the wider payment lifecycle in Salesforce while configured payment gateways perform relevant underlying transaction processing.
- Collect
- Track
- Manage
- Anticipate
- Operate
Concept
Salesforce provides relevant customer and business context. Bonza provides the Salesforce-native payment-management layer. Configured payment gateways perform relevant underlying payment processing. Payment activity then remains part of the wider Bonza payment lifecycle.
Architecture
Before You Configure Bonza, Understand the Three Layers.
Most payment confusion traces back to treating one of these three as though it were another. The stack below is described in text as well as drawn, so it does not depend on reading a diagram.
- SalesforceRelevant customer and business context — the account, the agreement, the relationship.
- Bonza PaymentsThe payment-management layer: position, receivables, refunds, credits, recurring activity and forward visibility.
- Configured payment gatewayRelevant underlying transaction processing, by whichever provider the business has configured.
- Payment activity returnsThe result comes back and stays part of the Bonza and Salesforce payment context.
Important
Do not confuse gateway configuration with the entire payment-management model. The gateway processes the relevant transaction; Bonza manages the payment lifecycle around it. Stripe, Razorpay and PayU are named here only as examples of gateways a business might configure, implying no partnership or endorsement.
Primary navigation
What Are You Trying to Do?
Eight tasks, each routing to the pages that currently cover it. Where a task needs configuration steps that have not been written, that is stated rather than implied.
I need to collect a payment.
I need to manage repeating payments.
I need to understand what is still open.
I need to handle a payment after collection.
I need to configure payment options.
I need to understand what is coming next.
I need to operate the payment function.
I need to troubleshoot something.
Caution
Each destination above is a capability page that explains what something does and where it sits in the lifecycle. None of them is a configuration guide, and none contains setup steps, field names or screen-by-screen instructions, because those have not been written.
2 · Collect & bill
Collect & Bill
Bonza documentation can cover payment management, one-time and recurring payments, invoices, receivables, due and overdue payment visibility, refunds and customer credits where corresponding documentation exists. This area covers how payment activity begins.
Payment management
Payment context, payment activity, relevant payment status, payment history, and how that activity connects to the wider lifecycle.
Payment ManagementOne-time & ad hoc payments
- Customer
- Payment requirement
- Payment
- Configured gateway
- Result
- Payment history
Recurring payments
- Schedule
- Collect
- Track
- Anticipate
Important
Recurring payment management is not full subscription billing. It focuses on repeating payment activity, and does not include pricing plans, usage, metering, proration or product catalogs.
3 · Manage & recover
Manage & Recover
What has been collected, what is still open, and what happens when payment value changes after collection.
Receivables
Collected, outstanding, due, overdue and the relevant customer payment position. The two questions this area exists to answer: what has been collected, and what is still open?
ReceivablesDue & overdue payments
- Outstanding
- Not yet due
- Due
- Overdue
- Attention
Note
An amount may remain outstanding before its relevant due date, become due when that date arrives, and become overdue only after it passes. The amount does not change; its timing state does.
Refunds
- Original payment
- Change required
- Refund
- Updated position
Caution
No refund service level, partial-refund rule, approval flow, fee or settlement timing is documented here, because none has been established.
Credit management
- Credit created
- Customer credit available
- Relevant future payment
- Credit used
- Updated credit position
Concept · terminology
Customer credit in Bonza refers to relevant credit recorded and managed for supported future payment use. It should not be interpreted as a bank balance or digital wallet. It is not cash, stored money, a stored-value account or funds held by Bonza.
4 · Connect & experience
Connect & Experience
How payments reach the customer, and which provider processes them. Bonza supports multiple configured payment gateways, including examples such as Stripe, Razorpay and PayU, while maintaining a wider payment-management experience in Salesforce.
Multiple payment gateways
- Configure
- Select
- Collect
- Track
Caution
Smart routing, least-cost routing, automatic failover, cascading, cross-gateway retry and AI gateway selection are not documented, because none is established. Gateway credential fields and per-provider configuration steps have not been written either.
Customer payment experience
- Understand
- Review
- Choose
- Pay
- Understand outcome
The customer-facing journey is not the same thing as gateway processing. One is what the customer reads and decides; the other is what moves the money.
Customer Payment ExperienceExperience Cloud payments
- Salesforce Experience CloudThe customer-facing environment.
- Customer and payment contextWho the customer is and what is expected of them.
- Bonza payment experienceThe payment-management capability inside it.
- Configured payment gatewayRelevant transaction processing.
Important
Salesforce Experience Cloud does not itself process the payment, and Bonza does not provide identity management or the whole portal. Experience Cloud component setup steps have not been written.
5 · Understand & optimise
Understand & Optimise
The operating view, the signals that surface into it, and the forward context around them.
Payment Command Center
The operational view across collected, outstanding, due, overdue and upcoming activity, receivables, forecasting, payment activity requiring attention, AI Payment Insights and payment-method expiry. No KPI customization is documented, because none is established.
Payment Command CenterAI Payment Insights
- Payment data
- Signal
- Context
- Insight or priority
- Human review
- Action
Important
Bonza AI Payment Insights are designed to surface relevant payment context for human review rather than autonomously making financial decisions. Nothing collects, contacts, approves, credits, writes off, reschedules or selects a gateway on its own, and no default or payment-failure prediction is made.
Payment forecasting
- Past — what happened
- Present — what is open
- Future — what is expected
Concept
Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow or treasury forecasting. Expected payment activity is not guaranteed collection.
Payment method expiry
An expiry date read against upcoming payment timing produces a relevant timing signal. Expiry does not guarantee payment failure, and no automatic card-updater behaviour is documented.
Payment Method ExpiryReference
Payment Terms That Should Not Be Treated as Interchangeable.
| Term | What it means in Bonza |
|---|---|
| Invoice | What was billed or expected. |
| Payment | Relevant payment activity that took place. |
| Receivable | The relevant amount still outstanding. |
| Due | An outstanding payment that has reached its relevant due point. |
| Overdue | A relevant payment remaining outstanding beyond its due point. |
| Refund | Relevant payment value returned through the applicable refund process. |
| Customer credit | Relevant value recorded and managed for the customer in Bonza for supported future payment use. |
Knowing Where to Click Is Not Enough if You Do Not Know What the Payment State Means.
Payment systems contain terms and states that look similar and behave differently. Useful documentation has to carry both the action and the concept.
- Outstanding≠Overdue
An amount can be outstanding well before its due date.
- Recurring payment≠Subscription billing
Repeating payment activity is not a billing platform with plans and metering.
- Payment forecast≠Cash-flow forecast
Expected customer payment activity is not a corporate cash position.
- Customer credit≠A wallet
Recorded value for future supported payments is not held cash.
- Payment gateway≠The payment management system
One processes the transaction; the other manages the lifecycle around it.
The documentation standard
Concept plus action equals useful documentation. Explaining a screen without explaining the payment state around it leaves the reader able to click and unable to judge.
6 · Administration & configuration
Administration & Configuration
Nothing published in this area
This section exists in the architecture and is empty on purpose. No setup, payment configuration, gateway configuration, customer payment experience configuration, Experience Cloud configuration, recurring payment configuration, user access, permission set or organization settings documentation has been written, so none is shown. Configuration screens and settings are not described here merely because they would be logical.
When this area is written it will sit under the structure above. Until then, the capability pages explain what each part of the suite does, which is a different question from how to configure it.
7 · Troubleshooting
Troubleshooting
No troubleshooting articles published
No error codes, error messages, known issues, diagnostic logs or resolution steps have been documented, and none is invented here. What follows is a diagnostic method rather than a fix list: it helps you work out which layer a payment issue sits in before you go looking for an answer.
First Identify the Layer. Then Troubleshoot the Payment.
- 01Customer experienceDid the customer reach the expected payment experience at all?
- 02Bonza payment contextWas the relevant payment context available — the right customer, the right expected amount?
- 03Configured gatewayWhich configured gateway was involved in the attempt?
- 04Payment resultWhat transaction result was returned by that gateway?
- 05Salesforce and Bonza statusWhat payment state is visible afterwards?
- 06Classify the areaIs this about collection, status, receivables, post-payment activity or future payment activity?
Answering those six narrows the problem to one layer, which is usually the difference between a five-minute question and an afternoon.
Discovery
Not Sure Where to Look? Follow the Payment.
If you know where the payment is in its lifecycle, you can find the page that explains what happens next.
| Where the payment is | Where to look |
|---|---|
| Payment requirement | Payment Management |
| Collection | One-Time & Ad Hoc Invoices |
| Processing | Multiple Payment Gateways |
| Open position | Receivables |
| Timing | Due & Overdue Payments |
| Change after collection | Refunds Credit Management |
| Future activity | Payment Forecasting Payment Method Expiry |
| The operation | Payment Command Center AI Payment Insights |
By role
Find Documentation for the Work You Do.
Salesforce administrator
Where each capability sits, what the customer sees, and which layer owns what. Setup and configuration steps have not been written.
- Payment experiences
- Gateways
- Experience Cloud
Salesforce architect
The Salesforce, Bonza and configured gateway boundary, the multi-gateway model and Experience Cloud. No data model or API reference exists.
- Architecture
- Multi-gateway model
- Lifecycle
Finance and Accounts Receivable
Position rather than events: what was collected, what remains open, what changed and what is expected next.
- Receivables
- Due & overdue
- Refunds & credits
- Forecasting
Payment operations
Payment status, recurring activity, post-payment change and what currently needs attention.
- Payment status
- Recurring
- Attention signals
Customer service
What happened to a customer's payment, whether anything was refunded or credited, and what the customer can see.
- Payment history
- Refunds
- Credits
Revenue operations
What happened after the commercial event, what remains open and what is expected next.
- Lifecycle
- Receivables
- Forecasting
Standard
What Good Bonza Documentation Should Help You Answer.
Eight questions any article in this set will need to answer. They are published here as the standard the documentation will be held to.
What am I configuring or using?
Where does it sit in the payment lifecycle?
What does this payment state mean?
What happens before this step?
What happens after this step?
Which system is responsible?
What should I expect to see?
Where should I look if something is different?
The principle
The best documentation does not only explain a screen. It explains the payment context around the screen — which is why the capability pages are a useful stand-in while the articles are unwritten.
Why one documentation model
One Payment Suite. One Connected Documentation Model.
Bonza Payments spans payment management, one-time and ad hoc payments, recurring payments, invoices, receivables, due and overdue payments, refunds, credit management, multiple payment gateways, customer payment experience, Experience Cloud payments, payment forecasting, payment-method expiry, AI Payment Insights and the Payment Command Center.
Documentation for a suite like that has to preserve the relationships between those capabilities rather than describing each as an isolated feature — which is the reason this page is organised by task and payment state rather than by screen. One payment lifecycle, many documentation paths, one connected model.
Documentation FAQ
Questions About This Documentation.
Where should I start with Bonza Payments documentation?
With the payment model rather than a capability. Bonza Payments manages the wider payment lifecycle in Salesforce while configured payment gateways perform relevant underlying transaction processing, and almost every later question depends on that boundary. The Payment Management page covers it.
What is Bonza Payments, and is it a payment gateway?
Bonza Payments is a Salesforce-native payment-management suite. It is not a payment gateway, a bank, an accounting system, an ERP or a full subscription billing platform, and it does not hold customer funds. Configured gateways such as Stripe, Razorpay or PayU perform the relevant transaction processing.
How much documentation is actually published right now?
None. No documentation article has been written. This page is the information architecture plus a working search across the 47 pages that do exist on this site. The availability table near the top states, area by area, what exists and what has not been written.
Is the search on this page real?
Yes, and it searches the pages published on this site rather than documentation, because there is no documentation to index. It is plain keyword matching over page titles and topics with no AI answering, no assistant and no generated responses.
Where can I find recurring payment, receivables or refund information?
Through the task router or the search above. Recurring activity is covered by Manage Recurring Payments, open amounts by Receivables and Due & Overdue Payments, and post-payment change by Refunds and Credit Management. These explain what each part does, not how to configure it.
Where can I find multiple gateway or Experience Cloud information?
Multiple Payment Gateways and Experience Cloud Payments. Neither documents gateway credential fields, per-provider configuration or Experience Cloud component setup, and neither claims smart routing, least-cost routing, automatic failover or cross-gateway retry.
Where can I find Payment Forecasting and AI Payment Insights information?
Payment Forecasting and AI Payment Insights. Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow or treasury forecasting, and Bonza AI Payment Insights are designed to surface relevant payment context for human review rather than autonomously making financial decisions.
Does Bonza have developer or API documentation?
No. There is nowhere to find Bonza technical documentation today, because none has been written: no data model, API reference, endpoint list, authentication method, event or webhook specification, sample code or Salesforce object reference has been published, so there is no developer section on this page and no "API Reference" in the navigation. Anything you find claiming otherwise did not come from here.
Are there installation or configuration instructions?
No. The Administration & Configuration section exists in the architecture and is deliberately empty: no setup steps, package details, Salesforce editions, permission sets, object or field names or organization settings have been documented.
Where can I find troubleshooting information?
No troubleshooting articles, error codes or resolution steps have been written. What the Troubleshooting section offers instead is a six-question method for identifying which layer a payment issue sits in, which is genuinely useful and does not require inventing an error list.
What is the difference between this and the rest of the Resources section?
Resources teach the concept; documentation helps you do the work. The Resources Hub routes from a question to a page, the Blog and Guides & eBooks explain the payment model, the Product Tour walks the lifecycle, and this page is where precise product guidance will live.
Where can I get help if this does not answer my question?
No product support channel has been published on this site, so there is no support desk to point you at. The practical route today is a conversation about the payment requirement you are trying to support in Salesforce.
Still looking
Still Looking for the Right Bonza Answer?
Explore the Product Tour for a connected walkthrough, look through the focused demo concepts, or discuss the payment requirement you are trying to support in Salesforce.