slug: braintree
provider: Braintree
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: braintree-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.85
  evidence: POST /subscriptions  createSubscription; PUT /subscriptions/{subscriptionId}  updateSubscription;
    PUT /subscriptions/{subscriptionId}/cancel  cancelSubscription
  reason: Create, modify and cancel recurring subscriptions is squarely subscription lifecycle management.
    Left at L1 because the operations span provisioning, in-life modification and cancellation rather
    than naming a single sub-capability.
- tag: Payment Methods
  spec_file: braintree-payment-methods-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.72
  evidence: POST /payment_methods  createPaymentMethod  Create a payment method; DELETE /payment_methods/any/{paymentMethodToken}  deletePaymentMethod
  reason: Lifecycle of stored/tokenised payment instruments for a customer — explicitly the 'payment-method
    management' element of payment collection. The frame's nearest honest home for a payment gateway's
    vault surface.
- tag: Transactions
  spec_file: braintree-transactions-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.72
  evidence: POST /transactions  createTransaction; PUT /transactions/{transactionId}/submit_for_settlement  Submit
    transaction for settlement; POST /transactions/{transactionId}/refund  refundTransaction
  reason: Authorisation, settlement, void and refund of card payments — payment authorisation and collection.
    Mapped to the collection sub-capability as the closest fit in this frame; gateway settlement mechanics
    are not a perfect match, hence 0.72 rather than higher.
- tag: Customers
  spec_file: braintree-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  Create a customer; PUT /customers/{customerId}  updateCustomer;
    schemas: CustomerRequest, Customer, PaymentMethod, Address'
  reason: Full CRUD over a customer master record (identity, address, attached payment methods) in Braintree's
    vault — this realises customer data/master-record management. Not raised higher because the record
    exists primarily to support payment processing rather than broader CRM lifecycle.