Book a Demo
  1. Home
  2. Resources
  3. Guides & eBooks

Guides & eBooks

Go Deeper on the Payment Problems That Matter.

Structured guidance for understanding Salesforce payment management across collection, receivables, recurring payments, refunds, customer credits, customer experience and payment operations.

Start With a Payment Problem Browse Payment Topics

Structured deep-dive learning from Bonza Payments. The Bonza Payments Guides & eBooks library provides structured, long-form educational resources on Salesforce payment management.

How a deep dive runs Six moves
  1. Payment management questionSomething the business cannot currently answer.
  2. Deep diveThe concept taken apart properly, not summarised.
  3. FrameworkA repeatable way to reason about it.
  4. Payment modelHow the lifecycle behaves once the framework is applied.
  5. DecisionWhat the organisation should now evaluate.
  6. Relevant Bonza capabilityThe page that covers it, once the model is clear.
  • Receivables
  • Recurring payments
  • Customer experience
  • Refunds & credits
  • Payment architecture
  • Payment forecasting
  • Payment operations
The premiseStart with the question. Go deeper into the operating model.

Definition

What Are the Bonza Payments Guides & eBooks?

The Bonza Payments Guides & eBooks library provides structured, long-form educational resources for organizations that want to understand customer payment management in Salesforce more deeply.

These resources are designed to help Finance, Accounts Receivable, Revenue Operations, Business Operations, Customer Service and Salesforce teams understand payment models, operational trade-offs, architecture decisions and the wider customer payment lifecycle.

The goal is education first. A guide should help you understand what a good payment operating model looks like before you evaluate the relevant Bonza capability — which is a different job from a product page, and a different job from an article.

Bonza guides can cover payment-management topics including one-time payments, recurring payments, receivables, due and overdue payments, refunds, customer credits, multiple payment gateways, customer payment experiences and forward payment visibility.

Guide discovery

Choose the Payment Problem You Want to Understand Better.

Eight problems that bring people to a payment project. Each one names what to explore and where it is already covered — pick one here, then see it taken apart stage by stage in the next section.

01

How should payments work in Salesforce?

  • Payment management
  • Processing vs management
  • Salesforce → Bonza → gateway
  • Multiple configured gateways
Payment Management
06

How should multiple payment gateways fit together?

  • Multiple payment gateways
  • Payment architecture
  • Configured gateway layer
  • Operational consistency
Multiple Payment Gateways

Choose the payment question first. The guide should help you understand the model behind it.

Signature

A Useful Guide Should Do More Than Explain the Feature.

The same six stages, applied to each of the eight problems above. Pick a problem and watch the scaffold fill in — the stages never change, only what goes in them. That repetition is the point: a guide is a decision model, not a document.

Choose the payment problem

Payment problem 1 of 8

How should payments work in Salesforce?

  1. 1

    Define the problem

    What are we actually trying to solve?

    Usually the stated problem is "we need to take a payment", when the real problem is that nobody can answer questions about that payment afterwards. Getting money to move is the easy half.

  2. 2

    Understand the model

    What does the payment lifecycle look like here?

    A relevant transaction is processed by a configured gateway, but the amount expected, the amount collected, what remains, what changed and what comes next all belong to a layer above it. Payment processing and payment management are different. Configured payment gateways process relevant transactions, while Bonza manages the wider Salesforce-native payment lifecycle.

  3. 3

    Identify the misunderstandings

    What do teams commonly get wrong?

    The common error is treating the gateway as the system of record. Its records are organised around transactions it processed, not around customers, positions or obligations, so every later question becomes a reconciliation exercise.

  4. 4

    Compare the options

    What are the trade-offs?

    Building payment logic directly against a gateway is fastest for the first requirement and most expensive for the fifth. A payment-management layer costs more to adopt and less to extend once one-time, recurring, invoice-driven, refunded and credited activity all have to coexist.

  5. 5

    Understand the operating impact

    What changes for Finance, Operations, Salesforce and the customer?

    Finance gains a position rather than a transaction list. Salesforce teams stop re-implementing payment logic per requirement. The customer sees payment activity that matches the relationship they already have.

  6. 6

    Choose the right next step

    Which capability or architecture should be evaluated?

    Start with what the management layer is responsible for, then look at how gateways attach beneath it.

    Payment Management Multiple Payment Gateways Salesforce Teams
Scaffold completeness48 of 48 stages written
Where stage six leads24 distinct destinations, all published here
PlaceholdersNo stage left as a placeholder

A good guide should leave the buyer with a better decision model, not just more product information.

Collections

Explore Guides by Payment Topic.

Seven topic collections, each defined by the questions a guide in it would have to answer. The guide formats listed against each are planned shapes for the library, not resources you can open today.

Collection 01

Payment Management Foundations

  • Foundational guide
  • Architecture guide
  • Buyer guide
  • What is payment management?
  • How is it different from payment processing?
  • What belongs in Salesforce?
  • What belongs in Bonza?
  • What belongs in the payment gateway?
Covered today byPayment Management Multiple Payment Gateways Salesforce Teams
Collection 03

Recurring Payment Operations

  • Recurring payments guide
  • Operational playbook
  • Comparison guide
  • What makes a payment recurring?
  • How should payment history stay connected?
  • How is recurring payment different from subscription billing?
  • How does the next payment affect operations?
Covered today byRecurring Payments Manage Recurring Payments Payment Method Expiry
Collection 04

Post-Payment Value Changes

  • Post-payment guide
  • Refund vs credit guide
  • Finance and service playbook
  • What happens after payment value changes?
  • Refund or customer credit?
  • How does post-payment activity affect the wider customer payment position?
Covered today byRefunds Credit Management Credits & Refunds
Collection 07

Payment Forecasting & Intelligence

  • Payment forecasting guide
  • Finance planning guide
  • Payment intelligence guide
  • What payment activity is expected next?
  • What is payment forecasting, and how is it different from cash-flow forecasting?
  • How does payment-method expiry become an attention signal?
  • What should AI surface, and what should it leave alone?
Covered today byPayment Forecasting Forecast Upcoming Payments AI Payment Insights

Depth

Choose the Depth You Need.

Six long-form formats the library is being built around. None is available yet — they are listed so the intended range is clear, not so you can pick one today.

▸ Planned

Foundational guide

Understand a payment concept end to end, starting from what it is rather than from what a product does with it.

▸ Planned

Buyer guide

Understand what to evaluate before choosing a payment approach, including the questions that are easy to skip early and expensive later.

▸ Planned

Architecture guide

Understand system responsibilities and integration boundaries: which layer owns customer context, payment management and transaction processing.

▸ Planned

Finance playbook

Understand operational finance and receivables workflows, from what was expected through to what currently needs attention.

▸ Planned

Comparison guide

Understand concepts that sound similar and solve different problems, which is where most payment mis-specification begins.

▸ Planned

Implementation guide

Understand what a strong payment-management implementation should consider, as education rather than as a services offer.

Deliberately absent from this list: research report, benchmark report and industry study. No research, benchmarking or survey work has been conducted, so no resource will carry those labels.

Standard

Built to Help You Make Better Payment Decisions.

What every long-form resource should include

  1. 01
    The business questionWhat are we solving, stated as the business would state it?
  2. 02
    The payment modelHow the lifecycle works once the question is taken seriously.
  3. 03
    The common mistakesWhat typically goes wrong, and why the mistake is reasonable.
  4. 04
    The architectureWhich system should own what, and what should stay outside.
  5. 05
    The operational impactHow it affects Finance, Operations, Customer Service and Salesforce.
  6. 06
    The decision frameworkWhat the organisation should evaluate next, in what order.
  7. 07
    The Bonza connectionWhich relevant Bonza capability applies — last, not first.
A good guide should help the buyer make a better payment decision — not just give them more content.

The order matters more than the contents. A resource that opens with the capability and works backwards to the problem is a product page wearing a guide's clothes, and readers can tell. The business question has to come first and the product connection has to come last, or the middle stages get quietly shaped to lead somewhere.

That is also why the sequence puts common mistakes before architecture. Most payment architecture decisions are made to solve a misunderstanding rather than a requirement, and naming the misunderstanding first tends to change what gets built.

Education first. Product connection second.

Learning paths

Choose a Guide Path Based on the Questions Your Team Asks.

Five ordered routes through pages that exist today. These are fixed sequences, not recommendations — nothing here is personalised, scored or AI-generated, and the order is editorial judgement about what to read first.

The path

Read the payment position before reading the payment event.

  • What has been collected?
  • What remains outstanding?
  • What is due?
  • What is overdue?
  • What is expected next?
  1. 1
    Receivables

    Start with how an expected amount becomes an outstanding one.

  2. 2
    Due & Overdue Payments

    Then separate a timing state from a collection problem.

  3. 3
    Accounts Receivable

    Then see why two identical AR totals can describe different situations.

  4. 4
    Credits & Refunds

    Then account for value that moved back after collection.

  5. 5
    Finance & Accounts Receivable

    Finish with the operating view Finance works from.

5 steps · every step is a page published on this site · ordered, not ranked

Before you evaluate anything

Seven Payment Concepts Worth Understanding Before Choosing a Solution.

Each pair sounds like one idea and behaves like two. Most payment requirements that get written down incorrectly trace back to one of these seven.

01
Payment processing≠Payment management

Payment processing and payment management are different. Configured payment gateways process relevant transactions, while Bonza manages the wider Salesforce-native payment lifecycle. Payment Management

02
Outstanding≠Overdue

An amount can be outstanding well before its relevant due date. It becomes overdue only once that date has passed, which makes one a timing fact and the other an operational signal. Due & Overdue Payments

03
Recurring payment≠Subscription billing

Recurring payment management and subscription billing are not the same. Recurring payment management focuses on repeating payment activity, while subscription billing may include pricing, usage, metering, proration and other billing logic. Manage Recurring Payments

04
Invoice≠Receivable

An invoice states what was asked for; a receivable is the portion still waiting to be collected. One is a document that does not change, the other is a position that does. Invoice-Based Payments

05
Refund≠Customer credit

Customer credit in Bonza Payments is credit recorded and managed within the payment lifecycle for relevant future supported payment use. It should not be described as stored customer cash or a digital wallet. A refund, by contrast, returns value outward through the applicable refund process. Credits & Refunds

06
Payment forecasting≠Cash-flow forecasting

Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow, treasury or bank-balance forecasting. Expected payment activity is also not guaranteed collection. Payment Forecasting

07
Customer payment experience≠Payment checkout

Checkout is the moment of payment. The customer payment experience is everything that determines whether the customer understood the amount beforehand and the outcome afterwards. Customer Payment Experience

Buyer guide

What Should You Evaluate Before Choosing a Salesforce Payment Solution?

Two lists. The first asks whether the payment model is complete; the second asks whether the architecture is clear. Most evaluations cover the first and skip the second.

Does the payment model include…

  • One-time payments
  • Recurring payments
  • Invoice-driven payments
  • Receivables
  • Due and overdue payments
  • Refunds
  • Customer credits
  • Multiple payment gateways
  • Customer-facing payment journeys
  • Experience Cloud
  • Upcoming payment visibility
  • Payment-method expiry
  • An operational payment view
  • AI-supported payment insights for human review

Then ask the architecture questions

  • Which system owns customer context?
  • Which system owns payment management?
  • Which system processes the transaction?
  • How will post-payment changes stay connected?
  • How will Finance see the current payment position?
  • How will customer-facing payments connect to Salesforce?
  • How will future payment activity be represented?

A good payment solution should fit the whole payment model — not just the first transaction.

Implementation thinking

What Good Salesforce Payment Implementation Should Achieve.

Eight outcomes worth designing towards. This is educational framing rather than a services offer — Bonza publishes it so the standard is legible, not to describe an engagement.

01

Clear responsibilities

Salesforce, Bonza, the configured gateway and any relevant business system each have a defined role, agreed once rather than per requirement.

02

Connected customer context

Payment activity is tied to the customer relationship it belongs to, not held beside it.

03

Consistent payment model

One-time, recurring, receivables and post-payment activity do not become four unrelated architectures.

04

Clear payment states

Collected, outstanding, due and overdue are distinguishable rather than summed into one figure.

05

Post-payment continuity

Refunds and customer credits remain attached to the payment they changed.

06

Customer experience continuity

Customer-facing payment activity stays part of the same lifecycle the business reads.

07

Visibility of what is expected

Relevant upcoming payment activity can be understood before it happens rather than reconstructed afterwards.

08

Human control

AI and payment signals support decision-making rather than silently taking autonomous financial action.

Business context

Apply the Payment Model to Your Business Context.

Each business context raises a different boundary question about where payment management should stop. These are the questions, not industry guides — no industry resource has been written.

Financial & Professional Services

How should client payment obligations, receivables and post-payment activity remain connected?

Explore

Education

How should payer payment activity remain connected without confusing payment management with student accounting?

Explore

Healthcare

Where does customer payment management end and healthcare billing begin?

▸ Page not yet published

Technology & SaaS

What is the difference between recurring payment management and subscription billing?

Explore

Membership & Associations

How is recurring payment different from membership renewal logic?

Explore

Real Estate & Property

How should property-related customer payments remain connected without turning payment management into property management?

Explore

Nonprofits

How should relevant payment activity remain connected without confusing payment management with fundraising?

Explore

Other Salesforce-Powered Businesses

Which payment model fits the business even when the industry does not have a dedicated category?

Explore

From model to capability

From Understanding the Payment Model to Evaluating the Right Capability.

The sequence that keeps a deep dive useful: understand the requirement before evaluating the product.

Learn

The concept, properly

Understand

The payment problem

Map

The payment model

Explore

The relevant capability

Operate

The wider lifecycle

The guide should help the visitor understand the requirement before they evaluate the product.

Editorial roadmap

The Guides This Library Is Being Built Around.

▸ Planned · nothing below is published

Seven guide concepts, with the chapter outlines they would follow. These are stated as a plan so the intended depth is visible. None of them exists yet: none has a page, a date, an author, a page count or a link, and none will be presented as available until it is written.

Concept 01 · Foundational

Payment management in Salesforce: from transaction to customer payment lifecycle

  • What payment processing actually solves
  • What payment management adds
  • Salesforce, Bonza and the gateway
  • One-time payments
  • Recurring payments
  • Invoice-driven payments
  • Receivables
  • Due versus overdue
  • Refunds versus customer credits
  • Customer payment experience
  • Multiple configured gateways
  • Payment forecasting
  • AI insights
  • Payment Command Center
TransactionCustomer contextPayment positionWhat changedWhat happens next
Concept 02 · Finance

The connected Accounts Receivable operating model

  • What was expected
  • What was collected
  • What remains open
  • What is not yet due
  • What is due
  • What is overdue
  • What changed through refund or credit
  • What is expected next
ExpectedCollectedOpenDue / overdueAttentionNext

Central distinction: an AR total is not an AR position.

Concept 03 · Comparison

Recurring payment management without confusing it with subscription billing

  • Recurring payment definition
  • One-time versus recurring
  • Recurring versus subscription billing
  • Current payment versus next payment
  • Receivables
  • Due and overdue
  • Payment-method expiry
  • Refund and credit
  • Forecasting
  • Exception management
Past paymentCurrent paymentNext payment

Central message: the payment repeats, the context accumulates.

Concept 04 · Post-payment

What happens after payment value changes?

  • Refund is not customer credit
  • Payment status is not payment position
  • Transaction history is not value history
  • Customer credit is not a wallet
Original paymentChange requiredRefund or customer creditUpdated payment position
Concept 05 · Customer experience

Building a customer payment experience that explains the payment, not just the form

  • Understand what am I paying
  • Review how much
  • Choose the relevant available option
  • Pay
  • Confirm what happened
  • Continue into the wider relationship
Pay buttonIs not the same asCustomer self-service
Concept 06 · Architecture

Salesforce to Bonza to payment gateway: designing a clean payment architecture

  • Who owns customer context
  • Who owns payment management
  • Who processes the transaction
  • What happens with multiple gateways
  • What happens with Experience Cloud
  • What should remain outside Bonza
Business systemSalesforceBonza PaymentsConfigured gateway
Concept 07 · Intelligence

From payment history to forward payment visibility

  • Past: collected, refunds, credits
  • Present: outstanding, due, overdue
  • Future: upcoming, recurring, forecast
  • Payment-method expiry as a forward signal
PastPresentFuture

Central distinction: payment forecasting is not cash-flow forecasting, and expected payment activity is not guaranteed collection.

Why this subject matter

Bonza Guides Are Built Around the Connected Payment Lifecycle.

Bonza Payments covers a connected Salesforce-native payment lifecycle rather than a single step in it. Building across that whole range is what makes a guide worth writing: the questions a buyer needs answered span the lifecycle, so the subject matter has to as well.

That produces a useful educational position. The question is not only "how do we process a transaction?" but "what happens before, during and after payment?" — and the second question is the one that determines whether a payment operation works a year later.

Bonza's guides teach the same connected payment model the product is designed around.

Explore Bonza Payments

The lifecycle these guides draw on

Configured gateways such as Stripe, Razorpay or PayU are named here only as examples of providers a business might configure. Naming them implies no partnership or endorsement.

Guides FAQ

Questions About These Guides.

What types of guides does Bonza Payments publish?

None yet. The library is planned around six long-form formats — foundational guide, buyer guide, architecture guide, finance playbook, comparison guide and implementation guide — and this page sets out that structure ahead of the guides themselves. Nothing is available to read or download today.

Who are the Bonza Payments guides for?

CFOs and finance leaders, Accounts Receivable teams, revenue operations, business operations, customer service leaders, and Salesforce leaders, architects and product owners — anyone who has to understand a customer payment model in Salesforce rather than just operate one screen of it.

Will the guides cover Salesforce payment management?

Yes, as the foundational collection. It deals with what payment management is, how it differs from payment processing, and what belongs in Salesforce, in Bonza and in the configured gateway respectively. The Payment Management page covers that ground today.

Will the guides cover Accounts Receivable and receivables?

Yes. The receivables collection covers what was expected, what was collected, what remains open, and the difference between outstanding, due and overdue — plus how Finance should read a payment position rather than an AR total.

Will the guides explain recurring payments?

Yes, including the distinction that causes the most mis-specification. Recurring payment management and subscription billing are not the same. Recurring payment management focuses on repeating payment activity, while subscription billing may include pricing, usage, metering, proration and other billing logic.

Will the guides explain refunds and customer credits?

Yes, as a post-payment collection. Customer credit in Bonza Payments is credit recorded and managed within the payment lifecycle for relevant future supported payment use. It should not be described as stored customer cash or a digital wallet.

Will the guides cover payment architecture and multiple gateways?

Yes. The architecture collection deals with how Salesforce, Bonza and configured gateways divide responsibility, what changes when a second gateway is introduced, and the point at which a payment integration has quietly become a payment architecture.

Will the guides cover Experience Cloud payments?

Yes, within the customer payment experience collection, which covers what a customer needs to understand before paying, the difference between a checkout and genuine self-service, and how payments delivered through Salesforce Experience Cloud fit the wider journey.

Will the guides explain Payment Forecasting?

Yes. Bonza Payment Forecasting focuses on relevant expected customer payment activity rather than corporate cash-flow, treasury or bank-balance forecasting. A guide on it would also cover why expected payment activity is not the same as guaranteed collection.

Are Bonza guides free, and will I need to provide my details?

No access rules exist yet, because no guide exists yet. Nothing on this page is gated, there is no form to complete and no email address is collected anywhere on it. When guides are published, how they are accessed will be stated on the page rather than assumed here.

Where can I find shorter payment-management articles?

The Blog is the shorter-form counterpart, covering the same topics as ongoing editorial pieces rather than structured long-form learning. It has no published articles yet either, but it carries the editorial explanation of each concept.

Where can I find all Bonza resources?

The Resources Hub is the guided entry point across everything published on this site. It starts from the question you are trying to answer and routes to the capability page that answers it, which is a different job from this page — the Hub helps you find the right page, these guides would explain the model behind it.

Understand the Payment Model Before You Build Another Payment Process.

Explore the payment topic that matches your requirement, or move directly into the capability that covers it.

Explore Payment Topics Discuss Your Payment Requirement