slug: visa-acceptance
provider: Visa Acceptance
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: 3
edges:
- tag: Captures
  spec_file: visa-acceptance-captures-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /pts/v2/payments/{paymentId}/captures  capturePayment  Capture Payment
  reason: Card payment capture is payment collection/authorisation processing; closest available candidate
    in this Software & Technology frame is Payment Collection & Dunning, though the frame lacks a true
    merchant-payment-acceptance capability, so confidence is moderate.
- tag: Invoices
  spec_file: visa-acceptance-invoices-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.7
  evidence: POST /pts/v2/invoices  createInvoice  Create Invoice
  reason: Operations create, list, retrieve and update customer invoices with LineItem schemas — invoice
    generation and delivery. Could also read as BC-200.30 Accounts Receivable; moderate confidence on
    the sub-capability choice.
- tag: Payments
  spec_file: visa-acceptance-payments-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /pts/v2/payments  authorizePayment  Authorize Payment
  reason: Card authorization and reversal — payment authorisation and collection. Best available fit is
    Payment Collection & Dunning; frame lacks a merchant acquiring capability.