Accept donations and Orthodox prayer requests on parish, church, cathedral or monastery websites using your own Stripe or PayPal account.<\/p>\n\n
Manual ZIP: four translations. WordPress.org: standard language packs; English until translations are published.<\/p>\n\n
Requirements: WordPress 7.1+, PHP 8.4+, mbstring\/GD for local PDFs, HTTPS callbacks and working WP-Cron.<\/p>\n\n
Stripe is contacted only for the configured payment features. The plugin uses https:\/\/api.stripe.com for Checkout sessions, subscriptions\/cancellation, invoice payment identification and refund reconciliation. Requests contain API credentials, donor email, EUR amounts, service titles, internal\/public payment identifiers, billing interval and return URLs as applicable. Prayer names and comments are not sent when creating payments.<\/p>\n\n
Stripe collects card\/billing details on its hosted checkout. Signed webhooks return payment status and available payer information. The site owner supplies their API key and endpoint signing secret; the plugin author receives no payments or credentials.<\/p>\n\n
The plugin uses https:\/\/api-m.paypal.com (Live) or https:\/\/api-m.sandbox.paypal.com (Sandbox) for REST OAuth authentication, Orders v2 creation\/capture, webhook signature verification, products\/plans\/subscriptions and cancellation. Capture references can be verified using the payments API.<\/p>\n\n
Requests contain application credentials, EUR amounts, service titles, payment\/subscription identifiers, billing interval and return URLs as applicable. Signature verification sends the received webhook event and transmission headers back to PayPal. Prayer names and comments are not sent when creating payments. PayPal collects payer information on its hosted checkout and returns payment results and available payer details.<\/p>\n\n
The site stores prayer names\/comments, donor email\/name, WordPress account ownership, service selections, amounts, payment identifiers\/statuses, available billing\/contact details, timestamps, subscriptions, refunds and action history in its own database. Card numbers and security codes are not stored. Campaign reports publish aggregates only.<\/p>\n\n
Emails use wp_mail and can include names, comments and payer details. Empty recipient settings disable staff notifications, without an admin-email fallback. Failed notifications retry via WP-Cron. Acceptance does not guarantee Inbox delivery; a crash after acceptance can cause a retry.<\/p>\n\n
The plugin author receives no requests, keys, telemetry or payments. Site owners must restrict access, define retention and document processing in their privacy policy. Deactivation and uninstall do not automatically delete records or settings.<\/p>\n\n
Readable sources and GPL-compatible licenses are included in third-party-notices.txt. Code\/prayer slips are GPL-2.0-or-later. No build or runtime code download is required.<\/p>\n\n
Source: https:\/\/github.com\/VAtapin\/kloster-prayer\/tree\/main\/georg-kloster-orthodox-donations<\/p>\n\n\n
Stripe API keys: https:\/\/dashboard.stripe.com\/apikeys\nStripe webhook endpoints: https:\/\/dashboard.stripe.com\/webhooks\nUse snapshot events for your account, with matching test\/live credentials. Thin events are not supported.<\/p>\n\n
PayPal REST apps: https:\/\/developer.paypal.com\/dashboard\/applications\/\nUse a matching Client ID, Secret, Webhook ID and Sandbox\/Live environment. For testing, use a Sandbox Business seller and a separate Personal buyer. PayPal Webhooks Simulator events are not a substitute for a real Sandbox checkout.<\/p>\n\n
One-time events:\nStripe: checkout.session.completed, charge.refunded.\nPayPal: PAYMENT.CAPTURE.COMPLETED, PAYMENT.CAPTURE.REFUNDED.<\/p>\n\n
Additional recurring events:\nStripe: invoice.payment_succeeded, invoice.payment_failed, customer.subscription.created, customer.subscription.updated, customer.subscription.deleted.\nPayPal: PAYMENT.SALE.COMPLETED, PAYMENT.SALE.REFUNDED, BILLING.SUBSCRIPTION.CREATED, BILLING.SUBSCRIPTION.ACTIVATED, BILLING.SUBSCRIPTION.CANCELLED, BILLING.SUBSCRIPTION.EXPIRED, BILLING.SUBSCRIPTION.SUSPENDED, BILLING.SUBSCRIPTION.PAYMENT.FAILED.<\/p>\n\n
Only verified payment events count as income; approval and return URLs do not. Cancellation stops future billing after the provider acknowledges it and does not refund previous payments. Closing a campaign prevents new payments\/agreements but does not cancel existing agreements.<\/p>\n\n
WP-Cron prepares new PayPal plans in the background; retry shortly if requested. Empty secret fields retain saved values; replace them when changing account\/environment.<\/p>\n\n
Donation\/support forms accept campaign_id=\"1\" to allocate payments to an open, unexpired campaign. Amounts are EUR 0.50-999,999.99 with up to two decimal places. Confirmed partial refunds reduce received totals; fully refunded, failed and pending payments are excluded. Expenses are entered separately by staff with manage_options.<\/p>\n\n
Layouts: standard, compact, wide, two_columns, cards, minimal. header=\"no\" hides supported headings. Without lang, WordPress\/the language plugin selects the language. The admin guide lists parameters\/defaults. Editors preserve other translations. Guest payments are not linked to accounts by email.<\/p>\n\n\n
Yes. Disabled providers do not require credentials.<\/p><\/dd>\n
No. It checks configuration availability. Test real provider test\/Sandbox transactions before enabling Live.<\/p><\/dd>\n
No. Records and settings are retained. Site owners must manage retention and backups.<\/p><\/dd>\n
Update provider webhook\/return URLs after moving. An API-domain override must serve the same WordPress site over HTTPS.<\/p><\/dd>\n\n<\/dl>\n\n\n