All Collections
Collecting payments
Payment methods
Accepting payments through Apple Pay
Accepting payments through Apple Pay

Connecting your Stripe account and enabling Apple Pay in Beacon

Updated over a week ago

Beacon enables collection of payments via Apple Pay through Stripe. Stripe is a world-leading payment gateway, built for simplicity and with a focus on ease of integration. Today it's used by leading charities including Oxfam, Unicef and Comic Relief.

Create a Stripe account and connect it to Beacon

To accept Apple Pay payments through Beacon, you'll need to connect your Stripe account to Beacon. Instructions for how to do this can be found in this article.

Enable Apple Pay in Beacon

You can enable Apple Pay in Beacon with just a few clicks.

  1. Go to Settings > Payments in your Beacon sidebar

  2. If you have not yet connected Stripe then follow these instructions to connect your stripe account.

  3. In the Apple Pay section of the Payment page check the Enable payments via Apple Pay toggle. This will automatically configure your Stripe account to accept Apple Pay payments.

  4. That's it! If you visit a donation form on an iPhone, iPad, or other Apple Pay compatible device you'll now see Apple Pay as a payment option.

Frequently asked questions

Does Apple Pay work in embedded forms?

No, currently Apple Pay is only supported in standalone Beacon forms, but not in embedded forms. This is due to an Apple restriction unfortunately!

Why isn't the Apple Pay button showing?

The Apple Pay button will show automatically on your form if:

  • Apple Pay is enabled in Settings > Payments in your Beacon account

  • You're using Safari, on a Mac, iPad, or iPhone

  • A card is saved in your Apple "Wallet"

  • You're not viewing an embedded form (see above)

If you'd like to test Apple Pay on your device, you can go to this page from Stripe. In a few seconds, it will show a Apple Pay or Google Pay payment button at the top of the page.

Can Apple Pay be used for recurring donations?

Yes absolutely!

Did this answer your question?