Skip to main content
Released October 20, 2026. Surface Admin · 23 Checkout · 3 Portal · 2 Integrations · 6 API · 1

New

Build saved queries, dashboards, and visualizations, then snapshot or export results. Reporting respects your organization’s time zone.
A branded popup handles donor identification, payment methods, guest and recurring giving, and multi-language support. Publishable and secret keys control test and live modes; card details are tokenized. A dashboard configurator previews branding before launch.
Personalized giving summaries show each donor their year at a glance. Organizations configure which portal settings appear and what content is included.
A single row in a Batch Payment Import can now split a gift across multiple designations instead of requiring one row per fund.
Mapping rules marked as literal now send the configured fixed value to Neon instead of attempting a data lookup. Previously the literal flag was ignored.
Dashboard users can sign in with their Google or Apple account. Existing email-verified accounts link automatically.
Donations, recurring plans, and event registrations now store the donor’s intended amount in their selected currency alongside the converted settlement amount and conversion rate.

Changed

Behavior that worked one way before this release and works another way now.
Changing a recurring plan’s total amount now proportionally adjusts each designation’s share. Previously, allocations stayed frozen at their original amounts after a total change.
Merging two donor records now moves pledges, addresses, household memberships, CRM identifiers, and merge history to the master record alongside the data that already transferred. Duplicate pivot rows are no longer created.
Replacing a step in a live journey now prompts for an explicit supporter destination. Supporters on the removed step are relocated via background jobs rather than silently dropped.
Date-only fields in filters, forms, detail pages, and tables no longer shift by a day for users west of UTC. Date helpers have been consolidated.
A failed Finix refund attempt no longer marks the donation as refunded, and unrecognized reversal subtypes are handled explicitly instead of ignored.
Campaign revenue snapshots now count recurring plans created. Previously the count showed zero.
A CRM pull that encounters repeated errors now stops itself instead of retrying indefinitely. Never-synced integrations also receive frequency limits.
Accepting a portal household invitation now moves the member into the inviter’s household with a confirmation step, instead of leaving the member in two households.
Journey analytics lists and cached totals now show data for the journey being viewed, not a stale or mismatched set.

Improved

HubSpot Deals now transition to a Refunded stage on refund. Custom-field mapping rules write from WeGive to HubSpot as well as the reverse. Deal merge and deletion webhooks are handled. The optional Payment mirror has been removed.
Organization and contact names stay intact during review. Company supporters are correctly identified. Clearing a match returns the row to Needs Review, and exact-email matching is more reliable.
Terminal recurring-plan statuses — natural endings, cancellations, and restores — now reliably sync to connected CRM systems, with historical remediation for previously missed updates.
The donor portal payment history now displays each transaction’s status, including failed donations that were previously hidden or shown incorrectly.
Payment detail pages now show linked payout items. Fee fields correctly show zero for offline and synchronized donations instead of displaying the full donation amount.
Returning donors switching accounts or selecting a saved payment method at checkout encounter fewer errors.
The Implement Element modal now includes a domain selector so admins can pick which domain hosts the checkout.
The supporter search in audience preview remains interactive while results load, and duplicating an email section with conditional content no longer produces blank messages.
Opening an archived record in the dashboard now shows its detail page with a restore option instead of returning a Not Found error.
DonorDirect imports can now determine success, processing, failed, and refunded outcomes from deposit and reversal data.
The processor’s failure code and reason message are now saved on failed transactions and available for Salesforce field mapping.

Fixed

Signing up as a company during checkout now stores contact details correctly so the donation receipt reaches the right address.
Multiply-by-precision settings now appear and apply only to Number-type custom fields, preserving text values that happen to look numeric.
Saving a journey or message rule with an incomplete row now shows a validation error instead of a server error or a partial record.
Submitting a checkout more than once no longer creates duplicate event registration records.
An eCheck transaction that settles and funds after an initial failure can now be reconciled to Succeeded status instead of staying stuck in Processing.
Saving an impact card with no audience rules now correctly leaves the audience empty instead of attaching every supporter in the organization.
Long text on the Salesforce integration page no longer bleeds outside the card boundary.