Best Merchant Account Providers for US Businesses

Before requesting rates, write down your US entity type, ownership, business activity, websites, customer locations, delivery times and payout bank details. Then ask whether the proposal supplies gateway technology, processing and acquiring services, or only some of those functions. Authorize.net explicitly distinguishes an All-in-one option from Gateway Only, and its support documentation requires a compatible merchant-services arrangement for gateway use. [4][5] Do not mistake technical gateway activation for completion of every required merchant approval.

For an internationally owned US company, request a specific response about owner verification and the operating footprint rather than treating company formation as the answer. Keep the bank destination and the party responsible for merchant acceptance visible in the comparison.

Stripe is a candidate to investigate when the priority is an online payment implementation with an appropriate approved business model. Its US standard page lists domestic-card processing at 2.9% plus $0.30 per successful transaction, while separately identifying additional charges for some circumstances. [1] Treat that published baseline as an input to a proposal, not a complete price for every product or transaction. Our practical evaluation is to map checkout, renewal, refund and reconciliation requirements to the chosen implementation, and price any additional services separately.

A familiar developer interface does not resolve underwriting. Stripe’s restricted-business policy distinguishes prohibited activities from categories needing further review; check the relevant policy and proposed service before investing in a migration. [6]

Square is a candidate for merchants evaluating payment tools alongside their point-of-sale workflow. Its US fees documentation distinguishes Square Free tap, dip or swipe payments at 2.6% plus $0.15, online or invoice payments at 3.3% plus $0.30, and Online API payments at 2.9% plus $0.30. [2] Those differences are a reason to specify the actual product rather than compare a generic Square rate.

Evaluate hardware, locations, inventory or staff workflows where relevant, and determine which subscription plan the quotation assumes. Its setup guide also separates identity and business onboarding from linking a verified bank account. [8] A successful bank link should therefore not be treated as evidence that every activation or verification requirement is finished.

Helcim’s US disclosures describe interchange-plus billing: underlying interchange and network or card-association charges are passed through, and a provider margin is added. Its first volume tier lists a 0.40% plus $0.08 card-present margin and a 0.50% plus $0.25 card-not-present margin. [3] The margin is not the total processing price. A merchant considering this model should supply a representative statement and ask for a transparent reconstruction covering card mix, transaction type, volume tier and all extra charges.

The useful comparison is the projected total for the same business, not an advertised markup against another provider’s blended rate. This approach can improve understanding of the bill without establishing that interchange-plus is cheaper for every merchant or that the activity is eligible.

Authorize.net’s published All-in-one option is $25 monthly plus 2.9% and $0.30 per transaction, subject to eligibility. Gateway Only is $25 monthly plus $0.10 per transaction and a $0.10 daily batch fee. [4] The second figure does not include a separate merchant-services provider’s processing charges. This distinction matters for a business retaining an approved merchant arrangement while adding compatible gateway technology.

Confirm the exact processor connection, currency and payment behaviours rather than assuming that every feature works on every configuration. The support documentation identifies US or Canadian merchant-services arrangements for gateway use. [5] Compare the full combination of contracts and fees, and identify which party handles a gateway incident, an acquiring restriction or a payout question.

A domestic retailer might begin by testing the point-of-sale workflow; an online merchant might begin with checkout and developer requirements; a business reviewing statement transparency might investigate interchange-plus; a merchant preserving an existing relationship might investigate a compatible gateway. These are Payment Guide scenarios, not measured superiority claims. The matrix below links each starting point to the evidence still required.

Stop when an essential activity, ownership, country, payment flow or bank condition cannot be satisfied. Do not average that failure into a score with attractive features. In particular, a general US comparison should not be repurposed as a guarantee of acceptance for gambling, financial services, adult content, telehealth or other activities requiring specific policy or eligibility checks.

Assume $30,000 of successful domestic-card payments in one month. Business A collects 1,000 payments averaging $30; Business B collects 200 payments averaging $150. At the same 2.9% plus $0.30 baseline, the percentage component is $870 for both. The fixed component is $300 for A and $60 for B, giving $1,170 and $930 respectively.

That is 3.90% versus 3.10% of sales without changing the provider or advertised rate. The table extends this arithmetic to other published models. Its rows describe different products and channels, so the lowest displayed number is not automatically an alternative for the same merchant. Hardware, optional software, international transactions, refunds, disputes and account-specific conditions are excluded from this deliberately narrow illustration.

The example is a processing-cost calculation, not a forecast of the bank balance. Request a dated illustration of when a captured sale becomes available, when the provider initiates the payout, what deductions or reserves may apply, and when your bank expects receipt. Obtain the account-specific conditions in writing instead of inferring them from a general marketing statement. Also include accounting time, exception handling, integration maintenance and subscription migration in the business case.

A small fee difference may be outweighed by a workflow that cannot reconcile payouts or preserve existing customer billing. Ask what data can be exported, which credentials can move, and what approval or customer action a change would require. These are procurement questions, not promises that every provider offers identical portability.

Use current provider requirements for the actual applicant. Square’s US payment terms describe registration and underwriting or identity verification; those terms should not be expanded into a universal checklist for every provider or ownership structure. [7] Likewise, legal permission for a business and a provider’s willingness to support it are separate questions. A price page establishes neither.

Document any relevant federal, state, network and provider requirements at their proper scope when the activity requires them. Outsourced payment collection also leaves responsibilities to allocate: PCI SSC says merchants must understand the third-party arrangement and confirm applicable compliance validation with the relevant accepting entity. [9] Ask for a responsibility schedule for your actual checkout or terminal implementation instead of assuming that outsourcing means no merchant security work.