Membership and finance blocks let a form sell memberships, create subscriptions, take payments and let contacts pay down balances. They are typically used together — a Subscription block paired with a Payment Method block.
Subscription block
The Subscription block exposes membership plans for respondents to select. Configure:
- Available Plans — the plans offered on the form. These must be pre-configured in SwiftFox. If no plans appear, set them up in your account first.
- Default subscription status — choose Active or On Hold for the subscription created on submission.
- Payment settings:
- Show Auto-renew — display the auto-renew option to respondents.
- Default Auto-renew — the default auto-renew setting.
- Default plan — the plan selected by default.
- Take immediate payment vs save payment method — choose whether to charge now or store the payment method for later.
The Subscription block is typically paired with a Payment Method block to collect payment details.
Payment Method block
The Payment Method block collects how the respondent pays. Select the block on the canvas, then configure its Payment settings in the right-hand panel:
- Payment provider type — choose which of your account's configured payment providers the respondent can pay with. The list shows only the providers set up on your account (for example a Stripe credit card option or a direct debit option), so it differs between accounts.
- Allow discount codes — let respondents apply discount codes. When a code brings the total to $0 (a 100% discount), the form clearly confirms the discount is in effect and shows which plan option it applies to, so respondents aren't left wondering whether the code worked.
- Fees — click Add to add a fee.
Invoicing
- Enable organisation billing — raise the invoice against the respondent's organisation rather than the person.
- Allow invoice as payment method — offer an invoice as a way to pay.
- Invoice reference — the reference displayed on the invoice. Allow user to input a reference number (Disabled, Optional or Required) controls whether the respondent supplies their own.
- Due date — the number of days from when the form is submitted until the invoice is due.
- Integrations — if you use Xero, select it here so invoices are generated in Xero.
Full detail on invoicing, organisation billing and the Xero mappings: Enabling invoicing on a standard Form (Payment Method block) (Document ID: 275).
Advanced options
Choose one of these two options:
- Always capture payment method — always collect and store the payment method.
- Don't ask for payment details if total is 0 — skip payment collection when the order total is zero (useful for free or fully discounted submissions).
Advanced options also shows the question IDs the block uses for the payer's first name, last name and email (Question ID of First name, Question ID of Last name, Question ID of Email).
Conditional settings
Use Conditional settings to show the Payment Method block only when an earlier answer meets a condition: choose the Conditional question, the Required answer and the Operator, and use Add Condition for more. The block only appears if all the conditions are met.
Transaction block
The Transaction block takes a one-off payment or donation on the form — for example a set of donation amount buttons ($100 / $500 / $1,000) plus an Other amount option. You can set a default value for the block (such as a commonly used donation amount — see Setting default answers on form questions (Document ID: 371)). Pair it with a Payment Method block to collect payment details.
Account Payment block
The Account Payment block shows the contact their account statement/summary and lets them pay off amounts — including subscriptions and arrears (outstanding balances).
Use Account Payment when you want members to view what they owe and settle balances directly through the form.
Membership data block
Do not use the Membership data block (see Forms — Limitations & best practice (Document ID: 204)).