OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Structured payment records are available for the authorized merchant.
Payment API reference ↗
List payments; Get a single payment · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Follow payment-list cursors to traverse the permitted collection.
Payment API reference ↗
List payments > meta.cursors; limit; before; after · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Customer, mandate, creditor, status and creation-time filters are documented.
Payment API reference ↗
List payments > Query parameters · Checked 2026-10-16
Access cost barrier -
-
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Send your first API request ↗
Creating a billing request > Create your first billing request · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
Send your first API request ↗
Creating a billing request > Create your first billing request · Checked 2026-10-16
Downstream permission -
-
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Send your first API request ↗
Creating a billing request > Create your first billing request · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Payment creation and metadata updates are documented; update scope is metadata, not arbitrary payment edits.
Payment API reference ↗
Create a payment; Update a payment · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Customer integrations use the documented API and token; third-party distribution eligibility is assessed separately.
Send your first API request ↗
Creating a billing request; Next steps · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Resource events and webhooks support refresh; no source-database CDC claim is made.
Event API reference ↗
Event; List events · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Numeric request limits, reset headers, 429 handling and creation idempotency guidance are published.
Limits and Safeguards ↗
Rate limiting; Timeouts; Idempotency keys · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Payment events identify state changes. Complete deleted-record identity and payload coverage is not established.
Event API reference ↗
Event; links.payment; action · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Repeat complete authorized payment-list traversal to rebuild selected current state. Event-retention limits, deleted payloads and intermediate-state recovery remain unestablished.
Payment API reference ↗
List payments > before; after; meta.cursors · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Structured payment responses can be retained externally.
Payment API reference ↗
List payments > Response 200 · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
A customer cancellation retrieval window and any exit charges have not been established.
Send your first API request ↗
Creating a billing request > Create your first billing request · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Portable selected payment records do not prove full scheme-document, account or historical-state export.
Payment API reference ↗
List payments > Response 200 · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
External client code implements custom payment workflows; native definition portability is unestablished.
Send your first API request ↗
Creating a billing request · Checked 2026-10-16
Rights to custom logic -
-
GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Send your first API request ↗
Creating a billing request > Create your first billing request · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A merchant copies an API access token from the dashboard and sends it as a Bearer token. A partner application uses OAuth to obtain authorization for each merchant; possession of a payer mandate does not establish application-distribution eligibility.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The payments list is cursor-paginated and accepts customer, creditor, mandate, status and creation-time selection. Event resources identify affected payments and actions; an event cursor is not a transactionally frozen copy of every merchant object.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| GoCardless customer API | API key | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
| GoCardless partner merchant OAuth | OAuth 2.0 | Integration provider | Not confirmed | Not confirmed | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /payments creates a payment against an eligible mandate, and PUT /payments/{payment_id} updates metadata. The metadata edit does not change the payment amount or authorize a new debit; create requests support Idempotency-Key and conflict responses identify a previously created resource.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Payment state changes produce webhooks and the Events API provides iterable event records. Native coverage and retention must be checked per resource; payment lists allow rebuilding selected present payment state, while complete deletion-payload recovery is unestablished.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Payment events identify state changes. Complete deleted-record identity and payload coverage is not established. | Event API reference ↗Event; links.payment; actionChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Repeat complete authorized payment-list traversal to rebuild selected current state. Event-retention limits, deleted payloads and intermediate-state recovery remain unestablished. | Payment API reference ↗List payments > before; after; meta.cursorsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
The merchant integration can retain structured payment and event records outside GoCardless. This does not establish full bank-account secrets, all scheme documents, historical versions or a restorable merchant configuration.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External integration code can implement customer rules against the documented APIs (with payment permissions and mandates enforced separately). Native workflow ownership and independent execution remain unresolved.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Structured payment records are available for the authorized merchant. | Payment API reference ↗List payments; Get a single paymentChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Follow payment-list cursors to traverse the permitted collection. | Payment API reference ↗List payments > meta.cursors; limit; before; afterChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Customer, mandate, creditor, status and creation-time filters are documented. | Payment API reference ↗List payments > Query parametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | Send your first API request ↗Creating a billing request > Create your first billing requestChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Send your first API request ↗Creating a billing request > Create your first billing requestChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Send your first API request ↗Creating a billing request > Create your first billing requestChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Payment creation and metadata updates are documented; update scope is metadata, not arbitrary payment edits. | Payment API reference ↗Create a payment; Update a paymentChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Customer integrations use the documented API and token; third-party distribution eligibility is assessed separately. | Send your first API request ↗Creating a billing request; Next stepsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Resource events and webhooks support refresh; no source-database CDC claim is made. | Event API reference ↗Event; List eventsChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Numeric request limits, reset headers, 429 handling and creation idempotency guidance are published. | Limits and Safeguards ↗Rate limiting; Timeouts; Idempotency keysChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Structured payment responses can be retained externally. | Payment API reference ↗List payments > Response 200Checked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. A customer cancellation retrieval window and any exit charges have not been established. | Send your first API request ↗Creating a billing request > Create your first billing requestChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. External client code implements custom payment workflows; native definition portability is unestablished. | Send your first API request ↗Creating a billing requestChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -GoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Send your first API request ↗Creating a billing request > Create your first billing requestChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGoCardless Payments API for a merchant’s payments, payment metadata and resource events; Bank Account Data, outbound payments and platform onboarding are separate scopes. Portable selected payment records do not prove full scheme-document, account or historical-state export. | Payment API reference ↗List payments > Response 200Checked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.