slug: paragon-bank provider: Paragon 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: 21 edges: - tag: International Payments spec_file: paragon-bank-international-payments-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.94 evidence: POST /international-payments "Initiate an International Payment"; schema OBWriteInternational3 reason: Initiation and tracking of international (cross-border) payments — cross-border payment management. - tag: Domestic Payments spec_file: paragon-bank-domestic-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.93 evidence: POST /domestic-payments CreateDomesticPayments Initiate a Domestic Payment reason: Operations initiate and retrieve domestic payment instructions under the Payment Initiation API — payment instruction capture and authorisation. - tag: Domestic Payment Consents spec_file: paragon-bank-domestic-payment-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.92 evidence: POST /domestic-payment-consents Create a Domestic Payment Consent ... Confirm availability of funds for a Domestic Payment reason: Open Banking payment initiation consent capture, authorisation and funds-availability validation — squarely Payment Initiation Management. - tag: International Payment Consents spec_file: paragon-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.92 evidence: POST /international-payment-consents "Create an International Payment Consent"; "Confirm Funds Availability for an International Payment" reason: Consent capture and funds confirmation for cross-border payment instructions under Open Banking payment initiation. - tag: International Scheduled Payments spec_file: paragon-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.92 evidence: POST /international-scheduled-payments "Initiate an International Scheduled Payment" reason: Initiation of future-dated cross-border payment instructions under the Payment Initiation API. - tag: Domestic Scheduled Payments spec_file: paragon-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 scheduled domestic payment instructions — payment instruction capture and validation. - tag: File Payment Consents spec_file: paragon-bank-file-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 /file-payment-consents "Create a File Payment Consent"; "Upload a File for a ConsentId"; schema OBWriteFileConsent3, OBSCASupportData1 reason: 'UK Open Banking Payment Initiation API: capture and authorisation (consent/SCA) of bulk file payment instructions — payment instruction capture, validation, authorisation.' - tag: File Payments spec_file: paragon-bank-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 retrieval of bulk file payment instructions under the Payment Initiation API — payment initiation management. - tag: International Scheduled Payments Consents spec_file: paragon-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.9 evidence: POST /international-scheduled-payment-consents "Create an International Scheduled Payment Consent"; "Confirm Funds Availability for an International Scheduled Payment" reason: Consent/authorisation surface for scheduled cross-border payments — cross-border payment initiation. - tag: International Standing Orders spec_file: paragon-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.9 evidence: POST /international-standing-orders "Submit an International Standing Order"; schema OBFrequency6Code reason: Set-up and retrieval of recurring international payment orders — cross-border payment management. - tag: Domestic Scheduled Payment Consents spec_file: paragon-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.88 evidence: POST /domestic-scheduled-payment-consents Create a Domestic Scheduled Payment Consent reason: Consent capture and authorisation for future-dated domestic payment instructions within the Payment Initiation specification. - tag: Domestic Standing Orders spec_file: paragon-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 and their payment details — payment initiation. - tag: International Standing Orders Consents spec_file: paragon-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.88 evidence: POST /international-standing-order-consents "Create an International Standing Order Consent"; schema OBWriteInternationalStandingOrderConsentResponse7 reason: Consent capture for recurring cross-border payment instructions under the Payment Initiation API. - tag: Domestic Standing Order Consents spec_file: paragon-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.87 evidence: POST /domestic-standing-order-consents Create a Domestic Standing Order Consent reason: Consent capture/authorisation for recurring domestic standing order instructions (frequency codes present) within Payment Initiation. - tag: Branch spec_file: paragon-bank-branch-api-openapi.yml capability_id: BC-1300.50 capability_id_l1: BC-1300 capability_name: Banking Channels Management confidence: 0.78 evidence: GET /branches under "Open Data Branch API" reason: Publishes the bank's branch network data, which is physical channel information — Banking Channels Management. - tag: Products spec_file: paragon-bank-products-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.78 evidence: GET /products 'Get Products'; schemas OBPCAData1, OB_FeeFrequency1Code, OB_InterestFixedVariableType1Code, OB_InterestCalculationMethod1Code reason: Open Banking Products endpoints publish the bank's product master data with fees, rates and interest calculation terms for an account — banking product catalogue exposure. Product parameters are also present, so some ambiguity between catalogue (.10) and parameter configuration (.20), but the operations only read the catalogue. - tag: BCA spec_file: paragon-bank-bca-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.72 evidence: GET /business-current-accounts under "Open Data BCA API" reason: UK Open Data product-reference endpoint publishing the bank's business current account product information — a published banking product catalogue rather than account servicing. - tag: ATM spec_file: paragon-bank-atm-api-openapi.yml capability_id: BC-1300.50 capability_id_l1: BC-1300 capability_name: Banking Channels Management confidence: 0.7 evidence: 'openapi title: Open Data ATM API; GET /atms' reason: UK Open Data endpoint publishing the bank's ATM estate — ATM channel information, which falls under banking channel operations. Single undocumented operation limits confidence. - tag: CCC spec_file: paragon-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 under "Open Data CCC API" reason: Open Data product-reference endpoint publishing commercial credit card product details — banking product catalogue publication. - tag: PCA spec_file: paragon-bank-pca-api-openapi.yml capability_id: BC-1310.10 capability_id_l1: BC-1310 capability_name: Product Catalogue Management confidence: 0.7 evidence: openapi title "Open Data PCA API"; GET /personal-current-accounts reason: Open Data endpoint publishing the bank's personal current account product information — a banking product catalogue surface rather than an account servicing surface. - tag: Parties spec_file: paragon-bank-parties-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.7 evidence: GET /accounts/{AccountId}/parties — 'Get Parties for an AccountId'; schemas OBParty2, OBPartyRelationships1, PartyNumber reason: UK Open Banking Account Information API surface exposing the account-holder (party) details and relationships — i.e. banking customer information/records, not a generic 'party' technical object. L2 Customer Information Management fits the read of customer data (name, address, phone, LEI, party relationships). Confidence moderate because the API is read-only reference data rather than full customer data stewardship.