For customers using Stripe as their payment gateway, MembershipWorks now supports Stripe Elements, which allows your members check out with Apple Pay, Google Pay, Amazon Pay, Cash App Pay, Link and more. This provides your members with more payment options and improves ease of use on desktop and mobile devices, thereby increasing conversions for your organization.

There are no additional MembershipWorks fees to process payments through these other payment methods, however do note that transaction processing fees assessed by Stripe do apply. Please check the following Stripe page for more information:
https://stripe.com/pricing/local-payment-methods
The payments are fully processed through your Stripe account – no additional accounts are required (ie. you do not need a Cash App account to accept Cash App payments). The payment methods available to your members are based on the default payment method configuration in your Stripe account. To enable or disable payment methods:
- Sign in to your Stripe account
- Navigate to Settings > Payments > Payment Methods
- Click on the payment method configuration labelled “Default / MembershipWorks configuration”
- Payment methods can be enabled or disabled on this screen
Note that even if you enable a payment method, it may not be available in certain situations:
- Apple Pay will only appear on an Apple device/browser, and Google Pay will only appear on a Chrome browser.
- Apple Pay or Google Pay methods will not appear if member is not signed in to a Apple or Google account on that browser, or if there are no cards stored in their Apple or Google account wallet.
- Certain payment methods cannot be used for automatic recurring billing.
- Certain payment method are only available for specific countries or currencies (please refer to https://docs.stripe.com/payments/payment-methods/payment-method-support)
Note that MembershipWorks does not yet support payment methods that cannot be captured immediately, such as bank transfers. Support for such payment methods will be released in an upcoming update.



Comments are closed.