Modern checkout, zero card data on your server
Donor Merchant embeds Stripe's Payment Element — the same payment UI used by some of the largest sites on the internet. Card numbers are typed into fields hosted by Stripe, inside the donor's browser. Your WordPress server never sees, transmits, or stores a card number, which keeps you in the simplest PCI compliance category (SAQ A).
Donors automatically see the payment methods that fit their device: cards everywhere, Apple Pay on Safari/iOS, Google Pay on Chrome/Android.
Engineered for trust, not just looks
- Totals are recomputed server-side. The charge amount is always recalculated from your settings on the server — a tampered browser can't change what gets charged.
- Completion is verified gateway-to-server. A donation is only marked complete after your server confirms the payment status with Stripe directly. Forged requests can't fake a gift.
- Signed webhooks. Stripe events (renewals, refunds, failures) are HMAC-verified with your signing secret and rejected if stale or tampered.
- Abuse protection. Per-IP rate limiting and a honeypot keep card-testing bots off your form.
Refunds and failures stay in sync
Refund a gift in the Stripe dashboard and the webhook marks the donation refunded in WordPress. Failed payments are flagged too, so your reports reflect reality, not wishful thinking.
What it costs
Nothing from us. Stripe charges its standard processing fee (typically 2.9% + 30¢ for U.S. cards), and with fee recovery your donors can cover that for you.