Description
Fundolar adds a donation shortcode to WordPress and connects to Fundolar Central for payment processing. Configure Stripe, PayPal, Paystack, Flutterwave, Pesapal, PawaPay, Mobile Money (UG), and more in your Fundolar dashboard, then sync them to your site.
What you get
- Shortcode
[fundolar_donate]— place the donation form on any page or post. - Fundolar Central — connect with your site key to sync payment gateways from a hosted dashboard.
- Appearance — preset amounts, currency, form layouts, and brand colors.
- Dashboard widget and Transactions list with fee breakdown (gross, gateway fee, platform fee, net).
- Security — encrypted secret storage, capability checks, and nonces on sensitive actions.
Fees and net
Each donation records donor gross, estimated gateway fees, the Fundolar platform fee (default 3.5%), and net after both deductions.
Who this is for
Churches, nonprofits, creators, and anyone who needs donations on WordPress with Stripe, PayPal, and regional payment methods — without managing API keys inside WordPress.
Privacy
This plugin:
- Stores donation transactions in a custom database table (amounts, status, gateway metadata, and donor fields your form collects).
- Sends admin support requests from the in-dashboard help UI to info@fundolar.com when a site administrator submits the form.
- Communicates with payment processors and Fundolar Central as described under External services when those features are configured.
Consult your privacy policy and processor agreements for lawful bases and retention. Use WordPress privacy tools where applicable for donor personal data.
For each third-party API, what is sent, when, and links to terms and privacy policies, see External services above.
External services
This plugin connects to third-party services when accepting donations or syncing with Fundolar Central.
Fundolar Central
- What: Site registration, gateway sync, donation reporting, and owner dashboard.
- Where:
https://app.fundolar.com(or your configured Central host). - When data is sent: When you connect or sync under Settings → Payments, when donations are recorded, and during background sync tasks.
- Terms: https://fundolar.com/terms
- Privacy: https://fundolar.com/privacy
Stripe
Used to create and verify PaymentIntents for card donations and receive signed webhooks at /wp-json/fundolar/v1/webhooks/stripe.
- When data is sent: When a donor chooses Stripe and during payment status updates.
- Terms: https://stripe.com/legal
- Privacy: https://stripe.com/privacy
PayPal
- Where:
https://api-m.paypal.com(live) or sandbox equivalent. - When data is sent: When a donor pays with PayPal.
- Terms: https://www.paypal.com/us/webapps/mpp/ua/useragreement-full
- Privacy: https://www.paypal.com/us/webapps/mpp/ua/privacy-full
Paystack
- When data is sent: When a donor pays with Paystack.
- Terms: https://paystack.com/terms
- Privacy: https://paystack.com/privacy
Flutterwave
- When data is sent: When a donor pays with Flutterwave.
- Terms: https://flutterwave.com/us/terms
- Privacy: https://flutterwave.com/us/privacy-policy
Pesapal
- When data is sent: When a donor pays with Pesapal.
- Terms: https://www.pesapal.com/support/knowledge-base/terms-and-conditions
- Privacy: https://www.pesapal.com/support/knowledge-base/privacy-policy
Payoneer Checkout
- When data is sent: When a donor pays with Payoneer card fields.
- Terms: https://www.payoneer.com/legal/terms-of-service/
- Privacy: https://www.payoneer.com/legal/privacy-policy/
PawaPay
- Where:
https://api.pawapay.io(live) orhttps://api.sandbox.pawapay.io(sandbox). - When data is sent: When a donor pays with PawaPay, during checkout creation, and when the donor returns so the plugin can confirm the payment.
- Terms: https://pawapay.io
- Privacy: https://pawapay.io
MarzPay (Mobile Money UG)
- Where:
https://wallet.wearemarz.com - When data is sent: When a donor pays with Mobile Money (UG), during collection requests, status polling, and webhook callbacks.
- Terms: Contact MarzPay for current terms.
- Privacy: Contact MarzPay for current privacy policy.
Installation
Before you start
- WordPress 6.0 or newer and PHP 7.4+ (match the headers above; newer versions are recommended).
- TLS — your site should use HTTPS for production donations.
- Fundolar account — register at Fundolar Central and configure the payment methods you want to offer.
Install the plugin
- Upload the
fundolarfolder towp-content/plugins/, or upload the ZIP via Plugins → Add New → Upload Plugin. - Activate Fundolar under Plugins.
- Updates are delivered through the WordPress.org plugin directory (Dashboard → Updates).
- In the admin, open Fundolar → Settings (or follow any onboarding links shown).
Set up payments
- Open Fundolar → Settings → Payments.
- Paste your site key from Fundolar Central.
- Click Connect, then Sync gateways.
- Enable payment methods in your Fundolar dashboard if none appear after syncing.
Publish the form
- Add
[fundolar_donate]to a page or post and publish. Run a small test donation.
Optional: payment logos
- For branded logos on the form, add SVG (preferred) or PNG files to
wp-content/plugins/fundolar/resources/images/logos/using the filenames listed in the FAQ.
Uninstall
Deactivating removes scheduled hooks tied to the plugin. Deleting the plugin via WordPress runs uninstall.php, which removes plugin options and the custom transactions table — back up data first if you need historical exports.
FAQ
Do I need a Fundolar account?
Yes. Create a free account at Fundolar Central, configure payment gateways there, and connect your WordPress site with the site key under Fundolar → Settings → Payments.
How do I update Fundolar?
Updates are delivered through the WordPress.org plugin directory. When a new version is released, go to Dashboard → Updates or Plugins and click Update now.
Does the plugin collect personal data?
Donation records in your database may include donor email and name when the form collects them. Card data is handled by your payment processor. See Privacy below.
cURL error 6 / Could not resolve host
Your server cannot reach Fundolar Central. Confirm outbound HTTPS is allowed and that DNS resolves app.fundolar.com. Contact your host if the problem persists.
Where do I get payment logos?
Add SVG or PNG files under wp-content/plugins/fundolar/resources/images/logos/ with these filenames:
stripe.svg,paypal.svg,paystack.svg,flutterwave.svg,pesapal.svg,mobile-money-ug.svg,payoneer.svg
Screenshots
Changelog
1.5.9
- Stop sending USD ledger amounts as the payment currency when syncing Mobile Money (UG) or M-Pesa donations to Fundolar Central.
- Skip Central amount reconcile when the local receipt amount is missing or unsafe for those gateways.
1.5.8
- Show every PawaPay country in the donation form, not only the countries that use the current currency.
1.5.7
- Load the PawaPay country list for logged-in visitors without a cookie check error.
1.5.6
- Show a country and phone number when a donor chooses PawaPay, then send a PIN prompt to that phone.
1.5.5
- Sync PawaPay from Fundolar Central and mark it active when the API key is saved there.
- Start PawaPay hosted checkouts for the currencies enabled on the PawaPay account.
1.5.4
- WordPress dashboard totals use net after gateway and platform fees (not donor gross).
1.5.3
- Fix fatal activation error caused by a corrupted PHP open tag in the payments bootstrap.
- Single WordPress.org distribution: no custom plugin updater; updates via WordPress.org only.
- Net amount deducts gateway fees then platform fee before display.
1.5.2
- Net amount now deducts gateway fees and the Fundolar platform fee (gross → gateway fee → platform fee → net).
- Transactions list shows gateway fee beside platform fee; existing rows are backfilled on update.
1.5.1
- Security: validate donation return URLs with wp_validate_redirect (blocks open redirects).
- Security: authenticate MarzPay webhooks with a per-site token; rate-limit donation REST endpoints.
- Security: encrypt Central API keys at rest; require OpenSSL for secret storage (no plaintext fallback).
- Security: allowlist Fundolar Central and update package hosts; optional SHA-256 package integrity check.
1.5.0
- Reliably record successful Stripe and PayPal donations in WordPress and Fundolar Central.
- Preserve platform donation ids when updating PayPal transaction meta.
- Re-create / upsert Central donation records when status sync runs without a prior create.
- Hourly resync of completed donations that never linked to Central.
1.4.0
- Fundolar.com distribution: payments are managed exclusively through Fundolar Central (own API key fields removed from Settings).
- Updated admin UI, how-to guide, form messages, and notices for a Central-only setup.
1.3.20
- WordPress.org review response: explicitly list all external service domains in readme.
- Settings save uses an allowlisted, sanitized field set (no raw $_POST pass-through).
- Donation REST route detection no longer reads $_GET[‘rest_route’].
- WordPress.org package excludes plugins_api updater code and does not mutate active_plugins.
1.3.19
- Add Payoneer Checkout card payments beside Stripe for donors (embedded card fields + hosted fallback).
1.3.18
- WordPress.org review: document PayPal api-m and MarzPay (wallet.wearemarz.com) with terms/privacy links.
- Remove custom plugins_api update hooks on WordPress.org builds; stop auto-activating/deactivating other plugins.
- Replace WP_PLUGIN_DIR hardcoding with plugin_dir_path-based paths.
- Add nonce checks for gateway return URLs and OAuth returns; tighten MarzPay webhook verification via API re-check.
- Sanitize admin settings POST input and REST route detection inputs.







