KindlyVote

Paid voting

• Paystack and Flutterwave, with webhook plus server-side verification
• The amount is always set on the server — the browser can never change the price
• Idempotent recording — a webhook and a browser callback can both fire without double-counting

Display and results

• [kvote_contest] — a responsive grid of contestants with vote buttons
• [kvote_leaderboard] — a ranked standings board with vote bars
• A mobile-friendly vote popup, and a Primary colour setting to match your site

Administration and audit

• A paginated Voting Logs screen — filter by status, voter email, and date range for a full audit trail
• Add or set a contestant’s vote count manually, recorded as an auditable adjustment
• A dashboard with live totals, revenue, and top contestants

KindlyVote is built on modern, secure, object-oriented foundations and is designed to scale to large events. For live real-time results, advanced analytics, and fully hosted elections, see KindlyVote Cloud at https://kindlyvote.com.

External services

This plugin relies on third-party payment and bot-protection services. None of them are contacted until you enable and configure that specific service in the plugin settings. If you run only free events with no CAPTCHA, the plugin makes no external connections.

Paystack (payment gateway)

• What it is and why: a payment gateway used to collect votes as payments on paid events.
• What is sent and when: when a voter chooses to pay, the plugin loads Paystack’s checkout script from js.paystack.co and sends the transaction details (amount, currency, a unique reference, and the voter’s email) to api.paystack.co to create and then verify the payment. Verification also happens server-to-server against api.paystack.co , and Paystack confirms payments back to your site via a signed webhook.
• Conditions: only on paid votes, and only if you have entered your Paystack API keys.
• Terms of service: https://paystack.com/terms
• Privacy policy: https://paystack.com/privacy/merchant

Flutterwave (payment gateway)

• What it is and why: a payment gateway used to collect votes as payments on paid events.
• What is sent and when: when a voter chooses to pay, the plugin loads Flutterwave’s checkout script from checkout.flutterwave.com and sends the transaction details (amount, currency, a unique reference, and the voter’s email) to Flutterwave. Verification happens server-to-server against api.flutterwave.com, and Flutterwave confirms payments back to your site via a signed webhook.
• Conditions: only on paid votes, and only if you have entered your Flutterwave API keys and selected Flutterwave as a gateway.
• Terms of service: https://flutterwave.com/terms
• Privacy policy: https://flutterwave.com/privacy-policy

Cloudflare Turnstile (optional CAPTCHA)

• What it is and why: a bot-protection challenge on the free vote form, used only if you enable Turnstile as your CAPTCHA provider.
• What is sent and when: when the vote form is shown, the challenge widget is loaded from challenges.cloudflare.com; on submit, the challenge token and the visitor’s IP are sent server-to-server to challenges.cloudflare.com/turnstile/v0/siteverify to confirm the visitor is human.
• Conditions: only on free-vote submissions, and only if Turnstile is configured.
• Terms of service: https://www.cloudflare.com/website-terms/
• Privacy policy: https://www.cloudflare.com/privacypolicy/

Google reCAPTCHA (optional CAPTCHA)

• What it is and why: a bot-protection challenge on the free vote form, used only if you enable reCAPTCHA as your CAPTCHA provider.
• What is sent and when: when the vote form is shown, the reCAPTCHA widget is loaded from www.google.com/recaptcha; on submit, the challenge token and the visitor’s IP are sent server-to-server to www.google.com/recaptcha/api/siteverify to confirm the visitor is human.
• Conditions: only on free-vote submissions, and only if reCAPTCHA is configured.
• Terms of service: https://policies.google.com/terms
• Privacy policy: https://policies.google.com/privacy