- Home
- Industries
- Customer Self-Service Payments
Customer Self-Service Payments
Let Customers Handle the Payment Moment—Without Losing the Payment Context.
Give customers a Salesforce-connected way to understand relevant payment context, complete supported payment actions and keep the resulting payment activity connected to the wider Bonza payment lifecycle.
Part of the Salesforce-native Bonza Payments suiteIllustrative customer self-service payment journey for one sample customer, Demo Customer, whose Salesforce customer context is connected. The first column, what am I paying, shows a relevant amount of $1,000.00, $1,000.00 outstanding, a relevant due date and $100.00 of available customer credit. The second column, what can I do, lists reviewing the payment, selecting a relevant payment option, choosing a relevant configured gateway where supported, using customer credit where relevant and supported, and making the payment. The third column, what happened, shows a relevant payment status, an updated payment position, refund and customer credit context where relevant, and the next relevant payment. Every figure on this page is illustrative sample data and is not real customer data. Bonza is not the payment gateway, does not hold customer funds, and is not a customer portal, customer-service platform or identity system.
Definition
What Are Customer Self-Service Payments in Bonza Payments?
A direct answer for anyone comparing customer payment experience, portal and payment-management capabilities.
Customer self-service payments are Salesforce-connected payment journeys that allow customers to understand relevant payment context and complete supported payment actions without requiring manual guidance for every payment interaction.
Bonza Payments connects customer-facing payment activity with the wider Salesforce payment lifecycle, including relevant payment status, receivables, customer credit, configured payment gateways and payment history. Customers can complete relevant payment actions in Salesforce-connected experiences, while payment management keeps the resulting activity attached to the same customer record the business already operates on.
The friction that survives a pay button
The Customer Wants to Pay. The Organization Still Makes Them Ask.
A customer can be ready to act and still be stuck on questions nobody has answered for them. None of these questions is about the transaction itself.
What am I paying?
How much is relevant?
Is anything still outstanding?
Is the amount due?
What payment option is available to me?
Do I have relevant customer credit?
What happened to my previous payment?
Did my payment go through?
What happens next?
When the answers live in six different places, the payment is online but the experience is not self-service:
Self-service fails when the customer can click “pay” but still needs a person to explain the payment.
Four different things
A Self-Service Payment Is Not a Checkout, a Portal or a Service Desk.
These get collapsed into one conversation constantly, which is how buyers end up expecting Bonza to be three products it is not.
Payment checkout
Asks one question: can the customer complete this transaction?- Present an amount
- Take the payment
- Report success or failure
Customer self-service payment
Asks five questions, only one of which is about the transaction.- What am I paying?
- How much is relevant?
- What payment action is available?
- What happened after I paid?
- How does this connect to my wider payment relationship?
Customer portal
A place where customers do many things, most of them not payments.- Profile management
- Authentication and identity
- Account administration
- Cases, knowledge, documents
Customer-service platform
Where service work is managed, such as Salesforce Service Cloud.- Cases and agents
- Routing
- Communications
- Service workflows
Self-service payment is a payment experience—not a complete customer-service or portal platform.
Pay button ≠ self-service
A Pay Button Is Not the Same as Self-Service.
A payment checkout and a self-service payment experience are different. Checkout focuses on completing a transaction, while self-service also provides the customer with relevant payment context before and after that transaction.
- What is this payment for?
- What remains outstanding?
- Did customer credit apply?
- What is the updated position?
- What happens next?
Payment processing enables the transaction. Self-service payment management enables the customer to understand the transaction in context.
Explore Customer Payment Experience Improve Customer Payment Experience
Signature · two views, one lifecycle
Self-Service Works Best When the Customer and the Business See the Same Payment Story.
Six stages of one illustrative payment. Both panels move together at every stage. The customer panel always shows less than the business panel, and never shows something the business does not hold.
Understand · the customer finds out what the payment is for
Before any button matters, the customer needs to know what this payment relates to and how much is relevant. Nothing has been paid yet.
What the customer needs in order to act.
Everything the customer sees, plus the operational context they do not need.
The customer sees three facts. The business already holds seven. That gap is the normal, healthy state of a self-service journey, not a failure of it.
Stage 1, understand. The customer sees the customer name, what the payment is for, and an amount of one thousand dollars. The business additionally holds the connected Salesforce account, zero dollars collected, one thousand dollars outstanding, and a payment method expiry of 31 October which is internal only and is not shown to the customer.
Payment-method expiry appears on the business side at every one of the six stages and on the customer side at none of them. Exposing internal expiry signals to customers is not established behaviour, so the page does not show it happening. All figures are illustrative sample data.
The customer does not need every internal detail. But the customer-facing action should connect to the same payment context the business operates.
Understand → act → confirm
A Good Self-Service Payment Journey Should Answer Three Questions.
Most payment experiences answer only the middle one. The first and the third are what make the action feel safe to take.
Understand
- What am I paying?
- What amount is relevant?
- What is outstanding?
- Is something due or overdue?
- Is customer credit relevant?
Act
- What supported payment action is available?
- What configured payment option can I use?
- Can I make the relevant payment now?
Confirm
- What happened?
- What is the payment status?
- How did the payment change my current position?
- What relevant payment activity comes next?
Self-service works when the customer can understand enough to act and see what changed afterward.
Where the pattern appears
Different Industries. Same Need for Customer Payment Independence.
These describe payment patterns, not industry-specific portal functionality. Each entry states what Bonza does not provide in that sector, because a shared payment pattern does not make the surrounding systems interchangeable.
Education Learner or payer
A learner or payer may need to understand and complete a relevant payment without contacting Finance for every payment interaction. The person who owes and the person who pays are often different people, which makes clear payment context more important rather than less.
Connect supported customer-facing payment activity with Salesforce. See Education.
- Student portal management
- Enrollment
- Financial aid
- Student accounting
Healthcare Customer payment action
A customer may need to complete a relevant supported payment through a Salesforce-connected journey. Bonza operates on the customer payment side of that picture only.
Provide the payment-management layer where relevant, connected to the Salesforce customer record.
- Patient portal
- Medical records
- Claims
- Medical billing
- Insurance
- A HIPAA compliance status
Technology & SaaS One-time or recurring
A customer may need to complete relevant one-time or recurring payment activity through a connected customer experience. Both patterns can sit on the same account without becoming a self-service subscription console.
Connect the payment journey with Salesforce. See Technology & SaaS.
- Subscription-management portal
- Customer-initiated plan changes
- Usage billing
- Customer-initiated cancellation
- Proration
Membership & associations Member payment action
A member or customer may need to complete a relevant payment without a separate manual process. Whether a payment is made has no bearing on membership status, which is held in the membership system or CRM and is never set by Bonza.
Connect customer-facing payment activity to the wider payment lifecycle. See Membership & Associations.
- Membership management
- Renewal logic
- Event management
- Member portal administration
Real estate & property Property-related payment
A relevant customer payment may be completed through a Salesforce-connected self-service journey. Bonza describes the payment and its position in neutral payment language rather than narrower terms that would imply functionality it does not provide.
Connect the payment action with customer and payment context. See Real Estate & Property.
- Tenant portal
- Lease administration
- Rent ledger
- Property management
Nonprofits Supporter payment action
A supporter or customer may complete relevant supported payment activity through Salesforce. Not every payment is a donation, and Bonza does not label them as one by default.
Manage the relevant payment activity and keep it connected. See Nonprofits.
- A donation
- A gift
- A pledge
- Fundraising portal
- Donor portal
- Campaign management
Financial & professional services Client payment action
A client may need to understand and complete a relevant payment while keeping the activity connected to Salesforce, alongside everything else the firm holds about that relationship.
Connect the payment action with the wider client relationship. See Financial & Professional Services.
- Client funds management
- Trust accounting
- Escrow
- A banking portal
Other Salesforce-powered businesses Any self-service payment need
Where customers need to understand and complete relevant payment actions themselves, Bonza can provide the payment-management layer where the supported capability fits. The qualifier is the point: this is a payment pattern, not a claim of universal compatibility.
Provide the payment-management layer above the configured gateway. See Other Salesforce-Powered Businesses.
- Universal gateway support
- A portal for every journey
- Vertical-specific functionality
The industry changes. The self-service requirement remains: understand, then act, then confirm.
How it works
From Customer Context to Completed Payment.
This is how self-service payments work in Salesforce with Bonza: seven stages, with the configured gateway doing the processing at stage four and Salesforce holding the context throughout.
Identify the customer context
The journey starts from a known customer and their relevant Salesforce context, not from an anonymous amount. Authentication and identity are handled by the surrounding platform, not by Bonza.
Present the payment context
What the payment relates to, how much is relevant, and where the position stands. This is the step that turns a checkout into self-service.
Present the relevant payment action
The supported payment option, and the configured gateway or payment route behind it. Customers may select from supported configured gateway options where the implemented experience allows it.
Complete the payment
A configured payment gateway performs the relevant underlying processing. Bonza is not the gateway, Salesforce does not process money, and no funds are held by Bonza at any point.
Record the payment activity
The result is written into the Bonza and Salesforce payment context against the same customer, rather than existing only in a provider dashboard.
Update the customer payment position
Payment status and the outstanding position move, with refund or credit context where relevant. The customer sees what changed; Finance sees the same change from the other side.
Continue the payment relationship
The next relevant payment activity is part of the same connected history, whether it repeats or not.
Experience Cloud
Bring Customer Self-Service Payments Into Salesforce Experience Cloud.
Where Salesforce Experience Cloud is used, Bonza Payments can support relevant customer-facing payment journeys while configured payment gateways handle the underlying payment processing.
The organisation's own portal. Bonza does not provide Experience Cloud itself.
Experience Cloud does not process the payment.
Payment patterns
Let Customers Complete Relevant One-Time Payments Without Creating a Disconnected Flow.
A payment may occur only once while still needing to remain part of the wider customer relationship.
Explore One-Time & Ad Hoc Payments
Self-Service Can Sit Around a Continuing Payment Relationship.
Where recurring payment activity is relevant, customer-facing payment context should remain connected across payment cycles rather than resetting each time.
- The current payment and its status
- The next relevant payment
- Outstanding or due context where relevant
- Refund or credit context where relevant
- Pause a recurring arrangement
- Skip a payment
- Cancel the arrangement
- Change the plan or the frequency
- Modify a subscription
None of these is claimed as customer-facing self-service behaviour unless separately established.
Receivables context
Help Customers Understand What Is Still Open Before They Pay.
When receivables are relevant, self-service should help the customer understand the payment context they are acting on rather than presenting a number with no history.
Explore Receivables Explore Invoices Explore Due & Overdue Payments
Credit and post-payment change
Make Relevant Customer Credit Part of the Payment Context.
Customer credit in Bonza Payments should be understood as credit recorded and managed within the payment lifecycle, not as a bank balance or stored customer cash.
Where customer credit exists in Bonza Payments and is relevant to the supported payment flow, the customer-facing journey can reflect that payment context. A customer who has credit available should be able to see it at the moment it matters, rather than discovering afterwards that it existed.
Illustrative.
Self-Service Payment History Should Still Make Sense After a Refund.
Post-payment activity can change how the customer understands the original payment. Bonza keeps relevant refund activity connected with the wider payment story instead of leaving it to be explained separately.
Raised by the business through the relevant configured refund process.
Explore Refunds Explore Credit Management Simplify Refunds & Credits
Gateways
Give Customers Payment Choice Without Exposing Gateway Complexity.
Bonza can support multiple configured payment gateways. A default gateway may be configured, and another configured gateway may be selected where relevant. In customer-facing experiences, customers may select from supported configured gateway options where the implemented experience allows it.
Configured by the business and selected where supported, not routed automatically.
Explore Multiple Payment Gateways Manage Multiple Payment Gateways
Relevant Payment-Method Timing Can Matter Before the Customer Acts.
Where future payment activity is expected, payment-method expiry can provide useful context for the business. It is an attention signal for internal teams, and this page treats it as one.
Illustrative.
Self-Service Should Not End at the Payment Submission.
Customers can see the relevant payment status once the payment has been made. The customer needs confidence about what happened; the business needs that result connected to the wider payment lifecycle.
Status here means the relevant supported payment status, not a claim about real-time streaming updates beyond what the implemented experience provides.
People are still part of this
Self-Service Should Reduce Unnecessary Questions—Not Remove Human Support.
The goal is not to keep customers away from the business. It is to make simple payment actions clear enough that they do not always require a handoff.
- Payment context
- Payment action
- Payment status
Can the customer understand and complete the relevant action?
No handoff needed for a simple, clear payment action.
A person picks it up with the same payment context in front of them.
- The same Bonza payment context underneath both paths
Customer Self-Service Should Still Produce an Operationally Useful Payment Record.
The customer and Finance need different information. They should still be looking at the same payment lifecycle.
- The relevant amount
- The payment action
- The resulting status
- Collected
- Outstanding
- Due
- Overdue
- Refund
- Customer credit
- Upcoming
Explore Finance & Accounts Receivable Explore Payment Forecasting
AI, scoped
Use AI to Surface Payment Context for Internal Teams—Not to Invent Customer Decisions.
AI Payment Insights read the payment context that already exists and point an internal user at what changed. The insight ends at a person.
- Payments moved into overdue status.
- Expected payment activity changed.
- Payment methods approach expiry.
- Communicate with customers automatically
- Choose payment methods for customers
- Approve refunds
- Approve credits
- Change payment schedules
- Make autonomous financial decisions
The signal goes to a business user for review. Any action after that is a human one.
The operational view behind it
See What Customer Self-Service Activity Means for the Wider Payment Operation.
Self-service is the customer-facing moment. This is the internal view of what those moments add up to.
Illustrative Payment Command Center view of customer self-service payment activity. The KPI strip shows $86,400.00 collected, $24,900.00 outstanding, $7,200.00 due, $4,100.00 overdue and $18,600.00 upcoming, all illustrative. The recent customer payment activity table lists four sample customer payments with amount and status. The customer payment position table lists four sample customers with collected, outstanding and next payment. The needs-attention panel lists an overdue item, a payment method approaching expiry and a relevant AI payment insight, each for human review. The post-payment activity strip lists a refund and customer credit, both raised by the business rather than by the customer. Every figure is illustrative sample data and is not real customer data.
| Customer | Payment | Amount | Status |
|---|---|---|---|
| Demo Customer | PAY-4471 | $900 | Collected |
| Sample Account | PAY-4476 | $1,450 | Collected |
| Example Client | PAY-4480 | $620 | Submitted |
| Test Organisation | PAY-4483 | $2,300 | Collected |
| Customer | Collected | Outstanding | Next payment |
|---|---|---|---|
| Demo Customer | $900 | $0 | Relevant date |
| Sample Account | $1,450 | $3,200 | Relevant date |
| Example Client | $620 | $1,900 | Relevant date |
| Test Organisation | $2,300 | $4,100 | Relevant date |
Test Organisation · $4,100 outstanding, past its relevant expected date.
Human reviewSample Account · method expires 31 Oct, next expected payment 15 Nov.
Internal signal · human reviewExpected payment activity changed for Example Client after a recorded refund.
Insight · human reviewAll values illustrative sample data, not real customer data. Refunds and customer credits shown here are raised and managed by the business; customers do not initiate them through self-service, and nothing is approved automatically. Bonza performs no bank reconciliation, settlement reconciliation or automatic accounting.
The handoff nobody budgets for
Customers Should Not Need an Internal Handoff for Every Payment Question.
The hidden cost of poor self-service is context switching, and most of it happens before the customer has paid anything at all.
Fewer steps, and none of them is a person reconstructing the payment on the customer's behalf.
If the customer needs your team to reconstruct the payment before they can act, the journey is not really self-service. Self-service removes unnecessary steps. It should not remove governance, context or human control.
Self-service ≠ full portal
A Customer Payment Experience Does Not Need to Become Your Entire Customer Portal.
There is a clean line here, and drawing it is what keeps a payment project from turning into a portal project.
- Identity and authentication
- Profile management
- Cases
- Documents
- Knowledge
- Other customer interactions
Owned by the surrounding platform. Bonza provides none of these.
- Relevant payment context
- The payment action
- Payment status
- Payment history context
- Configured gateway interaction
Owned by Bonza, and connected down into the payment lifecycle.
Bonza should own the payment experience it is designed for. It does not need to own every customer experience around it.
What goes wrong
Six Self-Service Payment Mistakes That Create More Friction.
Each one is a reasonable decision taken in isolation. Together they produce a payment page customers still have to phone about.
Calling a pay button “self-service”
Give the customer enough payment context to understand the action before they take it.
Showing payment without the current position
Where relevant, connect the payment action with outstanding and due context.
Exposing gateway complexity to the customer
Keep provider complexity behind the payment-management layer.
Separating customer-facing payment from internal operations
Keep the resulting payment activity connected to Salesforce and the same customer record.
Treating refunds and credits as unrelated processes
Keep post-payment activity in the same payment story as the payment it came from.
Assuming self-service should replace human support
Let simple actions be self-service while preserving human support for situations that need judgment.
Maturity
How Customer Payment Self-Service Matures.
A description of how these journeys tend to develop. No customer is scored here, and no level is assigned to anyone.
Payment link or action
The customer can initiate a relevant payment. The context around it is limited.
Contextual
The customer can understand the relevant amount and the payment context before acting.
Connected
Customer-facing payment activity connects with the records the business already operates on.
- Salesforce customer context
- Payment status
- Receivables
- Refund / credit context
- Configured gateways
Lifecycle-aware
The forward view joins the operating model, with expiry remaining an internal signal.
- Relevant next-payment context
- Recurring activity
- Payment Method Expiry, internally
- Payment Forecasting
Operationally connected
Internal teams can see the payment operation behind customer self-service, with people still deciding.
- Payment Command Center
- AI Payment Insights
- Finance visibility
- Customer Service context
Patterns
Common Customer Self-Service Payment Patterns Across Salesforce-Powered Businesses.
Six situations that recur regardless of sector, and what connecting them actually changes.
A customer has a relevant individual payment requirement.
The customer needs manual guidance to understand and complete it.
Present relevant payment context and connect the resulting payment activity.
A clearer self-service payment journey.
A customer has an outstanding relevant payment obligation.
The customer sees a payment request but not enough context.
Connect the relevant obligation, the payment action and the updated payment position.
Clearer payment understanding.
Relevant payment activity repeats.
The customer and the business lose continuity between payment cycles.
Keep relevant recurring payment context connected across cycles.
Greater payment continuity.
The customer has relevant credit recorded in Bonza.
The credit is disconnected from the next supported payment experience.
Connect relevant customer-credit context with future payment activity where supported.
Clearer customer value context.
The business has more than one configured gateway.
Customers or internal teams encounter provider-specific payment journeys.
Maintain a wider Salesforce payment-management layer above the providers.
More consistent payment context.
The organisation already has a Salesforce Experience Cloud customer journey.
Payment sends the customer into a disconnected experience.
Connect relevant payment activity with the Salesforce environment.
Greater continuity.
Business outcomes
What Connected Self-Service Actually Changes.
Defensible outcomes only. There is no claim here about reduced support tickets, higher payment conversion, higher payment success, higher CSAT, reduced call volume, reduced service cost, faster payments, higher collections, specific productivity improvements or specific ROI.
Help customers understand relevant payment actions before they take them.
Keep customer-facing payment activity tied to Salesforce.
Reduce dependence on disconnected systems to understand the customer's position.
Let customer-facing activity remain part of the same lifecycle Finance operates.
Keep refunds and customer credits connected with payment history.
Support multiple configured providers through one wider payment-management model.
Allow relevant payment actions to be completed without manual support at every step.
Keep a person available for the situations that actually need judgment.
Why Bonza
Why Build Customer Self-Service Payments Around Bonza?
Eight reasons, all of them about continuity rather than about the payment button itself.
Keep customer-facing payment activity connected with the Salesforce relationship.
Connect the payment action to the wider payment lifecycle rather than to a standalone page.
Support different relevant payment patterns through one wider payment-management model.
Where relevant, connect the customer action with outstanding, due and overdue context.
Keep post-payment value changes connected with the same payment history.
Use multiple configured gateways without exposing unnecessary provider complexity.
Bring relevant customer payment journeys into Salesforce Experience Cloud where applicable.
Connect self-service with Payment Forecasting, AI Payment Insights and the Payment Command Center.
The wider lifecycle
Customer Self-Service Is One Part of the Wider Payment Lifecycle.
Not every self-service journey requires every capability. These are the parts of the suite a customer-facing payment action can touch.
The customer sees the payment moment. Bonza connects the payment lifecycle behind it.
FAQ
Customer Self-Service Payment Questions.
Twelve questions buyers actually ask, answered against established product scope.
What are customer self-service payments?
Customer self-service payments are Salesforce-connected payment journeys that allow customers to understand relevant payment context and complete supported payment actions without requiring manual guidance for every payment interaction. The distinguishing part is the context, not the button.
How do customer self-service payments work in Salesforce?
The journey starts from a known customer and their relevant Salesforce context. Bonza presents the relevant payment context and the supported payment action, a configured payment gateway performs the underlying processing, and the resulting payment activity is recorded against the same customer in Bonza and Salesforce. The payment status and updated position are then part of the connected payment history.
What is the difference between a payment checkout and payment self-service?
A payment checkout and a self-service payment experience are different. Checkout focuses on completing a transaction, while self-service also provides the customer with relevant payment context before and after that transaction. A checkout can answer whether the payment succeeded; self-service also answers what the payment was for and what it changed.
Can customers make payments through Salesforce Experience Cloud?
Where Salesforce Experience Cloud is used, Bonza Payments can support relevant customer-facing payment journeys while configured payment gateways handle the underlying payment processing. Experience Cloud does not process the payment, and Bonza does not provide Experience Cloud, authentication or portal administration.
Can customers see relevant outstanding payment context before paying?
Where receivables context is relevant, the customer-facing journey can show what remains open, whether it is due, and the amount being acted on. This is payment context rather than invoice editing, and it does not imply a partial-payment capability.
Can customer credit be used in a self-service payment flow?
Where customer credit exists in Bonza Payments and is relevant to the supported payment flow, the customer-facing journey can reflect that payment context. Customer credit is recorded and managed within Bonza Payments, it is not a wallet, cash balance, stored funds, a customer bank balance or a stored-value account, and no credit is approved automatically.
Can Bonza support one-time and recurring customer payments?
Yes. Both patterns can be managed through the same wider payment-management model, and a customer can hold more than one pattern at a time. Customers cannot pause, skip, cancel, change the plan or change the frequency of a recurring arrangement through self-service unless that behaviour is separately established.
Can a self-service payment use multiple payment gateways?
Bonza can support multiple configured payment gateways. A default gateway may be configured and another may be selected where relevant, and customers may select from supported configured options where the implemented experience allows it. There is no smart routing, automatic gateway optimisation, least-cost routing, automatic failover, automatic retries or authorisation optimisation.
Does Bonza process the payment itself, or store customer funds?
No to both. Configured payment gateways perform the relevant underlying payment processing. Bonza is not the payment gateway, Salesforce does not process money, and Bonza does not hold or store customer funds. Customer credit recorded in Bonza is a payment-management record, not money held by Bonza.
Does Bonza replace a customer portal, or provide identity and authentication?
No. Bonza focuses on the payment-management experience. It does not provide a complete customer portal, identity management, authentication, single sign-on, profile management, knowledge or portal administration. Those belong to the surrounding platform unless separately established.
Does Bonza replace Salesforce Service Cloud?
No. Bonza provides relevant payment context and customer payment capabilities, not case-management or contact-center functionality. Self-service is meant to make simple payment actions clear enough that they do not always need a handoff, while human support remains available for anything requiring judgment.
Can customers request refunds through self-service, and does Bonza contact customers about overdue payments?
No to both. Self-service refund initiation is not claimed unless separately established: refunds are raised by the business through the relevant configured refund process, and no refund or credit is approved automatically. Bonza also does not automatically contact customers, send automatic reminders, or run dunning. Overdue amounts are surfaced internally for a person to review and decide.
Customer Self-Service Payments
Give Customers Enough Payment Context to Act Without Asking Your Team First.
See how Bonza Payments can connect customer-facing payment actions with Salesforce, receivables, customer credits, configured payment gateways and the wider payment lifecycle.