slug: recognise-bank provider: Recognise Bank 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: 18 edges: - tag: Domestic Payments spec_file: recognise-bank-domestic-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.92 evidence: POST /domestic-payments CreateDomesticPayments Initiate a Domestic Payment reason: Directly initiates and retrieves domestic payment instructions under the UK Open Banking Payment Initiation spec. - tag: Domestic Payment Consents spec_file: recognise-bank-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; "Confirm availability of funds for a Domestic Payment" reason: Open Banking PISP consent/authorisation stage of payment instruction capture, including funds confirmation — payment initiation. - tag: Domestic Scheduled Payment Consents spec_file: recognise-bank-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 reason: Consent capture and authorisation for scheduled domestic payment instructions — payment initiation management. - tag: Domestic Scheduled Payments spec_file: recognise-bank-domestic-scheduled-payments-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-payments Initiate a Domestic Scheduled Payment reason: Initiation and retrieval of future-dated domestic payment instructions. - tag: Domestic Standing Order Consents spec_file: recognise-bank-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 reason: Consent capture/authorisation for recurring standing order payment instructions under Open Banking PISP. - tag: Domestic Standing Orders spec_file: recognise-bank-domestic-standing-orders-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-orders Submit a Domestic Standing Order reason: Submission and retrieval of recurring domestic standing order payment instructions. - tag: File Payment Consents spec_file: recognise-bank-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 capture and authorisation under Open Banking payment initiation; the file upload is the payment instruction carrier, not generic file handling. - tag: File Payments spec_file: recognise-bank-file-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.85 evidence: POST /file-payments CreateFilePayments Submit a File Payment reason: Submission and status/reporting of bulk payment files — batch payment instruction initiation. - tag: International Payments spec_file: recognise-bank-international-payments-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-payments 'Initiate an International Payment' reason: Operations initiate and retrieve international payments — cross-border payment management within Payments & Card Management. - tag: Branch spec_file: recognise-bank-branch-api-openapi.yml capability_id: BC-1300.50 capability_id_l1: BC-1300 capability_name: Banking Channels Management confidence: 0.8 evidence: GET /branches — "Open Data Branch API" reason: Open Data branch locator listing the bank's physical branch network, which is banking channel information. - tag: International Payment Consents spec_file: recognise-bank-international-payment-consents-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.8 evidence: POST /international-payment-consents 'Create an International Payment Consent'; 'Confirm Funds Availability for an International Payment' reason: Open Banking Payment Initiation for international (cross-border) payments; consent capture and funds check are part of initiating cross-border payment instructions. - tag: International Scheduled Payments spec_file: recognise-bank-international-scheduled-payments-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.8 evidence: POST /international-scheduled-payments 'Initiate an International Scheduled Payment' reason: Initiation and status retrieval of scheduled international payments — cross-border payment initiation/processing. - tag: International Standing Orders spec_file: recognise-bank-international-standing-orders-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.8 evidence: POST /international-standing-orders 'Submit an International Standing Order'; schema OBFrequency6, NumberOfPayments reason: Recurring cross-border payment instructions (standing orders) submitted and retrieved — cross-border payment management. - tag: Products spec_file: recognise-bank-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 OBBCAData1, OB_OverdraftFeeType1Code, OB_InterestFixedVariableType1Code, OB_FeeFrequency1Code_2 reason: Retrieves banking product details (business current account data, overdraft fees, interest rate types) for accounts — banking product catalogue exposure. - tag: International Scheduled Payments Consents spec_file: recognise-bank-international-scheduled-payments-consents-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.78 evidence: POST /international-scheduled-payment-consents 'Create an International Scheduled Payment Consent' reason: Consent capture and funds confirmation preceding a cross-border scheduled payment instruction; part of international payment initiation. - tag: International Standing Orders Consents spec_file: recognise-bank-international-standing-orders-consents-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.75 evidence: POST /international-standing-order-consents 'Create an International Standing Order Consent' reason: Consent authorisation step for recurring international payment instructions; belongs to cross-border payment initiation. - tag: Parties spec_file: recognise-bank-parties-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.75 evidence: GET /party 'Get Party'; schemas PartyId, PartyNumber, OBPartyRelationships1, LEI, Name_3 reason: Exposes account holder / party identity, name, address and relationship data for banking customers — banking customer information management. - tag: CCC spec_file: recognise-bank-ccc-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.7 evidence: GET /commercial-credit-cards — "Open Data CCC API" reason: Open Data endpoint publishing the bank's commercial credit card product information — a product catalogue/terms disclosure surface rather than card issuance or transaction processing.