slug: chargedesk
provider: ChargeDesk
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
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: 4
edges:
- tag: Subscriptions
  spec_file: chargedesk-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.8
  evidence: POST /subscriptions  createSubscription  Create a subscription record; POST /subscriptions/{subscription_id}  updateSubscription  Update
    a subscription record
  reason: Create/read/update of subscription records on a recurring-billing platform is subscription lifecycle
    management. Operations are generic CRUD spanning creation and in-life change, so no single L2 is asserted.
- tag: Customers
  spec_file: chargedesk-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.72
  evidence: 'POST /customers  createCustomer  Create a customer record; GET /customers/grouped  getGroupedCustomers  Get
    structured billing history for customers; schemas: Customer, CustomerInput, BillingAddress'
  reason: CRUD over customer records with billing addresses is customer master data management. The grouped
    billing-history operation pulls slightly toward billing, so confidence is moderate rather than high.
- tag: Gateway
  spec_file: chargedesk-gateway-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /gateway/products/charge  gatewayCreateCharge  Create a live charge, subscription, or
    payment request via gateway; POST /gateway/charges/{charge_id}/refund  gatewayRefundCharge  Refund
    a charge via gateway; POST /gateway/charges/{charge_id}/capture  Capture an authorized charge via
    gateway
  reason: These operations authorise, capture, refund and void live payments through payment gateways,
    which is payment collection. Two operations also cancel and re-plan subscriptions, so the tag straddles
    subscription modification, limiting confidence in the single sub-capability.
- tag: Webhooks
  spec_file: chargedesk-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.7
  evidence: GET /webhooks listWebhooks List all webhooks; POST /webhooks createWebhook Create a webhook;
    DELETE /webhooks/{webhook_id} deleteWebhook
  reason: The tag exposes lifecycle management (list/create/delete) of outbound webhook subscriptions
    for an external developer integrating with ChargeDesk, which is exactly Webhook & Event Subscription
    Management in the developer-platform capability. It is deliberately not mapped to billing/payment
    capabilities since the operations manipulate subscription endpoints, not charges. Confidence held
    moderate because webhook plumbing can reasonably be treated as non-business infrastructure.