slug: lightspark
provider: Lightspark
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: 7
edges:
- tag: KYC/KYB Verifications
  spec_file: lightspark-kyc-kyb-verifications-api-openapi.yml
  capability_id: BC-1300.20
  capability_id_l1: BC-1300
  capability_name: KYC & Customer Due Diligence Management
  confidence: 0.95
  evidence: POST /verifications createVerification 'Submit customer for verification'; POST /customers/{customerId}/kyc-link
    'Generate a hosted KYC link'; schemas BeneficialOwner, KycProvider, VerificationStatus
  reason: Operations perform customer identity verification and beneficial-owner collection — the definition
    of KYC/CDD for a financial services provider.
- tag: Cards
  spec_file: lightspark-cards-api-openapi.yml
  capability_id: BC-1340.60
  capability_id_l1: BC-1340
  capability_name: Card Issuance Management
  confidence: 0.92
  evidence: POST /cards createCard 'Issue a card'; POST /cards/{id}/reveal 'Reveal card details'; schemas
    CardState, CardBrand, CardForm
  reason: Operations issue, update and activate/reveal payment cards — card issuance lifecycle, not transaction
    switching.
- tag: Cross-Currency Transfers
  spec_file: lightspark-cross-currency-transfers-api-openapi.yml
  capability_id: BC-1340.40
  capability_id_l1: BC-1340
  capability_name: Cross-Border Payment Management
  confidence: 0.85
  evidence: GET /receiver/uma/{receiverUmaAddress} 'Look up an UMA address for payment'; POST /quotes
    'Create a transfer quote'; POST /quotes/{quoteId}/execute 'Execute a quote'; schema CurrencyPreference
  reason: Cross-currency payee lookup, FX quoting and execution of international transfers — cross-border
    payment management including FX.
- tag: Agent Operations
  spec_file: lightspark-agent-operations-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.75
  evidence: POST /agents/me/quotes 'Create a transfer quote'; POST /agents/me/quotes/{quoteId}/execute
    'Execute a quote'; POST /agents/me/transfer-out 'Create a transfer-out'
  reason: Operations capture, quote and execute transfers on behalf of an agent principal — payment instruction
    capture, validation and execution. Sub-capability could arguably be cross-border, so confidence held
    below 0.8.
- tag: Same-Currency Transfers
  spec_file: lightspark-same-currency-transfers-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.75
  evidence: POST /transfer-in createTransferIn 'Create a transfer-in request'; POST /transfer-out createTransferOut
    'Create a transfer-out request'
  reason: Creating transfer-in/transfer-out requests is capture and submission of payment instructions,
    i.e. payment initiation. Slight ambiguity between initiation and downstream processing keeps confidence
    moderate.
- tag: Transactions
  spec_file: lightspark-transactions-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.75
  evidence: GET /transactions listTransactions 'List transactions'; POST /transactions/{transactionId}/approve
    'Approve a pending incoming payment'
  reason: Retrieval and approval/rejection of payment transactions on a money-movement rail sits squarely
    in payments management; evidence spans both authorisation and processing so no single L2 is asserted.
- tag: Customers
  spec_file: lightspark-customers-api-openapi.yml
  capability_id: BC-1300.40
  capability_id_l1: BC-1300
  capability_name: Customer Information Management
  confidence: 0.7
  evidence: POST /customers 'Add a new customer'; PATCH /customers/{customerId} 'Update customer by ID';
    schemas BusinessInfo, BeneficialOwnerRole, SourceOfFundsCategory
  reason: Customer master record lifecycle for a regulated payments provider, carrying entity/beneficial-owner
    and source-of-funds attributes. Primarily customer information management, though it also feeds onboarding/KYC,
    hence 0.7.