Guides
Setting up Mandates
Direct Debit Mandates Verified Mandates Collecting mandates offline Importing MandatesSend an outbound payment
Adding a new recipient Initiate an outbound payment Approve an outbound payment Cancel an outbound paymentSetting up mandates / collecting payments
Billing Request with Actions: Setting up a Direct Debit mandate Collecting a Direct Debit payment Billing Request with Actions: Taking an Instant Bank Payment Billing Request with Actions Dual Flow: Taking an Instant Bank Payment and setting up a Direct Debit mandateIntegration Companion
Plan your GoCardless integration from end to end. Get oriented with the Billing Request — the API that powers our payment flows — then choose the integration path that suits your team and use the interactive guide below to map out the exact steps you'll need to build.
The Billing Request API
What is a Billing Request?
A Billing Request helps create resources that require input or action from a customer. This single API supports all geographies and features offered by GoCardless.
What to use it for?
Set up a Direct Debit, PayTo, or VRP mandate; take a one-off Instant Bank Payment via Open Banking; or combine both.
How it works?
Create a Billing Request specifying your desired outcome
Complete the required actions
Use the Billing Request Flow to complete any remaining actions
Integration paths
Pick the approach that fits the level of control you want over the customer experience.
Simplest
Hosted payment pages
GoCardless handles the full customer UX. You redirect your customer to a GoCardless-hosted page to complete their mandate or payment authorisation, then we redirect them back.
Best for: Getting live quickly with minimal frontend work.
JavaScript Drop-in flow
Embed a GoCardless-managed modal directly into your page. Customers complete the payment flow without leaving your site, while GoCardless handles the UX inside the drop-in.
Best for: Keeping customers on your site with minimal integration effort
Most flexible
Custom payment pages
You own the full customer UX and call the GoCardless API directly at each step. Requires more development effort but gives you complete control over design and flow.
Best for: Teams with engineering resources who want a fully branded experience.