slug: aza-finance
provider: AZA Finance
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: 6
edges:
- tag: Payout Methods
  spec_file: aza-finance-payout-methods-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.8
  evidence: '"Creating a payout method"; schemas PayoutMethodDetailsIBAN, PayoutMethodDetailsNGNBank,
    PayoutMethodDetailsMobile, PayoutMethodDetailsXOFCash'
  reason: Defines and maintains the destination instruments (IBAN, local bank, mobile wallet, cash) used
    to disburse payments — clearly payments and card management at L1.
- tag: Payin Methods
  spec_file: aza-finance-payin-methods-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.75
  evidence: '"Fetching a payin method", "Retries PayinMethod"; schemas PayinMethodDetailsNGNBank, PayinMethodDetailsMobile'
  reason: Manages the instruments by which funds are collected (bank, mobile money) for a transfer — payments
    capability. Evidence does not clearly single out initiation vs processing, so L1 only.
- tag: Payment Methods
  spec_file: aza-finance-payment-methods-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.7
  evidence: '"This method returns possible payin methods." / "This method returns possible payout methods."'
  reason: Reference catalogue of supported pay-in/pay-out rails and their field validations — payments
    domain, but too generic to pin a sub-capability.
- tag: Senders
  spec_file: aza-finance-senders-api-openapi.yml
  capability_id: BC-1300
  capability_id_l1: BC-1300
  capability_name: Banking Customer Management
  confidence: 0.7
  evidence: '"Creating a sender"; schemas Sender, Document, PoliticallyExposedPerson, SenderState'
  reason: Sender records carry identity documents and PEP flags and move through states — onboarding/customer
    information for a regulated financial provider. Ambiguous between onboarding, KYC and customer information,
    so L1 only.
- tag: Transactions
  spec_file: aza-finance-transactions-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.7
  evidence: '"Creates a new transaction", "Validates a transaction payload", "Calculates transaction amounts",
    "Creates a new transaction and funds it from account balance"'
  reason: Core capture, validation, calculation and funding of payment instructions — payment initiation.
    Could arguably be cross-border payment management given the vendor's Africa corridors, hence 0.7.
- tag: Webhooks
  spec_file: aza-finance-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.7
  evidence: '"Creating a webhook", "Unsubscribing from a webhook", "Find possible webhook events"; schemas
    WebhookDefinitionResponse, TransactionWebhook'
  reason: Outbound event subscription lifecycle on a developer platform — matches webhook & event subscription
    management; no banking business capability is realised.