Contact Bonza
Tell Us What Your Payment Operation Needs to Handle.
Share what you are trying to manage across payment collection, recurring payments, receivables, refunds, customer credits, configured gateways, customer payment experiences or future payment visibility, and give the Bonza team enough context to understand the conversation.
Salesforce-Native Payment Management Suite
Start here
What are you trying to solve?
What would help us most
Tell us how customers pay today and what the business needs to see afterwards.
Where this sits
Tell Us About Your Payment Requirement
Tell us enough to understand the payment problem. You do not need to provide a complete technical specification, and you do not need to know which Bonza capability applies.
16 payment problems to start from · 0 verified contact facts on this page · 9 things named as not established · every one of those counted from the ledger rather than written as text
Orientation
What Would Make This Conversation Useful?
You do not need to arrive with a complete payment architecture. A useful starting point can be as simple as one sentence.
“We need customers to make payments in Salesforce.”
“We need recurring payments.”
“Finance cannot clearly see what is still outstanding.”
“We need to understand due and overdue activity.”
“We have more than one payment gateway.”
“We need refunds and customer credits to stay connected.”
“We want customers to pay through Experience Cloud.”
“We need better visibility into what payment activity is expected next.”
“We have built several payment processes and want a more connected model.”
Start with the problem. The architecture can come next.
By business question
Not Sure Which Bonza Capability You Need?
Choose the question instead. You do not need to know the product module.
How do we collect a customer payment?
How do we manage repeating payments?
How do we know what is still open?
How do we know what is due or overdue?
What happens after a refund?
How should customer credit work?
How do multiple gateways fit together?
How do customers pay through Salesforce?
What payment activity is expected next?
What needs attention?
You do not need to know the product module. Start with the business question.
Conversation type
What Kind of Conversation Do You Need?
A small number of intent-led paths. Two of them deliberately lead away from the form.
Evaluating
I'm evaluating Bonza Payments
Best for organizations exploring whether the payment model fits. Start with the requirement rather than the product.
Technical
I have a specific payment architecture question
Best for Salesforce architects, product owners and technical teams. The same form handles this conversation; choose “Payment management or architecture”.
Partnership
I'm interested in partnering
Choose “Partnership” in the form, or read what a partnership conversation can and cannot cover first.
Documentation
I need product documentation
This is not a sales conversation and is not treated as one. Go straight to the documentation index.
Research
I want to see the product first
Entirely reasonable. The Product Tour walks the connected payment lifecycle.
Support
I'm an existing customer and need support
This path renders only when a verified support route exists.
After you make contact
What Happens Next?
A shape rather than a schedule. No response time, meeting length or next-step commitment has been established, so none is stated here.
1. Share the requirement
Tell Bonza what payment problem you are trying to solve, in whatever words fit it.
2. Add the relevant context
Salesforce, the payment model, the configured gateway, the customer experience, receivables and future payment needs — only where they are relevant.
3. Discuss the payment model
Explore how the requirement fits into the wider payment lifecycle before anything is proposed.
4. Identify relevant capabilities
Only after the requirement is understood, and only the ones that actually apply.
5. Define the next step
Based on the actual conversation rather than a predetermined sequence.
The first conversation should determine fit. It should not assume the answer before the requirement is understood.
The first question
Don't Start With “Which Gateway Do You Use?”
The gateway matters. It is just rarely the question that shapes the architecture.
Start with
- What does the customer need to pay?
- Who needs to see the payment?
- What happens after collection?
- What remains open?
- What repeats?
- What changes after payment?
- What happens next?
Then
- Which configured gateway is relevant?
The gateway matters. But it is only one part of the payment architecture.
Fit
Bonza May Be Worth a Conversation When…
Thirteen situations where payment management, rather than payment processing, is the actual problem.
- Your customer payment activity needs to stay connected to Salesforce.
- You need more than one payment model.
- You manage both one-time and recurring customer payments.
- Finance needs visibility into what was collected and what remains open.
- Due and overdue payment context matters.
- Refunds need to stay connected to payment history.
- Customer credits need to remain relevant to future payment activity.
- You have more than one configured payment gateway.
- Customers need to pay through a Salesforce-connected experience.
- You need visibility into relevant upcoming payment activity.
- Payment-method timing matters.
- You want one operational view across relevant payment activity.
- You have created multiple payment processes and want to understand whether a more connected model is possible.
The more questions you need to answer after “did the payment process?”, the more likely the problem is payment management.
Boundaries
Clear Product Boundaries Save Everyone Time.
If the requirement is primarily one of these, Bonza is probably not the system responsible for that layer, and it is better to know that before the first call than after it.
The contact page should help establish fit, not force every inquiry into Bonza.
Architecture
Where Bonza Fits
If this looks like the payment layer you are trying to solve, that is a good reason to start a conversation.
An architecture stack. Customer and business sit above Salesforce, which holds customer and business context. Beneath it, Bonza Payments provides the payment-management lifecycle, a configured payment gateway performs the relevant underlying transaction processing, and the resulting payment activity feeds back into Bonza and Salesforce.
And the capabilities around it
By team
Different Teams Usually Start With Different Questions.
You don't need to contact Bonza using product language. Start with the question your team is trying to answer.
Finance & AR
What are we owed?
- What has been collected?
- What remains outstanding?
- What is due or overdue?
- What is expected next?
Revenue Operations
What happens between the deal and the cash?
- What happens between the commercial event and collection?
- What is still open?
Business Operations
What needs attention?
- What happened?
- What changed?
- What needs attention?
Customer Service
What happened to this customer?
- What happened to this customer's payment?
- Was anything refunded?
- Does relevant customer credit exist?
Salesforce Team
Where does payment belong?
- How should payment requirements fit into the wider Salesforce architecture?
Everyone else
Start anywhere
- If none of the above matches, “something else” in the form is a real option, not a fallback.
About this form
A Better Contact Form Produces a Better First Conversation.
A generic name, email, company and message form forces the visitor to explain the Bonza product model before they know it. A payment-led form starts with what you are trying to solve and uses that answer to do some of the orientation work. No AI involved, just information architecture.
No pressure
Still Researching?
A good contact page should make it easy to contact Bonza. It should also make it easy not to, until you are ready.
Questions
Contacting Bonza, Answered.
Including what this form can and cannot currently do.
What happens after I submit the form?
Your details and the payment context you describe are emailed to the Bonza team, so they can reply to the address you provide. If sending fails, the page says so and keeps what you entered, ready to copy or send again.
How do I contact Bonza Payments?
Through this page. No email address, phone number, office address or working hours has been established for Bonza, so none is published here and none should be inferred. The form is the contact method, and it currently produces a summary for you to send rather than sending it itself.
What should I include when contacting Bonza?
Enough to understand the payment problem, and no more. Helpful context includes how customers pay today, whether payments are one-time or recurring, how receivables are currently tracked, whether you use more than one gateway, whether Experience Cloud is involved, and what you would like Finance or Operations to be able to see. A complete technical specification is not expected.
Do I need to know which Bonza capability I need?
No. A Bonza payment conversation can begin with the business problem; the buyer does not need to identify the exact Bonza capability before making contact. The form starts with what you are trying to solve and does some of the orientation work from there.
What information should I avoid submitting through the form?
Card details, payment credentials, passwords, API or gateway secret keys, customer financial records and any other sensitive customer financial data. A general contact form is not the right channel for any of those, and nothing on this page is designed to receive them.
Can I request a Bonza Payments demo?
You can ask for one in the form, but no demo process has been established on this site: there is no scheduler, no published duration, no meeting platform and no assigned contact, so none of those is offered or implied. Choose the payment problem you want to see and describe it, and that becomes the basis of the conversation.
Does Bonza provide pricing on the website?
No pricing is published on this site, and there is no pricing page, calculator, plan selector or pricing-request workflow. Commercials can be raised inside a conversation about the requirement; nothing on this page implies a hidden pricing mechanism.
Can existing customers use this form for support?
No customer support route has been established on this site. There is no support portal, support address, ticketing system or service level agreement, so none is offered here and the existing-customer path is deliberately not shown. If you are an existing customer, use whichever channel was set up during your implementation.
Can I contact Bonza about a Salesforce payment architecture question?
Yes. Choose “Payment management or architecture” in the form. Architecture questions tend to produce a more useful first conversation than product questions, because they start from what the customer actually needs the payment layer to do.
Can I discuss one-time, recurring, receivables or overdue payment requirements?
Yes, and each is a separate option in the form. Bonza can discuss relevant payment-management scenarios involving one-time payments, recurring payments, invoices, receivables, due and overdue activity, refunds, customer credits, customer payment experiences, Experience Cloud, forecasting, payment-method timing and payment operations. Recurring payment management is not full subscription billing.
Can I discuss multiple payment gateways or Experience Cloud payments?
Yes, both are options in the form. Multiple configured gateway options can sit beneath one Bonza payment-management experience, with the business configuring which applies; Bonza does not route, retry or fail over between gateways. Experience Cloud is a customer-facing environment and does not itself process the payment.
Can I contact Bonza about partnerships?
Yes. Choose “Partnership” in the form and describe the customer or payment opportunity. No partner programme, tier, referral fee, commission or reseller arrangement has been established, so none is assumed by making contact. The Partners page sets out what a partnership conversation can and cannot cover.
Does Bonza replace my payment gateway?
No. Bonza Payments provides a Salesforce-native payment-management layer while configured payment gateways perform relevant underlying transaction processing. Bonza is not a payment gateway, is not the processor, is not a bank or acquirer, and does not hold customer money.
How is the information I enter handled?
Our Privacy Policy explains how this information is stored, shared and retained. What you submit is emailed to the Bonza team so they can reply.
Start the conversation
Start With the Payment Problem.
Tell us what customers need to pay, how payments work today and what your team needs to understand afterward. That is enough to start a useful Bonza conversation.
You don't need the finished architecture to start the conversation.