Wallet setup

Wallet setup turns on the one-tap payment methods donors already have on their phones — Apple Pay, Google Pay, and Stripe Link. When it's active, your donation widget shows a big wallet button at the top of the form, and most mobile donors finish their gift in two taps.

You'll find this in your campaign's Embed tab, right below the live preview of your widget. It lives on the campaign page so the same setup covers every place you've pasted that widget — your homepage, donation landing pages, sidebars, or a dedicated giving page.

Why each wallet needs registration

Stripe requires us to verify your website once before donors can use wallets there. This is called a "payment method domain." It proves to Stripe that you actually control the site where the donation form is loading — not somebody pretending to be you. You do this once per domain, then wallets work everywhere that widget appears on your site.

What you need before starting

• Your website must be live at a public URL. Staging servers on localhost or internal-only URLs won't work — Stripe has to be able to reach the site from the public internet.
• You must be an Admin or Owner in your GiveLink organization. Members can't activate wallets.
• For Apple Pay, you need a way to upload a small verification file to /.well-known/apple-developer-merchantid-domain-association on your site. Some website platforms make this easy; others block it. See the table below.

Which wallets work where

GiveLink's widget runs on any website, but Apple Pay verification depends on whether your website platform lets you upload a file to a specific folder. Google Pay and Link don't have this requirement, so they work nearly everywhere.

"Not yet verified" means GiveLink hasn't confirmed an Apple Pay setup path on that platform — usually because the platform doesn't allow file uploads to /.well-known/. Google Pay and Link still work for your donors. A subdomain workaround that enables Apple Pay on these platforms is coming soon.

What each status means

Each domain row in the Wallet Setup card shows a status for every wallet. Here's what each one means and what to do next.

• Waiting for install ping. You added the domain manually and GiveLink is listening for the widget to load from your site. As soon as your site sends its first install ping, the row activates. If you haven't pasted the widget snippet on your site yet, do that now.
• Ready to activate. The widget is installed and detected. Click Activate wallets for donors to register this wallet with Stripe. Google Pay and Link activate in a second or two.
• Registered — wallets live. Donors who are signed into this wallet on a supported browser will see the one-tap button.
• Needs your attention. Apple Pay couldn't finish verification — usually because the verification file isn't reachable yet. The row expands into step-by-step instructions for your platform.
• Released. Someone at your organization manually released this domain. The row stays visible for history but no longer serves wallets. A different GiveLink organization can now claim it.

www and apex

Browsers treat www.yoursite.org and yoursite.org as two different origins, even if they point to the same site. Stripe treats them separately too — so if your donors land on both, you need both registered.

When the Wallet Setup card detects only one of the pair, it shows a banner with a Register both button that sets them up in one click.

In-app browsers

Apple Pay and Google Pay buttons are hidden inside the in-app browsers that Facebook, Instagram, and LINE use when someone taps a link from those apps. This is a platform restriction — not something we can override. Donors in those in-app browsers still see the card-entry form and can complete their gift normally.

Wallets do appear in Safari, Chrome, Edge, Firefox, and other standard mobile browsers.

Releasing or transferring a domain

If a domain needs to move to a different GiveLink organization — for example, you're spinning off a program into its own account — an Admin or Owner can release the domain from the Wallet Setup card.

Releasing is the only way to move a claim. Stripe enforces one claim per domain per platform account, so the new organization can't register the domain until the current one lets it go.

When you release a domain, GiveLink asks for a short reason and writes an audit entry so there's a record of who released it and when. Existing donations already collected through that widget aren't affected.

FAQ

Can two GiveLink organizations register the same domain? No. Stripe allows only one active claim per domain per platform account. If another GiveLink organization has already claimed your domain, see the how-to page below for next steps.

Will every donor see Apple Pay or Google Pay? No — wallet availability is up to the donor's device, browser, country, and whether they've set up a wallet at all. A donor on a desktop Chrome session with no saved card will see the card form instead. That's normal.

What happens to existing donations if I release a domain? Nothing. Release only stops future wallet checkouts on that domain. Prior donations, receipts, recurring schedules, and donor records are all untouched.

See also

• Activate Apple Pay, Google Pay, and Link

How is this guide?GoodBad