October 12, 2026 — Connect Card Capture, TouchPoint Giving, and Integration API Updates

Note

This release introduces Connect Card, a new way to turn paper connect cards into people records: upload photos or PDFs of your cards, review what TouchPoint read from each one, and add the person or update the person who is already in your database. It also expands the wallet payments offered through TouchPoint Giving and adds several Integration API endpoints for phone and texting partners.

People — Connect Card

  • New Connect Card (People → Connect Card) lets staff capture paper connect cards by uploading photos or PDFs, review the information read from each card, and either add a new person to TouchPoint or update a person who is already there; it is available to users with the Access role once Connect Card has been turned on for your church

  • New On the Capture tab, choose a card template, an involvement and one of that involvement’s recent meetings, then drag in or browse for image files or PDFs; each page of a multi-page PDF becomes its own card, and the involvement, meeting and template stay attached to each card

  • New Quick Capture, opened from the Capture tab, is an upload-only page sized for a welcome desk tablet or phone, so a volunteer can capture cards without seeing the rest of Connect Card; a Quick Capture link that includes ?involvementId= or ?meetingId= opens with that involvement or meeting already selected

  • New The Capture Queue tab lists every captured card with its status (Needs Review, Extracting, Failed or Reviewed), involvement, capture date and template; it opens to the cards that still need attention, can be filtered by name, source, involvement, capture date, template and status, and lets you resubmit or delete selected cards in bulk

  • New Reviewing a card shows the card image beside the values read from it, marks values TouchPoint was unsure of so you know what to check, and lets you correct the name, email, phone numbers, address, date of birth, the template’s extra values and any prayer request before importing

  • New Before a card is imported, Connect Card looks for people already in TouchPoint who may match it; when there are possible matches you must choose either the person to update or Create new person instead, and each match’s name links to their profile so you can confirm you picked the right person

  • New Updating an existing person fills in the values from the card without erasing information the card left blank, and does not change the person’s Origin or Entry Point; a new person is created with an Origin of Connect Card and, when the card was captured for an involvement, that involvement’s Entry Point

  • New The address on a card is checked before import, letting you choose between the address as written and a corrected address; a card must have a first and last name to be imported, and a card that creates a new person must also have an email address or phone number

  • New Once a card is imported it moves to Reviewed, opens read-only, and links to the person it created or updated

  • New The Templates tab describes each style of card your church prints — which person fields and which standard extra values it collects; build a template from scratch or upload a blank card and let TouchPoint propose the fields, create a new standard extra value from within the template editor, and duplicate or deactivate templates

Giving — TouchPoint Giving

  • New TouchPoint Giving now offers Google Pay, alongside Apple Pay, PayPal and Venmo

API

  • New GET /v1/Integration/Settings returns the Integration call, text and email keyword settings and the default campus and entry point, along with whether each one is configured, so a phone or texting partner can confirm the setup before logging calls or messages; requires the Edit or Admin role and accepts a Personal Access Token

  • New GET /v1/Integration/Roster returns a caller ID roster of current people — names, phone numbers, email address, picture and Do Not Call flag, with no giving, attendance, address or membership data — with paging and a modifiedDate filter for retrieving only changes since a given date; archived and deceased people are never returned; requires the Access role and accepts a Personal Access Token

  • New GET /v1/Account/Current returns the user, username, person and name that the credential making the request belongs to

  • Change The Integration endpoints now publish complete response schemas in the API documentation, including the taskNoteId returned when a call, text message or email is logged and the {"error": "..."} body returned with validation errors

  • Change Creating a Personal Access Token with an expiration date that is not in the future is now rejected

  • Fix Personal Access Tokens now stop working once their expiration date is reached, for both the API and the MCP server; a token stops working at the start of its expiration date in your church’s time zone, and tokens that are already past their expiration date stop working when this release is installed

  • Fix GET /v1/Integration/Contacts now returns each person’s memberStatus instead of always returning null, and also returns a new memberStatusId