No payouts until verified
Your account must be fully verified to receive a payout. GoCardless may also suspend services while verification is in progress or if it cannot be completed. [6]
Guides · payments · Popular APIs
Sandbox and live GoCardless accounts, each with its own read-write access token and webhook endpoint secret. Live payouts wait until GoCardless has verified the business, its people and its bank account.
Researched · not yet run liveLast researched 25 October 2026 · GoCardless · provider site
Sandbox and live are completely separate GoCardless accounts, each with its own dashboard, access tokens, webhook endpoints and API base URL.
Partner integrations (acting for other merchants) have their own go-live checklist and app credentials.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
You sign up for a free sandbox account yourself.
Where: https://manage-sandbox.gocardless.com/
In the sandbox dashboard, open the Developers tab, create an access token, name it and pick Read-Write. Copy it now; it cannot be viewed again.
verapli captures GOCARDLESS_SANDBOX_ACCESS_TOKEN here by plain code: encrypted in your browser, never shown to AI.
Where: https://manage-sandbox.gocardless.com/
Add an HTTPS endpoint URL and a name in the sandbox dashboard, then open the endpoint and copy its secret.
verapli captures GOCARDLESS_SANDBOX_WEBHOOK_SECRET here by plain code: encrypted in your browser, never shown to AI.
Where: https://manage-sandbox.gocardless.com/
You create the live GoCardless account and fill in the onboarding form yourself (or with your GoCardless Account Executive).
Where: https://manage.gocardless.com/
GoCardless checks the business and at least one individual, and verifies the payout bank account with a small verification payment or a bank statement. Collected funds are not paid out until this is complete.
If you build your own payment pages, GoCardless's compliance team must approve them before you take real payments.
In the live dashboard Developers tab, create a Read-Write access token and copy it; it cannot be viewed again. Change your base URL to https://api.gocardless.com.
verapli captures GOCARDLESS_ACCESS_TOKEN here by plain code: encrypted in your browser, never shown to AI.
Where: https://manage.gocardless.com/
Repeat the webhook setup in the live dashboard and copy the live endpoint secret.
verapli captures GOCARDLESS_WEBHOOK_SECRET here by plain code: encrypted in your browser, never shown to AI.
Where: https://manage.gocardless.com/
Plain-English summary, not legal advice. Each card links its source.
Your account must be fully verified to receive a payout. GoCardless may also suspend services while verification is in progress or if it cannot be completed. [6]
Restricted activities include payday loans, money remittance, currency conversion, debt recovery, unregulated financial advice, crowdfunding and investment opportunities, gambling and lotteries, cryptocurrency, adult entertainment and dating, counterfeit goods, pyramid schemes, firearms, buying social followers, outbound telemarketing, and the travel industry (tour operators, airlines, travel agents). A breach can lead to suspension. [7]
You indemnify GoCardless for chargebacks, claims and refunds initiated by your customers, and for losses from restricted activity or your breach of the terms. [8]
A read-write access token gives full API access and cannot be viewed again after creation. Keep it out of source control. [1]
GoCardless handles all verification communication in writing, not by phone. [5]
| Env var | Secret | Format | What it is |
|---|---|---|---|
GOCARDLESS_SANDBOX_ACCESS_TOKEN | secret | Read-write access token for the sandbox (api-sandbox.gocardless.com) | |
GOCARDLESS_SANDBOX_WEBHOOK_SECRET | secret | Sandbox webhook endpoint secret for checking Webhook-Signature | |
GOCARDLESS_ACCESS_TOKEN | secret | Read-write access token for live (api.gocardless.com) | |
GOCARDLESS_WEBHOOK_SECRET | secret | Live webhook endpoint secret for checking Webhook-Signature |
Source [9]
The same entry as JSON: /api/v1/entries/gocardless/api · requirements /api/v1/requirements/gocardless/api · terms /api/v1/terms/gocardless/api.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for GoCardless API, and how long will it take?"
→ tools/call requirements { "provider_id": "gocardless/api" }Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. GoCardless is not affiliated with verapli.