slug: fifth-third-bancorp
provider: Fifth Third Bancorp
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: 7
edges:
- tag: Transfers
  spec_file: fifth-third-bancorp-transfers-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.82
  evidence: POST /transfers  Initiate a Transfer; PUT /transfers/{uid}/cancel  Cancel a Transfer
  reason: Initiating and cancelling transfers is payment instruction capture and authorisation on a banking
    platform — payment initiation management.
- tag: Combined Transfers
  spec_file: fifth-third-bancorp-combined-transfers-api-openapi.yml
  capability_id: BC-1340.10
  capability_id_l1: BC-1340
  capability_name: Payment Initiation Management
  confidence: 0.78
  evidence: POST /combined_transfers    Create a new Combined Transfer
  reason: On this Banking-as-a-Service platform a Transfer is a movement of funds between accounts; creating
    and retrieving combined transfers is payment instruction capture and execution, mapping to Payments
    management and specifically initiation. Some ambiguity between initiation and processing sub-capabilities.
- tag: Customers
  spec_file: fifth-third-bancorp-customers-api-openapi.yml
  capability_id: BC-1300.40
  capability_id_l1: BC-1300
  capability_name: Customer Information Management
  confidence: 0.78
  evidence: POST /customers    Create a new Customer; PUT /customers/{uid}    Adjust Customer Data; DELETE
    /customers/{uid}    Archive a Customer
  reason: Full CRUD over banking end-customer records on a BaaS platform — creation, data adjustment and
    archival — which is customer information/record management within Banking Customer Management. Could
    also touch onboarding, hence not higher.
- tag: Customer Products
  spec_file: fifth-third-bancorp-customer-products-api-openapi.yml
  capability_id: BC-1300.10
  capability_id_l1: BC-1300
  capability_name: Customer Onboarding Management
  confidence: 0.72
  evidence: POST /customer_products    Onboard Customer onto a Product
  reason: The operation explicitly onboards a customer onto a banking product, which is customer onboarding/account
    activation rather than product catalogue definition. Slight ambiguity with Banking Product Management,
    but the verb is onboarding a customer.
- tag: Custodial Accounts
  spec_file: fifth-third-bancorp-custodial-accounts-api-openapi.yml
  capability_id: BC-1330.10
  capability_id_l1: BC-1330
  capability_name: Deposit Account Management
  confidence: 0.7
  evidence: GET /custodial_accounts    List Custodial Accounts; GET /custodial_account_closing_balances    List
    Custodial Account Closing Balances
  reason: Custodial accounts in this BaaS platform are the real bank deposit accounts holding end-customer
    funds, with closing balance retrieval — deposit account management. Only read operations are exposed,
    so confidence is moderate.
- tag: Products
  spec_file: fifth-third-bancorp-products-api-openapi.yml
  capability_id: BC-1310.10
  capability_id_l1: BC-1310
  capability_name: Product Catalogue Management
  confidence: 0.7
  evidence: GET /products  List Products; GET /products/{uid}  Get a single Product
  reason: On this Banking-as-a-Service platform, /products exposes the catalogue of financial products
    offered to end customers, read-only listing and retrieval — a banking product master/catalogue surface.
    Evidence is thin (two GETs, no schemas), hence moderate confidence.
- tag: Transactions
  spec_file: fifth-third-bancorp-transactions-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.7
  evidence: PUT /transactions/{uid}/authorize  Approve or deny a transaction; GET /transaction_events  List
    Transaction Events
  reason: Transaction retrieval plus approve/deny authorisation and custodial/synthetic line items is
    money-movement transaction processing on the banking platform. Not enough evidence to say whether
    this is card switching or general payment processing, so only the L1 is given.