slug: trustly
provider: Trustly Group
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: Customers
  spec_file: trustly-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: POST /customers 'Create or Update a Customer'; GET /customers/{customerId} 'Get Customer by
    ID'; schemas Customer, Address, DriverLicense, CustomerCustomData
  reason: Full CRUD over customer records with identity attributes (address, driver licence, custom data)
    is maintenance of the customer master record. Confidence 0.7 rather than higher because in a payments
    context these records may serve onboarding/KYC purposes as much as a golden customer record.
- tag: Transactions
  spec_file: trustly-transactions-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: POST /transactions/{transactionId}/capture 'Capture transaction'; POST /transactions/{transactionId}/capture/preAuth
    'Preauthorize transaction'; POST /transactions/{transactionId}/refund 'Refund transaction'; POST /transactions/{transactionId}/deposit
    'Deposit transaction'
  reason: Authorise, capture, refund and reclaim operations are the core money-movement lifecycle for
    collecting payment from a customer, matching the 'payment authorisation' element of Payment Collection
    & Dunning. Held at 0.7 because the capability's L1 is framed around subscription billing whereas this
    is a general payment-acceptance API.