slug: payt
provider: Payt
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: 7
edges:
- tag: Invoices
  spec_file: payt-invoices-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.9
  evidence: POST /v1/invoices 'Upsert invoices in bulk'; PATCH /v1/invoices/block 'Block invoices'; schema
    CustomerApi_V1_InvoiceLineEntity
  reason: Customer invoice lifecycle (create, update, block/resume from the dunning flow) inside an accounts-receivable
    platform — squarely customer invoicing and collections.
- tag: Debtors
  spec_file: payt-debtors-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.85
  evidence: POST /v1/debtors 'Create or update administration debtors'; schema CustomerApi_V1_DebtorEntity
  reason: Debtor master records in an accounts-receivable collections platform; creating and retrieving
    debtors is core customer/receivables accounting data supporting invoicing and collections.
- tag: Payment Plans
  spec_file: payt-payment-plans-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.8
  evidence: PATCH /v1/payment_plans/{id}/approve 'Approve a proposed payment plan'; schema CustomerApi_V1_PlannedPaymentEntity
  reason: Proposal, approval, rejection and deactivation of debtor instalment arrangements — a collections/receivables
    settlement mechanism in the vendor's AR workflow.
- tag: Payments
  spec_file: payt-payments-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.75
  evidence: GET /v1/payments 'Get administration payments'; schemas CustomerApi_V1_BankTransactionEntity,
    CustomerApi_V1_PspTransactionEntity on an 'accounts receivable management platform'
  reason: Payments received against debtor invoices in an AR/collections platform — cash application and
    collections under Accounts Receivable Management, not a general ledger or treasury function.
- tag: credit_cases
  spec_file: payt-credit-cases-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.75
  evidence: 'GET /v1/credit_cases ''Get administration credit_cases''; vendor runs ''the collections workflow:
    automated reminders, flexible payment plans, debt-collection cases'''
  reason: Credit/debt-collection cases against debtors are the collections element of Accounts Receivable
    Management.
- tag: Messages
  spec_file: payt-messages-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.7
  evidence: POST /v1/messages 'Send a message to a debtor'
  reason: Outbound debtor communication is the reminder/dunning correspondence of the collections workflow,
    part of accounts receivable management rather than generic messaging; some ambiguity as it could also
    be read as customer correspondence.
- tag: psp_transactions
  spec_file: payt-psp-transactions-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.7
  evidence: GET /v1/psp_transactions 'Get administration PSP transactions'; CustomerApi_V1_PspTransactionEntity
  reason: Payment service provider transactions collected against debtor invoices — cash collection/application
    within Accounts Receivable Management.