Book a Demo
  1. Home
  2. Resources
  3. Blog

Bonza Payments Blog

Payment Management, Explained Beyond the Transaction.

Practical thinking on Salesforce payment management, receivables, recurring payments, refunds, customer credits, payment gateways, customer payment experiences, forecasting and payment operations.

Explore the Thinking Browse Payment Topics

Insights from the Salesforce-native Bonza Payments suite. The Bonza Payments Blog provides practical educational content on Salesforce payment management, receivables, recurring payments, customer payment experiences and payment operations.

One payment Seven questions

What happened?

Collected

The transaction One payment Processed once, at one moment, by a configured gateway.

What is open?

Receivables

What needs attention?

Due & overdue

What changed?

Refund & customer credit

What is next?

Recurring & forecast

What does the customer see?

Payment experience

What does the business see?

Command Center & AI Payment Insights

The editorial premiseThe transaction is one event. The questions around it create the payment operation.

Start here

Start With the Payment Lifecycle.

This blog has no published articles yet. Rather than fill the space with placeholders, the reading path below points at the Bonza pages that already explain each part of the customer payment lifecycle — in the order the lifecycle actually runs.

  1. 01

    A payment is taken. Payment Management explains what a Salesforce-native payment-management layer holds that a transaction record does not.

  2. 02

    Some of it is still expected. Receivables and Due & Overdue Payments separate what is merely outstanding from what has passed its relevant due date.

  3. 03

    Value moves back. Credits & Refunds covers what a refund and a customer credit each do to the payment story after collection.

  4. 04

    Another payment is expected. Manage Recurring Payments and Payment Method Expiry cover repeating activity and the signals that precede it.

  5. 05

    Someone has to look at all of it. Payment Command Center and AI Payment Insights cover the operating view and the signals raised for human review.

Editorial position

The Payment Is Only One Part of the Story.

A payment gateway can tell you whether a relevant transaction was processed. A business usually needs to answer considerably more than that.

Payment processing and payment management are different. Configured gateways process relevant transactions, while payment management covers the wider lifecycle around the transaction. That single distinction is the reason this blog exists, and most of what follows is an attempt to make it practical rather than rhetorical.

  • What was the customer expected to pay?
  • What has been collected?
  • What remains outstanding?
  • What is due?
  • What is overdue?
  • Was anything refunded?
  • Does customer credit exist?
  • Is another payment expected?
  • Is a payment method approaching expiry?
  • Which payment activity deserves attention?

The editorial spine

  1. 01
    TransactionA relevant payment is processed by a configured gateway.
  2. 02
    Customer contextWhich customer, which agreement, which record in Salesforce it belongs to.
  3. 03
    Payment positionWhat has been collected and what is still expected against the whole amount.
  4. 04
    What changedRefunds and customer credits recorded after collection.
  5. 05
    What happens nextRecurring activity, upcoming payments and forward visibility.
  6. 06
    What needs attentionOverdue activity, payment-method expiry and signals raised for review.

That is the difference between writing about payment processing and writing about payment operations.

Signature explainer

A Successful Transaction Doesn't Answer Every Payment Question.

One illustrative payment. Eight questions a business might reasonably ask about it. Step through them and watch which panel runs out of answers — the facts on both sides stay frozen, only the question changes.

Question 01 of 08

Did the transaction process?

Transaction view

  • Customer Demo Customer
  • Amount $1,000
  • Gateway Configured gateway
  • Status Successful

Answered by this record

Yes. The transaction was processed successfully by the configured gateway.

Payment lifecycle view

  • Original amount $1,000
  • Collected $750
  • Outstanding $250
  • Due · refund · credit Tracked
  • Next payment · expiry Tracked

Answered by this view

Yes. The same processed transaction is held as part of the wider payment record it belongs to.

Transaction record answers 1 of the 8 questions
Payment lifecycle view answers 8 of the 8 questions
Answered by both views 1 question answered by both views

All amounts, customers and statuses shown here are illustrative sample values used to explain the concept. They are not real customer data and not a Bonza performance claim.

The transaction tells you what happened at one moment. The payment lifecycle explains what that moment means before and after it.

Explore Payment Management

Questions worth asking

Better Payment Operations Start With Better Questions.

Twelve questions this blog keeps returning to. Each one hides a conflation — two things that sound like one thing — and each answer points at the Bonza page where the distinction gets operational.

The best payment content does not begin with a product feature.

It begins with a question the business needs to answer.

Editorial streams

Explore the Ideas Shaping Payment Operations.

Seven standing streams rather than a category grid. Each stream is defined by the question it keeps asking, not by a keyword.

Stream 01

Payment Management

What happens around the transaction?

  • Payment management vs processing
  • Customer payment lifecycle
  • Salesforce-native payment management
  • Payment architecture
  • Connected payment history
Reads intoPayment Management
Stream 03

Recurring Payments

How do repeating payments become a manageable operation?

  • Recurring payment management
  • Recurring payment vs subscription billing
  • Next-payment visibility
  • Payment-method expiry
  • Exception handling
Reads intoRecurring Payments Manage Recurring Payments

Comparisons

Understand the Differences That Change Payment Decisions.

Eleven pairs that get used interchangeably in payment conversations and shouldn't be. One sentence each, then the page where the distinction has consequences.

Payment processingvsPayment management
Processing is the act of moving a relevant transaction through a gateway; management is everything the business still needs to know about that payment before and after the moment it cleared. Payment Management
One-timevsRecurring
A one-time payment is complete when it is collected; a recurring payment creates a standing expectation that something will happen again and therefore needs managing between occurrences. One-Time & Ad Hoc Payments
Recurring paymentsvsSubscription billing
Recurring payment management is not the same as full subscription billing. Recurring payment management focuses on repeating payment activity, while subscription billing may include pricing plans, usage, metering, proration and product-catalog logic. Manage Recurring Payments
InvoicevsReceivable
An invoice is the statement of what was asked for; a receivable is the part of it the business is still waiting to collect. One is a document, the other is a position. Invoice-Based Payments
OutstandingvsDuevsOverdue
Outstanding means not yet collected, due means collection is expected now, and overdue means the relevant due date has already passed. Collapsing the three into one number is how receivables reporting stops being useful. Due & Overdue Payments
RefundvsCustomer credit
A refund returns value outward through the original payment path; a customer credit records value that remains available for future supported payment use. Same trigger, different destination. Credits & Refunds
Payment checkoutvsCustomer payment experience
Checkout is the form; the payment experience is everything that decides whether the customer understood what they were paying, why, and what happened afterwards. Customer Payment Experience
Payment forecastingvsCash-flow forecasting
Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash flow, treasury or bank balances. Cash-flow forecasting is a treasury exercise that also takes in expenses, payroll and financing. Payment Forecasting
Sales forecastingvsPayment forecasting
Sales forecasting predicts whether commercial agreements will be won; payment forecasting looks at expected customer payment activity arising from agreements that already exist. Forecast Upcoming Payments
Gateway viewvsPayment Command Center
A gateway portal is organised around transactions it processed; an operating view is organised around customers, positions and what currently deserves attention. Payment Command Center
Transaction statusvsCustomer payment position
A status describes one event as success or failure; a position describes where the whole customer relationship stands across everything collected, outstanding, refunded, credited and expected. Accounts Receivable

Assumptions worth challenging

Common Payment Assumptions Worth Challenging.

Seven beliefs that are reasonable, widely held, and quietly expensive once a payment operation grows past its first integration.

If the gateway shows success, the payment story is complete.

Reality

The business may still need receivables, refund, credit, recurring, customer and future-payment context. A successful transaction is the start of the record, not the end of it.

Outstanding means overdue.

Reality

A payment can remain outstanding before reaching its relevant due date. Treating the two as one number makes a healthy receivables position look like a collections problem, and sometimes the reverse.

Recurring payments mean we need a subscription billing platform.

Reality

Recurring payment management and full subscription billing solve different problems. Buying the larger system to solve the smaller problem is a common and costly substitution.

Adding another gateway is just another integration.

Reality

Provider diversity can create operational fragmentation if the business process becomes hard-wired to each gateway. The second gateway is usually where an integration turns into an architecture.

A refund is separate from the original payment.

Reality

A refund changes the payment story after collection. Recorded away from the original payment, it leaves two partial truths and no single answer about what the customer actually owes.

Forecasting upcoming payments means forecasting cash flow.

Reality

Bonza Payment Forecasting focuses on relevant upcoming customer payment activity, not bank balances, expenses, payroll or treasury.

AI should automatically act on every payment signal.

Reality

Bonza AI Payment Insights are positioned as decision-support signals for human review rather than autonomous financial decision-making.

Better payment operations often start by correcting the model, not adding another tool.

Architecture

Understand Who Should Own What in the Payment Stack.

  1. Layer 01Business or industry systemRelevant business-specific logic that is particular to how this organisation operates.
  2. Layer 02SalesforceCustomer and business context — the accounts, agreements and relationships the payment belongs to.
  3. Layer 03Bonza PaymentsThe payment-management lifecycle: position, receivables, refunds, credits, recurring activity and forward visibility.
  4. Layer 04Configured payment gatewayRelevant transaction processing, performed by whichever provider the business has configured.
And back again
Payment activityBonzaSalesforce context
Good payment architecture does not require pretending that one system should perform every responsibility.

A recurring theme of this blog is architectural clarity rather than consolidation for its own sake. Salesforce has a role: it holds the customer and the commercial context. Bonza has a role: it manages the payment lifecycle in that same place. The configured payment gateway has a role: it processes the relevant transaction. Industry-specific systems may have a role too, where the logic genuinely belongs to the industry rather than to payments.

Most payment architecture arguments turn out to be ownership arguments in disguise. Deciding which layer owns a responsibility is usually more productive than asking which product can technically be made to hold it.

Explore payment architecture topics

Editorial series

The Same Lifecycle, Read From Four Different Desks.

Four standing series. Each one takes the same payment lifecycle and asks what it looks like to the people who have to act on it.

For Finance

Understand the Payment Position, Not Just the Payment Event.

Finance rarely needs to know that a transaction cleared. It needs to know what has been collected, what remains outstanding, what has changed through refund or credit, and what is expected next — which is a position across time rather than a list of events.

Past
  • Collected
  • Refunds
  • Customer credits
Present
  • Outstanding
  • Due
  • Overdue
Future
  • Recurring
  • Upcoming
  • Forecast
  • Payment-method expiry

Read across Payment Command Center and AI Payment Insights.

Explore Finance & AR topics

For Salesforce teams

Stop Treating Every Payment Requirement as an Isolated Integration.

Payment requirements almost never arrive all at once. They arrive one at a time, each individually reasonable, and the architecture is decided by the first one rather than the last.

  1. FirstAdd a payment.
  2. SecondWe also need recurring.
  3. ThirdWe need another gateway.
  4. FourthWe need refunds.
  5. FifthWe need customer credits.
  6. SixthWe need Experience Cloud.
  7. SeventhFinance needs receivables.
  8. EighthWe need upcoming payment visibility.

You are no longer adding a payment feature.

You are operating a payment architecture.

Topics in this series: gateway integration versus a payment-management layer, custom payment logic, multiple gateways, Experience Cloud, reusable payment capability, post-payment architecture and payment intelligence.

Explore Salesforce team topics

For Operations

Know What Happened, What's Open, What's Next and What Needs Attention.

Payment processing answers "did it happen?". Payment operations also asks "what happens now?" — and that second question is the one that fills people's days.

Happened
  • Collected
  • Refunded
  • Credit recorded
Open
  • Outstanding
  • Due
  • Overdue
Next
  • Upcoming
  • Recurring
  • Forecast
Attention
  • Overdue
  • Payment-method expiry
  • Relevant AI insight
Explore payment operations topics

For Customer Experience

Payment Friction Often Starts Before the Payment Form.

By the time a customer reaches a payment form, most of the confusion has already happened. The questions they could not answer earlier are what turn a simple payment into a support conversation.

  1. Understand

    What am I paying?

  2. Review

    How much?

  3. Choose

    What relevant option is available?

  4. Pay

    Complete payment

  5. Understand outcome

    What happened?

  6. Continue

    What does this mean for the wider relationship?

The pay button is one moment. The payment experience is the journey around it.

Explore customer payment experience topics

One payment, six lenses

The Same Payment Looks Different Depending on Who Is Asking.

One illustrative payment. Six teams, six sets of questions, one underlying record they all have to agree on.

Illustrative payment $5,000 Customer A. Sample value used to explain the concept — not real customer data.

One customer payment lifecycle, read six ways. Nothing about the payment changes between the rows below; only the question does.

  • Finance

    What has been collected?

    What remains open?

  • Accounts Receivable

    Is anything due or overdue?

  • Customer Service

    What happened to the customer's payment?

    Was anything refunded or credited?

  • Revenue Operations

    What happens after the commercial event?

  • Business Operations

    What is next?

    What needs attention?

  • Salesforce team

    How is the payment architecture connected?

Different teams ask different questions. The underlying payment story should remain connected.

Industry perspectives

Payment Questions Change With the Business Context.

Not industry summaries — the specific boundary question each context tends to raise about where payment management stops.

Financial & Professional Services

How should client payments remain connected to the client relationship?

Read

Education

How should relevant payer payment activity remain connected without turning payment management into student accounting?

Read

Healthcare

Where does customer payment management end and healthcare billing begin?

▸ Page not yet published

Technology & SaaS

Where does recurring payment management end and subscription billing begin?

Read

Membership & Associations

How is recurring payment different from membership management?

Read

Real Estate & Property

How should relevant property-related customer payments remain connected without turning Bonza into property management software?

Read

Nonprofits

Where does payment management end and fundraising management begin?

Read

Other Salesforce-Powered Businesses

Should you start with the industry label — or the payment model?

Read

Quick answers

Payment Questions, Answered Clearly.

Answer first, explanation second. These are the definitions the rest of this blog assumes.

What is payment management?

The lifecycle around the transaction.

Payment management covers the wider customer payment lifecycle around relevant transactions, including payment context, receivables, recurring activity, refunds, customer credits and future payment visibility. Salesforce-native payment management means that lifecycle is managed inside Salesforce, alongside the customer record it belongs to, rather than in a separate portal.

Is Bonza a payment gateway?

No.

Configured payment gateways handle relevant underlying transaction processing. Bonza manages the broader Salesforce-native payment lifecycle. Stripe, Razorpay and PayU are examples of the kind of gateway a business might configure; Bonza is the layer that manages what the business needs to know around whichever one is in use.

Is recurring payment management the same as subscription billing?

No.

Recurring payment management focuses on repeating payment activity. Subscription billing can additionally include product catalogs, pricing plans, usage, metering, proration and other billing logic. A business with repeating payments does not automatically need the second thing.

Is outstanding the same as overdue?

No.

A payment may be outstanding before its relevant due date. It becomes overdue after the relevant due date passes. An outstanding balance is a normal state; an overdue balance is an operational signal, and reporting that merges them loses the difference.

Is customer credit a wallet?

No.

Customer credit is relevant value recorded and managed within Bonza Payments for future supported payment use. Bonza does not hold customer cash, does not operate a stored-value account and is not a bank or acquirer. The credit is a record of value available against future supported payments, not money sitting somewhere.

Is payment forecasting the same as cash-flow forecasting?

No.

Bonza Payment Forecasting focuses on relevant expected customer payment activity. It should not be described as treasury, bank-balance or corporate cash-flow forecasting. Payment-method expiry is a related forward signal: a card or mandate approaching its end date becomes operationally relevant before a recurring payment is attempted, not after it fails.

From concept to capability

When the Concept Becomes a Payment Requirement.

Educate first, connect to the product second. Three worked pathways from an idea on this page to the capability, solution and role it touches.

Editorial roadmap

What This Blog Intends to Cover.

▸ Planned · nothing below is published

These are the seven clusters this blog is being built around. They are stated here as an editorial plan so the direction is visible — every line below is a topic the blog intends to address, not an article that exists. None of them has a page, a date, an author or a link, and none will appear as published until it is written.

Cluster 01

Payment management foundations

  • What payment management means in Salesforce
  • Payment management versus payment processing
  • Why a gateway is not a payment operating system
  • What Salesforce-native actually implies
  • The customer payment lifecycle end to end
Cluster 02

Receivables

  • Invoice versus receivable
  • Outstanding versus due versus overdue
  • Why receivables visibility needs more than a total
  • What Finance should see about customer payments
Cluster 03

Recurring

  • Recurring payments versus subscription billing
  • Why recurring payments still create recurring manual work
  • What Finance should know about the next payment
  • Payment-method expiry before a recurring payment
Cluster 04

Post-payment

  • Refund versus customer credit
  • What happens to the payment story after a refund
  • Why customer credit should not become a stranded record
  • Payment status versus payment position
Cluster 05

Payment architecture

  • Salesforce, Bonza and the configured gateway
  • When a payment integration becomes an architecture
  • Why multiple gateways create a design problem
  • Experience Cloud payment architecture
Cluster 06

Payment intelligence and forecasting

  • Payment forecasting versus cash-flow forecasting
  • Past, present and future payment visibility
  • What a payment command center should show
  • What AI should and should not do in payment operations
Cluster 07

Customer-side payment experience

  • Why payment experience starts before checkout
  • Checkout versus customer payment experience
  • What customers need to understand before paying
  • Customer self-service versus a payment form

Why this point of view

Bonza Looks at Payments as a Lifecycle — Not a Collection of Transactions.

Bonza Payments is a Salesforce-native payment-management suite covering relevant one-time and recurring payments, invoices, receivables, due and overdue payment visibility, refunds, customer credits, multiple configured gateways, customer payment experiences and forward payment visibility.

Building across that range is what produces the editorial perspective on this page. Once a product has to answer what came before a payment and what remains after it, the lifecycle stops being a framing device and becomes the thing being modelled.

  • The transaction is important — but so is what came before it.
  • What remains after it.
  • What changes later through refund or credit.
  • What happens next, as recurring or upcoming activity.
  • What the customer sees at each point.
  • What Finance needs to see that a gateway does not show.
  • What Operations actually needs to act on.
Explore Bonza Payments

Capabilities this perspective comes from

This blog teaches the connected payment model that the Bonza suite is designed around.

Blog FAQ

Questions About This Blog.

What topics does the Bonza Payments Blog cover?

Salesforce payment management, payment operations, receivables and Accounts Receivable, recurring payments, customer payment experience, payment architecture, multiple payment gateways, refunds and customer credits, payment forecasting, payment-method expiry and AI-supported payment operations. The seven editorial streams on this page show how those topics are grouped.

Who is the Bonza Payments Blog for?

CFOs and finance leaders, Accounts Receivable teams, revenue operations, business operations, customer service leaders, and Salesforce leaders, architects and product owners — broadly, anyone responsible for customer payments that run through Salesforce.

What is payment management in Salesforce?

Payment management covers the wider customer payment lifecycle around relevant transactions: payment context, receivables, recurring activity, refunds, customer credits and future payment visibility. Salesforce-native means that lifecycle is managed inside Salesforce rather than in a separate system.

What is the difference between payment management and payment processing?

Payment processing and payment management are different. Configured gateways process relevant transactions, while payment management covers the wider lifecycle around the transaction.

Does the Bonza Blog cover Accounts Receivable?

Yes. Receivables and Accounts Receivable are one of the seven standing editorial streams, covering the distinction between outstanding, due and overdue, receivables visibility, payment context and the operating views Finance works from.

Does the Blog cover recurring payments?

Yes, as a standing stream. It covers recurring payment management, the difference between recurring payments and full subscription billing, next-payment visibility, payment-method expiry and exception handling.

Does Bonza publish content for Salesforce architects and admins?

Yes. The For Salesforce Teams series is written for that audience and deals with payment architecture: where a gateway integration ends and a payment-management layer begins, multiple gateways, Experience Cloud, reusable payment capability and post-payment architecture.

Does the Blog cover customer payment experience?

Yes. The customer payment experience stream and the For Customer Experience series both deal with what a customer needs to understand before and after paying, including payment context, amount clarity, available payment choices and self-service payment journeys.

Does the Blog discuss multiple payment gateways?

Yes, mainly as an architecture question rather than a provider comparison: what changes operationally when a business configures a second gateway, and how to keep the payment process from becoming hard-wired to any one provider.

Does the Blog cover payment forecasting and AI insights?

Yes, within the payment intelligence stream. Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash flow, treasury or bank balances. Bonza AI Payment Insights are positioned as decision-support signals for human review rather than autonomous financial decision-making.

How many articles are published on this blog right now?

None. This page is the Blog's editorial architecture, published ahead of the articles themselves. Everything on it is either original explanation or a link to a page that genuinely exists elsewhere on this site — there are no placeholder articles, dates, authors or reading times anywhere on it.

Where can I find broader Bonza payment resources?

The Resources Hub is the guided entry point: it starts from the question you are trying to answer and routes to the capability page that answers it. This Blog is the ongoing educational counterpart — the Hub helps you find the right page, the Blog explains how the payment model works.

Turn the Payment Question Into a Connected Payment Model.

If your payment operation is split across Salesforce, gateway portals, recurring processes, receivables, refunds, credits or customer experiences, see how Bonza Payments connects the wider payment lifecycle.

Explore Bonza Payments Discuss Your Payment Requirement