specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Huntington Bancshares providerId: huntington-bancshares created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - FinOps - FOCUS - Banking - Treasury - Payments description: 'FOCUS-aligned FinOps for Huntington Bank treasury APIs: API access is bundled with the commercial banking treasury management contract. Cost surface is account-analysis fees, per-transaction fees (ACH, wire, RTP), and ERP-integration service charges rather than per-call API consumption.' notes: Per-call API pricing is not published; cost flows through the broader Huntington commercial banking relationship. sources: - https://hnbdevportal.huntington.com/ - https://www.huntington.com/Commercial/treasury-management alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: The Huntington National Bank serviceCategory: Banking & Treasury Management billingModel: pricingCategory: Bundled (Commercial Banking Contract) billingFrequency: Monthly account analysis billingCurrency: USD chargeCategories: - Usage - Purchase - Adjustment focusColumns: ServiceName: Huntington Treasury Management API ServiceCategory: Banking & Treasury Management ProviderName: Huntington Bancshares PublisherName: The Huntington National Bank InvoiceIssuerName: The Huntington National Bank BillingCurrency: USD ChargeCategory: Usage meters: - name: account_analysis_fees description: Monthly account-analysis charges from the treasury management agreement; the primary cost surface for API-enabled treasury workflows. unit: month aggregation: sum dimensions: - account - service_code - name: ach_transactions description: ACH origination and receipt transaction count submitted via the API. unit: transaction aggregation: sum dimensions: - direction - account - name: wire_transactions description: Wire-transfer count submitted via the API; typically priced per wire at the contracted rate. unit: transaction aggregation: sum dimensions: - type - account - name: rtp_transactions description: Real-Time Payments / FedNow transactions submitted via the API. unit: transaction aggregation: sum dimensions: - account - name: api_requests description: API call volume across the 500+ interfaces; not directly billed but useful for capacity and quota monitoring. unit: request aggregation: sum dimensions: - api - consumer_key principles: - name: Visibility description: Reconcile monthly account-analysis statements against API transaction logs. Use the developer portal usage view (when surfaced) to track per-consumer-key call volume against Apigee quotas. - name: Allocation description: Tag API consumer keys per ERP system / business unit. Map account-analysis service codes back to the consuming team for chargeback. - name: Optimization description: Batch ACH origination where possible; minimize same-day wire usage in favor of standard ACH or RTP for predictable lower fees; cache reference data (account balances, payee lists) to reduce redundant API calls; review unused services on the account-analysis statement quarterly. - name: Accountability description: Designate a treasury-operations owner accountable for per-transaction fee variance. Establish SLAs with Huntington partner enablement for quota raises and incident response. maintainers: - FN: Kin Lane email: kin@apievangelist.com