slug: mangopay
provider: Mangopay
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: Notifications
  spec_file: mangopay-notifications-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.8
  evidence: POST /hooks  Create a Hook; PUT /hooks/{hookId}  Update a Hook; GET /events  List all Events
  reason: Lifecycle management of outbound webhook (hook) subscriptions and the event stream delivered
    to integrating developers — exactly BC-4270.80 Webhook & Event Subscription Management on the platform-provider
    side.
- tag: UBO Declarations
  spec_file: mangopay-ubo-declarations-api-openapi.yml
  capability_id: BC-130.10
  capability_id_l1: BC-130
  capability_name: Regulatory Compliance Management
  confidence: 0.7
  evidence: POST /users/{userId}/kyc/ubodeclarations 'Create a UBO Declaration'; 'Submit a UBO Declaration';
    vendor describes 'KYC/KYB identity verification'
  reason: Ultimate Beneficial Owner declarations under the /kyc/ path are a statutory AML/KYC obligation
    for regulated payment institutions, so the operations realise regulatory compliance management rather
    than any customer-data or payment capability. Confidence held at 0.7 because the frame has no dedicated
    KYC/financial-crime capability and BC-130.10 is the nearest honest fit.