slug: avaloq
provider: Avaloq
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: 3
edges:
- tag: Payments
  spec_file: avaloq-payments-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.82
  evidence: POST /v1/payments createPayment "Avaloq Create Payment Instruction"
  reason: Capture and listing of payment instructions is payment initiation within a core banking platform.
- tag: Payment Status
  spec_file: avaloq-payment-status-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.75
  evidence: GET /v1/payments/{paymentId} getPayment "Avaloq Get Payment Status"
  reason: Payment status retrieval is plainly payments management; too thin to pick between initiation
    and processing sub-capabilities.
- tag: Customers
  spec_file: avaloq-customers-api-openapi.yml
  capability_id: BC-1300.40
  capability_id_l1: BC-1300
  capability_name: Customer Information Management
  confidence: 0.7
  evidence: 'POST /v1/customers createCustomer "Avaloq Create Customer"; description: "account management,
    transactions, and customer data"'
  reason: Banking platform customer master records (create/list/get customer) realise banking customer
    information management; could arguably be onboarding, hence moderate confidence on the L2.