Tinwell – Charity Donation Platform

By nebuladesign

0+ active installationsVersion 3.0.0

Donation forms, regular giving, campaigns and Gift Aid declarations for UK charities, with donor data protected by default.

Description

Tinwell is a donation platform for charities. Build donation forms, take one-off and regular card gifts through your own Stripe account, run campaigns with live totals, and keep every Gift Aid declaration HMRC asks you to hold — without paying a platform fee on any donation.

Tinwell is built for UK charities. For now it takes donations in pounds sterling (GBP, £) only, and its Gift Aid features follow HMRC’s rules.

Tinwell treats donor data as something to protect, not a feature to sell. Everything that keeps it safe is included in the free plugin.

Taking donations

  • Donation form block and shortcode, built in a drag-and-drop Form Builder. Unlimited forms, your colours, preview and duplicate.
  • Stripe with your own keys: one-off and regular card gifts. Money goes straight to your Stripe account.
  • Testing mode to rehearse with keys from a Stripe sandbox before going live.
  • Card-testing defences, submission checks and rate limits, so your form is never a tool for fraudsters.
  • Refunds and disputes reflected in your totals and receipts automatically.

Running your fundraising

  • Dashboard with headline figures and recent gifts.
  • Dark mode for the whole admin, switched from the top bar.
  • Analytics for any date range: headline figures, giving over time, payment methods, gift sizes, one-off against regular giving, Gift Aid and your top donors.
  • Donations and donors: search, detail, resend receipts, cancel regular gifts and consent status.
  • Campaigns with goals and live raised totals, plus a Progress Bar block.
  • Emails in your own voice: thank-you, receipt, refund and new-donation emails, with an editor.
  • Gift Aid declarations captured on the form and recorded against every gift, and a Gift Aid page listing every declaration with totals, search, filters and which gifts are claimed.

Protecting donor data (all included)

  • Encryption of donor details at rest, with key rotation.
  • Roles and step-up authentication for sensitive actions.
  • A security onboarding wizard that must be completed before going live.
  • Tamper-evident access and audit logs, an incident kill switch, a self-integrity check and security headers.
  • Anonymisation and erasure, wired into the WordPress personal data exporter and eraser.

Tinwell Pro

Growing charities can add Tinwell Pro: Direct Debit through GoCardless, CRM sync with Donorfy, Beacon and Salesforce, email marketing with Mailchimp and EmailOctopus, a donor portal (a passwordless page where donors see their giving history, download receipts, manage regular gifts and change their contact preferences), CSV exports of donations and donors, fund pots within campaigns, the Gift Aid claims workflow (exporting the HMRC claim schedule, for all donors or one, and marking gifts as claimed), more analytics (period comparison with a PDF report, smart insights, campaign performance, form conversion, giving by hour and an activity heatmap), donation maps, donor retention tools, campaign scheduling by start and end date, more campaign components (Donate Buttons and Totaliser among them), gifts on behalf of a company with a Companies page, donation comments, Donor Access (hand donor data to a named Donation Manager, who approves time-limited access for the rest of your team), tribute gifts, an impact thank-you email, an address lookup field, campaign components from your theme’s tinwell-blocks folder, API tokens and headless mode. Tinwell works fully without it.

External services

Tinwell connects to Stripe, and to GoCardless only when Tinwell Pro is installed and its Direct Debit is switched on. It contacts no service run by Tinwell or its developer, and sends nothing else anywhere.

Stripe — card payments.
Stripe.js is loaded from js.stripe.com on pages that show a donation form, and card details go from the donor’s browser straight to Stripe; they never touch your server. When a donor gives, your site calls the Stripe API (api.stripe.com) with your own secret key to create the payment or regular gift, to check its state when Stripe reports a change to it, and to refund or cancel one. Stripe sends your site webhooks about those payments. The data sent is what the payment needs, such as the amount, currency, the donor’s name and email address, and references back to the donation.
Stripe terms: https://stripe.com/legal/ssa — privacy policy: https://stripe.com/privacy

GoCardless — Direct Debit, only with Tinwell Pro.
When Tinwell Pro is installed and Direct Debit is switched on, a donor who chooses Direct Debit is sent from the form to GoCardless’s own page (pay.gocardless.com, or pay-sandbox.gocardless.com in test mode) to set up the mandate, and your site calls the GoCardless API (api.gocardless.com, or api-sandbox.gocardless.com in test mode) with your own access token to create and manage the mandate, its payments and the regular gift. GoCardless sends your site webhooks about them. The data sent is what the Direct Debit needs: the amount, the donor’s name, email and address, and references back to the donation; bank details go from the donor straight to GoCardless. Without Tinwell Pro, Tinwell never contacts GoCardless.
GoCardless terms: https://gocardless.com/legal/merchants — privacy policy: https://gocardless.com/privacy/payers

REST API

Tinwell exposes REST endpoints under /wp-json/tinwell/v1.

Authentication
* Admin endpoints require a logged-in WordPress user with the right Tinwell capability (cookie and REST nonce in wp-admin).
* The free plugin accepts no API tokens or other server-to-server credentials. API tokens are part of Tinwell Pro.
* The public endpoints are the donation form’s own (submitting a gift and its checks, rate limited) and the payment providers’ webhooks, which are verified by their signature.

Error Responses
* 401 Unauthorized: missing or invalid credentials
* 403 Forbidden: authenticated but lacks permission
* 429 Too Many Requests: rate limit reached
* Responses include X-Correlation-Id for troubleshooting

Source code

The JavaScript and CSS in the build folder are compiled. Their uncompiled source ships with the plugin, in the src folder, together with the build tools: package.json lists them (the build runs on @wordpress/scripts) and webpack.config.js configures them. To rebuild from the plugin folder:

  1. npm install
  2. npm run build for the blocks, then npm run build:admin for the admin app.

Installation

  1. Install Tinwell from the Plugins screen, or upload the tinwell folder to /wp-content/plugins/.
  2. Activate it, then open Tinwell in the admin menu.
  3. Work through the security onboarding wizard, and add your Stripe keys under Settings → Payment gateways.
  4. Create a donation form and add it to a page with the Tinwell block or shortcode.

FAQ

Does Tinwell take a fee from donations?

No. Donations go straight to your own Stripe account. Only Stripe’s standard fees apply.

Can charities outside the UK use Tinwell?

Tinwell is designed for UK charities. It takes donations in pounds sterling (GBP, £) only for now, and Gift Aid is a UK tax relief, so its Gift Aid features apply to UK donors and charities only.

Which payment methods are supported?

Card payments through Stripe, for one-off and regular gifts. Direct Debit through GoCardless is part of Tinwell Pro.

Can I claim Gift Aid?

Tinwell captures the declaration on the form and records it against every gift, so you have what HMRC needs, and the Gift Aid page lists every declaration and whether it has been claimed. Exporting the HMRC claim schedule, marking gifts as claimed and the CSV exports (which carry each gift’s declaration) are part of Tinwell Pro.

Where is donor data stored?

In your own WordPress database, with donor details encrypted at rest. Tinwell only sends data to the services listed under External services.

Does Tinwell track donors or visitors?

No. Nothing leaves your site beyond what the payment services above need to take a gift. To show how many people reach each step of a donation form, the form adds one to an anonymous daily count in your own database: no cookie, no IP address and no identifier is stored.

Can I customise the donation form?

Yes. The Form Builder lets you add fields, change colours and adjust the layout to match your brand. For anything more, style the form through your theme (Appearance → Customize → Additional CSS, or the Site Editor’s Styles).

Screenshots

Changelog

3.0.0

  • Added: with Tinwell Pro, custom emails in Settings › Emails. Write your own and choose what sends them: a donation, a regular gift collected, a Direct Debit regular gift cancelled or failed, a Direct Debit set up, Gift Aid declared, a campaign milestone or fund pot goal, a donor portal action, a donor’s first-gift anniversary, a set number of days after a gift, a donor who has gone quiet, or by hand to one donor or a filtered Donors list. Marketing emails reach only donors who agreed to email, with a link to unsubscribe.
  • Added: with Tinwell Pro, a campaign progress bar inside a donation form, from the Form Builder. It shows the campaign the form’s gifts count toward.
  • Changed: an email held back on purpose, for instance because the donor said no to email, shows on the donor’s timeline as Skipped rather than Pending.
  • Changed: Tinwell Pro 3.0.0 needs Tinwell 3.0.0, and Tinwell Pro now always updates before Tinwell, however the update is started.

2.9.1

  • Changed: Tinwell now updates through WordPress.org. Nothing else has changed since 2.9.0.

2.9.0

  • Added: dark mode for the admin, switched from the top bar and remembered in your browser. Previews of a form, an email or a component stay light, as donors will see them.
  • Fixed: the Donations and Gift Aid searches find part of a name or email, as the Donors list and the top bar do.
  • Fixed: in testing mode, a donation form’s fund pots show the test money they hold instead of £0.
  • Fixed: with Tinwell Pro, a donor giving by regular Direct Debit no longer reads as giving one-off gifts only.
  • Fixed: a donor’s and a company’s largest and last gift count a part-refunded gift.
  • Changed: the host-hardening check shows a warning while the host still reports a problem, so Plugin Health and the Security tab agree.
  • Added: with Tinwell Pro, Salesforce Nonprofit Cloud as a CRM. Donors, one-off and regular gifts, fund pots, refunds, fees, contact preferences, company gifts and, if you switch it on, the emails sent to donors all reach Salesforce.
  • Added: with Tinwell Pro, Pull from Salesforce and Push to Salesforce on the Campaigns page, a Salesforce tab on each campaign, a Salesforce fund on each pot, and an In Salesforce card on the donor page.
  • Fixed: a manual donation’s street address now reaches the CRM and the donor’s contact panel, and its country code is no longer taken for a dialling prefix or a country name. Donations already recorded are unchanged.
  • Fixed: after a refused card, trying again starts a new payment instead of retrying the refused one.
  • Fixed: with Tinwell Pro, the note on a company gift to Beacon no longer ends in a doubled full stop.
  • Added: a regular card gift you pause in Stripe (Pause subscription, or Pause payment collection) now shows as paused in Tinwell and in the donor portal, and resuming it there shows it active again. With Tinwell Pro, Donorfy, Salesforce and Beacon hear about the pause and the resume too.
  • Changed: the Stripe set-up steps follow Stripe’s current dashboard: sandboxes instead of Test mode, and Workbench’s event destinations for the webhook, where you must choose Snapshot events. The webhook’s event list adds customer.subscription.paused, customer.subscription.resumed and charge.dispute.closed; webhooks you set up before keep working as they are.
  • Changed: update Tinwell and Tinwell Pro together. Tinwell Pro 2.9.0 needs Tinwell 2.9.0.
  • Changed: Tinwell now updates from WordPress.org. With Tinwell Pro, an update of either waits until the same version of the other is on offer, so the two always update together, and an automatic update runs only when both will, Tinwell Pro first.
  • Fixed: the Campaigns page no longer offers CRM actions when no CRM can be connected.
  • Fixed: clicking a field in the Form Builder’s list now adds it to the form; before, only dragging it did.
  • Fixed: with Tinwell Pro, a regular gift’s first Direct Debit collection is no longer refused by Salesforce when its schedule had been set to start a month late; such a schedule is moved back to the collection, so a Retry records it. Beacon’s next payment date counts that first collection too.
  • Fixed: a donor’s and a company’s own page now count a part-refunded gift at what it kept, as the Donors and Companies lists do.
  • Fixed: previewing a form from the forms list or the Form Builder no longer raises an error in the browser.
  • Changed: the Donors search finds a part of a name or email among recent gifts, as the search in the top bar does.
  • Changed: without Tinwell Pro, the Donations table leaves out the Mandate and CRM columns, which only Pro fills.
  • Changed: long campaign titles no longer break mid-word, and the Security log and certificate show dates as the rest of Tinwell does.

2.8.3

  • Added: with Tinwell Pro, a high-value thank-you email to the donor, off until you switch it on in Settings > Emails. It goes for a one-off gift or the first collection of a regular donation, when the donation reaches the amount you set.
  • Added: with Tinwell Pro, the high-value alert to the admin has a box for the amount a donation must reach. It starts at 500, as before.
  • Changed: update Tinwell and Tinwell Pro together. On an older Tinwell the new amount box is a plain text box.

2.8.2

  • Fixed: with Tinwell Pro, a GoCardless event for something the account in use does not have, such as a live event reaching a site in testing mode or a dashboard test, is acknowledged instead of being asked for again for days. If a local gift holds it, it is still recorded as failed and named in the Activity Log, so it can be retried from the GoCardless dashboard. An outage or a refused token still retries.
  • Changed: the plugin no longer names the older default key by its stored label. Nothing stored changes. Tinwell Pro 2.8.2 needs Tinwell 2.8.2, and the other way round: update both together.
  • Fixed: updating from before 2.8 also clears a search hash that an earlier Key rotation left on an anonymised donation.