slug: payjp
provider: PAY.JP
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: Subscriptions
  spec_file: payjp-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.75
  evidence: POST /subscriptions createSubscription 'Create a subscription (定期課金)'; 'Pause a subscription';
    'Cancel a subscription'
  reason: Operations create, update, pause, resume and cancel recurring subscription objects — the in-life
    lifecycle of a subscription agreement. That is Subscription Lifecycle Management; the evidence spans
    provisioning, modification and cancellation so no single L2 is named. (It sits on a payment gateway,
    so some of this could equally be read as recurring billing, hence moderate confidence.)
- tag: Charges
  spec_file: payjp-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}/capture  captureCharge  Capture a previously authorized charge
  reason: Create, capture, re-authorise and refund of charges is payment authorisation and collection
    against a customer's payment method. BC-4250.40 is the only candidate covering payment authorisation;
    the subscription framing of the parent limits confidence.