slug: cynergy-bank provider: Cynergy 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: cynergy-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: Explicitly initiates and tracks domestic payment instructions via the Open Banking Payment Initiation API — Payment Initiation Management. - tag: Domestic Scheduled Payments spec_file: cynergy-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 CreateDomesticScheduledPayments Initiate a Domestic Scheduled Payment reason: Initiation and status retrieval of future-dated domestic payment instructions under the Payment Initiation specification. - tag: International Payments spec_file: cynergy-bank-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" reason: Initiation and status retrieval of international payments with OBStructuredRegulatoryReporting3 and currency/charge schemas; plainly cross-border payment management. - tag: Domestic Standing Orders spec_file: cynergy-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"; openapi title "Payment Initiation ... API" reason: Open Banking Payment Initiation surface for capturing and submitting domestic standing order payment instructions, with mandate and creditor schemas (OBMandateRelatedInformation1, OBUltimateCreditor1). This is payment instruction capture/authorisation, i.e. Payment Initiation Management. - tag: International Scheduled Payments spec_file: cynergy-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.88 evidence: POST /international-scheduled-payments — "Initiate an International Scheduled Payment" reason: Initiation of future-dated international payment instructions via the Payment Initiation API — cross-border payment management. - tag: International Standing Orders spec_file: cynergy-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.87 evidence: POST /international-standing-orders — "Submit an International Standing Order"; schema OBWriteInternationalStandingOrder4 reason: Submission and retrieval of recurring international payment orders, with mandate and regulatory reporting schemas — cross-border payment management. - tag: Domestic Payment Consents spec_file: cynergy-bank-domestic-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 /domestic-payment-consents CreateDomesticPaymentConsents Create a Domestic Payment Consent; GET .../funds-confirmation Confirm availability of funds for a Domestic Payment reason: Consent creation, SCA support data and funds-availability confirmation are payment instruction capture, validation and authorisation under Open Banking payment initiation. - tag: Domestic Scheduled Payment Consents spec_file: cynergy-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.85 evidence: POST /domestic-scheduled-payment-consents CreateDomesticScheduledPaymentConsents Create a Domestic Scheduled Payment Consent reason: Consent and authorisation capture (OBSCASupportData1) preceding a scheduled domestic payment instruction is payment initiation management. - tag: Domestic Standing Order Consents spec_file: cynergy-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.85 evidence: POST /domestic-standing-order-consents CreateDomesticStandingOrderConsents Create a Domestic Standing Order Consent; OBWriteDomesticStandingOrderConsentResponse6 reason: Capture and authorisation of recurring standing order payment instructions via Open Banking payment initiation consents. - tag: International Payment Consents spec_file: cynergy-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.85 evidence: POST /international-payment-consents — "Create an International Payment Consent"; "Confirm Funds Availability for an International Payment" reason: Consent capture and funds confirmation specifically for international (cross-border) payment instructions, including regulatory reporting schemas — Cross-Border Payment Management. - tag: International Scheduled Payments Consents spec_file: cynergy-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.85 evidence: POST /international-scheduled-payment-consents — "Create an International Scheduled Payment Consent"; "Confirm Funds Availability for an International Scheduled Payment" reason: Consent and funds-availability steps that authorise cross-border scheduled payment instructions. - tag: International Standing Orders Consents spec_file: cynergy-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.83 evidence: POST /international-standing-order-consents — "Create an International Standing Order Consent"; schema OBWriteInternationalStandingOrderConsent6 reason: Consent capture authorising recurring cross-border payment instructions under the Payment Initiation API. - tag: File Payments spec_file: cynergy-bank-file-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.82 evidence: POST /file-payments — "Submit a File Payment"; GET /file-payments/{FilePaymentId}/report-file reason: Submission and status/reporting of bulk file payment instructions via the Payment Initiation API; the operations perform payment instruction submission, i.e. payment initiation. - tag: File Payment Consents spec_file: cynergy-bank-file-payment-consents-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.8 evidence: POST /file-payment-consents — "Create a File Payment Consent"; "Upload a File for a ConsentId"; schema OBSCASupportData1 reason: Consent creation and SCA support data for bulk/file payment instructions under the Payment Initiation API — this is capture, validation and authorisation of payment instructions rather than a technical file-upload utility. - tag: Products spec_file: cynergy-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, OBBCAData1, OB_OverdraftFeeType1Code, OB_InterestRateType1Code_0 reason: Exposes the bank's personal/business current account product data (fees, overdraft, rates) per account — a banking product catalogue surface. Some ambiguity between catalogue and parameter/pricing sub-capabilities. - tag: Parties spec_file: cynergy-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 /accounts/{AccountId}/parties 'Get Parties for an AccountId'; schemas FullLegalName, EmailAddress, PhoneNumber, PartyNumber, OBPartyRelationships1 reason: Open Banking Account Information 'Parties' endpoint returns the account holder / related party details (legal name, contact details, relationships) — i.e. banking customer information rather than any trading counterparty notion. - tag: Standing Orders spec_file: cynergy-bank-standing-orders-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.74 evidence: GET /standing-orders 'Get Standing Orders'; schemas StandingOrderId, NextPaymentDateTime, OBMandateRelatedInformation1, OBFrequency6Code reason: Standing order (recurring payment mandate) data on bank accounts — payments capability; sub-capability not determinable from read-only operations. - tag: Scheduled Payments spec_file: cynergy-bank-scheduled-payments-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.72 evidence: GET /accounts/{AccountId}/scheduled-payments 'Get Scheduled Payments for an AccountId'; schema OBScheduledPayment3 reason: Retrieval of scheduled payment instructions on a bank account — clearly payments domain; too read-only/generic to pin a specific sub-capability.