slug: synctera provider: Synctera 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: KYC Verification spec_file: synctera-kyc-verification-api-openapi.yml capability_id: BC-1300.20 capability_id_l1: BC-1300 capability_name: KYC & Customer Due Diligence Management confidence: 0.95 evidence: POST /customers/{customer_id}/verify "Verify a customer's identity"; schemas customer_kyc_status, customer_verification_result reason: Explicit KYC identity verification of banking customers — KYC & Customer Due Diligence Management. - tag: Cards spec_file: synctera-cards-api-openapi.yml capability_id: BC-1340.60 capability_id_l1: BC-1340 capability_name: Card Issuance Management confidence: 0.9 evidence: POST /cards issueCard "Issue a Card"; POST /cards/activate "Activate a card"; schemas physical_card_response, shipping, virtual_card reason: Operations create, personalise, ship, activate and update payment cards for banking customers — card issuance lifecycle within Payments & Card Management. - tag: KYC/KYB Verifications spec_file: synctera-kyc-kyb-verifications-api-openapi.yml capability_id: BC-1300.20 capability_id_l1: BC-1300 capability_name: KYC & Customer Due Diligence Management confidence: 0.9 evidence: POST /verifications/verify "Verify a customer's identity"; POST /verifications/adhoc "Check if an individual is on any watchlists" reason: KYC/KYB identity verification and watchlist checks on customers and businesses — customer due diligence; watchlist element also touches sanctions screening. - tag: ACH spec_file: synctera-ach-api-openapi.yml capability_id: BC-1340.30 capability_id_l1: BC-1340 capability_name: Clearing & Settlement Management confidence: 0.85 evidence: POST /ach addTransactionOut Send an ACH; schemas outgoing_ach_request, outgoing_ach_list reason: Origination and management of outbound ACH transactions — domestic clearing rail (ACH) payment processing. - tag: Applications spec_file: synctera-applications-api-openapi.yml capability_id: BC-1320.10 capability_id_l1: BC-1320 capability_name: Credit Origination Management confidence: 0.85 evidence: GET /applications listApplications List credit applications.; POST /applications createApplication Create a credit application. reason: Credit application intake and status lifecycle — credit origination management. - tag: Accounts spec_file: synctera-accounts-api-openapi.yml capability_id: BC-1330.10 capability_id_l1: BC-1330 capability_name: Deposit Account Management confidence: 0.8 evidence: POST /accounts createAccount Create an account; schemas account_creation, account_line_of_credit, patch_interest, balance_floor reason: Bank deposit/credit account creation, maintenance, relationships and account products on a BaaS platform — deposit account management. - tag: PaymentSchedules spec_file: synctera-paymentschedules-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.8 evidence: POST /payment_schedules "Create a payment schedule"; schemas payment_instruction, ach_instruction, internal_transfer_instruction, outgoing_ach_request reason: Capture and scheduling of payment instructions (ACH, internal transfers) with statuses and holds — payment initiation management. - tag: Watchlist spec_file: synctera-watchlist-api-openapi.yml capability_id: BC-1400.20 capability_id_l1: BC-1400 capability_name: Sanctions Screening Management confidence: 0.8 evidence: POST /customers/{customer_id}/watchlists/subscriptions watchlistSubscribe Subscribe a customer to watchlist monitoring; suppressWatchlistEntityAlert Suppress entity alert reason: Ongoing watchlist (sanctions/PEP) screening of customers with alert handling and suppression — Sanctions Screening Management; could also be framed as KYC ongoing monitoring. - tag: Persons spec_file: synctera-persons-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.75 evidence: 'POST /persons createPerson Create a person; schemas: is_customer, ssn_source, verification_status, address' reason: Person records for banking customers of a BaaS platform — customer master data (create/update/prefill person, is_customer, verification_status). Maps to Banking Customer Management, most specifically Customer Information Management; some chance the intended sub-capability is onboarding. - tag: Wires (alpha) spec_file: synctera-wires-alpha-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.75 evidence: POST /wires createWire Send a wire; PATCH /wires/{wire_id} cancelWire Cancel an outgoing wire reason: Initiation and cancellation of wire transfers — payment instruction capture and authorisation under Payments & Card Management. - tag: Businesses spec_file: synctera-businesses-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.7 evidence: POST /businesses createBusiness Create a business; schemas is_customer, verification_status, address reason: Business customer records with verification status on a banking platform — banking customer information management (KYB verification adjacent). - tag: Customers spec_file: synctera-customers-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.7 evidence: POST /customers "Create a Customer"; GET /customers/{customer_id}/risk_ratings; schemas customer, patch_customer, customer_kyc_status, employment reason: CRUD over banking customer master records (identity, employment, risk rating) for a BaaS platform — customer information management under Banking Customer Management; some overlap with onboarding/KYC hence not maximal confidence. - tag: Monitoring spec_file: synctera-monitoring-api-openapi.yml capability_id: BC-1400 capability_id_l1: BC-1400 capability_name: Financial Crime Management confidence: 0.7 evidence: POST /monitoring/subscriptions "Subscribe a customer or business to monitoring"; GET /monitoring/alerts "List monitoring alerts"; schema monitoring_alert reason: 'Not system observability: subscriptions attach customers/businesses to ongoing screening with alerts handled via vendor data — financial crime monitoring; unclear whether AML monitoring or watchlist/sanctions screening, so L1 only.' - tag: Relationships spec_file: synctera-relationships-api-openapi.yml capability_id: BC-1300.40 capability_id_l1: BC-1300 capability_name: Customer Information Management confidence: 0.7 evidence: 'schemas: person_business_owner_relationship, business_business_owner_relationship, person_business_relationship' reason: Models relationships between persons and businesses including beneficial-owner links — customer information/relationship data for banking customers. Could also support KYB due diligence, hence moderate confidence. - tag: Remote Check Deposit (beta) spec_file: synctera-remote-check-deposit-beta-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.7 evidence: POST /rdc/deposits createRdcDeposit Create a Remote Check Deposit reason: Remote deposit capture of cheques initiates a deposit/payment instruction into the bank. Payments & Card Management with payment initiation is the best fit; some ambiguity vs deposit account operations. - tag: Transactions spec_file: synctera-transactions-api-openapi.yml capability_id: BC-1340.20 capability_id_l1: BC-1340 capability_name: Payment Processing Management confidence: 0.7 evidence: POST /transactions/internal_transfer createInternalTransfer Create an internal transfer; GET /transactions/pending, GET /transactions/posted reason: Creating internal transfers and reading pending/posted transactions is payment/transaction processing on the core banking ledger. Payments & Card Management, processing sub-capability; some ambiguity with account transaction reporting.