Billing Updates: Cards, Receipts, Emails, and Primary Contact Changes
Use this SOP whenever a church's billing details change: a new card, a repeat failed payment, a new email address, a new receipt recipient, or a whole new primary contact.
Spiffy is the source of truth for billing. Always start in Spiffy and finish by confirming Spiffy matches. The saved card details themselves live in Stripe, so you will jump into Stripe to fix cards, and ChargeDesk still needs to match for receipts and alerts.
1. Card Updated Notification
Run this any time you get a "card updated" notification: a routine update, a PayPal-to-card switch, or a retry after a failed or past-due payment. Goal: Stripe has the right default card, Spiffy matches it, and no stale cards remain. Video: Card update walkthrough
- Identify the scenario. Proactive update, PayPal-to-card switch, or update after a failed/past-due payment.
- Find the customer in Spiffy. Search by email (or account name), open the customer, and open their Grow account subscription to see payment status. Confirm whether a payment failed or was retried and whether the card change went through.
- Jump to Stripe. From the most recent payment in Spiffy, click View Payment.
- Set the correct default card. On the Stripe customer page, find the card that succeeded on the latest payment (or the new card for a proactive update, after checking its expiration). Click the three dots and choose Set as default. Confirm it shows as default.
- Remove stale cards from Stripe. Only after the correct default is set, remove invalid or old cards so Stripe cannot fall back to them. Ideally leave only the default. If a card expires before the next billing cycle, consider removing it now.
- Sync Spiffy. In Spiffy, open View Customer and remove any outdated card info so it matches Stripe.
- Close it out. Mark the task complete. If you have several, finish each one fully before starting the next. If you were unsure about anything, leave a note on the account.
2. Customer Updated Their Card but Payment Still Fails
Usually the new card is not set as the default, so Stripe (via Spiffy) keeps charging the old card.
- Log in to Stripe and find the customer.
- Set the new card as the default payment method.
- Confirm Spiffy shows the same card.
- If payments keep failing after the correct default is set, or Stripe and Spiffy will not sync, escalate to your team lead instead of repeating the steps.
3. Change Who Gets Receipts
Video: 90-second walkthrough
- Copy the new email address.
- Open the member's profile in the ChargeDesk sidebar. In Help Scout the right account usually appears automatically. In the ChargeDesk extension, search the primary contact's email.
- Click Edit. Under email, choose Yes, but specify emails.
- Enter the receipt recipient in the Email To box.
- Scroll down and click Save Customer.
- Reply to the customer to let them know they are all set.
4. Update a Contact's Email (Same Person)
If they are the primary contact for billing or setup
Video: Primary contact email update
- Confirm which contact is the primary contact on the account.
- In WordPress, find the user by name, change the email to the new address, and keep the username unchanged.
- Update the email in Spiffy.
- Update the email in Stripe and confirm it syncs to ChargeDesk. Keep the old email in ChargeDesk for reference if useful.
- Update the contact and account-level information in the software (the church sub-account and the church profile).
- Do a final review of every system you touched.
If they are not the billing or setup contact
Video: Team member email update
- Confirm the current and new email from the conversation.
- In WordPress, check whether the new email already exists. If not, update the username (most important), nickname, and email, then save.
- Check whether this person is connected to Spiffy or Stripe. If not, no billing changes are needed.
- Test that they can log in with the new email. Send a magic login link if needed.
- Email them to confirm the change, including the magic link.
5. Transfer the Primary Contact to a New Person
When a new admin takes over billing or a pastor transitions out, update every system in this order so nothing gets missed.
- Verify the new contact first. Get the new person's full name, email, and title from a reliable source (the church or the requester). Confirm the direction (old to new) and the church account. Do not proceed on a guess.
- Spiffy: change the customer name to the new contact, save, and confirm.
- Stripe: from Spiffy, click View Payment, edit the Stripe customer's name and role/title (for example, Church Administrator), save, and verify.
- ChargeDesk: remove the old contact's email if it is no longer valid. Leave a shared phone number alone unless it is clearly the old contact's. If ChargeDesk will not let you change the display name, update what you can and note it.
- Former contact left the church? Apply DND on all channels. Retaining the record is usually safer than deleting it. Check with your lead if unsure.
- GHL Settings and Staff: make sure the former contact is not still an active staff user. Remove or deactivate them if so.
- Custom Values: search for the former contact's name or title and replace each one, including sender fields. Use the new person's real title.
- Business Profile: replace the former contact's name and save.
- Set the new contact as Primary Point of Contact.
- Final pass: recheck Spiffy, Stripe, ChargeDesk, GHL staff, Custom Values, and Business Profile. Custom Values and Business Profile are the easiest to miss.
Confirmation note template: "Confirmed: [New Contact Name] is now the primary point of contact on [Church Name]'s account across billing and account systems. [Former Contact Name] has been updated or removed as needed."
If something will not update or contact info conflicts across systems, escalate to your team lead before marking it complete, and document what is done and what is outstanding.