slug: tap-payments
provider: Tap Payments
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: 2
edges:
- tag: Charges
  spec_file: tap-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  createCharge  Create a charge; schemas Charge, ChargeInput, Source, Redirect
  reason: Creating and tracking charges is the act of collecting a payment from a customer through the
    gateway. Payment Collection is the closest candidate; confidence tempered because the L1 is framed
    around SaaS subscription billing while Tap is a general-purpose acquirer.
- tag: Customers
  spec_file: tap-payments-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; PUT /customers/{customer_id}  updateCustomer; schemas Customer,
    CustomerInput
  reason: Full CRUD over customer master records used across charges, cards and invoices — this is maintenance
    of the customer record itself rather than a billing or servicing action.