Raisely integration

Raisely is a fundraising platform with its own hosted campaign pages and donation forms, and many charities use it as their supporter database too. Tinwell’s Raisely integration is for the charity that wants to keep donors on its own WordPress website, with its own theme, Apple Pay, Google Pay and GoCardless Direct Debit, and still have every gift and donor in Raisely. When a donation is made on your site, Tinwell writes it to Raisely through Raisely’s official API within seconds.

What gets written to Raisely

• The donor. Name, email and address from the form, matched to an existing Raisely user where one exists.
• The donation. Amount, date, payment method, the campaign it was given to, and the Stripe or GoCardless reference.
• Regular giving. Monthly gifts create a subscription record in Raisely, and each collection is written as it is taken.
• Consent and Gift Aid. The contact preferences and the Gift Aid declaration status, so Raisely’s records match Tinwell’s export.

Rather see Tinwell than read about it? Open the live demo to try the donation form, the donor portal and the admin dashboard with sample data.

Why run the form on WordPress rather than on Raisely

Raisely’s default pricing is free to the charity and funded by optional donor tips, which is attractive, and its hosted pages are good. The case for Tinwell alongside it is about where the donor is when they give. A form on your own domain, in your own theme, with no redirect and no tip request, converts better and keeps your analytics whole. Direct Debit through GoCardless and the HMRC-ready Gift Aid export are the other two reasons UK charities add Tinwell to a Raisely set-up. If you are on Raisely’s flat-fee option, the fee calculator shows what that costs against a Tinwell licence.

Setting it up

1. In Raisely, create an API key for Tinwell.
2. In Tinwell’s settings, open Integrations, choose Raisely and paste the key.
3. Map Tinwell campaigns and fund pots to your Raisely campaigns.
4. Make a £1 test donation, check the user and donation in Raisely, then refund it in Stripe.

The set-up docs for the donation plugin cover each step, and the free onboarding add-on at checkout includes connecting Raisely.

Peer-to-peer on Raisely, direct giving on your site

The pattern that works for most charities on Raisely is to keep what Raisely is best at (fundraiser pages, challenge events, campaign microsites) on Raisely, and to take direct donations from the main website with Tinwell. A supporter who arrives at your homepage from a search or an email gives on your page without a redirect; a supporter running a half marathon for you builds a page on Raisely. Both end up on the same Raisely record, because Tinwell writes the direct gift to the donor’s Raisely profile, so your fundraising team still has one view of each supporter.

Campaign components on your pages

Tinwell’s progress bar, totaliser, impact cards, countdown and supporter wall read live figures from the donations taken on your site, and can be placed on any WordPress page as blocks or shortcodes. If a Raisely campaign and a Tinwell campaign are running towards the same target, map them to each other so the Raisely total includes the website gifts.

What is shared, and on what basis

Tinwell sends Raisely only what the donor entered on your form and what the payment produced: identity and contact details, the gift, the regular schedule, the consent choices and the Gift Aid declaration status. It does not send card or bank details; those stay with Stripe and GoCardless. Your charity is the data controller for both the website and Raisely, so the transfer is between two of your own processors and should be described in your privacy notice as part of how you process donations. A line such as “we record your donation and contact preferences in our supporter database” covers it; your data protection lead may want the exact wording.

Reconciliation at month end

Because every donation written to Raisely carries the Stripe or GoCardless payment reference, finance can tie the CRM to the payout statements without a mapping spreadsheet. The usual month-end routine becomes: export the period from Stripe and GoCardless, compare the totals with Tinwell’s dashboard and with Raisely’s reports for the same dates, and investigate only the lines that differ, which are nearly always refunds or failed Direct Debit collections. Tinwell marks refunds and failures on the donor record so they are visible in both places.

Before you go live

• Agree which Raisely funds, campaigns and codes each Tinwell campaign and fund pot maps to, and who owns changing the mapping when a new appeal starts.
• Decide how new, unmatched donors should be handled: created and flagged for review, or created silently. Tinwell’s default is to flag.
• Run a £1 test as a brand-new donor and again as an existing supporter, and check both records in Raisely before refunding in Stripe.
• Set up a monthly test gift and confirm the schedule appears in Raisely, then cancel it in the donor portal and confirm that is reflected too.
• Add the website donation process to your data protection records and privacy notice.

Frequently asked questions

See all integrations, the features, or pricing. The Raisely integration is included in the licence.