Real-world treasury connectivity is rarely "API-only". Many clients keep host-to-host/files for bulk flows and use APIs for status, reporting, exceptions, and event-driven operations. This page translates those operating patterns into industry-specific treasury workflows.
Simple rule: use the right rail for the right job.
Bulk payment files and statement ingestion are operationally mature and often the fastest path to high volume and predictable cutoffs.
APIs can reduce latency in status reporting and investigations. This is where many clients see the clearest ROI.
Most clients run an integration layer that routes between API and file rails, manages retries, and centralizes audit and monitoring.
Each card shows typical flows and a recommended split between API and H2H.
Typical flows: high-frequency settlements, refunds, chargebacks, payouts, marketplace disbursements.
Use APIs for: real-time status, payouts tracking, reconciliation-ready identifiers, webhook/callback events.
Use H2H/files for: bulk payout runs, nightly reporting, statement ingestion at scale.
Validate early: status granularity, dispute workflows, return handling, and reporting fields.
Typical flows: API-driven money movement, partner integrations, KYC/AML workflows, event-driven operations.
Use APIs for: initiation, account/balance data, status callbacks, automation and monitoring.
Use H2H/files for: contingency rails, high-volume reporting, multi-bank normalization.
Validate early: onboarding prerequisites, entitlement model, and region coverage.
Typical flows: supplier payments, payroll, FX, multi-entity cash management, statements and reconciliation at plant/legal-entity level.
Use APIs for: status, balances, and exception handling; targeted initiation for urgent payments.
Use H2H/files for: scheduled pay runs, bulk statements, standardized reporting.
Validate early: ERP constraints, ISO 20022 mapping, and reference data ownership.
Typical flows: remote operations payments, supplier payments, multi-country FX, liquidity visibility across entities.
Use APIs for: near-real-time balances and status where connectivity allows; monitoring and alerts.
Use H2H/files for: stable bulk processing where networks are constrained; standardized statements.
Validate early: connectivity resilience, fallback operations, and regional bank differences.
Typical flows: large-value payments, project-based disbursements, strict controls, and audit requirements.
Use APIs for: approval status, reporting, and investigations; selective initiation for time-sensitive flows.
Use H2H/files for: bulk scheduled payments and reporting with strong control frameworks.
Validate early: entitlements, dual approvals, audit trails, and support model.
Pick your segment above, then compare public portal signals and limitations. For Citi-specific signals, use the Citi portal page and Citi vs JPM comparison.