November 9, 2026 — TouchPoint Giving Updates ============================================ .. note:: This release focuses on **TouchPoint Giving**. Fraud and card-testing checks now run before a payment is charged instead of after, declined payments now appear on the Transactions page, and deposits now reconcile to their batches even when a payment or refund never made it into TouchPoint. Alerts about money now go to your Finance staff instead of your general admin address. It also includes fixes for Apple Pay and Google Pay on giving pages and for saving TouchPoint gateway accounts on the Payment Gateways page. Giving — TouchPoint Giving Payment Checks ----------------------------------------- .. release-notes:: - New: Declined TouchPoint Giving payments now appear on the Transactions page with a status of Failed and the reason the payment was declined, as declines from other payment gateways always have. This includes staff-assisted registration payments, and each declined attempt shows the giving page or involvement it came from - Change: When using the new payment gateway, the checks that protect your giving pages and registration payments now run before a TouchPoint Giving payment is charged - Change: When verifing billing addresses in online giving, a TouchPoint Giving card or bank account gift whose billing address cannot be verified is now refused before it is charged, with the existing "Invalid billing address" message. Wallet payments remain exempt - Change: The billing name the donor enters is now always sent with a TouchPoint Giving payment, whatever order the donor fills in the form, and payments from donors who were not signed in are now labeled with the person TouchPoint recorded the gift to. This lets TouchPoint support match a payment in the payment processor's records to the gift in your database - Change: When **Enable Failed Transaction Limit** (Settings → Finance → Online Giving) is on, declined TouchPoint Giving payments, including registration payments, now count toward the limit, so someone repeatedly testing cards is blocked from starting another payment once the limit is reached. The limit uses your existing **FailedConsecutiveGiftLockout**, **Failed Transaction Time Frame**, **Failed Transaction Block Time** and **Failed Transaction Ignored IPs** settings. TouchPoint support is also alerted when repeated declines reach your limit within a single payment session. With the setting off, nothing is counted or blocked, as before - Fix: The failed transaction limit now counts failures against a signed-in person's user account as well as their IP address, so a signed-in person who changes networks is still blocked; previously only the IP address count worked. This applies to every payment gateway - Fix: A TouchPoint Giving payment is now confirmed with the payment processor before it is recorded, and a payment that has already been recorded cannot be recorded a second time - Fix: A TouchPoint Giving gift from a donor who is not signed in and cannot be matched to a person, such as a wallet payment that supplies no name, is now recorded without a person for your finance staff to assign, and the donor sees a successful gift. Previously the donor was charged but shown an error, and no gift was recorded Giving — TouchPoint Giving Recurring Gifts ------------------------------------------ .. release-notes:: - Change: Deleting a saved TouchPoint Giving payment method, or purging a person who has one, now also deactivates the payment method with the payment processor - Fix: A TouchPoint Giving recurring gift whose nightly charge fails with an error from the payment processor, such as a card the processor has deactivated, is now handled like a decline: the failed transaction is recorded, the donor and your finance staff get the usual failure emails, a Failed Gift task is created where enabled, and the gift's next date is calculated. Previously the gift stopped running permanently, and the donor's other recurring gifts were skipped that night - Fix: A TouchPoint Giving recurring charge that timed out but went through at the payment processor is now recorded as the successful gift it was, instead of as a decline Finance — TouchPoint Giving Deposits and Batches ------------------------------------------------ .. release-notes:: - New: A payment that appears in a TouchPoint Giving deposit but was never recorded in TouchPoint, for example because the donor's browser lost its connection after the card was charged, is now recorded with a gift in that deposit's batch, so the batch count and total match the deposit. The gift goes to the giving page's fund when the page has a single fund, to your church's default fund otherwise, and to the Non-contribution fund for a registration payment; it is assigned to the giver when TouchPoint knows who made it and is left unassigned otherwise. No registration is created. Your finance staff receive a **TouchPoint Giving Unrecorded Payment Alert** naming the fund and batch, so the gift can be corrected rather than entered a second time - New: A refund made outside TouchPoint, or one in a TouchPoint Giving deposit with no matching reversal, is now recorded as a reversal against the original gift. When TouchPoint has no record of the original payment, a negative gift is added to the deposit's batch and your finance staff receive a **TouchPoint Giving Unrecorded Refund Alert**. Previously these refunds were not recorded, and the donor's contribution stayed at the full amount - New: **Retrieve Batch Data** (Administration → Batch Actions → Retrieve Batch Data) now brings in TouchPoint Giving deposits for the date range you enter, and a scheduled check of the past week does the same automatically. A deposit TouchPoint missed no longer leaves its payments in the Pending batches, and deposits already brought in are skipped - Fix: TouchPoint Giving deposit batches are now created with your church's default fund and the same creator as batches from other payment gateways, and the "-ADJ" reversal batch now has a source and your church's default fund, so it appears in batch searches and reports filtered by source. Existing batches are not changed - Fix: The nightly batch sync and **Retrieve Batch Data** no longer stop for every payment gateway when a TouchPoint Giving account has not finished setup; that account is skipped and the other gateways' settlement data is still retrieved Finance — TouchPoint Giving Alerts ---------------------------------- .. release-notes:: - Change: TouchPoint Giving alerts about money - a payment or refund held for review, a refund reversed by the payment processor, chargebacks, and failed deposits - now go to every user with the **Finance** role who has an email address, excluding TouchPoint staff accounts, instead of to your **AdminMail** address. When no such user exists, they go to **AdminMail** as before. These alerts are now sent even when **AdminMail** is blank, as long as a Finance user can receive them - Change: TouchPoint Giving merchant account alerts (merchant application and merchant status alerts) now go to your church's finance manager as well as your **AdminMail** address. When no finance manager is set, the first **Finance** user by last name receives them; TouchPoint staff accounts are never used - Change: TouchPoint's finance team is now notified, along with your Finance staff, when a TouchPoint Giving payment or refund is held for review, so TouchPoint can work with the payment processor to release it sooner - Fix: TouchPoint Giving alert and donor email subjects, two merchant alert email bodies, and the **Merchant ID** tooltip on the TouchPoint Giving Configuration page now show a dash (—) instead of the characters "—" Giving — Apple Pay and Google Pay --------------------------------- .. release-notes:: - Fix: Apple Pay gifts and registration payments from someone who is not signed in no longer fail with "Email required." The email address and phone number are now taken from the Apple Pay sheet. If the giver chooses a contact with no email address or phone number, the Apple Pay sheet asks them to choose a different contact or use a different payment method - Fix: The Apple Pay and Google Pay buttons on a giving page now appear the first time the **One Time** tab is shown, wherever the browser supports them. Previously a button could stay hidden until the donor switched between **One Time** and **Recurring** several times, and after switching back, clicking Google Pay could do nothing Administration — Payment Gateways --------------------------------- .. release-notes:: - Fix: Saving an existing **TouchPoint** gateway account on the Payment Gateways page (Administration → Setup → Payment Gateways), or assigning it to another payment process, no longer erases the account's credentials. Previously this stopped online payments with the error "UserId setting not found, which is required for TouchPoint." An account that was already erased now opens with its credential fields so they can be entered again and saved