{"id":25947,"date":"2026-11-17T08:56:29","date_gmt":"2026-11-17T13:56:29","guid":{"rendered":"https:\/\/wpexpert.ca\/?p=25947"},"modified":"2026-11-17T08:56:31","modified_gmt":"2026-11-17T13:56:31","slug":"givingtuesday-2026-donation-website-checklist","status":"publish","type":"post","link":"https:\/\/wpexpert.ca\/fr\/givingtuesday-2026-donation-website-checklist\/","title":{"rendered":"GivingTuesday 2026: Is Your Website Ready to Accept Donations?"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Your GivingTuesday emails are ready. Your social posts are scheduled. Your team has a clear fundraising goal. But when someone clicks <strong>Donate<\/strong>, will everything work?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GivingTuesday 2026 takes place on Tuesday, December 1<\/strong>, as confirmed by <a href=\"https:\/\/www.canadahelps.org\/en\/givingtuesday\/\">CanadaHelps<\/a>. For Canadian charities and nonprofits, preparation should include more than a compelling campaign page. You need confidence that supporters can complete their gift and that your team receives the information needed to follow up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This GivingTuesday website checklist focuses on that complete journey. A page that loads successfully is a good start. It is not proof that your donation process works.<\/p>\n\n\n\n<div class=\"wp-block-group wp-block-wpseopress-table-of-contents is-layout-flow wp-block-group-is-layout-flow\">\n<h2 class=\"wp-block-heading\">Table of Contents<\/h2>\n\n\n<ol class=\"wp-block-list\">\n<li><a href=\"#donation-journey\">Map the Complete Donation Journey<\/a><\/li>\n\n<li><a href=\"#campaign-links\">Check Every Campaign Entry Point<\/a><\/li>\n\n<li><a href=\"#mobile-accessibility\">Test Mobile, Accessibility and Language<\/a><\/li>\n\n<li><a href=\"#payments\">Test Payments Safely<\/a><\/li>\n\n<li><a href=\"#follow-up\">Verify Confirmation and Follow-Up<\/a><\/li>\n\n<li><a href=\"#two-week-plan\">A Two-Week Plan That Leaves Room for Fixes<\/a><\/li>\n\n<li><a href=\"#campaign-day\">Prepare Your Campaign-Day Plan<\/a><\/li>\n\n<li><a href=\"#final-checklist\">Your Final GivingTuesday Checklist<\/a><\/li>\n\n<li><a href=\"#faq\">Foire aux questions<\/a><\/li>\n<\/ol>\n\n<\/div>\n\n\n\n<h2 id=\"donation-journey\" class=\"wp-block-heading\">Map the Complete Donation Journey<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Start by writing down every step a supporter takes:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Campaign link \u2192 donation page \u2192 donation form \u2192 payment result \u2192 confirmation \u2192 staff notification \u2192 donor record.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your website may handle all of these steps, or it may send supporters to an external fundraising platform. Either way, test the route you actually advertise. A successful test of the homepage says little about a campaign link that lands on an outdated form.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For each step, record the expected result, who will check it and what counts as a failure. Keep a simple test log with the date, device, language, scenario and outcome. This makes unresolved issues visible instead of leaving everyone with a vague \u201cit looked fine.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our guide to <a href=\"https:\/\/wpexpert.ca\/maximize-donations-wordpress-nonprofits\/\">optimizing WordPress for nonprofit donations<\/a> covers the wider conversion experience. This checklist is the practical rehearsal before you invite people to give.<\/p>\n\n\n\n\n\n<h3 class=\"wp-block-heading\">Build a Small Test Matrix Before You Start<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need to test every possible combination of browser, device and donation amount. Start with the routes your campaign actually offers, then choose a manageable set of scenarios. Give each scenario a clear expected result so \u201ctested\u201d means more than someone opened the page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following matrix is a useful starting point. Adapt it to your platform and run payment scenarios only through its approved testing tools.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Scenario<\/th><th>What to check<\/th><th>Evidence to record<\/th><\/tr><\/thead><tbody><tr><td>One-time gift on a phone<\/td><td>The advertised link opens correctly, the amount stays selected and the test payment completes.<\/td><td>Device, campaign URL, test transaction reference and outcome.<\/td><\/tr><tr><td>Recurring gift<\/td><td>The frequency is clear before submission and agrees with the resulting test record.<\/td><td>Selected frequency, amount and subscription status.<\/td><\/tr><tr><td>Declined test payment<\/td><td>The supporter receives a useful error, not a success message.<\/td><td>Error wording and the next action available.<\/td><\/tr><tr><td>Incomplete form<\/td><td>Missing information is identified without making the person guess.<\/td><td>Field affected and whether entered information remains available.<\/td><\/tr><tr><td>French-language journey<\/td><td>The page, form and follow-up stay consistent with the chosen language.<\/td><td>Any untranslated or mismatched messages.<\/td><\/tr><tr><td>Staff follow-up<\/td><td>The expected notification and donor record reach their intended destinations.<\/td><td>Inbox, campaign assignment and time received.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Assign each row one of three outcomes: <strong>passed, needs fixing or not tested<\/strong>. \u201cNot tested\u201d is useful information. It is better than treating an assumption as a successful check.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use fictional donor details and a designated test inbox. Avoid copying real supporter information into screenshots or shared troubleshooting documents. For each failure, add an owner, a next step and a retest date. Once the fix is in place, repeat the original scenario rather than checking only the individual setting that changed.<\/p>\n\n\n\n<h2 id=\"campaign-links\" class=\"wp-block-heading\">Check Every Campaign Entry Point<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open the exact links planned for your email, social posts, website banner and QR code. Use a private browser window so your WordPress administrator session does not hide problems visitors might encounter.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Destination:<\/strong> Does each link reach the correct campaign rather than last year\u2019s appeal?<\/li>\n\n\n\n<li><strong>Message:<\/strong> Do the campaign name, purpose and donation options match what the supporter just read?<\/li>\n\n\n\n<li><strong>Currency:<\/strong> Is the currency clear before the person commits?<\/li>\n\n\n\n<li><strong>Trust:<\/strong> Can visitors identify your organization and find help if something goes wrong?<\/li>\n\n\n\n<li><strong>Continuity:<\/strong> If you send people to another platform, is that transition clear?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you use tracking parameters, test the complete tagged URL. Keep personal information out of links. For campaign inspiration and official resources, visit the <a href=\"https:\/\/www.givingtuesday.org\/participate\/\">GivingTuesday participation hub<\/a>.<\/p>\n\n\n\n<h2 id=\"mobile-accessibility\" class=\"wp-block-heading\">Test Mobile, Accessibility and Language<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ask someone who did not build the page to try it on their phone. Watch where they hesitate. A form can technically work while still making a supporter wonder what to do next.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the amount selector, custom amount field, recurring-gift option and submit button. Make sure banners, chat widgets and the on-screen keyboard do not cover essential controls. Try enlarging the text and rotating the device.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Check more than appearance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Complete the form using a keyboard, without a mouse. Can you see which control has focus? Can you reach the payment fields and move past embedded content without getting stuck?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Labels and instructions should remain clear, and errors should explain what needs fixing. The <a href=\"https:\/\/www.w3.org\/WAI\/tutorials\/forms\/\">W3C accessible forms tutorial<\/a> provides practical guidance on labels, instructions and notifications. Our <a href=\"https:\/\/wpexpert.ca\/accessible-wordpress-forms-tips\/\">WordPress forms accessibility guide<\/a> offers additional context.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you offer English and French, test both complete journeys. Check donation options, validation messages, confirmation pages and emails, not just the campaign headline. These checks are useful preparation, but they do not replace a full accessibility review.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Make the Mobile Rehearsal Realistic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Try the journey on the connection and device a supporter might actually use, not only on a large monitor with a fast office connection. Open the campaign from a test email on a phone. If social media is a major channel, also check what happens when the link opens inside that app\u2019s browser.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pay particular attention to the moment when someone starts entering information. Does the keyboard cover the next field? Can they review the amount without losing their place? If they move back a step, does the form unexpectedly reset? Note these problems even when they do not stop the transaction completely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A useful exercise is to ask a colleague to narrate what they expect to happen. If they say \u201cI think this is a monthly donation\u201d or \u201cI\u2019m not sure whether that went through,\u201d the interface needs clarification.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"1024\" src=\"https:\/\/wpexpert.ca\/wp-content\/uploads\/multilingual_donation_form.webp\" alt=\"Illustrated donation form with English, Spanish and French language choices, currency options, name and email fields, and a Donate button.\" class=\"wp-image-9926\" style=\"width:500px\" srcset=\"https:\/\/wpexpert.ca\/wp-content\/uploads\/multilingual_donation_form.webp 1024w, https:\/\/wpexpert.ca\/wp-content\/uploads\/multilingual_donation_form-300x300.webp 300w, https:\/\/wpexpert.ca\/wp-content\/uploads\/multilingual_donation_form-150x150.webp 150w, https:\/\/wpexpert.ca\/wp-content\/uploads\/multilingual_donation_form-768x768.webp 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Check the Details That Translation Can Miss<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For an English-and-French campaign, review the journey side by side. A translated page can still lead to an English-only error or confirmation. Check the labels for a one-time gift, a recurring gift, an optional contribution and any campaign designation. The meaning should stay consistent, not merely the appearance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Try realistic names containing accents, apostrophes or hyphens. Check whether text is cut off on narrow screens and whether longer French labels push important controls out of view. Ask a fluent reviewer to read the confirmation email in context rather than reviewing isolated translated strings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Finally, check the help route. If someone encounters a problem in French, is it clear how they can contact your organization? State the support options your team can actually provide. A simple, accurate explanation is more useful than promising immediate bilingual assistance when nobody is assigned to deliver it.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"1024\" src=\"https:\/\/wpexpert.ca\/wp-content\/uploads\/team_testing_donation_and_security.webp\" alt=\"Two team members review a donation form on a laptop and a large screen displaying a warning symbol.\" class=\"wp-image-9584\" style=\"width:500px\" srcset=\"https:\/\/wpexpert.ca\/wp-content\/uploads\/team_testing_donation_and_security.webp 1024w, https:\/\/wpexpert.ca\/wp-content\/uploads\/team_testing_donation_and_security-300x300.webp 300w, https:\/\/wpexpert.ca\/wp-content\/uploads\/team_testing_donation_and_security-150x150.webp 150w, https:\/\/wpexpert.ca\/wp-content\/uploads\/team_testing_donation_and_security-768x768.webp 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 id=\"payments\" class=\"wp-block-heading\">Test Payments Safely<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Have your web partner use your donation platform\u2019s documented test environment. Avoid experimenting with payment settings on a live fundraising page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For GiveWP, the <a href=\"https:\/\/docs.nexcess.com\/software\/give\/test-mode\/\">official test-mode guide<\/a> explains how to test donations, configure the gateway for testing and check the resulting records. A staging copy is preferable when changing settings. The donation plugin and payment gateway must both be configured for the intended test environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you use Stripe, follow its <a href=\"https:\/\/docs.stripe.com\/testing\">official testing documentation<\/a>. Use sandbox credentials and the supplied test payment details. Do not use real card details to simulate transactions in live mode.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Include unsuccessful attempts<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Test a successful payment and the supported failure scenarios, such as a declined card. Confirm that an unsuccessful attempt produces a useful message rather than a misleading thank-you screen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Where available, check one-time and recurring gifts separately. Verify the selected amount, frequency and campaign designation. Do not assume that a successful one-time donation proves the recurring setup works.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before launch, have the responsible person confirm that production uses the correct live configuration. A passing sandbox test is useful evidence, not a guarantee that every production setting is correct.<\/p>\n\n\n\n<h2 id=\"follow-up\" class=\"wp-block-heading\">Verify Confirmation and Follow-Up<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Do not stop at the thank-you page. Follow each test through the systems your team relies on.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Donor confirmation:<\/strong> Does the message accurately reflect the amount, frequency and result?<\/li>\n\n\n\n<li><strong>Email delivery:<\/strong> Does the confirmation reach the designated test inbox, with readable formatting and working links?<\/li>\n\n\n\n<li><strong>Staff notification:<\/strong> Does it reach a monitored address rather than a former employee?<\/li>\n\n\n\n<li><strong>Donor database:<\/strong> If you use a CRM, does the expected record appear with the correct campaign and gift details?<\/li>\n\n\n\n<li><strong>Follow-up:<\/strong> Can staff identify who needs help without searching several disconnected systems?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Check your organization\u2019s actual receipting workflow separately. A payment confirmation and an official donation tax receipt are not necessarily the same document.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you measure conversions, verify that your reporting distinguishes completed gifts from button clicks or form starts. Compare campaign reports with your donation platform\u2019s records before drawing conclusions. Keep test activity clearly separated from real fundraising results.<\/p>\n\n\n\n<h2 id=\"two-week-plan\" class=\"wp-block-heading\">A Two-Week Plan That Leaves Room for Fixes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A donation rehearsal is most useful when there is still time to act on what it reveals. For a December 1 campaign, use the following schedule as a practical planning example. If your first fundraising email goes out earlier, move the checks forward accordingly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">November 17\u201320: Gather the Pieces<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm the campaign owner, website contact and fundraising contact. Collect the final destination links, offered payment methods, language versions and notification addresses. Decide which team member can inspect the donation platform and donor database. Someone with access to WordPress alone may not be able to verify the whole journey.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agree on the test environment and the boundaries of the rehearsal. Document what you can test safely and what requires help from your payment or fundraising provider. Identify any campaign content still awaiting approval.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">November 21\u201325: Rehearse and Fix<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Run your test matrix and record the results. Prioritize problems that block giving, display an incorrect amount or frequency, misreport the outcome, or prevent the team from identifying the gift. Fix these before spending time on optional visual refinements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After a change, retest the affected journey from its starting link. If the fix touches a shared form or payment component, check the other relevant campaign routes too. Avoid closing an issue solely because its error message has disappeared.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">November 26\u201330: Confirm Readiness<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review the final email and social links, campaign copy and unresolved issues. Confirm the production configuration with the person responsible for it. Make sure staff know where to find the runbook and how to report a problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agree on a short pause for nonessential website changes around the campaign launch. This is not a reason to delay an urgent security fix. It is a way to avoid introducing optional changes without enough time to check their effects.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">December 1 and After: Watch, Then Learn<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use your planned checkpoints during the campaign. Afterwards, compare the donation records with the campaign report, review support questions and note any confusing steps. Keep the updated test matrix for your next appeal so the work becomes a reusable process rather than a once-a-year scramble.<\/p>\n\n\n\n<h2 id=\"campaign-day\" class=\"wp-block-heading\">Prepare Your Campaign-Day Plan<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Technical preparation needs an owner. Decide who checks the campaign, who responds to donor questions and who can contact your hosting or payment provider.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose sensible checkpoints, such as before the first email, after a major campaign send and later in the day. Look at completed donations, reported errors and incoming support requests together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Uptime monitoring answers \u201cIs the website responding?\u201d It does not, by itself, answer \u201cCan a supporter complete a donation?\u201d<\/strong> Similarly, contact-form testing should not be mistaken for verification of a payment gateway or recurring-gift workflow.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Finish nonessential design changes before your final rehearsal. Do not ignore urgent security issues, but avoid introducing optional changes immediately before a campaign without time to test them. Agree on an escalation plan and a verified alternative donation route if your main journey becomes unavailable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Write a Runbook Someone Else Can Follow<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Your campaign-day instructions should fit on a page and make sense to a colleague covering for you. Include the campaign URL, the donation platform, the owner and backup contact, the monitored support inbox, and where authorized staff can inspect transaction records. Store access details securely rather than putting passwords into the runbook.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add the signs that require action. These might include a donor reporting an error, a sudden pattern of failed transactions or notifications that stop arriving while donation records continue to appear. Set expectations around your own campaign and usual activity. A quiet hour alone does not prove the website is broken.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Separate a Payment Problem from a Reporting Problem<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If something looks wrong, identify which part of the journey failed before changing settings. A missing staff email does not necessarily mean a gift failed. An analytics event does not necessarily mean money was received. Ask an authorized colleague to compare the relevant records in the donation and payment platforms.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep a brief incident log: what was reported, when it started, which routes are affected and who is investigating. Share only the information needed to resolve the issue. Do not ask donors to email card details or send screenshots containing payment information.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tell Supporters What You Know<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Prepare a short service message before launch so nobody has to invent one under pressure. For example: \u201cWe\u2019re investigating a problem with our online donation form. If you are unsure whether your gift completed, please contact us before trying again.\u201d Add your organization\u2019s verified contact route.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use a message only when it matches the actual situation. Avoid declaring that every donation failed, promising an immediate fix or directing everyone to retry when the outcome is uncertain. Your fundraising and technical contacts should agree on what is known and what supporters should do next.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you offer an alternative donation route, verify it in advance and explain it clearly. Do not improvise a new payment destination during an incident. Once the issue is resolved, repeat the relevant checks, update the team and remove any outdated service notice.<\/p>\n\n\n\n\n\n<h2 id=\"final-checklist\" class=\"wp-block-heading\">Your Final GivingTuesday Checklist<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Campaign links and QR codes lead to the correct destination.<\/li>\n\n\n\n<li>Mobile, keyboard and offered language journeys have been reviewed.<\/li>\n\n\n\n<li>Payment scenarios have been tested using the provider\u2019s approved tools.<\/li>\n\n\n\n<li>One-time and recurring options have been checked separately.<\/li>\n\n\n\n<li>Donor confirmations and staff notifications reach the right people.<\/li>\n\n\n\n<li>Expected donor records and campaign details appear correctly.<\/li>\n\n\n\n<li>Production configuration has been reviewed after testing.<\/li>\n\n\n\n<li>Unresolved issues have an owner and a decision before launch.<\/li>\n\n\n\n<li>Campaign-day monitoring and escalation responsibilities are clear.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need a last-minute redesign to make this exercise worthwhile. A focused rehearsal can reveal a broken link, unclear instruction or missing notification while there is still time to fix it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/wpexpert.ca\/fr\/contacter\/\">Talk to WP Expert<\/a> about reviewing your WordPress donation journey before GivingTuesday. Bring your campaign link, donation platform and launch date so we can identify the checks that matter for your setup.<\/p>\n\n\n\n<h2 id=\"faq\" class=\"wp-block-heading\">Foire aux questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">When is GivingTuesday 2026?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">GivingTuesday is Tuesday, December 1, 2026. Leave time before your campaign launches to fix issues and repeat the affected checks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do we need to test if donations are handled by another platform?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Check the links from your website and campaign messages, the handoff to the platform and the supporter\u2019s return or confirmation experience. Use that provider\u2019s approved testing process.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does a working donation button prove the payment process works?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. It only proves that particular interaction works. Payment processing, confirmation, notifications and donor records need their own checks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should we make a small real payment as a test?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use your provider\u2019s documented testing method instead. For Stripe, that means sandbox testing with test payment details, not real card details in live mode.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What should we prioritize if time is short?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Start with the advertised campaign link and the main mobile donation journey. Then verify payment outcomes, confirmations and staff notifications. Fix anything that prevents giving or makes the outcome unclear before polishing optional design details.<\/p>","protected":false},"excerpt":{"rendered":"<p>Before GivingTuesday on December 1, test more than your Donate button. Use this practical checklist to verify mobile donations, payment processing, confirmations and donor records.<\/p>","protected":false},"author":5,"featured_media":8216,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,70],"tags":[],"class_list":["post-25947","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles","category-nonprofits"],"meta_box":{"post_icon":false},"_links":{"self":[{"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/posts\/25947","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/comments?post=25947"}],"version-history":[{"count":6,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/posts\/25947\/revisions"}],"predecessor-version":[{"id":25954,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/posts\/25947\/revisions\/25954"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/media\/8216"}],"wp:attachment":[{"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/media?parent=25947"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/categories?post=25947"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpexpert.ca\/fr\/wp-json\/wp\/v2\/tags?post=25947"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}