Describe your publication, prices, and delivery options. Makeform creates a signup that captures subscriber details, records the plan, and sends the payer to GoCardless-hosted direct debit authorization.
Route subscriptions to GoCardless, Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a publishing model, tailor its prompt, or send it to the Makeform builder. Examples are starting structures, not live payment results.
Audience
Readers subscribing to a recurring print magazine
Format
Plan and delivery form with direct debit handoff
Prompt size
309 chars
Example form structure
Plan and delivery form with direct debit handoff
Subscriber name and contact details
Where should we deliver the magazine?
Choose monthly or annual billing
Which issue should start the subscription?
Accept terms and continue to direct debit
Suggested routing tags
Mandate pending
Subscription active
Fulfilment review
Keep bank details out of text fields. Use GoCardless-hosted authorization, then store the returned customer, mandate, and subscription references.
Step 1
Choose
edition, term, start issue
Step 2
Subscribe
reader and delivery details
Step 3
Authorize
GoCardless direct debit
Step 4
Fulfil
subscriber enters circulation
Built for recurring circulation
Keep plan, delivery, authorization state, and payment references in one record.
Show each option's price, frequency, included issues, and renewal pattern. Conditional sections request only relevant details.
After order review, create a GoCardless billing request and redirect to hosted authorization without handling raw bank details.
Use returned states to separate incomplete signups from confirmed subscriptions, then route fulfilment details to circulation.
Publishing models
Change plan labels, cadence, issue count, delivery rules, and routing.
Capture address, start issue, region, and collection choice for home delivery.
Use the account email as the fulfilment key and activate access after confirmation.
Separate payer and recipient while collecting a message, announcement date, and issue term.
Add company, quantity, invoice reference, and delivery contact for bulk copies.
Subscription workflow
Design the reader journey, GoCardless authorization, and fulfilment handoff together.
Specify editions, territories, frequency, prices, terms, delivery formats, and available start issues.
Branch print and digital questions, separate gift purchaser from recipient, and show the order summary before acceptance.
Map plan amount and cadence into hosted authorization, then return customer, mandate, payment, and subscription references.
Notify circulation on confirmation. Route failed, cancelled, or incomplete mandates to review instead of delivery.
Choose the right setup
Connect product and delivery details to recurring payment without manual matching.
Field guide
These six sections create a complete order and a record circulation can use after authorization.
Subscriber identity
Collect structured subscriber contact details. For gifts or companies, separate the payer from the recipient or fulfilment contact.
Plan selection
Show edition, format, issue count, price, collection cadence, and renewal pattern together before authorization.
Delivery setup
Print needs an address, region, quantity, and first issue. Digital needs the email or account identifier receiving access.
Consent and terms
Place the order summary and terms before acceptance. Keep optional marketing consent separate and link to privacy information.
GoCardless authorization
After order confirmation, redirect to GoCardless for bank authorization and return to a status page. Do not collect bank details in form fields.
Status and operations
Submission starts signup but does not prove authorization finished. Define which confirmed state creates circulation, welcome, and first-issue tasks.
Related tools
Build general subscriptions, another payment route, cancellations, newsletter opt-ins, or one-off payments.
FAQ
Answers about recurring signups, direct debit authorization, and circulation.
It collects plan, subscriber, delivery, start-issue, and acceptance details, then sends the payer to GoCardless for direct debit authorization. Returned customer, mandate, and subscription references help circulation distinguish started signups from confirmed subscriptions.
Do not put bank details in ordinary fields. Collect the order, redirect to GoCardless-hosted authorization, then return the reader to a confirmation or pending page. Keep the references and statuses needed for reconciliation.
Yes. Give each plan a label, amount, currency, issue entitlement, collection frequency, and renewal description. Map each choice to its GoCardless billing configuration and show the final amount and cadence before acceptance.
Separate purchaser and recipient. The purchaser authorizes payment; recipient, address, gift message, announcement preference, and first issue go to fulfilment. For a fixed term, state the issue count and what happens afterward.
Activate from a defined payment-workflow status, not form submission alone. Keep incomplete or failed authorizations in review. On confirmation, update circulation with edition, address, quantity, and first issue.
Yes. Print and bundle readers can see delivery, region, and first-issue questions; digital readers see account email. Both paths share contact details, plan summary, acceptance, and GoCardless authorization.
Yes. Makeform is unlimited free for generating, editing, and publishing forms. The paid tier removes the Makeform badge. GoCardless account pricing, supported schemes, and terms are separate.
Link payment events to the subscriber and route exceptions to a named queue. A cancellation or failure can notify circulation, pause fulfilment, and trigger a service message. Preserve status history for review.
Turn interest into a subscription.
