How to Create a Donation Website in Canada: A Practical Step-by-Step Guide

A donation website has to do more than display a worthy cause.

It must, at the very least:

• Show who is asking,

• Explain what a gift will fund,

• Process money safely, and

• Give each donor the right kind of acknowledgement.

Such website should make one decision easy: “I trust this organization, I understand what my gift will do, and I can donate safely right now.”

You can build that website without custom development.

The most flexible route is an owned WordPress site connected to a secure hosted donation form or payment processor.

Before choosing the software, confirm whether your organization can issue official donation receipts. In Canada, a nonprofit and a registered charity are not the same thing.

In this guide, I’ll take you from that very first decision to a working, tested donation page.

Decide What Kind of Donation Website You Are Building

Start with the legal recipient of the money. Your website copy, payment account, and receipt process must all name the same organization.

The Canada Revenue Agency (CRA) distinguishes registered charities from nonprofit organizations:

Only a registered charity or another qualified donee can issue an official donation receipt for income tax purposes.

A Stripe or PayPal payment confirmation proves that money changed hands; it is not automatically a Canadian tax receipt.

If your charity application is pending, build the site but do not display a registration number or tax-receipt promise you cannot yet support.

Choose an Owned Website or a Hosted Campaign Page

An owned website takes longer to set up, but it gives the organization a permanent home for programs, reports, volunteer information, and future campaigns.

A hosted campaign page is quicker but provides less control over the donor experience.

For an organization that expects to fundraise more than once, I recommend this stack:

• An organization-owned domain.

• Truehost WordPress Hosting for the public website.

• WordPress for pages and content.

• An embedded donation form or WordPress donation plugin.

• A hosted payment provider so the website does not collect raw card details.

If you only need a small information site that links to a hosted donation page, the Truehost AI Website Builder is a simpler alternative.

Build the Donation Website Step by Step

1) Register the Domain in the Organization’s Name

Choose a short name that matches the organization’s public identity. Avoid a campaign slogan that will become irrelevant when the first appeal ends.

A .ca domain signals a Canadian connection. The registrant must meet one of CIRA’s Canadian Presence Requirements.

Keep the domain under an organization-controlled account rather than a volunteer’s personal login.

Record the renewal date and recovery contact, enable automatic renewal, and turn on multi-factor authentication when available.

2) Set Up WordPress Hosting

Choose the appropriate Truehost WordPress Hosting plan and connect the domain.

From the hosting control panel, open the WordPress installer. The exact label can differ by control-panel version, but the setup normally asks for:

• the domain;

• the site name;

• an administrator username;

• a strong administrator password; and

• an organization-controlled administrator email.

Do not use admin as the username. After installation, sign in through yourdomain.ca/wp-admin/ and confirm that the site opens over https:// without a certificate warning.

3) Choose a Lightweight Theme and Create the Core Pages

In WordPress, open Appearance > Themes > Add New.

Choose a maintained theme with responsive layouts, readable typography, visible keyboard focus, and support for the block editor.

Then open Pages > Add New and create:

• Home: mission, current need, one proof point, and a visible Donate button;

• About: legal name, location, leadership, history, and charity registration details when applicable;

• Programs: who each program serves, where it operates, and what it does;

• Impact: current results, annual reports, financial information, and links to public CRA records;

• Donate: the campaign appeal and donation form;

• Contact and Privacy: real contact information, privacy policy, and accessibility contact.

Add Donate to the main navigation and mobile menu. A donor should not have to search through several pages to find the form.

4) Choose the Donation Provider

Compare the complete workflow, not only the card-processing percentage.

Also check:

• one-time and monthly gifts;

• CAD support and donor payment methods;

• refunds and recurring-payment cancellation;

• payout schedules;

• donor-data exports;

• CRM or bookkeeping integrations;

• currency-conversion and dispute fees;

• mobile and keyboard accessibility; and

• eligibility for your organization type.

5) Add the Donation Form to WordPress

You can embed a provider’s form, install a donation plugin, or link to hosted checkout.

Route A: Embed a CanadaHelps or Other Hosted Form

Create the form in the provider’s dashboard and copy its approved embed code.

In WordPress:

1. Open Pages > Donate > Edit.

2. Select the location where the form should appear.

3. Add a Custom HTML block.

4. Paste the provider’s complete embed code without altering its scripts or field names.

5. Use Preview to test the form on desktop and mobile.

6. Publish only after a successful test transaction.

Embedding keeps the donation experience inside the organization’s page while the provider handles the sensitive payment fields.

Route B: Use a WordPress Donation Plugin

Plugins such as GiveWP and Charitable create donation forms and connect to supported gateways.

In WordPress:

1. Open Plugins > Add New Plugin.

2. Search for the selected plugin and verify the developer, update history, compatibility, and support information.

3. Select Install, then Activate.

4. Complete the plugin’s setup wizard.

5. Connect the approved Stripe, PayPal, or other supported account.

6. Create a form with one-time, monthly, and custom-amount choices as required.

7. Add the plugin’s form block or shortcode to the Donate page.

8. Test in the gateway’s test mode before enabling live payments.

Feature names vary by plugin version.

Confirm which functions require a paid add-on, especially recurring gifts, PDF receipts, peer-to-peer campaigns, donor dashboards, and CRM integrations.

Route C: Link to Hosted Checkout

For the simplest implementation, add a Donate button that leads to a provider-hosted payment page.

Use the same organization name, logo, colours, currency, and campaign language on both pages so the handoff does not look suspicious.

6) Build the Donation Page Around One Decision

The first mobile screen should identify the organization, show the outcome, and provide a Donate button or the first part of the form.

Use this copy structure:

Headline: Help provide weekend food packs to students in Scarborough.

Need: Some students leave school on Friday without enough food for the weekend.

Action: Your gift helps our local team purchase and distribute practical food packs through participating schools.

Suggested amounts: CA$25, CA$50, CA$100, or another amount.

Trust note: Donations are processed securely by [provider]. Eligible donors will receive [receipt timing and method].

Connect suggested amounts to supportable examples. If CA$25 does not always fund one complete pack, write “CA$25 can help provide weekend food” rather than making a precise claim the organization cannot prove.

Ask only for information the organization will use. Keep marketing consent separate from the donation itself, and do not preselect an optional email subscription.

7) Configure the Receipt and Thank-You Process

Every donor should receive a payment acknowledgement.

The CRA’s official receipt checklist lists required information such as the filed charity name and address, registration and serial numbers, donor name and address, donation and eligible amounts, relevant dates, authorized signature, and the CRA web address.

If the charity emails official receipts, the CRA’s computer-generated receipt guidance says the document should be read-only or non-editable.

The thank-you page and email should confirm:

• gift amount and frequency;

• selected campaign or fund;

• receipt eligibility and delivery timing;

• how to correct donor details;

• how to update or cancel a monthly gift; and

• one useful next step, such as reading the latest impact report.

If WordPress sends organization emails, use a domain address such as [email protected]. Configure the sending service’s SPF and DKIM records and send test messages to several mailbox providers.

A receipt workflow is not complete if its emails consistently land in spam.

Complete the Canadian Launch Checklist

Keep the legal detail concise, but do not skip these controls.

Receipting and Fundraising Claims

State the legal recipient and receipt policy beside the form.

Do not claim that every dollar goes directly to programs unless the organization can support that statement.

CRA fundraising guidance requires truthful and accurate representations.

Privacy and Email Consent

Publish a privacy policy that explains what information is collected, why it is needed, which providers receive it, how long it is kept, and how donors can request access or correction.

PIPEDA does not generally apply to a nonprofit’s ordinary fundraising when the activity is not commercial, but other activities and provincial privacy laws may apply.

Review the Privacy Commissioner’s guidance for charities and nonprofits and the applicable province.

CASL can apply to commercial electronic messages sent by nonprofits and charities.

A registered charity may have an exemption when a message’s primary purpose is fundraising, but that does not cover every future promotional email. Use a separate opt-in and a working unsubscribe mechanism. See the CRTC’s CASL guidance.

Organizations operating in Quebec or across Canada should also confirm applicable French-language and Quebec privacy requirements before launch.

Payment Security and Administrator Access

Use a hosted or embedded payment form supplied by a validated provider. Do not collect card numbers in a normal WordPress form or email.

Protect the site with:

• https:// on every page;

• named administrator accounts;

• multi-factor authentication;

• prompt WordPress, theme, and plugin updates;

• least-privilege access;

• tested backups; and

• removal of unused themes and plugins.

The PCI Security Standards Council explains that SAQ A eligibility depends on outsourcing payment processing and meeting all applicable criteria.

A redirected checkout still requires protection because attackers can replace a legitimate payment link.

Accessibility

Ontario’s AODA rules require covered public websites to meet WCAG 2.0 Level AA.

Other accessibility and human-rights obligations may also apply.

At minimum, test that:

• text has sufficient contrast;

• images have useful alt text;

• every field has a visible label;

• every control works by keyboard;

• keyboard focus remains visible;

• errors are explained in text;

• the page works when zoomed; and

• the form works with a screen reader and on a phone.

Ontario publishes guidance on making websites accessible, and W3C provides an accessible forms tutorial.

Books and Records

Reconcile gross donations, processor fees, refunds, chargebacks, net payouts, restricted funds, and receipt numbers.

The CRA’s books and records guidance requires registered charities to keep adequate records in Canada.

Test and Troubleshoot Before Launch

Run the provider’s test mode first, then make a small live donation with board or staff approval.

Common problems have practical fixes:

• The form is blank: disable page caching for the Donate page, check whether a security plugin blocked the embed script, and compare the pasted code with the provider’s original.

• The embed is cut off on mobile: remove fixed heights, test the provider’s responsive embed option, or use hosted checkout instead.

• The site returns to the wrong page: update the provider’s success and cancellation URLs.

• Emails do not arrive: check spam, verify the sending address, configure SPF and DKIM, and inspect the provider or SMTP delivery log.

• Test payments work but live payments fail: confirm that the live account completed identity and bank verification and that the site uses live rather than test credentials.

• Changes do not appear: clear the WordPress, server, and browser caches before editing the form again.

• The browser shows a security warning: stop the launch and fix the SSL certificate or mixed-content resource first.

Ask one person unfamiliar with the organization to complete a live-style test without coaching. Give them one task: “Find what a CA$50 gift supports and make a test donation.” Their hesitation will reveal problems that the build team no longer notices.

Launch the Website and Bring Donors to It

Launch to a small audience first. Ask board members, volunteers, and trusted supporters to test the wording and payment process before promoting it widely.

Then use:

• an email to existing supporters who can legally receive it;

• links from the organization’s social profiles;

• campaign-specific landing pages;

• QR codes on verified event materials; and

• links from trusted community partners.

Track four numbers monthly: donation-page conversion rate, average gift, new monthly donors, and net donation revenue after fees and refunds. Do not send names, email addresses, card details, or receipt data to website analytics.

Build the Site Once, Then Improve Each Campaign

An effective donation website makes four things clear: who receives the money, what the gift supports, how payment is protected, and what acknowledgement the donor will receive.

Begin with the organization’s status and receipt process. Then build the site on an organization-owned domain, connect one approved donation system, and test the entire flow through payout and bookkeeping.

If you want an owned WordPress site that can support donation plugins, embedded forms, reports, and future campaigns, start with Truehost WordPress Hosting.

Donation Website FAQs