Why Bonza
Because Payment Processing Is Only One Part of the Payment Problem.
Bonza Payments brings the wider customer payment lifecycle into Salesforce — from one-time and recurring payments to receivables, refunds, customer credits, multiple configured gateways, upcoming payments and operational visibility. Bonza Payments is designed for Salesforce-powered organizations that need payment management beyond individual transaction processing.
Salesforce-Native Payment Management Suite
How it usually grows
SalesforceA fragmented payment view
The Bonza model
SalesforceOne connected payment lifecycle
One customer payment lifecycle.
Not a collection of payment projects.
In short
Why Choose Bonza Payments?
Bonza Payments is designed for Salesforce-powered organizations that need more than transaction processing. It provides a connected payment-management layer around the customer relationship, so relevant payment collection, receivables, recurring activity, refunds, customer credits, customer payment experiences, multiple configured gateways and future payment visibility can be understood as part of one payment lifecycle.
Bonza Payments provides the Salesforce-native payment-management layer, while configured payment gateways perform relevant underlying payment processing. Bonza connects relevant customer payment activity across one-time and recurring payments, receivables, due and overdue activity, refunds, customer credits, configured gateways and future payment visibility.
The difference between a payment gateway and Bonza Payments is that the gateway focuses on relevant transaction processing while Bonza manages the wider customer payment lifecycle in Salesforce. The question worth asking is not whether a payment can be processed. It is whether the customer payment lifecycle around that payment can be managed.
The real buyer problem
Most Payment Complexity Appears After the First Successful Integration.
The first requirement is easy to solve well. It is the next nine that decide what the payment operation becomes.
“We need to take a payment.”
Connect a gateway. One system.
“We also need recurring payments.”
Add recurring logic. Two.
“Finance needs receivables.”
Add reports or a spreadsheet. Three.
“We need refunds.”
Add another workflow. Four.
“We need customer credits.”
Add another data model. Five.
“We need another gateway.”
Add another integration. Six.
“Customers need to pay through Salesforce.”
Add another customer journey. Seven.
“We need to see upcoming payments.”
Add forecasting. Eight.
“We need payment insights.”
Add another layer. Nine.
“We need one operating view.”
Build a dashboard over all of it. Ten.
Add the requirements one at a time
Solved one requirement at a time
The same requirements, one payment model
One requirement, one place to put it. Both models look the same here.
The business never intended to build ten payment systems. It simply solved ten payment requirements one at a time.
Each of those decisions was defensible on the day it was made. What none of them asked was what the whole payment lifecycle should look like — which is the question Bonza is built around.
Why Bonza 01
1. Keep the Payment Connected to the Customer Relationship.
Two systems hold different halves of the same event, and neither one holds both.
What the gateway knows
- Amount
- Transaction status
- Provider reference
What the business also needs
- Customer
- Account
- Relevant payment obligation
- Payment history
- Receivables
- Recurring context
- Refund and credit context
- Upcoming payment activity
- Payment attention signals
- Customer
- Salesforce
- Bonza
- Payment activity
- Current payment position
- Next payment context
The gateway explains the transaction. Salesforce explains the customer relationship. Bonza connects the payment lifecycle to that relationship.
Why Bonza 02
2. Manage What Happens Before and After the Transaction.
The transaction is one moment in four stages. Most tooling covers the second.
Before payment
- Customer
- Invoice or payment requirement
- Recurring context
Payment
- Customer experience
- Configured gateway
- Transaction result
After payment
- Collected
- Outstanding
- Receivable
- Refund
- Customer credit
Next
- Recurring
- Upcoming
- Forecast
- Expiry
- Attention
A payment gateway is essential to processing. But processing alone does not explain the full customer payment position.
Why Bonza 03
3. Avoid Turning Every Payment Requirement Into Another Point Solution.
Fourteen capabilities in four bands. Each solves a different payment problem; the model underneath them is the same one.
Collect & bill
- Payment Management
- One-Time & Ad Hoc
- Recurring
- Invoices
Manage & recover
- Receivables
- Due & Overdue
- Refunds
- Credit Management
Connect & experience
- Multiple Gateways
- Customer Payment Experience
- Experience Cloud Payments
Understand & optimize
- Payment Command Center
- AI Payment Insights
- Payment Forecasting
- Payment Method Expiry
Each capability solves a different payment problem. Bonza connects them through one payment-management model.
Why Bonza 04
4. Support Different Payment Models Without Creating Different Payment Worlds.
Three payment models, one customer. The models differ; the customer payment story should not fragment along with them.
- One-time
- Recurring
- Invoice-related
- Bonza payment management
- Customer context
- Payment history
- Current position
The payment models are different. The customer payment story should still remain connected.
Recurring payment management is not full subscription billing. It does not include pricing plans, usage, metering, proration or product catalogs.
Why Bonza 05
5. Know What Was Collected and What Is Still Open.
A successful payment and an open balance can both be true at once.
Illustrative figures — not customer data
Expected
10,000what was billed or expectedCollected
6,000what has actually been paidOutstanding
4,000the receivable still openOf which
3 statesnot yet due, due, overdueA successful payment does not always mean the customer payment position is complete.
Why Bonza 06
6. Keep Refunds and Customer Credits in the Same Payment Story.
Collection is not the end of the payment. Value can change afterwards, along two different paths.
- Payment
- Collected
- Value change
Path one
- Refund, returning value to the customer
- Attached to the payment it relates to
Path two
- Customer credit, recorded for future supported payment use
- Attached to the Salesforce customer
- Updated payment position
What happens after collection should not become a disconnected finance event.
Customer credit is credit recorded and managed within Bonza for future supported payment use. It is not a wallet, stored cash, a bank balance or funds held by Bonza.
Why Bonza 07
7. Use Multiple Configured Gateways Without Letting Each Gateway Define the Payment Experience.
The gateway layer can change without the payment-management experience changing with it.
- Salesforce
- Bonza
- Gateway A, B or C
Examples of configured gateway options
- Stripe
- Razorpay
- PayU
One payment-management experience. Multiple configured gateway options.
A relevant default or alternative configured gateway may be supported where applicable, and the business configures which applies. Bonza does not perform smart routing, least-cost routing, automatic failover, cross-gateway retry or gateway optimization. The gateways above are named only as examples and imply no partnership or endorsement.
Why Bonza 08
8. Connect What the Customer Sees With What the Business Needs to Know.
The same payment event, read from two sides, asking different questions.
Customer view
- What am I paying?
- How much?
- What relevant option is available?
- Did the payment complete?
Business view
- Who paid?
- What was expected?
- What was collected?
- What remains open?
- What changed?
- What is expected next?
The customer needs a payment journey. The business needs a payment operating view. Bonza connects the two around the same payment lifecycle.
Why Bonza 09
9. Keep Relevant Payment Journeys Inside the Salesforce Customer Experience.
Where the relationship already runs through Experience Cloud, paying can be part of that journey rather than a departure from it.
- Customer
- Salesforce Experience Cloud
- Bonza payment experience
- Configured payment gateway
- Payment activity
- Bonza / Salesforce context
Experience Cloud
- The Salesforce customer-facing environment
Bonza
- Relevant payment-management capability
Configured gateway
- Relevant payment processing
Experience Cloud provides the environment. It does not itself process the payment, and neither does Bonza.
Why Bonza 10
10. Understand More Than Transaction History.
Four time bands around one customer. Most payment systems explain the first one well.
4 time bands · 15 capabilities across them · 10 requirements in the complexity builder
Most payment systems explain what happened. Good payment management should also help explain where things stand and what may be coming next.
Why Bonza 11
11. See Relevant Payment Activity Before the Payment Date Arrives.
Bonza Payment Forecasting provides visibility into relevant upcoming, recurring and expected customer payment activity.
What it covers
- Expected
- Upcoming
- Scheduled
- Forecasted
What it is not
- Not guaranteed collection
- Not treasury forecasting
- Not corporate cash-flow forecasting
- Not bank-balance forecasting
- Not revenue forecasting
Expected payment activity is useful context. It is not guaranteed cash.
Why Bonza 12
12. Add Timing Context Before the Next Payment Happens.
Two dates exist independently. The relationship between them is the useful part.
Illustrative example — not customer data
Payment method expiry
- 31 Oct
Next expected payment
- 15 Nov
- Timing signal
- Human review
The expiry date is data. The relationship between expiry and future payment timing creates operational context.
This does not mean the payment will fail. Bonza does not update cards automatically, contact customers automatically, or remediate anything on its own.
Why Bonza 13
13. Use AI to Reduce Interpretation Work While Keeping Financial Decisions Human.
The decision stays with a person. What AI removes is the work of reading the context first.
- Payment data
- Context
- Signal
- AI payment insight
- Human review
- Action
What it can surface
- A payment moved into overdue status
- A relevant payment method expires before upcoming payment activity
- A customer payment position changed after a refund or credit
- Upcoming payment activity changed
What it does not do
- Collect payment
- Contact the customer
- Approve refunds
- Create credits
- Write off receivables
- Change schedules
- Choose gateways
- Predict payment failure or default
Surface, explain, prioritize. The financial decision stays human.
Why Bonza 14
14. See the Wider Payment Operation From One Command Center.
Thirteen sections above describe one customer at a time. A payment operation has to be read across all of them.
Illustrative structure — no figures, no customer data
Top KPIs
- Collected
- Outstanding
- Due
- Overdue
- Upcoming
Main panels
- Receivables
- Payment Forecast
- Recurring Activity
- Needs Attention
- Payment Method Expiry
- AI Insights
Recent activity
- Payments
- Refunds
- Customer Credits
- Recurring Events
The Command Center is not the entire product. It is the operating view across connected Bonza payment activity.
The honest comparison
Why Not Just Use What You Already Have?
Four reasonable alternatives. Each one is credited with what it genuinely does well before anything is said about where it strains — because a comparison you cannot trust is not worth reading.
4 alternatives · each credited with what it does well before any criticism · 16 strengths named · 0 argued against without that
Custom development is not automatically wrong, gateways are not the problem, and spreadsheets are not the enemy. The risk is that every new payment requirement becomes another payment project.
Architecture
Who Owns What in a Salesforce Payment Architecture.
Three layers, and the boundary between them does not move. Each one states what it does not do, Bonza included.
3 layers · each states what it does not do, Bonza included · 11 boundaries named
The gateway explains the transaction. Salesforce explains the customer relationship. Bonza connects the payment lifecycle to that relationship.
Trade-offs
Different Approaches Solve Different Parts of the Payment Problem.
This is an architecture comparison, not a scoreboard. Every approach leads on something, and none of the labels is a tick or a cross.
| Capability | Payment gateway | Custom build in Salesforce | Spreadsheet or manual process | Point solutions | Bonza payment management |
|---|
13 capabilities × 5 approaches · 9 labels, none of them a tick or a cross · 5 of 5 approaches lead on something
A gateway leading on transaction processing is not a weakness, and Bonza relying on one is not a gap. The table is about where each approach puts its effort, so the architecture trade-off is visible rather than argued.
What Bonza does differently
Bonza Is Designed Around the Payment Relationship, Not Only the Transaction.
Seven pillars. None of them is a single feature — the differentiation is the connection between them.
Salesforce-native payment management
Relevant payment activity stays connected to Salesforce customer and business context rather than sitting beside it.
Payment-lifecycle orientation
Before the payment, the payment itself, after the payment, and what comes next — treated as one sequence.
Multiple payment models
One-time, ad hoc, recurring and invoice-related activity in one connected model. Recurring management is not full subscription billing.
Receivable context
Collected, outstanding, due and overdue stay distinct from one another and readable at the same time.
Post-payment continuity
Refunds and recorded customer credit stay attached to the original payment instead of becoming separate finance events.
Multi-gateway flexibility
Configured gateway choices sit beneath one payment-management model. Selection is configured by the business, not automated.
Forward and attention visibility
Expected activity, payment-method timing and surfaced context extend visibility past transaction history.
And the customer-facing side
What the customer sees and what the business needs to know stay connected to the same lifecycle rather than being assembled separately.
Decision framework
When Does Bonza Become Relevant?
Not every organisation needs a payment-management layer. These are the conditions under which one starts to earn its place.
- Payment activity needs to stay connected to Salesforce customer context.
- The organisation uses more than one payment model.
- Finance needs visibility into collected and outstanding activity.
- Due and overdue states matter operationally, not just in reporting.
- Recurring payments create ongoing questions rather than a one-off setup.
- Refunds and credits need to stay connected to the original payment story.
- More than one configured payment gateway is relevant.
- Customers need a Salesforce-connected payment experience.
- Finance wants visibility into upcoming payment activity before its date.
- Payment-method timing matters before the next payment.
- Teams need one operational payment view rather than several.
- Payment signals should support human review rather than act on their own.
The more questions you need to answer after “can we process the payment?”, the more you are dealing with payment management rather than payment processing.
For your evaluation
Questions to Ask Before Choosing a Salesforce Payment Solution.
Ask these of us, and of anyone else you are considering. They are the questions that separate a gateway integration from a payment-management model.
- Does the solution stay connected to Salesforce customer context?
- Is it only a gateway integration, or a wider payment-management model?
- Can it support one-time and recurring payment requirements?
- Can it connect invoice-related payment activity?
- Can Finance understand what was collected and what remains open?
- Can it distinguish outstanding, due and overdue?
- Can it keep refunds connected to the original payment?
- Can it manage relevant customer credit?
- Can multiple configured gateways fit beneath one operating model?
- Can customer-facing payment journeys stay connected to internal payment context?
- Can it provide relevant forward payment visibility?
- Can payment-method timing be understood before the next payment?
- Can teams see what may need attention?
- Does AI support human decision-making rather than silently taking financial action?
Choose the payment model, not only the checkout experience.
Trust through boundaries
Clear Boundaries Are Part of the Bonza Value Proposition.
A product that claims everything is harder to evaluate than one that is specific about where it stops. Bonza is not positioned as any of these.
What it is
Salesforce-native payment management.Bonza does not need to replace those systems, and nothing on this site suggests it does. Configured payment gateways still perform the processing, your accounting system still does the accounting, and Bonza manages the payment lifecycle in between.
A clear architecture is easier to trust than a product that claims to do everything.
Who benefits
Why Bonza Matters to Different Teams.
Five teams, five sets of questions, one underlying payment story.
Finance & AR
Visibility into collected, outstanding, due, overdue and relevant upcoming payment activity, without rebuilding it from exports.
Finance & Accounts ReceivableRevenue operations
Connect the commercial relationship with what actually happens during the payment lifecycle that follows it.
Revenue OperationsBusiness operations
Understand payment activity across current status, changes, upcoming activity and attention signals in one place.
Consolidate Payment OperationsCustomer service
Understand what happened to a specific customer’s payment, including refunds and relevant recorded credit, without an internal handoff.
Customer ServiceSalesforce teams
Use a reusable payment-management layer rather than creating a separate integration pattern for every payment requirement.
Salesforce TeamsEveryone at once
Different teams need different views. The question is whether the underlying payment story changes depending on who is asking.
Improve Receivables VisibilityIndustry relevance
Different Industries. The Same Need for Connected Payment Context.
The payment model comes first. What changes by industry is which parts of it matter, not what Bonza claims to be.
What changes
What Choosing a Connected Payment Model Can Change Operationally.
Eight things that are different once the lifecycle is connected. All of them are about visibility and continuity, because those are the ones that can be stated honestly.
Connected payment visibilityRelevant payment activity can be understood in customer context rather than as isolated transactions.
Clearer receivable positionCollected, outstanding, due and overdue activity can be understood as four distinct facts.
Connected payment historyOne-time, recurring and post-payment activity stay related to the same customer story.
Better customer and business alignmentCustomer-facing and internal payment views can remain connected to the same lifecycle.
Forward payment awarenessRelevant upcoming payment activity becomes visible before its date arrives.
Multi-gateway flexibilityConfigured gateway choices can sit beneath one management model rather than defining it.
Attention visibilityRelevant payment situations can be surfaced with context for human review.
Less payment-story reconstructionTeams can reduce how often they manually rebuild context from disconnected payment sources.
Deliberately not on that list: a return-on-investment figure, a days-sales-outstanding improvement, a collection-rate or payment-success increase, a revenue or retention gain, churn reduction, or cost and headcount savings.
Those depend on your customers, your terms and how your team works, none of which a product page can know. Connected visibility is what Bonza provides; what an organisation does with it is what produces a result.
In one view
Why Bonza, in One View.
One customer relationship, running down through the layer that keeps it connected.
Context
Salesforce customer contextCollect
One-timeRecurringInvoicesManage
ReceivablesDue & overdueRefundsCustomer creditConnect
Configured gatewaysCustomer payment experienceExperience CloudUnderstand
Upcoming & forecastPayment method timingAI Payment InsightsCommand CenterOne customer.
Many payment events.
One Salesforce-native payment-management suite.
Questions
Why Bonza, Answered.
Why should we choose Bonza Payments?
Because payment processing is only one part of the payment problem. Bonza Payments is designed for Salesforce-powered organizations that need payment management beyond individual transaction processing: collection, receivables, recurring activity, refunds, customer credits, configured gateways and forward payment visibility understood as one lifecycle rather than as separate projects.
How is Bonza different from a payment gateway?
The difference between a payment gateway and Bonza Payments is that the gateway focuses on relevant transaction processing while Bonza manages the wider customer payment lifecycle in Salesforce. The gateway answers whether a transaction was authorised. Bonza answers who the customer is, what was expected, what remains open, what was refunded, whether credit exists and what is expected next.
Why not just integrate Stripe directly with Salesforce?
That integration is a reasonable first step and Bonza does not replace it. Bonza Payments provides the Salesforce-native payment-management layer, while configured payment gateways perform relevant underlying payment processing. The question is what happens when recurring payments, receivables, refunds, credits and a second gateway each arrive as their own requirement.
Why not build payment functionality ourselves in Salesforce?
Custom development is not automatically wrong, and the first component is usually straightforward. The risk is that each new payment requirement becomes another custom payment project to build and maintain. Bonza is a reusable payment-management layer rather than a claim of no-code, zero development or no implementation effort, all of which would be untrue.
How is Bonza different from using spreadsheets for receivables?
Spreadsheets are genuinely good at manual tracking, temporary reporting and ad hoc reconciliation. The issue is not that they are bad; it is that manually reconstructing payment context across customer, payment, receivable, refund and credit does not scale well as the lifecycle becomes more complex.
Can Bonza support multiple configured payment gateways?
Yes. Bonza can support multiple configured payment gateways without positioning gateway selection as autonomous smart routing or automatic failover. Businesses configure the gateways they use and select a relevant default or another configured option where supported. Stripe, Razorpay and PayU are named only as examples of configured options, implying no partnership.
Does Bonza automatically route payments between gateways?
No. There is no smart routing, no least-cost routing, no automatic failover, no cascading and no cross-gateway retry. Gateway selection is configured by the business. What Bonza provides is one payment-management experience regardless of which configured gateway performed the processing.
Can Bonza support both one-time and recurring payments?
Yes, and they stay distinct capabilities inside one connected model rather than being treated as the same thing. Recurring payment management is not full subscription billing: there are no pricing plans, product catalogs, usage or metered billing, or proration.
Can Bonza show outstanding, due and overdue payments?
Yes, and the distinction matters. Outstanding describes unresolved value regardless of timing. Due means the relevant date has arrived. Overdue means it has passed. An amount can be outstanding without being due, and the amount does not change when the timing does.
How does Bonza handle refunds and customer credits?
Both stay attached to the payment story. A refund remains connected to the customer, the original payment, the relevant history and the updated position. Customer credit is relevant value recorded and managed within Bonza for future supported payment use. It is not a wallet, stored cash, a bank balance or funds held by Bonza.
Can customers pay through Salesforce Experience Cloud?
Relevant payment journeys can operate through Salesforce Experience Cloud. Experience Cloud provides the customer-facing Salesforce environment, Bonza provides the payment-management capability, and a configured gateway performs the processing. Salesforce itself does not process the payment.
What does Payment Forecasting add?
Forward visibility. Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow or treasury forecasting. Expected, scheduled and upcoming activity become visible before their dates. Expected payment activity is useful context; it is not guaranteed cash.
What is the Bonza Payment Command Center?
The operating view across connected Bonza payment activity: collected, outstanding, due, overdue, upcoming and what needs attention in one place. It is not the entire product. The capabilities it reads from are what actually manage the lifecycle.
How do AI Payment Insights work?
Bonza AI Payment Insights are designed to support payment interpretation and human review rather than autonomous financial decision-making. Payment activity and context are used to surface a signal with an explanation and a priority, and the decision stays with a person. Nothing collects payment, contacts customers, approves refunds, creates credits, writes off receivables, changes schedules or chooses gateways on its own.
Does Bonza replace our accounting or ERP system?
No. Bonza is not positioned as a bank, payment gateway, ERP, accounting system, treasury platform or full subscription-billing platform. It does not perform general ledger accounting, revenue recognition or bank reconciliation. Its role is Salesforce-native payment management, alongside those systems rather than instead of them.
Is Bonza a full subscription-billing platform?
No. Recurring payment management covers payments that repeat on a schedule and the operational context around them. Full subscription billing adds pricing plans, product catalogs, usage and metered billing, proration and plan changes, none of which Bonza is positioned as providing.
The conversation
If Your Payment Problem Is Bigger Than the Transaction, Bonza Is Built for That Conversation.
See how Bonza Payments could connect your customer payment lifecycle across collection, receivables, recurring activity, refunds, customer credits, configured gateways and forward payment visibility inside Salesforce.