slug: temenos provider: Temenos 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: 28 edges: - tag: Sanction Screening spec_file: temenos-sanction-screening-api-openapi.yml capability_id: BC-1400.20 capability_id_l1: BC-1400 capability_name: Sanctions Screening Management confidence: 0.95 evidence: GET /screening/customers/{customerId}/alerts getCustomerSanctionAlerts; POST /screening/transactions scanTransactionMessage Scan Payment Message; schema SanctionAlert reason: Operations screen onboarding customers and payment messages against sanctions/watchlists and expose sanction alerts — unambiguously sanctions screening within financial crime management. - tag: Trade Finance spec_file: temenos-trade-finance-api-openapi.yml capability_id: BC-1350 capability_id_l1: BC-1350 capability_name: Trade Finance Management confidence: 0.95 evidence: GET /tradeFinance/lettersOfCredit listLettersOfCredit; GET /tradeFinance/guarantees listGuarantees reason: Operations expose letters of credit and bank guarantees, i.e. trade finance instruments; spans both documentary credit and guarantees sub-capabilities so only the L1 is asserted. - tag: Alert Management spec_file: temenos-alert-management-api-openapi.yml capability_id: BC-1400 capability_id_l1: BC-1400 capability_name: Financial Crime Management confidence: 0.9 evidence: '"API for anti-money laundering, fraud detection, and compliance including ... transaction monitoring, and alert management"; PUT /alerts/{alertId} "Update Alert Disposition"' reason: Explicitly financial-crime alerts (AML/fraud/sanctions) with disposition handling; sub-capability ambiguous between AML monitoring alerts and investigations case handling. - tag: Transaction Monitoring spec_file: temenos-transaction-monitoring-api-openapi.yml capability_id: BC-1400.10 capability_id_l1: BC-1400 capability_name: AML Transaction Monitoring Management confidence: 0.9 evidence: GET /monitoring/alerts listMonitoringAlerts List Transaction Monitoring Alerts; schema MonitoringAlert, within 'anti-money laundering, fraud detection, and compliance' reason: Alerts produced by AML transaction monitoring in a financial crime mitigation product — clearly AML transaction monitoring; slight ambiguity with fraud detection alerts. - tag: Bulk Payments spec_file: temenos-bulk-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.85 evidence: POST /bulkPayments createBulkPayment "Create Bulk Payment Batch"; POST /bulkPayments/{batchId}/approve "Approve Bulk Payment Batch" reason: Creation and authorisation/approval of bulk payment batches is payment instruction capture and authorisation within a payments hub. - tag: Lending spec_file: temenos-lending-api-openapi.yml capability_id: BC-1320 capability_id_l1: BC-1320 capability_name: Credit & Lending Management confidence: 0.85 evidence: 'POST /lending/facilities createLendingFacility "Create Lending Facility"; description: "front-to-back services for accounts, deposits, lending, trade finance"' reason: Operations create and list lending facilities, squarely Credit & Lending Management; facility creation could be origination or servicing so no L2 asserted. - tag: Loans spec_file: temenos-loans-api-openapi.yml capability_id: BC-1320 capability_id_l1: BC-1320 capability_name: Credit & Lending Management confidence: 0.85 evidence: GET /loans listBnplLoans "List BNPL Loans"; "full loan lifecycle management" for interest-free and interest-bearing BNPL products reason: BNPL loan records with decisioning and lifecycle management are consumer credit/lending; L2 ambiguous between origination/decisioning and loan servicing. - tag: Payment Orders spec_file: temenos-payment-orders-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.85 evidence: POST /paymentOrders createPaymentOrder Create Payment Order; GET /paymentOrders/{paymentOrderId}/status getPaymentOrderStatus reason: Capture and tracking of payment instructions in a bank payments hub — payment initiation/instruction management. - tag: Cards spec_file: temenos-cards-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.8 evidence: 'GET /cards listCards List Customer Cards; PUT /cards/{cardId} updateCardControls Update Card Controls; schemas: CardControls, Card' reason: Operations list a customer's payment cards and update card controls (limits/blocks), which sits in Payments & Card Management. No single L2 fits cleanly — control updates are card servicing rather than issuance or transaction switching — so only the L1 is asserted. - tag: Credit Offers spec_file: temenos-credit-offers-api-openapi.yml capability_id: BC-1320.10 capability_id_l1: BC-1320 capability_name: Credit Origination Management confidence: 0.8 evidence: POST /offers createCreditOffer Create Credit Offer; POST /offers/{offerId}/accept acceptCreditOffer; "buy now pay later services with embedded Explainable AI for automated decisioning and credit offer matching" reason: Creation, retrieval and acceptance of BNPL credit offers is credit origination (application/offer intake and acceptance) within Credit & Lending Management; decisioning is adjacent but the operations expose the offer lifecycle. - tag: Customer Risk Assessment spec_file: temenos-customer-risk-assessment-api-openapi.yml capability_id: BC-1300.20 capability_id_l1: BC-1300 capability_name: KYC & Customer Due Diligence Management confidence: 0.8 evidence: GET /kyc/customers/{customerId}/riskScore getCustomerRiskScore; POST /kyc/customers/formSubmission Submit Customer KYC Form; schema KycFormSubmission reason: KYC form submission and customer risk scoring is customer due diligence. Some overlap with financial crime management, but the endpoints are explicitly /kyc/customers, i.e. CDD risk rating rather than transaction monitoring or sanctions hits. - tag: Customers spec_file: temenos-customers-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.8 evidence: GET /customers/{customerId} getCustomer Get Customer Profile; PUT /customers/{customerId} updateCustomer Update Customer Profile; schemas Customer, CustomerUpdate, Address reason: Read and maintenance of banking customer profile data in a digital banking platform maps to Banking Customer Information Management. - tag: Deposits spec_file: temenos-deposits-api-openapi.yml capability_id: BC-1330 capability_id_l1: BC-1330 capability_name: Deposits & Savings Management confidence: 0.8 evidence: GET /deposits listCmbDeposits List Deposits; schema CmbDeposit; "front-to-back services for accounts, deposits, lending, trade finance, and payments" reason: Exposes deposit records from a cloud core banking product set, clearly Deposits & Savings Management. A single list operation does not distinguish demand deposits from term deposits, so no L2 is asserted. - tag: Direct Debits spec_file: temenos-direct-debits-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.8 evidence: GET /directDebits listDirectDebits List Direct Debit Mandates; "direct debit management, and payment stop requests ... integrated clearing through the Temenos Payments Hub" reason: Direct debit mandate retrieval within a payments hub is Payments & Card Management; mandate inquiry straddles initiation and clearing/settlement so only the L1 is asserted. - tag: Payment Stops spec_file: temenos-payment-stops-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.8 evidence: POST /paymentStops createPaymentStop Create Payment Stop Request; "payment stop requests" reason: Stop-payment instructions on bank payments clearly sit in Payments & Card Management, but they straddle instruction authorisation and downstream processing/servicing, so no L2 is asserted. - tag: Request to Pay spec_file: temenos-request-to-pay-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.8 evidence: 'POST /requestToPay createRequestToPay Create Request-to-pay; description: ''request-to-pay, bulk payment initiation, direct debit management''' reason: Request-to-pay messages are payment request/initiation instructions within the Temenos Payments Hub, so payment initiation is the closest fit; some ambiguity as R2P also touches clearing scheme messaging. - tag: Payments spec_file: temenos-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.78 evidence: POST /payments createCmbPayment Create Payment; GET /payments/{paymentId} getPayment Get Payment Status reason: Digital/core banking channel operations to initiate a payment and query its status — payment instruction capture. Sparse surface, so L2 confidence is moderate. - tag: Entitlements spec_file: temenos-entitlements-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: GET /entitlements listEntitlements List User Entitlements; POST /entitlements createEntitlement Assign Entitlement; "user entitlements" reason: Assignment and listing of user entitlements is access rights administration for the platform, i.e. Identity & Access Management, not a banking product entitlement. - tag: Pricing Quotation spec_file: temenos-pricing-quotation-api-openapi.yml capability_id: BC-1310.30 capability_id_l1: BC-1310 capability_name: Banking Product Pricing Management confidence: 0.75 evidence: POST /quotations/simulate Simulate Account Creation Pricing; POST /quotations/simulateEvent Simulate Event Pricing reason: Simulation of applicable interest rates, fees and cashback to produce a price quotation for banking products — banking product pricing determination. - tag: Accounts spec_file: temenos-accounts-api-openapi.yml capability_id: BC-1330 capability_id_l1: BC-1330 capability_name: Deposits & Savings Management confidence: 0.72 evidence: POST /accounts createCmbAccount "Create Commercial Banking Account"; GET /accounts/{accountId} "Get Account Details"; schema CmbAccountCreate reason: Creation and retrieval of banking accounts is deposit/current account management; ambiguous between deposit account management and account lifecycle operations, so L1 only. - tag: Analytics Data Store spec_file: temenos-analytics-data-store-api-openapi.yml capability_id: BC-610.50 capability_id_l1: BC-610 capability_name: Analytics & BI Management confidence: 0.72 evidence: '"Provides banking-specific analytical and operational data for comprehensive intra-day and historical analysis, reporting"; GET /analytics/transactions listAnalyticsTransactions' reason: Exposes an analytics/operational data store for reporting and analysis — analytics & BI delivery rather than a banking product process. - tag: Payment Configuration spec_file: temenos-payment-configuration-api-openapi.yml capability_id: BC-1340.20 capability_id_l1: BC-1340 capability_name: Payment Processing Management confidence: 0.72 evidence: GET /configuration/paymentRoutes listPaymentRoutes List Payment Routing Configurations; schema PaymentRoute reason: Single operation exposes payment routing configuration in a payments hub with ISO 20022 messaging and integrated clearing — payment processing/routing. Config-flavoured but the object is unambiguously payment routing, not generic app settings. - tag: Pricing Adjustment spec_file: temenos-pricing-adjustment-api-openapi.yml capability_id: BC-1310.30 capability_id_l1: BC-1310 capability_name: Banking Product Pricing Management confidence: 0.72 evidence: PUT /quotations/{quotationReference} amendQuotationPricing Amend Quotation Pricing; "Supports pricing negotiation through quotation references and manual adjustment workflows" reason: Manual adjustment of quoted interest rates and fees for banking products — negotiated/customer-specific banking product pricing. - tag: Promotions spec_file: temenos-promotions-api-openapi.yml capability_id: BC-1310.30 capability_id_l1: BC-1310 capability_name: Banking Product Pricing Management confidence: 0.72 evidence: POST /promotions createPromotion Create Promotion Arrangement; "promotions management for banking products and services" reason: Creation of promotional pricing arrangements on banking products; the frame's banking product pricing L2 explicitly covers product pricing and promotions. - tag: Package Details spec_file: temenos-package-details-api-openapi.yml capability_id: BC-1310.40 capability_id_l1: BC-1310 capability_name: Product Bundling Management confidence: 0.7 evidence: GET /packages listPackages List Package Arrangements; "package arrangements, pricing adjustments ... for banking products" reason: Operations create and list package arrangements and retrieve package pricing for banking products — this is the banking product factory's bundling/package construct with relationship pricing, not a generic subscription or logistics package. - tag: Party spec_file: temenos-party-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.7 evidence: POST /party/customers createCustomer "Create Customer"; GET /party/customers/{customerId} getCustomer "Get Customer Details"; PUT updateCustomer "Update Customer Details"; schemas Customer, CustomerCreate, CustomerUpdate, Investor, Beneficiary, WealthClient, Address reason: The dominant surface is CRUD over party master records (customers, investors, distributors, beneficiaries, wealth clients) — a customer/party master data capability. Confidence held at 0.7 because part of the surface (AML screenings, FATCA/CRS records) is regulatory screening rather than customer data mastering. recovered_from: sweep-20260829T005356Z-edges.json - tag: Product spec_file: temenos-product-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.7 evidence: GET /product/products listProducts List Banking Products; GET /product/funds listFunds; GET /product/shareClasses listShareClasses reason: Read/create of the product master — banking products, funds and share classes — i.e. the product catalogue. Fund/share-class creation sits in fund administration but is still product master data. - tag: Standing Orders spec_file: temenos-standing-orders-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.7 evidence: POST /standingOrders createStandingOrder Create Standing Order, within 'Payment processing and management API' reason: Standing orders are recurring payment instructions captured and maintained in the payments hub, so payment instruction capture/initiation fits; could alternatively be viewed as account servicing, hence moderate confidence.