slug: coutts provider: Coutts 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: 16 edges: - tag: Domestic Payments spec_file: coutts-domestic-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.95 evidence: POST /domestic-payments CreateDomesticPayments "Initiate a Domestic Payment"; title "Payment Initiation Domestic Payments API" reason: UK Open Banking payment initiation API for domestic payments — instruction capture and status retrieval, squarely Payment Initiation Management. - tag: Domestic Scheduled Payments spec_file: coutts-domestic-scheduled-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.95 evidence: POST /domestic-scheduled-payments "Initiate a Domestic Scheduled Payment"; OBWriteDomesticScheduled2 reason: Initiation and retrieval of future-dated domestic payment instructions — payment initiation capability. - tag: Domestic Standing Orders spec_file: coutts-domestic-standing-orders-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.92 evidence: POST /domestic-standing-orders "Submit a Domestic Standing Order"; OBExternalMandateClassification1Code reason: Submission and retrieval of recurring domestic payment orders — payment initiation management. - tag: Domestic Payment Consents spec_file: coutts-domestic-payment-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.9 evidence: POST /domestic-payment-consents Create a Domestic Payment Consent; GET /domestic-payment-consents/{ConsentId}/funds-confirmation Confirm availability of funds for a Domestic Payment reason: Open Banking payment initiation consent capture, authorisation and funds availability confirmation for domestic payments — squarely payment instruction capture, validation and authorisation. - tag: Domestic Scheduled Payment Consents spec_file: coutts-domestic-scheduled-payment-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.9 evidence: POST /domestic-scheduled-payment-consents "Create a Domestic Scheduled Payment Consent"; OBInternalConsentStatus2Code reason: Consent creation is the authorisation step of payment instruction capture in Open Banking PIS; maps to Payment Initiation Management. - tag: File Payments spec_file: coutts-file-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.9 evidence: POST /file-payments "Submit a File Payment"; "Get payment details for a File Payment" reason: Submission and status of bulk file-based payment instructions — payment initiation management. - tag: International Payments spec_file: coutts-international-payments-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.9 evidence: POST /international-payments "Initiate an International Payment"; OBWriteInternational3 reason: Initiation and status of international payments, including financial institution identification — cross-border payment capability. - tag: International Scheduled Payments spec_file: coutts-international-scheduled-payments-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.9 evidence: POST /international-scheduled-payments "Initiate an International Scheduled Payment"; OBWriteInternationalScheduled3 reason: Future-dated international payment initiation — cross-border payment management. - tag: Domestic Standing Order Consents spec_file: coutts-domestic-standing-order-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.88 evidence: POST /domestic-standing-order-consents "Create a Domestic Standing Order Consent"; OBFrequency6Code, NumberOfPayments reason: Consent/mandate capture for recurring standing order payment instructions — payment instruction capture and authorisation. - tag: File Payment Consents spec_file: coutts-file-payment-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.85 evidence: POST /file-payment-consents "Create a File Payment Consent"; "Upload a File for a ConsentId" reason: Bulk/batch payment file consent and upload within the Payment Initiation API; the file upload is the mechanism for capturing payment instructions, not generic file handling. - tag: International Payment Consents spec_file: coutts-international-payment-consents-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.85 evidence: POST /international-payment-consents "Create an International Payment Consent"; "Confirm Funds Availability for an International Payment" reason: Consent capture for cross-border payment instructions within the Payment Initiation API — Cross-Border Payment Management. - tag: Products spec_file: coutts-products-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.8 evidence: GET /products 'Get Products'; schemas 'OBReadProduct2', 'OB_OverdraftFeeType1Code', 'OB_InterestRateType1Code_0', 'OB_FeeFrequency1Code_2' reason: Exposes the bank's product master data including rates and fee structures for accounts — banking product catalogue (with parameter detail). - tag: International Scheduled Payments Consents spec_file: coutts-international-scheduled-payments-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.75 evidence: POST /international-scheduled-payment-consents 'Create an International Scheduled Payment Consent'; 'Confirm Funds Availability for an International Scheduled Payment' reason: 'Open Banking Payment Initiation API surface: capture and authorisation of a payment instruction (consent) plus funds-availability validation — payment initiation. Cross-border flavour is present (international), so the L2 choice between initiation and cross-border carries some ambiguity.' - tag: Parties spec_file: coutts-parties-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.75 evidence: GET /accounts/{AccountId}/party 'Get Party for an AccountId'; schemas 'FullLegalName', 'EmailAddress', 'OBPartyRelationships1', 'LEI' reason: Returns the account holder / party identity and contact details held by the bank — banking customer information management, not a technical resource. - tag: International Standing Orders spec_file: coutts-international-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 /international-standing-orders 'Submit an International Standing Order'; openapi title 'Payment Initiation ... API' reason: Submission and retrieval of international standing order payment instructions is payment initiation/instruction management within Payments & Card Management; some ambiguity vs Cross-Border Payment Management. - tag: International Standing Orders Consents spec_file: coutts-international-standing-orders-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.7 evidence: POST /international-standing-order-consents 'Create an International Standing Order Consent' reason: Consent capture/authorisation for a recurring international payment instruction — payment initiation authorisation in the Payment Initiation spec; L2 could alternatively be cross-border.