Payments
Collect payments online with Stripe, PayPal, or GoCardless, and custom payment methods and processors.
Overview
A payment is an attempt to settle one or more invoices. A single payment can be linked to multiple invoices, for example when a member is settling a tab or has run up a debt. Payments have their own lifecycle (pending, processing, succeeded, and so on), separate from the invoice's financial status.
Staff can see the payments made on each invoice in the admin dashboard. The same records are available on the Payments API.
Payment statuses
| Status | Meaning |
|---|---|
| Pending | A custom payment method awaiting capture |
| Requires payment method | Collection cannot continue without a usable method. This can happen in rare cases where a payment processor rejects a payment method. |
| Requires action | The member must complete authentication (for example 3DS). |
| Processing | Delayed settlement methods (Bacs Direct Debit, ACH, SEPA, and similar) are settling (these payment types can take multiple business days to settle). |
| Succeeded | Funds collected successfully. |
| Failed | The payment attempt failed. See failure code and message when present |
| Canceled | The attempt was cancelled before success, used for custom payment methods. |
Payment processors
Members is deliberately payment processor agnostic, and can collects online payments through different payment processors:
- Stripe
- PayPal
- GoCardless
- Adyen (contact support)
- Worldpay (contact support)
- Checkout.com (contact support)
- Others (see Custom payment methods or contact support)
Members will automatically use the payment processor to charge the member's payment method when you charge the member on the dashboard.
Unlike other platforms, we never lock down your access to the raw payment data. You can connect an existing account to your Members organization, and see your payments via the processor dashboard as well.
For cash, cheque, bank transfer, or your own processor, use custom payment methods. Those create pending payments that staff (or your integration) confirm when money is received.
Payment methods
Through payment processors, Members can surface various payment methods for you or the member to choose from.
For example, Stripe documents 125+ payment methods that you can use. Most methods will be disabled by default and availability depends on factors like you Stripe account country, customer's country, and your Stripe preferences. Common categories include:
| Category | Examples |
|---|---|
| Cards | Visa, Mastercard, American Express, Discover, and other networks Stripe supports |
| Wallets | Apple Pay, Google Pay, Link, Cash App Pay, Amazon Pay, PayPal (via Stripe where enabled), Alipay, WeChat Pay |
| Bank debits | ACH Direct Debit (US), SEPA Direct Debit, Bacs Direct Debit (UK), ACSS Debit (Canada), BECS / NZ bank debit where enabled |
| Bank redirects | iDEAL, Bancontact, Przelewy24, Sofort, EPS, and similar local redirect methods |
| Bank transfers | Customer balance and bank transfer rails Stripe offers for your region |
| Buy now, pay later | Klarna, Affirm, Afterpay / Clearpay |
| Real-time and vouchers | PayNow, PromptPay, Swish, TWINT, Konbini, OXXO, Boleto, and other local methods Stripe supports |
Saving payment methods
A payment method is a stored payment method on the member, typically a card or bank debit. Members ensures PCI compliance by letting the payment processor handle the raw payment method data, and only storeing a reference to the payment method.
One method can be the member's default, useful for faster checkout.
Subscriptions use a payment method on file for renewal payments. It can be the same or different to the member's default payment method, and can be changed at any time for future renewals.
By default, members can add or update their methods in the member website and app. This is generally the best way to manage payment methods, because it allows the member to complete authentication steps like 3DS or receiving a one-time code on their own device.
For API users, see the Payment Methods API, including generating sessions for online vaulting.
Member self-serve payment
Members can pay open invoices from the member website and app. They will see a list of invoices that are due, and can pay for one or all of them at once. They can add and remove their own payment methods as needed.
Failed payments and authentication
Failed attempts leave failure details on the payment when the provider returns them. Depending on your configuration, Members can remind the member and retry according to your dunning setup.
How payments affect subscriptions
A subscription stays in good standing only when outstanding invoices are paid. Until then, benefits tied to that payment stay unavailable.
For payments with a long procesing time, by default Members will allow a grace period while the payment is processed. However, if the payment fails, the subscription will immediately become overdue, and the grace period will not apply to future payments. This is to prevent members from abusing the grace period by repeatedly failing to pay.
For more pause, cancel, and overdue behaviour, see Managing Subscriptions.