​

Giving distinguishes received gifts from payment attempts

Church finance teams can now open Giving as its own root product instead of looking for Donations inside Church Management. The existing overview, gifts, recurring gifts, funds, public links, and payment-provider workflows remain in place.

​

Received money stays trustworthy

Giving now distinguishes received gifts from pending, failed, and cancelled payment attempts. Only received gifts increase overview totals, averages, trends, payment-method summaries, donor summaries, dashboard giving totals, and ordinary exports. The Gifts list still keeps other attempts available for support and follow-up. Each row and detail view displays its status, and staff can filter the list to find a particular state.

​

Financial history is protected

A received gift can no longer be edited or deleted in place. This prevents a settled financial record from quietly changing after it has already appeared in reporting. Authorized staff can instead record a reasoned correction or reversal, and refunds or disputes appear as immutable audit entries. General gifts and Outreach Campaign cash support now appear in one searchable staff ledger with their source still visible. Each record separates the gift, gross payment, fees, refunds, disputes, and net settlement, while granular permissions control donor details, exports, adjustments, reconciliation, and provider settings. Read the Giving guide for the current staff workflow.

​

Receipts, recovery, and finance controls

Members can review gift acknowledgements and their recurring gifts in one place. They can pause or resume a recurring gift and change its future amount, frequency, or fund without changing the original gift. Failed schedules now show clear retry and action-required states instead of silently disappearing. Stripe checkout now records when a member closes the payment sheet, preserves the gift’s fee breakdown when a declined card is retried, and accepts a later successful confirmation for the same checkout. Refunds and disputes now keep acknowledgements aligned with the remaining received amount, while an acknowledgement with no remaining received amount is voided and cannot be resent as current. Flutterwave v3 checkout now records the donor’s gross charge, provider fee, settled amount, and provider reference from the verified transaction. Signed webhooks and callback-first confirmations can safely arrive more than once, and a declined or closed checkout stays available for support without increasing received-gift totals. Recurring Flutterwave choices remain hidden until the church account is approved and enabled for automated tokenized card charges. PayPal hosted checkout now records when a member closes the approval screen and keeps PayPal’s processor fee separate from the platform fee in the gift breakdown. Connected churches with PayPal’s partner Subscriptions capability can now receive recurring general and campaign gifts. PayPal owns the schedule and retries, while Giving reconciles every charge and synchronizes pause, resume, cancellation, failure, and lifecycle status. Finance teams can prepare controlled manual-gift batches, match provider or bank deposits to received gifts, and export allocation and settlement details in a provider-neutral format. Corrections, fund closure, batch close, and reconciliation close now wait for a different authorized person before they take effect.

​

Statements and accounting handoff

Finance teams can issue period and year-end statements from received gifts, with separate totals for each currency. Churches control their jurisdiction, registration details, address, and legal wording, and year-end issuance stays off until those settings are deliberately enabled. Household statements require explicit authorization and an adult household contact. Members can privately download their issued statements or request another email. If a statement needs correction, a different authorized person reviews the new version while the earlier version remains in the financial history. Funds and reconciled deposits can now carry accounting codes and account names into the provider-neutral finance export, giving future accounting connections a stable mapping contract.

​

Safer ways to reach the giving page

Churches can prepare a general or active-fund link and download a QR image or standard NFC URI record for it. Both open the public giving page without starting a payment. Church-owned text-to-give keywords can reply through the signed Twilio inbox with a short-lived secure link. The text never creates or charges a gift, and it does not enroll the sender in marketing updates.

​

Campaign stewardship and impact

Churches can now add a capital, missions, or general classification to an existing Outreach Campaign, set a monetary goal, record its funding state and project phase, and decide deliberately whether received and pledged totals are public. Received progress counts settled gifts only. Members can record a monetary pledge without charging a payment method or scheduling an automatic payment. They can review settled-gift progress, choose or turn off email reminders, cancel a pledge, and—when authorized—include eligible household gifts. Giving toward a pledge remains a separate checkout. Church teams can publish reviewed campaign or fund updates and prepare an annual generosity report from settled gifts and reviewed content. Public reports do not include donor identities, and consent-confirmed stories remain private until review and publication. Members can also request a confidential conversation about stock, asset, or legacy giving. The inquiry flow does not collect asset values, account numbers, credentials, private keys, wills, or custody instructions.