Security Center

Built to protect the people who give.

Stripe-powered payments, bank-level encryption, and donor records that stay private to your church. Here is exactly how your data is handled.

Payments by Stripe

PCI DSS Level 1

AES-256 encryption

At rest

TLS everywhere

In transit

No card data stored

Ever

Payments

Stripe handles the money. We never touch the card.

TithePay doesn't process, route through, or warehouse payment credentials. Gifts are completed on Stripe, so the most sensitive data in the transaction never reaches us or your church office.

  • Every gift is entered on a Stripe-hosted checkout page — TithePay never sees or stores a card number, CVV, or bank login.
  • Stripe is certified to PCI Service Provider Level 1, the most stringent level in the payments industry. Your church stays out of PCI scope entirely.
  • Stripe runs fraud screening and card verification on every transaction before a gift is ever recorded.
  • Funds settle through your church's own Stripe account. TithePay never holds, pools, or moves your congregation's money.

What happens when a donor gives

  1. 1

    Donor enters details

    On Stripe's secure checkout — never on a TithePay form.

  2. 2

    Stripe encrypts and verifies

    Card tokenized, fraud screening applied.

  3. 3

    Gift settles to your church

    Straight into your church's connected bank account.

  4. 4

    You see a receipt, not a card

    Your dashboard records the gift amount, fund, and donor — never payment credentials.

Encryption

Bank-level encryption, at every layer.

The same standards financial institutions rely on protect your giving data — whether it is moving across the internet or sitting in storage.

In transit

Every page, form, and API call runs over TLS (HTTPS). Giving data moving between your donors, Stripe, and TithePay is encrypted end to end and cannot be read in transit.

At rest

Donor records, giving history, and church settings are stored encrypted with AES-256 — the same standard used by banks and payment networks.

In the browser

Payment fields are rendered by Stripe's own secure components, so card details are encrypted before they ever leave the donor's device.

Donor information

We treat giving records as confidential.

Your congregation's data belongs to your church

Donor names, emails, phone numbers, and giving history are visible only inside your church's own dashboard.

Access is enforced in the database

Records are separated per church by database-level access rules — not just hidden in the interface.

Donor portals require an emailed code

Donors reach their own giving history and tax receipts by requesting a one-time code sent to their email address.

We never sell or advertise against donor data

No data brokers, no ad networks, no resale. Donor information is used solely to run your church's giving.

Only what we need, for as long as we need it

We keep the minimum donor detail required for receipts, reporting, and giving history — nothing more.

Sensitive actions are logged

Administrative and automated actions require server-side verification and are recorded so they can be reviewed.

Questions about a specific control, or reporting something that looks wrong? Reach our team through the contact page and we will respond directly. Full policy details live in our Privacy and Terms pages.

Calm horizon at dawn

Giving your church can trust.

Launch a secure giving page in minutes — Stripe protection and encrypted donor records included.