United States
Payments

The practical US payment decision is not simply cards versus bank transfers. A checkout payment, an invoice debit and an urgent supplier payout have different authorisation, failure and reconciliation requirements. Keep those use cases separate when choosing a PSP or banking partner.

Choose the payment route

Use a realistic transaction sample for comparison. A lower quoted price is useful only if it covers the same card mix, refund rate, average ticket and payout requirements.

Card Market — Interchange Is Not MDR

The Federal Reserve's Regulation II guide describes the covered debit interchange standard: $0.21 plus 0.05% of transaction value, with an additional $0.01 for qualifying fraud prevention. The rule contains exemptions, including for certain small issuers and payment products.

This is interchange, not the total merchant discount rate. For an illustrative $100 qualifying debit payment, $0.21 + $0.05 + $0.01 equals $0.27 of interchange if the adjustment applies. This calculation does not include the merchant's other contracted fees. It is not a $0.27 acceptance quote.

Ask the acquirer to separate interchange, network fees and its own charges. Also ask how debit routing is selected and reported. Regulation II addresses network choice as well as interchange; do not infer that an issuer exempt from the interchange ceiling is automatically exempt from all routing rules. The card-scheme fee guide explains how to read the remaining components.

FedNow and RTP — The Real-Time Rails

FedNow is operated by the Federal Reserve; RTP is operated by The Clearing House. Their network operators announced $10 million transaction ceilings effective November 2025 and 9 February 2025 respectively. These ceilings do not promise a $10 million limit for every customer: the institution and product can set lower limits or restrict supported use cases.

Confirm both ends of the intended payment. A bank appearing in a network directory does not tell you whether your account can originate that payment, whether the recipient's account is reachable through the selected route, or which API is included in your contract. Require an explicit result for accepted, rejected and uncertain-status payments, and agree how staff investigate each.

For example, an urgent supplier payment should not fall back silently from an instant route to a slower transfer. Make the fallback visible to the payer, preserve the original reference and prevent a retry from creating a duplicate payment. These are product-design checks, not a claim that every bank implements the same workflow.

ACH — Authorisation and Returns Matter

Nacha reports 35.2 billion ACH payments totalling $93 trillion in 2025. Those are network totals; they are not an estimate of ACH's share of all consumer checkout transactions.

Before enabling ACH collection, define whether the customer sends a credit or you originate a debit. Establish the authorisation evidence, bank-account verification, submission and settlement schedule, and who monitors returns. A successful initiation response should not be treated as a guarantee against a later return. Use the ACH return-code reference to connect a return to the appropriate next step and the provider's instructions.

Regulatory Environment

FinCEN's interagency guidance distinguishes federal MSB registration, where required, from applicable state licensing. It does not establish one uniform licence requirement for every business that accepts a payment.

Map the activity before building a licensing budget: accepting payment for your own goods, holding another party's funds, transmitting money and acting for a principal are not interchangeable descriptions. Identify the legal entity, customer locations, funds flow and contractual responsibilities. Obtain a jurisdiction-specific assessment of requirements and exemptions. A partner-bank or payment-facilitator arrangement is not, by itself, proof that your business is exempt.

Crypto and Digital Assets

The OCC announced its final GENIUS Act implementing rule on 21 October 2026. The release gives 18 January 2027 as the effective date for the rule and Act, and states that application opening will be announced separately. Publication of the rule is not itself approval for a named issuer.

A payments integration requires its own assessment of issuer permission, custody, redemption, sanctions controls and fiat payout. A legal framework or an issuer announcement does not establish that every provider's product is available to every merchant. See the GENIUS Act briefing for the dated implementation context.

Practical Notes for Operators

Keep the provider comparison tied to evidence: a sample pricing statement, a settlement report, a documented dispute or return flow, and a tested payout. Ask providers to identify which legal entity supplies each service and which conditions could suspend availability.

For a merchant collecting through cards and paying suppliers through bank transfers, maintain separate controls for incoming acceptance and outgoing beneficiary changes. Reconcile the order or invoice, the provider transaction and the bank credit rather than relying on a single dashboard balance. The US providers listed on this page are candidates to investigate, not a recommendation that one stack fits every business.