Bonza Payments Release Notes
See What’s Changed in Bonza Payments.
Review verified Bonza Payments updates by release, capability and change type, with clear guidance on what changed, who may be affected and whether any action is required. Bonza Payments Release Notes provide a chronological record of verified changes to the Bonza Payments product. No release record has been published to this page yet, so what follows is the structure a Bonza release note uses and how to read one when it arrives.
Salesforce-Native Payment Management Suite
Release date
— not yet recorded
A date appears here only when it comes from a verified release record.
Release or version
— not yet recorded
Version and package numbers are never generated for display.
Changes in this release
— no change entries
Change types are applied from the release record, not chosen for variety.
Affected Bonza areas
— none named
A capability is named here only where a change actually touched it.
Action required
— nothing to act on
This reads “action required” only when a release record names the step.
Every field above is fed from the page’s release record. The record is empty, so every field is blank. Nothing here is a placeholder standing in for information that exists elsewhere.
Release record
The Release Ledger Is Open. It Currently Holds Nothing.
Track verified product updates across the Bonza payment-management suite, including relevant capability changes, fixes, operational updates and important actions where applicable.
Release record
Verified product updates will appear here as Bonza Payments releases are published.
For current product information, explore Bonza Payments Documentation, take the Product Tour, or read the relevant Platform capability pages. Each of those describes how the product works today, which is a different question from what changed and when.
This is a statement about what has been published to this page, not a statement about the product’s history. No release date, version number, change description, fix, deprecation or required action has been written here, and none has been inferred, estimated or filled in to make the page look complete.
Figures on this page are counted from the release record, which currently holds 0 releases and 0 change entries.
Start here
How to Read a Bonza Release Note.
Each Bonza release note should identify what changed, which capability was affected and whether users or administrators need to take any action. Those five fields are what make a change readable by someone who has to decide whether it touches their work.
What changed
The specific product change, described in terms of behaviour rather than internal work. One change, one entry.
“What is different now?”
Affected area
Which Bonza capability the change sits in, named the same way the product and its documentation name it.
“Is this a part of Bonza I use?”
Who should care
The user, administrator or team the change is likely to reach — finance, payment operations, a Salesforce administrator, or a customer-facing team.
“Is this mine to read?”
Action required
Whether anything has to be done, stated as none, review or a named step. Left as none unless the release record says otherwise.
“Do I have to do something?”
Related documentation
Where to understand the affected capability in more detail, because a change summary is not an explanation.
“Where do I go to understand it?”
The release date tells you when. The release note should tell you what it means.
Release impact map
From Product Change to Operational Meaning.
A release note is only useful once the reader can trace a product change through to the person whose work it touches. This is the path that trace follows.
Release
The verified record: a date, a summary, and where real, a version. This stage holds nothing on this page yet, which is why the four stages after it have nothing to describe.
Capability changed
The named Bonza capability the change lands in.
- Collect & bill capabilities
- Manage & recover capabilities
- Connect & experience capabilities
- Understand & optimise capabilities
Payment workflow
The part of the payment lifecycle that workflow belongs to — before the payment, at the payment, or after it, where the position has to be kept straight.
Role affected
Whoever owns that part of the workflow.
- Finance
- Payment operations
- Salesforce administrator
- Customer-facing teams
Action status
Informational, review, or a named required step — the answer to the only question most readers actually have.
A good release note connects product change to operational impact. The map above is the structure of that connection, not a record of one: stage one is empty, so nothing downstream of it is asserted. Release Notes describe product changes, while Bonza Documentation explains how supported capabilities work and how to use them.
Information or action
Not Every Product Change Requires Customer Action.
Work a release note through the two questions that decide its status. The path is fixed logic over the note’s own fields, not a recommendation about your organisation.
Release note
Does the release note describe a change to product behaviour your organisation relies on?
Read the note’s What Changed and Affected Area fields before answering.
Status 01
Informational
A verified change occurred somewhere in the product and nothing is asked of you. Most entries in a healthy changelog sit here.
Status 02
Review
The change may be relevant to how your organisation uses Bonza. Read the documentation for the affected capability, then decide.
Status 03
Action required
A configuration, upgrade or operational step is named in the release record and has to be carried out by someone with the right permission.
Today
Nothing carries a status yet
Change entries currently marked as requiring action: 0.
Change types currently in use across published Bonza release notes: 0.
Do not turn every release into an urgent task. Clear release notes should distinguish information from action.
Release note quality
What Every Bonza Release Note Should Tell You.
Seven questions. A note that answers all seven reduces uncertainty around change; a note that answers three of them creates work for the reader.
What changed?
The behaviour that is different now, in one entry per change.
Where did it change?
The named Bonza capability, matching how the product and documentation name it.
Who should care?
The role or team the change reaches, so readers can skip what is not theirs.
Does it change existing behaviour?
Stated plainly, because this is the question that decides whether anyone needs to look further.
Do I need to do anything?
None, review, or a named step — never implied by tone or left for the reader to infer.
Where can I learn more?
A link to documentation for the affected capability, not a repeat of the summary.
When did the change become available?
The verified release date. Where no verified date exists, the field stays empty rather than being approximated.
Release notes should reduce uncertainty around change. Future or unverified functionality should not be presented as a released Bonza capability.
Administrator view
What Salesforce Administrators Should Look For.
When release notes arrive, these are the fields an administrator reads first. Nothing below is a notice: it is the checklist to run a note against.
Changes that land in setup rather than in the product surface. These are the ones where a note marked review can still turn into work, because the behaviour depends on how your organisation configured Bonza in the first place.
- Configuration changesWhether a Bonza or payment setting behaves differently, or a new setting exists.
- Permission changesWhether the access a role needs to perform a payment task has moved.
- Deprecated configurationWhether a setting your organisation depends on is being phased out.
Administrator notices published so far: 0 of 0 change entries.
Changes that affect the Salesforce org around Bonza rather than Bonza itself. A note here usually names the step, which is what separates it from an informational entry.
- Package updatesWhether the release involves an update to install, and who can install it.
- CompatibilityWhether a change depends on something else in the Salesforce org being at a particular state.
- Migration stepsWhether existing records or configuration have to be moved, and in what order.
Compatibility and package notices published so far: none.
Changes users will see without being told. These are worth reading even when marked informational, because a support team hears about them before an administrator does.
- Interface changesWhether a screen, field or control your team uses daily has moved.
- Behaviour changesWhether a payment action produces a different result than it did before.
- Experience Cloud impactWhether anything customers see in a Salesforce Experience Cloud site is affected.
Interface and behaviour notices published so far: none.
Finance and operations view
What Finance and Payment Operations Should Look For.
Finance rarely needs the whole release. It needs to know whether the numbers and the daily payment routine mean the same thing they meant last week.
- Payment collectionWhether taking a payment behaves differently at any point.
- Recurring activityWhether scheduled payment management changed, including how upcoming activity is shown.
- ReceivablesWhether what counts toward the outstanding position changed.
- Due and overdueWhether the point at which an amount becomes due or overdue is interpreted differently.
- RefundsWhether a refund changes the customer payment position in a new way.
- Customer creditsWhether recorded credit is applied or reported differently.
- Upcoming payment visibilityWhether expected payment activity is derived or displayed differently.
- Payment method expiryWhether the expiry signal changes timing or coverage.
- Command Center and insightsWhether the operating view or the surfaced payment context changed.
Finance and payment-operations notices published so far: 0.
Related documentation
Understand the Change in Context.
A release note says what moved. The capability page says how the thing that moved works. When a note names one of these areas, this is where to read next.
| If a release note names | Read next | Because it explains |
|---|---|---|
| Recurring payments | Recurring Payments | How scheduled payment management works, and what it deliberately is not. |
| Receivables, due or overdue | Accounts Receivable | What makes up the outstanding position and when an amount becomes overdue. |
| Refunds or customer credit | Credits & Refunds | How a post-payment change moves the customer payment position. |
| A configured gateway | Multiple Payment Gateways | Where Bonza stops and a configured gateway starts. |
| Experience Cloud payments | Experience Cloud Payments | What the customer-facing Salesforce environment does and does not do. |
| Forecasting or expiry | Payment Forecasting | How expected payment activity is built, and why it is not a guarantee. |
| Command Center or AI Payment Insights | Payment Command Center | What the operating view shows and where human judgement stays. |
| Anything else, or the whole suite | Documentation | The documentation index, including a plain statement of what has not been written yet. |
Related learning
Need More Context Than the Release Note?
Documentation
The index for understanding and working with Bonza, and an honest account of which areas have nothing written yet.
Explore Documentation → I want to see it in actionVideos & Demos
Drawn demonstrations of what each capability does, with the same honesty about what is not yet recorded.
See the capability in action → I want the full lifecycleProduct Tour
One illustrative customer followed through the whole payment lifecycle, step by connected step.
Take the Product Tour → I want the product overviewPayment Management
The platform view of the suite. Bonza Payments is a Salesforce-native payment-management suite covering relevant payment collection, recurring payments, receivables, refunds, customer credits, configured gateways, customer payment experiences and payment visibility.
Explore Bonza Payments →Release notes tell you what changed. Documentation tells you how it works. If you are not sure which you need, start with the capability page: a change only makes sense once you know what the thing being changed does. The Resources hub lists everything published across both.
Questions
Questions About Bonza Release Notes.
What are Bonza Payments Release Notes?
They are the chronological record of verified changes to Bonza Payments: what changed, which capability it sits in, who it reaches, whether anything has to be done, and where to read more. This page holds that record and the structure it uses. No release has been published into it yet.
What changed in the latest Bonza release?
No release record has been published to this page, so there is no latest release to summarise here and no date, version or change description to report. That is a statement about what has been published, not a claim about the product’s history. For what the product does today, read the Documentation index or the relevant capability page.
How often are Bonza release notes published?
No release cadence has been established or published, so there is nothing accurate to state here. You will not find a monthly, quarterly or major-and-minor rhythm described on this page, because inventing one would be more misleading than saying nothing.
Where can I find Bonza release history?
This page is the place it will live. The ledger above shows the counts drawn from the release record, which is currently empty, and the release timeline in the hero shows the fields each record fills in.
How do I know whether a release requires action?
Every Bonza change entry carries an action status: informational, review, or a named required step. The triage above walks a note through the two questions that decide which of the three it is, using only the note’s own fields. A change is marked as requiring action only when the verified release record names the step.
How can I find changes to a specific Bonza capability?
Once releases exist, each change entry names the Bonza capability it affects, so changes to recurring payments, receivables, refunds, gateways, forecasting or the Command Center can be read by area. Capability filters are not shown on this page yet, because a filter over an empty record would suggest there is something to filter.
Where can I find documentation for a release change?
Each change entry links to the documentation for the capability it affects. Until entries exist, the table above maps each capability a note might name to the page on this site that explains it. Release Notes describe product changes, while Bonza Documentation explains how supported capabilities work and how to use them.
Where are Bonza breaking changes documented?
They belong in this record, marked clearly and carrying the required action and anyone affected. No breaking change has been published, and normal product improvements are never relabelled as breaking changes to make a release look significant.
Does Bonza publish known issues?
No known-issue list has been published on this site, so there is none to read here. Nothing on this page infers a defect from a product limitation either: a capability Bonza does not have is not a bug, and describing it as one would be inaccurate.
Can I subscribe to Bonza release updates?
No release-notification mechanism has been published, so there is no email list, feed or in-product subscription to join and no sign-up form on this page. Checking this page is the route available today.
Do Release Notes include future roadmap features?
No. Release Notes document verified product changes rather than speculative future functionality. You will not find planned capabilities, dates or “coming soon” entries on this page, because a changelog that mixes shipped and planned work stops being useful for deciding whether anything affects you.
What is the difference between Bonza Documentation and Release Notes?
Documentation answers how a capability works and how to use it. Release Notes answer what changed in it, when, and whether that change reaches you. They are read at different moments: documentation when you are learning or configuring, release notes when something is different from last time.
Understanding a change
Need Help Understanding a Bonza Product Change?
Review the related documentation, see the capability in action, or explore how the updated capability fits into the wider Bonza Payments lifecycle.
No product support channel has been published on this site, so there is no support desk linked from this page. The practical route today is a conversation about the change you are trying to understand.