slug: n3xt
provider: N3XT
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: 2
edges:
- tag: Payments
  spec_file: n3xt-payments-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.9
  evidence: POST /payments/instant 'Instant Payment'; POST /payments/request 'Request Payment'; PATCH
    /payments/request/{id} 'Update Payment Request Status'; schemas InstantPaymentRequest, PaymentStatusEnum
  reason: Operations capture, submit and track payment instructions and payment requests — plainly payment
    initiation for a payments bank; real-time rail relevance is secondary but initiation dominates the
    surface.
- tag: Programmable
  spec_file: n3xt-programmable-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.75
  evidence: POST /payments/programmable 'Create Programmable Payment Request'; PUT /payments/programmable/{id}/fulfillment
    'Fulfill Programmable Payment Delivery'; PUT .../cancellation 'Cancel Programmable Payment'
  reason: Creation, fulfilment and cancellation of conditional payment instructions is payment instruction
    capture and authorisation; slight ambiguity as the fulfilment/settlement leg could also be read as
    payment processing.