slug: gocardless
provider: GoCardless
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Banking & Capital Markets
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 7
edges:
- tag: payments
  spec_file: gocardless-payments-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.88
  evidence: POST /payments createPayment "Create a payment"; POST /payments/{id}/actions/cancel "Cancel
    a payment"
  reason: Direct creation, amendment and cancellation of payment instructions on bank debit rails — unambiguous
    payment initiation management.
- tag: mandates
  spec_file: gocardless-mandates-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.75
  evidence: POST /mandates createMandate, POST /mandates/{id}/actions/cancel cancelMandate "Cancel a mandate"
  reason: Direct debit mandate lifecycle — the payer's standing authorisation permitting collections.
    This is payment instruction authorisation management, core to BC-1340.10.
- tag: blocks
  spec_file: gocardless-blocks-api-openapi.yml
  capability_id: BC-1400.30
  capability_id_l1: BC-1400
  capability_name: Fraud Detection & Investigation Management
  confidence: 0.72
  evidence: POST /blocks createBlock Create a block (anti-fraud rule)
  reason: The operation summary explicitly labels a block as an anti-fraud rule on a payments platform,
    which is fraud detection/prevention. Evidence is a single annotated operation, hence moderate rather
    than high confidence.
- tag: billing_request_flows
  spec_file: gocardless-billing-request-flows-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.7
  evidence: POST /billing_request_flows createBillingRequestFlow Create a billing request flow (hosted
    authorization link)
  reason: The flow is a hosted authorisation journey through which a payer authorises a bank debit mandate/payment
    — payment instruction capture and authorisation. Confidence moderated because the object is a hosted
    UI flow wrapper rather than the payment instruction itself.
- tag: billing_requests
  spec_file: gocardless-billing-requests-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.7
  evidence: POST /billing_requests createBillingRequest Create a billing request; 'Subset of the public
    GoCardless REST API for collecting bank debit and open-banking payments'
  reason: Billing requests are the instruction objects used to collect a bank debit or open-banking payment,
    i.e. payment instruction capture and authorisation. Only three generic CRUD operations, so confidence
    held at moderate.
- tag: customers
  spec_file: gocardless-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: POST /customers createCustomer, PUT /customers/{id} updateCustomer "Update a customer"
  reason: Plain CRUD over customer master records (create, read, update, list) — customer data management.
    Generic enough that confidence is capped, but the operations are unambiguously customer record maintenance.
- tag: payer_authorisations
  spec_file: gocardless-payer-authorisations-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.7
  evidence: POST /payer_authorisations createPayerAuthorisation "Create a payer authorisation"
  reason: Captures the payer's authorisation to be debited, which is exactly payment instruction validation
    and authorisation.