slug: upgrade
provider: Upgrade
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: 1
edges:
- tag: Transactions
  spec_file: upgrade-transactions-api-openapi.yml
  capability_id: BC-1340.70
  capability_id_l1: BC-1340
  capability_name: Card Transaction Processing Management
  confidence: 0.7
  evidence: '"POST /v1/transactions authorizeTransaction Authorize Transaction", "captureTransaction",
    "voidTransaction", "refundTransaction"; "the Transactions API (authorize, capture, void, refund —
    the Direct Settle disbursement model)"'
  reason: The classic card authorisation lifecycle — authorize, capture, void, refund — against the virtual-card
    payout rail, which is card transaction processing. Sub-capability choice between card transaction
    processing and general payment processing carries some residual ambiguity.