slug: us-bancorp
provider: US 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: Credit Transfers
  spec_file: us-bancorp-credit-transfers-api-openapi.yml
  capability_id: BC-1340.50
  capability_id_l1: BC-1340
  capability_name: Real-Time Payment Management
  confidence: 0.9
  evidence: POST /rtp/credit-transfers 'initiateRTPCreditTransfer Initiate RTP Credit Transfer'; GET /rtp/credit-transfers/{transactionId}
    'Get RTP Credit Transfer Status'
  reason: Initiation and status tracking of RTP (real-time payments) credit transfers — squarely Real-Time
    Payment Management. The title's 'Account Information' wording is an artefact; the operations are RTP
    payments.
- tag: Push to Card Payments
  spec_file: us-bancorp-push-to-card-payments-api-openapi.yml
  capability_id: BC-1340
  capability_id_l1: BC-1340
  capability_name: Payments & Card Management
  confidence: 0.8
  evidence: POST /push-to-card/payments 'initiatePushToCardPayment Initiate Push to Card Payment'; schema
    'PushToCardRequest'
  reason: Initiation and status of push-to-card disbursements — clearly Payments & Card Management, but
    it straddles payment initiation and card-network transaction processing, so no L2 is asserted.
- tag: Request for Payment
  spec_file: us-bancorp-request-for-payment-api-openapi.yml
  capability_id: BC-1340.50
  capability_id_l1: BC-1340
  capability_name: Real-Time Payment Management
  confidence: 0.8
  evidence: POST /rtp/requests-for-payment  initiateRTPRequestForPayment  Initiate RTP Request for Payment
  reason: Initiates and tracks Request-for-Payment messages on the RTP instant payment rail; clearly real-time
    payment management (initiation over the RTP scheme).
- tag: RTP Eligibility
  spec_file: us-bancorp-rtp-eligibility-api-openapi.yml
  capability_id: BC-1340.50
  capability_id_l1: BC-1340
  capability_name: Real-Time Payment Management
  confidence: 0.78
  evidence: GET /rtp/eligibility  getRTPEligibility  Check RTP Eligibility
  reason: Single operation checks whether an account/routing endpoint is reachable on the RTP (real-time
    payments) rail — a real-time payment rail capability, not general account information despite the
    spec title.
- tag: Exceptions
  spec_file: us-bancorp-exceptions-api-openapi.yml
  capability_id: BC-1400.30
  capability_id_l1: BC-1400
  capability_name: Fraud Detection & Investigation Management
  confidence: 0.75
  evidence: GET /positive-pay/exceptions 'Get Positive Pay Exceptions'; POST /positive-pay/exceptions/{exceptionId}/decision
    'submitExceptionDecision'
  reason: Positive Pay is a cheque-fraud prevention service; retrieving suspect items and submitting pay/return
    decisions is fraud detection and case decisioning rather than generic payment processing.
- tag: Accounts
  spec_file: us-bancorp-accounts-api-openapi.yml
  capability_id: BC-1330.10
  capability_id_l1: BC-1330
  capability_name: Deposit Account Management
  confidence: 0.7
  evidence: '''The Corporate Account Information API provides U.S. Bank corporate customers with programmatic
    access to deposit account balances and transaction data''; GET /accounts ''List Accounts'''
  reason: Exposes the bank's corporate deposit account inventory to customers — deposit account information
    within Deposits & Savings Management. Single read operation limits certainty on the sub-capability.
- tag: Exception History
  spec_file: us-bancorp-exception-history-api-openapi.yml
  capability_id: BC-1400.30
  capability_id_l1: BC-1400
  capability_name: Fraud Detection & Investigation Management
  confidence: 0.7
  evidence: GET /positive-pay/exceptions/history 'getExceptionHistory Get Exception History'; schema 'ExceptionHistoryItem'
  reason: Positive Pay exception history is the audit trail of check-fraud exception items, part of fraud
    detection and investigation. History-only read surface keeps confidence moderate.