1. Home
  2. Resources
  3. Payment Insights

Payment Insights

Turn Payment Data Into Payment Understanding.

Learn how to interpret customer payment activity across collected, outstanding, due, overdue, recurring and upcoming payments, refunds, customer credits and payment-method timing inside Salesforce.

Educational resources for Salesforce payment operations. Payment insights are interpretations of customer payment data that help users understand changes, timing, patterns and situations that may deserve attention.

Raw payment data

  • Collected $45,000
  • Outstanding $5,000
  • Due $1,200
  • Overdue $800
  • Upcoming $3,000

Illustrative sample values, not real customer data.

Context applied

  • Customer
  • Timing
  • Payment history
  • Recurring activity
  • Refund & credit context
  • Payment-method timing

The same figures mean different things once they are read against the customer and the calendar.

Payment insights

  • An outstanding item has moved into an overdue position.
  • A payment method expires before an upcoming expected payment.
  • Relevant upcoming payment activity has changed.
  • A customer payment position changed after a refund.

Then a person decides

Review contextUnderstand impactChoose relevant action

Definition

What Are Payment Insights?

Payment insights are interpretations of customer payment data that help teams understand changes, timing, patterns and situations that may deserve attention.

In Bonza Payments, relevant payment context can include payment activity, receivables, due and overdue states, recurring activity, upcoming payments, refunds, customer credits and payment-method timing. Bonza Payments can connect relevant payment context across receivables, due and overdue activity, recurring payments, upcoming payments, refunds, customer credits and payment-method timing.

Payment insights should support human decision-making. They should not be positioned as autonomous financial decisions, and nothing on this page describes Bonza making one.

Insight is not another payment status. It is context that helps a person understand what may matter.

The real problem

Most Payment Teams Do Not Have a Data Problem. They Have an Interpretation Problem.

The records usually exist. What is missing is the reading of them.

A business may already hold

  • Payment records
  • Gateway transactions
  • Invoices
  • Receivables
  • Recurring payment information
  • Refund records
  • Customer-credit records
  • Future expected payments

All of it accurate, all of it available, and none of it answering the question someone actually has at nine in the morning.

And still have to work out

  • What changed since yesterday?
  • What moved from normal to needing attention?
  • Which overdue payment is actually important?
  • What does this refund change?
  • Does customer credit affect the next payment?
  • Is a payment method expiring before relevant future activity?
  • Did expected recurring payment activity change?
  • What should Finance review first?

More payment data does not automatically create better payment decisions.

The data needs context.

The core distinction

Payment Data Tells You What Happened. Payment Insight Helps Explain Why It Matters.

Payment data and payment insight are different. Payment data records the event or state, while payment insight adds context that helps explain why it may matter operationally.

Payment data

"What is the recorded state?"

  • Payment collected
  • $5,000 outstanding
  • Payment due today
  • Payment overdue
  • Next payment expected
  • Payment method expires
  • Refund recorded
  • Customer credit exists

Payment insight

"What changed, what is unusual, or what may deserve attention?"

  • An outstanding amount has moved into an overdue position.
  • A relevant payment method expires before upcoming expected payment activity.
  • A recurring payment pattern has changed.
  • A relevant customer payment position changed after a refund or credit.
  • Upcoming payment activity deserves review.

Data is the input. Insight is the interpretation layer around the data.

Signature

Most Useful Payment Insights Begin With One Question: What Changed?

One customer payment position, six scenarios. The same six fields are compared before and after, and an insight appears only where a field actually moved. Nothing here is asserted: pick the quiet scenario and the page produces nothing, because an unchanged position is not a signal.

Choose what happened

Scenario 1 of 6

Nothing about the amount changed. The date did.

Field
Before
After
Moved
Outstanding
$5,000
$5,000
No change
Timing state
Not yet due
Overdue
Changed
Next expected payment
15 Nov
15 Nov
No change
Payment method expiry
31 Dec
31 Dec
No change
Refund recorded
None
None
No change
Customer credit
None
None
No change

Insights derived from the comparison

  • The outstanding amount has moved into an overdue position. The figure is identical to yesterday’s; only its timing state has changed, and that is what makes it worth looking at.
Then Human reviewDecisionRelevant action
Fields that moved6 field changes across 6 scenarios
Insights produced6 insights produced
TraceabilityEvery insight traces to a field that moved

All values shown are illustrative sample data used to explain the concept. They are not real customer data, not a measured Bonza result and not a performance claim.

The absolute values matter. The change between states often matters more.

The pipeline

How Payment Data Becomes Operationally Useful.

  1. 01
    DataA payment record exists. On its own it states a fact and asks nothing.
  2. 02
    ContextCustomer, payment history, receivables, timing, recurring activity, refunds and credits.
  3. 03
    ChangeSomething moved, something became overdue, something is approaching, something changed after collection.
  4. 04
    SignalThe situation may deserve attention.
  5. 05
    InsightAn explanation of what changed and why it may matter.
  6. 06
    Human reviewAn authorised person evaluates the context.
  7. 07
    ActionA relevant business action is chosen — by a person.

And the distinction it produces

A Payment Status Is Not Automatically a Payment Signal.

Status

"What state is this payment in?"

  • Outstanding
  • Due
  • Overdue
  • Collected
  • Refunded

Signal

"What changed or became operationally relevant?"

  • Moved into overdue
  • Overdue amount increased
  • Upcoming payment changed
  • Expiry occurs before a future payment
  • A refund changed the customer position
  • Customer credit may be relevant to future payment activity

Status describes the state. Signal describes the meaningful change.

Signal explorer

Six Payment Signals, Read From Raw Data Through to Human Review.

Each signal type shown in four steps. Every one ends with a person, because that is where the decision belongs — this is a fixed explanation, not a recommendation engine and not AI.

The situation

A relevant due date has passed on an amount that is still open.

Raw data

An outstanding amount of $5,000 is recorded against the customer, with a relevant due date attached to it.

Relevant context

The customer, the original expected amount, what has been collected so far and where this sits against the rest of their position.

Possible signal

The amount has moved from not-yet-due into an overdue position.

Human review

An authorised person decides what, if anything, to do about it. Nothing is chased, escalated or written off automatically.

Covered in Bonza by Due & Overdue Payments Accounts Receivable

Time context

The Same Payment Means Different Things at Different Points in Time.

Past

What has already happened?

Settled facts that still shape the present.

  • Collected
  • Refunded
  • Customer credit
  • Payment history

Present

What is happening now?

The position as it currently stands.

  • Outstanding
  • Due
  • Overdue
  • Current payment position

Future

What may matter next?

Expected activity, not settled activity.

  • Upcoming payment
  • Recurring payment
  • Payment forecast
  • Payment-method expiry

The insight layer sits across all three

What changed, what needs attention, what deserves review?

  • What changed?
  • What needs attention?
  • What deserves review?

Payment insight needs time context.

The same amount can have a different operational meaning yesterday, today and tomorrow.

Where context creates the signal

Six Payment Situations Where the Interpretation Does the Work.

In each of these, the underlying data is unremarkable. What makes it operationally meaningful is what it is read against.

01

Timing turns an open payment into an operational signal.

  • Outstanding
  • Not yet due
  • Due
  • Overdue
  • Attention
  • Human review

An amount remaining outstanding is information. The point at which it moves into a due or overdue state is what adds operational meaning — the number itself may not have moved at all.

Not claimedNothing here describes automatic collections, automatic dunning, customer chasing, automatic reminders or legal escalation. The signal ends at a person.
Explore Due & Overdue Payments
02

The receivables total is data. The composition is insight.

  • Total outstanding
  • Not yet due
  • Due
  • Overdue
  • Recurring & upcoming
  • Refund & credit context

Two organisations can report an identical receivables total and be in entirely different situations. One may be almost entirely not-yet-due; the other almost entirely overdue. The total cannot tell them apart, and only the composition answers which part of the balance may deserve attention.

Explore Accounts Receivable
03

Recurring payments create insight through continuity.

  • Payment 01
  • Payment 02
  • Payment 03
  • Next expected
  • Change

A series of collected payments is a history. What makes it interpretable is the comparison between occurrences: an occurrence that moved into overdue, a next expected payment that shifted, an expiry that now falls before the next attempt, or a refund that changed the history behind it.

The signal is often not the payment itself. It is the change across payment events.

Explore Recurring Payments
04

The expiry date matters most when you compare it with what comes next.

  • Expires 31 Oct
  • Next payment 15 Nov
  • Timing conflict
  • Human review

An expiry date alone is data. Its relationship with relevant future payment activity is what creates the operational context: 31 October matters because 15 November is expected, and would matter far less if nothing were expected at all.

Not claimedPayment Method Expiry should be treated as a timing signal rather than proof that a future payment will fail. No automatic card updater, automatic remediation, automatic customer outreach or failure prediction is described anywhere on this page.
Explore Payment Method Expiry
05

A refund changes more than the transaction history.

  • Original $1,000
  • Refund $250
  • Updated history
  • Updated position

Once $250 has been returned against an original $1,000, the collected figure stops being a description of where the customer stands. The original amount is still true and no longer sufficient.

Post-payment events should be interpreted in the context of the original payment and the wider customer relationship, rather than recorded beside it as unrelated activity.

Explore Refunds
06

Customer credit matters most when it is connected to future payment context.

  • Credit $200
  • Upcoming payment $1,000
  • Payment context
  • Human decision

Recorded customer credit of $200 is a fact. It becomes useful when read against a relevant upcoming payment, because then it may be relevant to future supported payment activity rather than sitting as an isolated record.

Not claimedCustomer credit is recorded and managed within Bonza Payments. It is not a wallet, stored cash, a bank balance or funds held by Bonza, and nothing is applied to a future payment automatically.
Explore Credit Management

Forward context

Expected Payment Activity Is Useful — As Long as It Is Not Confused With Guaranteed Cash.

  1. —
    TodayThe position as recorded now.
  2. —
    Next 7 daysExpected payment activity.
  3. —
    Next 30 daysExpected recurring activity.
  4. —
    BeyondRelevant upcoming payments.

Bonza Payment Forecasting focuses on relevant expected customer payment activity. Expected payment activity does not guarantee collection.

The distinction is the whole value of the section. Payment forecasting answers "what relevant customer payment activity is expected?" It does not answer "how much cash will definitely be in the bank?", and treating the first answer as the second is how a useful forward view becomes a misleading one.

Not claimedBonza Payment Forecasting is not cash-flow forecasting, treasury forecasting, bank-balance forecasting, revenue forecasting, liquidity forecasting or working-capital forecasting, and no forecast is described as guaranteed.
Explore Payment Forecasting

Scope of context

A Gateway View Shows Provider Activity. Payment Insight Needs the Wider Customer Context.

  1. —
    Configured gatewaysProvider-level transactions, whichever providers are configured — Stripe, Razorpay or PayU are examples only.
  2. 02
    Bonza payment managementThe lifecycle layer above them.
  3. 03
    Customer payment contextWhich customer, which agreement, which position.
  4. 04
    Receivables & timingWhat remains open and when it matters.
  5. 05
    Refunds & creditsWhat changed after collection.
  6. 06
    Upcoming activityWhat is expected next.
  7. 07
    Payment insightRead across all of it rather than per provider.
Not claimedNo settlement consolidation, gateway optimisation, smart routing, least-cost routing or automatic failover is described. Gateways remain the configured processing layer.
Explore Multiple Payment Gateways

And the two audiences it serves

The Customer Sees a Payment. The Business Needs to Understand the Wider Context.

Customer view

  • What am I paying?
  • How much?
  • Payment status
  • Relevant customer credit
  • Next relevant payment context

Business view

  • Collected
  • Outstanding
  • Due
  • Overdue
  • Refund
  • Credit
  • Upcoming
  • Signal

The customer and the business need different views. The payment context should still connect.

Explore Customer Payment Experience

Where AI fits

Surface the Signal. Keep the Decision Human.

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

What goes in

  • Payment data
  • Customer context
  • Receivables
  • Recurring activity
  • Upcoming payments
  • Payment-method timing

And the order it comes out in

  1. 01Signal
  2. 02Explanation
  3. 03Recommendation or context
  4. 04Human review
  5. 05Decision
  6. 06Relevant action

Not the Bonza positioning

SignalAutomatic financial action

This shorter path is what the page is arguing against. Removing the review step does not make payment intelligence stronger; it makes the consequences of a misread signal unreviewable.

Examples of what an insight can say

  • A relevant payment moved into an overdue state.
  • Upcoming recurring payment activity changed.
  • Payment-method expiry occurs before future expected payment activity.
  • A refund or customer credit changed the customer payment position.
  • A relevant payment situation deserves review.
Not claimed anywhereAI does not collect money, contact customers, decide whether to refund, decide customer credit entitlement, perform financial write-offs, change recurring schedules, select gateways, score credit, predict default or guarantee collection. It surfaces something for a person to look at.
Good payment intelligence helps people make better decisions. It does not remove appropriate human judgement from financial operations.
Explore AI Payment Insights

Where insights sit

Insights Become More Useful When They Sit Inside the Wider Payment Operation.

The Bonza Payment Command Center provides a wider operational view, while payment insights help users interpret what within that payment activity may deserve attention.

Collected$45,000
Outstanding$5,000
Due$1,200
Overdue$800
Upcoming$3,000

Customer payment position

  • Customer ACollected $12,000 · outstanding $5,000 · next 15 Nov
  • Customer BCollected $20,000 · outstanding $0 · next 01 Dec
  • Customer CCollected $13,000 · outstanding $800 overdue

Payment insights

  • A payment moved to overdueCustomer C
  • An upcoming payment changedCustomer A
  • Relevant customer credit existsCustomer B
  • A payment method expires before the next paymentCustomer A

Needs attention

  • Overdue itemFor review
  • Expiry signalFor review
  • AI payment insightFor review
PaymentRefundCustomer creditRecurring payment event

Illustrative sample values used to explain the concept. Not real customer data.

The Command Center shows the operation. Payment insights help explain what within it may deserve attention.

Explore Payment Command Center

Multi-dimensional

One Customer Payment Relationship Can Generate Several Different Insights.

These are not competing readings of one payment. They are simultaneous, and a single customer can hold all of them at once.

  1. CustomerOne relationship
  2. ObligationAn amount was expected
  3. Current positionOutstanding
  4. Timing signalDue or overdue
  5. Future signalAn upcoming payment
  6. Method signalPayment-method expiry
  7. Post-payment signalRefund or customer credit
  8. Human reviewA person reads all of it together

Payment insight is multi-dimensional. The same customer can have history, a current position, future activity and attention signals at the same time.

Six types worth understanding

01

Status insight

Where does the payment stand?

  • Collected
  • Outstanding
  • Due
  • Overdue
02

Timing insight

When does the state become relevant?

  • Upcoming
  • Due
  • Overdue
  • Expiry
03

Change insight

What changed?

  • Status changed
  • Expected activity changed
  • Position changed
04

Lifecycle insight

What happened before and after the transaction?

  • Refund
  • Customer credit
  • Recurring activity
05

Customer context insight

How does it relate to the wider relationship?

  • Payment history
  • Current position
  • Future activity
06

Attention insight

What may deserve human review?

  • Overdue
  • Expiry
  • Unexpected change
  • Relevant AI insight

No single payment metric explains the entire payment relationship.

By role

Different Teams Need Different Insights From the Same Payment Data.

The data can be shared. The interpretation changes by role.

Revenue Operations

  • What happened after the commercial event?
  • What remains open?
  • What is expected next?

Customer Service

  • What happened to this customer's payment?
  • Was anything refunded?
  • Does customer credit exist?
  • What is the current status?

Salesforce Teams

  • How is payment context represented?
  • Where do insights come from?
  • What belongs in Salesforce, Bonza and the gateway?

By business context

The Signal Changes With the Business Context. The Insight Model Stays Consistent.

The question each context asks is different. The way an insight is produced — data, context, change, signal, review — does not change.

Financial & Professional Services

Which client payment situations require attention?

Explore

Education

Which supported payer payment states or timing changes deserve review?

Explore

Healthcare

Which relevant customer payment events have changed?

▸ Page not yet published

Technology & SaaS

What is happening across relevant recurring payment activity?

Explore

Membership & Associations

What relevant payment activity has changed across the customer or member payment relationship?

Explore

Real Estate & Property

Which supported property-related customer payment situations need attention?

Explore

Nonprofits

What relevant payment activity changed across the customer or supporter payment relationship?

Explore

Other Salesforce-Powered Businesses

What changed in the payment lifecycle, regardless of the business model?

Explore
Deliberately not impliedNo medical billing or claims intelligence, no MRR, ARR, churn or subscription-health metrics, no membership-status intelligence, no property analytics, and no donor propensity or fundraising intelligence. The subject throughout is customer payment activity.

What goes wrong

Seven Mistakes That Turn Payment Data Into Noise.

01

Tracking metrics without context.

BetterConnect amounts to the customer, the timing and the lifecycle state they belong to.

02

Treating every outstanding payment as a problem.

BetterDistinguish not-yet-due from due and overdue. Most outstanding balances are healthy.

03

Looking only at historical transactions.

BetterInclude relevant future payment context, because some signals only exist ahead of time.

04

Treating each gateway as a separate payment world.

BetterInterpret payment activity through the wider customer lifecycle rather than per provider.

05

Ignoring post-payment changes.

BetterKeep refunds and customer credits inside the payment story they changed.

06

Confusing a forecast with certainty.

BetterRead expected payment activity as expected, not as guaranteed cash.

07

Automating the decision too early.

BetterUse payment intelligence to inform authorised human review.

The hidden cost

The Hidden Cost Is the Time Spent Reconstructing Why a Payment Matters.

One question — "does this customer need attention?" — answered two ways.

Reconstructed by hand

  1. Check Salesforce
  2. Check the gateway
  3. Check receivables
  4. Check recurring activity
  5. Check refunds
  6. Check customer credit
  7. Check the next payment
  8. Check the payment method
  9. Interpret manually, then answer

Connected model

  1. Payment data
  2. Bonza payment context
  3. Signals
  4. Payment insights
  5. Human review, then answer

The second path does not remove the judgement. It removes the reconstruction that has to happen before the judgement can start.

If users have to reconstruct the payment story before they can interpret the signal, the insight layer is still fragmented.

Maturity

How Payment Visibility Becomes Payment Intelligence.

Five levels, described so you can recognise where a payment operation currently sits. Not every organisation needs all five, and nothing here scores you.

  1. Level 1

    Transactional

    Users see individual transactions.

    "What happened?"

  2. Level 2

    Status-aware

    Collected, outstanding, due and overdue are distinguishable.

    "Where does the payment stand?"

  3. Level 3

    Contextual

    Payment data connects with the customer, receivables, recurring activity, refunds and credits.

    "What does this mean in context?"

  4. Level 4

    Forward-looking

    Upcoming activity, payment forecasting and payment-method expiry are visible.

    "What may happen next?"

  5. Level 5

    Attention-driven

    Relevant signals surface in an operating view for review.

    "What deserves review?"

Worked through

From Payment Event to Payment Insight.

Five short walk-throughs. Data, then the change, then the reading, then what it means operationally.

01

Overdue

  • DataAn outstanding payment remains unresolved.
  • ChangeThe relevant due date passes.
  • InsightThe payment moved into an overdue state.
  • MeaningMay deserve Finance review.
02

Expiry

  • DataA payment method expires 31 Oct.
  • ChangeAn expected payment sits at 15 Nov.
  • InsightThe payment method expires before future expected payment activity.
  • MeaningRelevant timing may deserve review. This is not a statement that the payment will fail.
03

Refund

  • DataA payment was collected.
  • ChangeA refund is recorded later.
  • InsightThe original payment amount no longer explains the current customer payment position.
  • MeaningThe payment history has changed.
04

Customer credit

  • DataCustomer credit exists.
  • ChangeA relevant upcoming payment exists.
  • InsightCustomer credit may be relevant to future supported payment activity.
  • MeaningThe future payment context changed.
05

Recurring

  • DataRelevant payment activity normally repeats.
  • ChangeUpcoming expected payment activity changes.
  • InsightThe recurring pattern changed.
  • MeaningMay deserve operational review.

The standard

A Useful Payment Insight Should Answer More Than "Something Changed."

01

What moved?

The event or the state that moved.

02

Why does it matter?

The relevant payment context around it.

03

What does it relate to?

The customer and the payment it belongs to.

04

What happens next?

The relevant future context.

05

Does this need review?

The attention signal, stated as a question rather than a verdict.

06

Who should decide?

The appropriate authorised person.

Insight should reduce interpretation work.

It should not hide the context that makes the signal understandable.

Why connected context helps

Payment Insight Gets Stronger When the Payment Lifecycle Is Connected.

Bonza Payments brings together established payment-management capabilities across the customer payment lifecycle. That creates broader context around a single payment event, which is what makes an interpretation of it possible at all.

A transaction can then be understood alongside the customer, the amount, the current payment position, the timing, post-payment activity, relevant future payment activity and operational attention — rather than on its own.

From activity to an attention-driven operating model

  1. Payment activity
  2. Payment management
  3. Receivables and timing
  4. Recurring and upcoming
  5. Refund and credit
  6. Payment-method context
  7. AI Payment Insights
  8. Payment Command Center
  9. Finance · Operations · Customer Service · Salesforce teams

The insight layer should sit on top of connected payment context, not isolated transaction data.

Explore Bonza Payments

The capabilities that supply the context

Keep reading

Explore Payment Insight Topics.

Quick answers

Payment Interpretation Questions, Answered Clearly.

What is a payment insight?

An interpretation, not a status.

A payment insight is relevant interpretation of payment data that helps users understand changes, timing, patterns or situations that may require attention. Payment intelligence is the broader practice of producing those interpretations from connected payment context.

What is the difference between payment data and payment insight?

Input versus interpretation.

Payment data records an event or state. Payment insight adds context that helps explain why the event or state may matter operationally. A payment signal is the specific change that an insight is built around.

Is an outstanding payment automatically a problem?

No.

An outstanding payment can exist before the relevant due date. Timing determines whether the item is not yet due, due or overdue, and only the last of those is an attention signal.

Does payment-method expiry mean the next payment will fail?

No.

Payment Method Expiry should be treated as a timing signal rather than proof that a future payment will fail. It tells you two dates are in conflict, which is worth reviewing and is not a prediction.

Is payment forecasting guaranteed cash?

No.

Bonza Payment Forecasting focuses on relevant expected customer payment activity. Expected payment activity does not guarantee collection, and it is not cash-flow, treasury or bank-balance forecasting.

Does AI make the financial decision?

No.

Bonza should be positioned as using payment insights to support human review and decision-making, not as an autonomous financial decision-maker. Bonza does not predict payment failure or customer default, and does not score customer credit.

Payment Insights FAQ

Interpreting Payment Activity, Answered.

What are payment insights?

Payment insights are interpretations of customer payment data that help users understand changes, timing, patterns and situations that may deserve attention. They are not an additional payment status; they are context around the statuses you already have.

How are payment insights different from payment reports?

A report presents payment data on request, usually for a period you choose. An insight starts from a change and explains why that change may matter now. A report can tell you the overdue total; an insight tells you that something moved into overdue since you last looked.

What is the difference between payment data and payment insight?

Payment data and payment insight are different. Payment data records the event or state, while payment insight adds context that helps explain why it may matter operationally.

Does AI Payment Insights automatically make financial decisions?

No. Bonza AI Payment Insights should be positioned as decision-support for human review rather than autonomous financial decision-making. Nothing is collected, refunded, credited, written off, rescheduled or sent to a customer on the strength of a signal alone.

Can payment insights show overdue and upcoming payments?

Yes, and the two are read differently. An overdue item is a present state that has passed its relevant due date; upcoming activity is expected rather than settled. Both can be surfaced for review, and the Due & Overdue Payments and Payment Forecasting pages cover each capability.

How does Payment Method Expiry become an insight?

By being compared with something. An expiry date on its own is a field on a record. Read against the next expected payment date, it becomes a timing relationship that may deserve review — which is the whole of the signal, and not a forecast of failure.

How do refunds affect payment insights?

A refund changes the customer payment position after collection, so the original collected amount stops being a complete description of where that customer stands. Kept against the original payment, it adjusts one story rather than creating a second, unrelated one.

How does customer credit affect payment context?

Recorded customer credit may be relevant to future supported payment activity, which is why it is most useful when read alongside what is expected next. Customer credit is recorded and managed within Bonza Payments and is not a wallet, stored cash, a bank balance or funds held by Bonza.

Can payment insights work across multiple payment gateways?

That is the reason the interpretation sits above the gateway layer rather than inside it. Provider-level transaction information is useful, but the business usually needs a reading across the wider customer payment lifecycle rather than one per configured provider.

What is the relationship between Payment Insights and the Payment Command Center?

The Bonza Payment Command Center provides a wider operational view, while payment insights help users interpret what within that payment activity may deserve attention.

Does Bonza predict payment failure or customer default?

No. Neither is claimed anywhere. Bonza surfaces recorded states, timing relationships and changes between them for human review. It does not score customer credit, predict default, predict payment failure or guarantee the accuracy of any signal.

Where can I read more around this topic?

The Resources Hub routes from a question to the capability that answers it, the Blog covers these concepts as editorial pieces, and Guides & eBooks sets out the long-form learning structure. This page is the interpretation layer between them.

See More Than the Payment Status. Understand What It Means.

See how Bonza Payments connects customer payment activity, receivables, recurring payments, refunds, credits, future payment context and relevant payment signals inside Salesforce.