GC Logo
Developer Docs

Guides

Collect Payments
Overview Integration Companion
Setting up MandatesDirect Debit Mandates Verified Mandates Collecting mandates offline Importing Mandates
One-off PaymentsOne-off Direct Debit Instant Bank Payment
Recurring PaymentsSubscription Instalments Variable Recurring Payments Instant Bank Payment + Direct Debit
Integration TypesGoCardless Hosted Pages Javascript Drop-in Flow Custom Payment Pages
Events & WebhooksMandate Events Billing Requests Events
Managing paymentsFX Payments Reconciling Payouts
Scheme guidanceACH and PAD Consent Types Billing Request Purpose Codes VRP Commercial Payment Purpose Codes PayTo Agreements and Payments

Integration Companion

View as Markdown

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?

  1. Create a Billing Request specifying your desired outcome

  2. Complete the required actions

  3. 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.

Hosted payment pages guide →

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.