Ecommerce
merchant accounts.

01 / The foundations

What an ecommerce merchant account actually does

An ecommerce merchant account is the acquiring arrangement that lets an online business accept card payments and receive the proceeds, subject to its agreement. It is different from your operating bank account, where you pay suppliers and payroll. It also does a different job from the payment form shoppers see at checkout.

Several services sit behind that one button. One provider may bundle them; another may connect separate companies. Names vary, so ask who performs each role and who is accountable when something fails. “Payment service provider,” or PSP, is a broad provider term; a payment facilitator describes a particular operating model, not every PSP. Adyen’s industry glossary distinguishes these roles, including the acquiring institution, processor, gateway, and card issuer.¹

Approved, captured, and paid out are different events

Authorization is the issuer’s approval of a payment attempt. Capture submits an authorized amount for completion. Payout moves available proceeds to your bank. A storefront’s “order placed” message is not proof that all three happened.

Some integrations capture immediately; others separate authorization and capture. That distinction matters when stock availability, partial shipments, or fraud review comes first. Authorizations expire, and eligible capture windows depend on the payment method and configuration. Stripe’s documentation illustrates why a delayed-capture workflow needs explicit timing controls.²

Assign an owner to each transition: accepted order, successful payment, shipment, refund, and bank deposit. For a broader introduction, read the merchant accounts guide.

02 / Build around your business

Choose the account for the way you sell

Two stores can process the same monthly volume and need different setups. A stocked apparel shop, a preorder furniture brand, and a subscription business have different delivery obligations, return patterns, and cash needs. Describe those differences before comparing quotes.

A payment facilitator can provide convenient onboarding and an integrated stack. A separately underwritten merchant account can offer another way to structure your provider relationships and commercial terms. Neither structure automatically guarantees lower costs, uninterrupted funding, or acceptance of a particular product. Compare the actual agreement and service, not the category’s reputation. Our merchant account versus payment facilitator guide explores the distinction.

Do not present a marketplace as an ordinary store, or leave a restricted product off the application. The right starting point is a complete description of the business. The NUMUS retail and ecommerce page is the service overview; this guide is the buying and operating playbook.

03 / Approval and growth

Make your business easy to understand

Underwriting is easier to navigate when your application, website, statements, and explanations tell the same story. Start with legal identity and ownership, then show what customers purchase, how orders are delivered, and how you handle problems.

Your website is part of that story. Stripe, for example, requires online merchants to identify the website, social profile, or application used to promote or sell their products.³ For your own review, make pricing, delivery expectations, contact information, and return terms easy to find. A checkout cannot compensate for unclear product claims or an unreachable business.

Apply for the next stage, with evidence

Prepare both current volume and a realistic growth scenario. Explain an upcoming promotion, a larger average order, a new country, or a move into recurring billing before it changes your transaction pattern. Ask which changes require advance approval and how volume or ticket limits are reviewed.

A useful growth note is specific: “Our normal monthly volume is $80,000. We have inventory for a launch that could reach $160,000, with most orders shipping within three business days.” Attach the supporting operational plan rather than assuming a forecast will be accepted.

04 / The conversion experience

A good account still needs a good checkout

Start with the platform your team can operate. Confirm the exact plugin, version, gateway, payment methods, currencies, and subscription features. “Works with ecommerce” is too broad to be useful. A standard card integration may not support the wallet, recurring billing, or partial capture flow you intend to use.

Hosted checkout, embedded forms, and custom components carry different development responsibilities. Stripe’s documentation offers all three approaches; that does not make their maintenance effort interchangeable.⁴ Choose how much control you need and who will keep the implementation working.

Test the purchase your customer will actually make

• Mobile: readable fields, useful error messages, and no keyboard covering the payment button.
• Price clarity: shipping, tax, recurring terms, and the final total before commitment.
• Recovery: a clear path after a decline, authentication challenge, or interrupted connection.
• Confirmation: an accurate order status and a usable receipt.
• Exceptions: out-of-stock products, partial refunds, duplicate clicks, and abandoned payments.

Add payment methods because your buyers need them. Evaluate cards and wallets for everyday checkout, then assess bank payments or other methods for suitable use cases. Each brings its own cost, timing, return, and integration considerations. For invoice-driven customers, our ACH merchant accounts guide provides a separate starting point.

Measure each change. A faster-looking form is not an improvement if successful orders fall or support requests rise.

05 / The economics

Compare the cost of an order, not just a rate

The price quoted to a merchant combines commercial terms with underlying payment costs. Visa distinguishes the interchange paid between financial institutions from the merchant discount negotiated with the merchant’s provider.⁵ An advertised percentage alone is not a complete forecast.

Request a written breakdown of percentage charges, per-transaction charges, monthly costs, and conditional charges. For interchange-plus pricing, clarify what is passed through and every markup. For bundled pricing, clarify exclusions and surcharges. For tiered pricing, ask how your actual transactions fall into each tier. Then model the same volume, ticket size, and card mix across every quote.

Small tickets magnify fixed fees

Consider an illustrative 2.9% plus $0.30 transaction charge. This is arithmetic, not a NUMUS quote or a recommendation of any provider.

At $100,000 in monthly charges, 10,000 orders incur $3,000 in $0.30 charges; 2,000 orders incur $600. Both produce the same percentage-based cost. Average order value changes the economics even when monthly volume is identical.

Check the layers outside the processing quote

Review gateway and platform costs, fraud tools, currency conversion, dispute handling, refund treatment, premium funding, minimums, and cancellation terms. Shopify specifically documents third-party transaction fees that can apply in addition to an external provider’s processing fees.⁶ Compatibility and total cost belong in the same comparison.

Refunds also deserve their own line. Stripe states that original processing fees are not returned when a payment is refunded; refund-related charges depend on the applicable pricing schedule.⁷ Check your own agreement rather than assuming a returned sale erases its payment costs.

Track payment expense divided by gross processed card volume, using the same period and scope each month. Keep lost merchandise, refund principal, and money held in reserve separate so the number remains interpretable. See our processing fees guide and fee calculator for deeper comparisons.

Protect contribution margin as well as the rate

On $100,000 of monthly volume, a 0.10 percentage-point reduction saves $100 before other changes. Recovering ten legitimate orders that each contribute $40 after goods, fulfillment, and payment expense would contribute $400 before fixed overhead. Both are hypothetical examples, but they show why conversion, acceptance, and operating reliability belong in a pricing decision.

Do not assume a provider change will recover those orders. Establish the baseline, identify the failure, and measure the result. A lower rate that adds platform charges or engineering work may lose its advantage. A more expensive setup needs measurable benefits to justify its premium.

06 / Protect the margin

Control fraud without rejecting good customers

Your target is profitable, legitimate orders. Blocking more transactions can lower fraud while also losing real customers. Review the reasons behind declines and manual reviews, rather than treating a single approval percentage as the whole story.

Use a layered approach appropriate to the business: address and card-security checks, device and velocity signals, authentication, and a defined manual-review process. EMV 3-D Secure exchanges transaction, payment, and device information to help issuers authenticate online shoppers.⁸ Authentication is not a guarantee against every dispute; confirm the applicable protections and exceptions with your provider.

Dispute prevention starts before the payment

Make the product description, delivery promise, recurring terms, and customer-service route consistent across the ad, store, and receipt. Use a recognizable billing descriptor. Visa’s merchant guidance emphasizes clear refund and cancellation policies, recognizable merchant information, and prompt responses when disputes arise.⁹

Build evidence while serving the order: what was purchased, which terms were accepted, when it shipped or became available, and how the customer communicated with you. Assign a person to response deadlines. Better records help your team respond accurately; they do not guarantee a win.

Keep the checkout’s security work visible

A hosted form does not make website security someone else’s entire job. PCI SSC’s ecommerce guidance addresses payment-page scripts, integrity, and tamper detection. The applicable validation responsibilities depend on the implementation and compliance program.¹⁰ Confirm your scope with the acquirer or appropriate adviser, inventory checkout integrations, and give changes an owner. An unnecessary marketing script should not enter a sensitive payment page by accident.

07 / Cash flow at scale

Revenue is not the same as available cash

Ad spend, inventory purchases, wages, and shipping may be due before a payout arrives. A growing store can therefore sell more and become more cash-constrained at the same time. Put the payment timeline into the cash forecast.

Ask separately about settlement timing, payout schedule, bank arrival, initial funding, weekends, and exceptions. Stripe’s payout documentation explicitly distinguishes when a balance becomes available from the schedule that sends available funds to the bank.¹¹ “Daily payouts” does not by itself mean today’s orders are available today.

A reserve is restricted cash, not a processing fee

Providers may retain funds to cover potential exposure. PayPal, for example, describes rolling and other reserve structures.¹² Your agreement determines the actual calculation, release conditions, and review process. Ask about refund deductions and what happens after processing stops.

As a simple illustration, withholding 5% of $100,000 monthly volume puts $5,000 a month into reserve before any releases. After three such months, $15,000 would be held if nothing had been released or applied. This is a hypothetical cash-flow example, not a typical offer.

A payment setup is ready to scale when growth leaves enough cash to fulfill the orders it creates.

Stress-test a promotion with slower payouts, extra returns, and a supplier payment arriving early. Give the team a spending limit based on available funds, not the storefront’s gross sales dashboard.

08 / Run it like an operation

Build a payment dashboard your team can act on

Use the same order and transaction references across the store, processor, refunds, fulfillment system, and accounting records. Reconcile gross captured sales to refunds, fees, disputes, reserve movements, and the bank deposit. A payout is a net movement; booking it as gross sales hides the adjustments. Bridge opening and closing pending and available balances as well, because sales and payouts can fall in different periods.

Give your developer a practical acceptance test: a customer pays, closes the tab before seeing the confirmation, and later contacts support. The team should still be able to establish the payment’s real status without charging again or shipping twice. Ask how the integration handles delayed notifications, repeated requests, and interrupted checkouts. Test those paths in the provider’s test environment.

Give finance and support the access they need without sharing an administrator login. Someone should own each daily exception queue: paid but unfulfilled, shipped but not captured, refund requested but unfinished, and payout expected but missing. A clear queue is more useful than several dashboards that disagree.

These are internal management definitions, not card-network monitoring formulas. Keep any required network metrics separately. Retries can inflate attempts; disputes can arrive long after the original order. Compare like periods and explain the lag.

Subscriptions need their own operating plan

A saved card is not unlimited permission to charge. Stripe’s saved-payment documentation calls for consent covering the intended future use, payment timing and amount, and applicable cancellation terms.¹³ Store the agreement, provide clear customer controls, and define what happens after a failed renewal. Decide who owns retry settings and customer outreach before launch.

International sales add more than a currency selector

Ask about permitted countries, supported presentment and settlement currencies, conversion costs, authentication, delivery evidence, and refund handling. Model the full margin after shipping and returns. Launch a manageable market first and compare results before widening availability. A payment method appearing at checkout does not establish that every product can legally be sold in every destination.

09 / Changing providers

Make the exit plan before you need it

Ask who controls stored payment credentials, whether a supported transfer is available, and what the receiving provider needs. Token identifiers are not automatically portable between systems. Stripe documents a coordinated process for importing payment data from another provider; that is a concrete example of why migration is a project rather than a settings toggle.¹⁴

Inventory subscriptions, saved cards, payment links, refunds, open disputes, and accounting connections. Confirm contract notice periods and any exit charges. Keep access to historical records and the ability to handle existing transactions after new orders move.

1. Approve the destination: business model, commercial terms, platform, and recurring use cases.
2. Test the journey: successful and failed payments, authentication, refunds, and reconciliation.
3. Plan the cutover: a quiet period, named owners, monitored results, and a rollback path.
4. Close deliberately: reconcile residual balances and outstanding obligations before ending the old relationship.

Do not email raw card data or move it through an ordinary spreadsheet. Use the providers’ approved transfer process. The processor switching playbook expands the operational checklist.

10 / The buying conversation

Ask questions that produce usable answers

Give every provider the same business profile and ask for written answers. It makes omissions easier to spot and prevents a low introductory price from dominating the decision.

1. Fit: Are these products, fulfillment times, sales channels, and countries approved?
2. Economics: What would our last representative month have cost, including all layers?
3. Growth: What are our volume and ticket limits, and how do we request changes?
4. Funding: When do funds become available, and what may delay or restrict them?
5. Technology: Which exact integrations and features are supported, and who maintains them?
6. Support: Who owns an urgent funding issue, checkout incident, or dispute deadline?
7. Control: What can we export, change, or move if the relationship ends?

Score answers against your priorities: contribution margin, cash availability, operational effort, customer experience, and room to grow. Ask for clarification when “included,” “instant,” or “unlimited” appears without a definition.

11 / Prepare your application

Turn a store description into a complete review

Gather legal business and ownership information, your live website, settlement-bank details, recent available bank or processing statements, and any documents relevant to your product category. Exact requirements vary by the business and provider; a startup should explain its stage rather than invent processing history.

Include average and highest expected tickets, current and forecast monthly volume, fulfillment times, refund policy, subscription details, and the platform you use. If the store has a problem today, describe it directly: a missing feature, unpredictable funding, high costs, or a business-model mismatch.

Have sensitive documents ready for the application workflow rather than placing them in a general email conversation. You can start the NUMUS merchant application with your business information and supporting documents. Submission begins the review; final acceptance, pricing, funding, and integration availability depend on the applicable approval and agreement.