slug: recharge-payments
provider: Recharge
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: 5
edges:
- tag: Subscriptions
  spec_file: recharge-payments-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.92
  evidence: POST /subscriptions/{id}/cancel cancelSubscription; POST /subscriptions/{id}/activate Activate
    a cancelled subscription; POST /subscriptions/{id}/change_next_charge_date
  reason: Operations create, modify, cancel and reactivate subscriptions — the end-to-end subscription
    commercial lifecycle. Spans provisioning, modification and cancellation sub-capabilities, so L1 only.
- tag: Payment Methods
  spec_file: recharge-payments-payment-methods-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.85
  evidence: POST /payment_methods createPaymentMethod Create a payment method; schema PaymentMethod
  reason: Stored payment instruments used to collect recurring subscription charges — directly the 'payment-method
    management' element of Payment Collection & Dunning in a subscription billing platform.
- tag: Customers
  spec_file: recharge-payments-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: 'POST /customers createCustomer; schema: Customer; GET /customers/{id}/delivery_schedule'
  reason: Create/read/update/delete of customer records that anchor subscriptions — customer master record
    management. Subscription context could also argue for subscription lifecycle, but the operations are
    plainly customer data CRUD.
- tag: Charges
  spec_file: recharge-payments-charges-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /charges/{id}/process processCharge — Process a charge; POST /charges/{id}/refund refundCharge
  reason: 'Recurring-billing charge lifecycle: processing, skipping, refunding and discounting of charges
    against subscriptions. Clearly Subscription Billing & Revenue Management; the process/refund emphasis
    points to payment collection, though invoicing is an alternative sub-capability reading.'
- tag: Discounts
  spec_file: recharge-payments-discounts-api-openapi.yml
  capability_id: BC-440.30
  capability_id_l1: BC-440
  capability_name: Discount & Promotion Management
  confidence: 0.7
  evidence: 'POST /discounts createDiscount — Create a discount; schema: Discount'
  reason: Lifecycle management of discount definitions applied to subscription orders, matching Discount
    & Promotion Management. Alternative reading is rating/charging within subscription billing, so confidence
    is moderate.