Mobile is now the majority of your donation-page traffic but a minority of your revenue, and the fastest way to close that gap before GivingTuesday on December 1 is one-tap express checkout. Apple Pay, Google Pay, and PayPal at the top of your form remove the typing that quietly kills mobile gifts.
The short version
- Mobile drove 52 percent of nonprofit website traffic in 2026 but only 28 percent of online revenue, according to M+R Benchmarks. That is a conversion gap, not a traffic problem.
- Mobile donation pages convert worse than desktop: 8 percent against 11 percent on the main donation page, and just 4 percent on mobile for small nonprofits.
- Express checkout lifts one-time conversion by about 1.5 percentage points, per Fundraise Up, because it removes manual card entry on a phone.
- Only 57 percent of nonprofits offer Apple Pay. If you are in the other 43 percent, this is the highest-leverage fix you can ship before December 1.
Mobile is where your donors are, and where you are losing them
Your phone traffic is not a rounding error anymore, and it is converting at a discount. In the 2026 M+R Benchmarks study of roughly 180 US nonprofits, mobile accounted for 52 percent of all website traffic but only 43 percent of donation transactions and 28 percent of online revenue. The average gift told the same story: 168 dollars on desktop against 88 dollars on mobile. Fundraise Up, which analyzed about 1,000 organizations across four markets, found US mobile giving crossed the majority threshold in early 2026, reaching 53 percent of donations, up from 48 percent a year earlier. More than half the people who land on your donate page are on a phone, and most pages are still built for the half who are not.
The conversion math is where it hurts. M+R put the main donation page at 11 percent for desktop visitors and 8 percent for mobile visitors, and for small nonprofits mobile conversion fell to 4 percent. A mobile visitor is worth less not because they care less, but because the form asks them to type a 16-digit card number, an expiration date, a security code, and a billing ZIP on a glass keyboard, usually one-handed, often on a slow connection. Every one of those fields is a place to give up.
Express checkout is the highest-leverage change you can ship this month
One-tap wallets remove the typing, and the conversion data backs it up. Fundraise Up's 2026 Pulse of the Donor report found that adding express checkout to the mobile web flow increased one-time donation conversions by about 1.5 percentage points. On a page converting at 8 percent, that is close to a one-in-five improvement in completed gifts from the same traffic. The same report named digital wallets the fastest-growing payment category in every market it studied: Apple Pay's share of US transactions grew 38 percent year over year while credit card share fell by roughly a tenth. Donors are already reaching for the wallet. The question is whether your page offers it.
Apple Pay and Google Pay work because the donor's name, card, and billing address already live in the device. One tap and a fingerprint or face scan replaces a minute of error-prone typing. For a GivingTuesday visitor who arrived from an email or an Instagram story and has a narrow window of intent, that minute is the difference between a gift and a bounce.
The honest caveat: mobile gifts are smaller, so design for it
Express checkout raises completion, not gift size, and pretending otherwise will set the wrong expectation with your board. Remember the M+R split: 88 dollars average on mobile against 168 on desktop. Wallet payments do not close that gap on their own, and in some of Fundraise Up's cuts the average wallet gift ran below the average card gift. What express checkout buys you is more completed gifts from traffic you already paid to acquire.
To protect revenue per visitor, pair it with two things. First, lead with a monthly ask, because a recurring supporter acquired on GivingTuesday is worth far more than the first gift. Fundraise Up's pre-donation recurring option converted at 2.4 percent in the US last year, up 20 percent year over year, and it costs you nothing but a toggle. Second, set suggested amounts deliberately for mobile, where a sensible default does more work than it does on desktop because the donor is less likely to stop and type a custom number.
How to actually ship it before December 1
If your payment processor already supports wallets, this is an afternoon of work, and domain verification is the only real gate.
- Confirm your processor supports wallet payments. Stripe, Fundraise Up, Classy, and Givebutter all do. If you are on a processor that does not, that is the real project, and it is worth starting now rather than in late November.
- Enable Apple Pay, which requires registering and verifying every domain where the button appears. In practice that means serving the page over HTTPS and hosting a domain-association file your processor provides at a fixed path under /.well-known/. Stripe documents the exact steps.
- Enable Google Pay, which rides the browser Payment Request API and has fewer setup hoops, but still needs HTTPS and a supported browser to render.
- Put the wallet buttons above the card fields, not below them. A donor who can finish in one tap should never have to scroll past a full card form to find out.
- Test on a real iPhone in Safari and a real Android in Chrome. The buttons only render on supported devices and browsers, so desktop emulation will lie to you.
One detail trips teams up on Webflow and other visual builders: if you embed a hosted donation form in an iframe, wallet support depends on the processor's domain, not yours, and you inherit whatever they configured. If you build a custom form with Stripe's Payment Element on your own domain, you own the domain verification and cannot skip it. When I added express checkout for a legal-services nonprofit client last fall, the entire delay was a misconfigured HTTPS redirect that broke the domain-association file. The Apple Pay button simply did not appear until the file resolved cleanly over HTTPS, which is exactly the failure mode the Stripe docs warn about. Budget an hour for that, not a week.
What this does not cover
This is a conversion fix for your existing donation page, not a strategy overhaul. It does not cover offline and mail giving, which still converts far higher than any web channel and runs on a different playbook. It does not cover a full donation-page redesign or copy rewrite, and a new layout will not save a page that still forces manual card entry. It does not get into payment-processor selection economics or PCI compliance, both of which deserve their own decision. And while wallet buttons reduce friction, they do not exempt your page from accessibility: the buttons still need sufficient color contrast and a visible focus state to meet the Web Content Accessibility Guidelines (WCAG) 2.2.
Frequently asked questions
Will Apple Pay and Google Pay raise my average gift?
No. They raise the share of visitors who complete a gift, not the size of it. Average mobile gifts run smaller than desktop gifts, 88 dollars against 168 in M+R's 2026 data, and wallets do not change that on their own. Treat express checkout as a completion lever and use a monthly ask to grow value per donor.
Do I still need Apple Pay if I already offer PayPal?
Yes, for most audiences. PayPal is the most common wallet on donation pages, offered by 79 percent of nonprofits in M+R's 2026 data, but iPhone users increasingly expect the native Apple Pay sheet and it is the fastest path on iOS. Offering one does not replace the other, because donor preference splits by device.
How long does it take to add express checkout before GivingTuesday?
If your current processor supports wallets, plan for an afternoon to a day of work, most of it domain verification and device testing. If your processor does not support wallets, you are looking at a migration, and five weeks before December 1 is a tight but workable window to start.
Does express checkout work inside an embedded donation form?
It can, but it depends on how the form is embedded. A hosted form in an iframe uses the provider's domain and configuration, so wallet support follows whatever they enabled. A form you build on your own domain requires you to verify that domain yourself before Apple Pay will appear.
Is this worth it for a small nonprofit?
Especially for a small nonprofit. Small-organization mobile conversion sat at 4 percent in M+R's 2026 data, roughly half the overall mobile rate, which means small teams have the most completion to recover and usually the least custom development standing in the way.
GivingTuesday is 36 days out. If you want me to run a mobile-conversion teardown of your donation page before December 1 and hand you a short list of exactly what to ship, in priority order, book a 20-minute read-out. I build and maintain sites for mission-driven nonprofits as a nonprofit website developer, and express checkout is the fix I would start with this month.