Stripe
Overview
beabee integrates with Stripe for recurring payments. New payments, updates and cancellations are synced from Stripe to beabee so community organisers can track the revenue from their community. Emails such as payment failed and expired payment methods are automatically sent.
Setup
We need to create a product, API key and webhook inside Stripe. You will be given a URL by the beabee team to use during the setup
URL: https://<audience URL>/webhook/stripe
1. Add a new product

2. Give it a name (e.g. Membership), remove the price information and save it

3. Copy the product ID and send it to the beabee team

4. Add a new webhook endpoint

5. Use the endpoint URL that you received from the beabee team and the description "beabee live". Select the following 7 events to listen to:
customer.deleted
customer.subscription.updated
customer.subscription.deleted
invoice.created
invoice.paid
invoice.updated
payment_method.detached

6. Reveal the webhook signing secret, copy it and send it to the beabee team

7. Create a new secret API key

8. Give it the name "beabee live"

9. Copy the secret API key and send it back to the beabee team. This token should be kept secret and sent to the team securely, anyone who has it could create payments on your account.

10. Copy the publishable API key and send it back to the beabee team

11. (Optional) Configure how you want subscriptions to handle things like failed payments

12. We recommend marking subscriptions as unpaid if a payment fails as this means Stripe will continue to try to bill a user next month.

Emails
Stripe can automatically send emails for certain events, or beabee can handle sending them (to do). If you are using Stripe you should add your domain to your Stripe account.
Stripe email settings can be found here:
General email settings: https://dashboard.stripe.com/settings/emails
Subscription email settings: https://dashboard.stripe.com/settings/billing/automatic
General emails
One-off payment successful
Recurring payment successful
Payment failed
Payment method expiring
Bacs direct debit emails
The Bacs direct debit scheme has specific requirements for emails:
Confirmation of sign up: Sent when payment details are initially setup
Advanced notice of payment: sent two days before a payment. If the amount and period don't change this is not necessary
The above can be combined into one email if the initial payment is within a month
Stripe has specific requirements for allowing customers to handle their own emails, you can find more details here: https://stripe.com/docs/payments/bacs-debit/email-customization#approval-process
SEPA direct debit emails
The SEPA direct debit scheme has specific requirements for emails:
Advanced notice of payment: must be sent for all payments
There are specific requirements for these emails, you can find more details here: https://stripe.com/docs/payments/sepa-debit#debit-notification-emails
Last updated
Was this helpful?