Keep Every Supporter Payment Connected to the Relationship Behind It.

By keeping the payment operation in the same environment as the relationship. Bonza Payments is Salesforce-native, so relevant one-time and recurring payment activity, receivables, refunds, customer credits and upcoming payment visibility stay associated with the Salesforce constituent or customer record rather than living in a gateway portal, a recurring-payment process and a spreadsheet separately.

Yes, and together on the same person. A relevant one-time or ad hoc payment and a recurring arrangement can run on the same supporter or customer, both visible in one payment position. An amount from one motion can be outstanding while the other keeps collecting on schedule, and both facts stay in the same place.

Yes, and it treats them as three different operational states rather than one unpaid figure. Outstanding means still expected, due means expected now, and overdue means past the expected date. Timing is what distinguishes what is still expected from what may require review, and a person decides what happens next.

Yes. Bonza Payment Forecasting gives forward visibility into relevant expected customer payment activity, including upcoming payments and recurring payment activity. It should not be positioned as fundraising forecasting, donation forecasting, grant forecasting, revenue forecasting, cash-flow forecasting or treasury forecasting, and expected payment activity is not guaranteed collection.

Yes. A refund stays attached to the payment it came from, so the collected figure remains explainable rather than simply lower. Customer credit is available credit recorded and managed within Bonza Payments, available for relevant future payment use where supported. It is not a supporter wallet, a donor wallet, a cash balance, stored funds or stored value, and Bonza does not hold anyone's money.

Yes. Bonza supports multiple configured gateways, including a configured default and selection of another configured gateway where a scenario calls for it, while keeping a broader payment-management layer in Salesforce. There is no smart routing, least-cost routing, automatic failover, automatic retry through another gateway, settlement reconciliation or token portability, and provider capabilities are not interchangeable.

Where a nonprofit already uses Salesforce Experience Cloud for relevant customer or constituent experiences, Bonza can support connected payment journeys inside that Salesforce environment, with payment activity flowing back to Salesforce. Bonza does not provide nonprofit community management, donor portal management, constituent authentication, campaign management, grant portal functionality or volunteer portal functionality.

No, and no replacement claim is made. Bonza focuses on the payment-management layer. Where an organization uses Salesforce for constituent relationships, Bonza can manage relevant payment activity around those relationships — the relationship record stays where it is, and Bonza adds the payment lifecycle beside it.

No. Bonza should not be positioned as a fundraising or campaign-management platform, and it does not manage donations, gifts, pledges, campaigns, appeals or peer-to-peer and event fundraising. It manages relevant payment activity. Whether a given payment is a donation is a question for the organization's own relationship and fundraising systems, not for Bonza.

No to both. Grant management, grant accounting and grant portals are not Bonza capabilities, and neither is donor management, a donor database, donor segmentation or donor scoring. Bonza manages the payment lifecycle around relationships that live in the organization's CRM.

No. Bonza manages the customer payment lifecycle, not the general ledger or the accounting close. It is not an accounting platform, an ERP, fund accounting, nonprofit accounting, grant accounting or a revenue-recognition system.

Recurring payment management covers the payment schedule, the payment event, its status, the next payment, any outstanding amount, payment method context and payment history. Fundraising or membership logic may determine membership status, supporter segmentation, campaigns, program relationships, benefits, eligibility and communications — none of which Bonza owns. AI Payment Insights sits only on the payment side: it surfaces changes such as relevant payments moving into overdue status, expected recurring activity changing, or a payment method approaching expiry before a future payment, then hands those to a person. There is no donor propensity scoring, donation likelihood, retention or churn prediction, major-gift prediction, fundraising recommendation engine, automatic supporter outreach or autonomous financial action.