By Raied Muheisen | Merchant services and Clover POS experience | Last reviewed June 18, 2026
Merchant-account onboarding succeeds when the account, equipment, software, deposits, and operating procedures are treated as one implementation. Approval alone does not mean a business is ready to accept payments. This checklist organizes the documents and tests required before go-live.
Printable merchant account onboarding checklist
| Stage | Items to confirm | Owner | Complete |
|---|---|---|---|
| Business identity | Legal name, DBA, entity, tax ID, address, owners, contact details | Merchant | ☐ |
| Banking | Deposit account, voided check or bank letter, authorized signer | Merchant/provider | ☐ |
| Processing profile | Products, channels, average and high ticket, monthly volume, delivery timing | Merchant/provider | ☐ |
| Agreement | Pricing, monthly fees, term, equipment, gateway, apps, cancellation | Merchant | ☐ |
| Equipment | Devices, accessories, ownership, shipping, installation, replacement | Provider/merchant | ☐ |
| Software | Menu/catalog, taxes, tips, users, permissions, receipts, integrations | Implementation owner | ☐ |
| Testing | Sale, void, refund, tip, receipt, batch, deposit, outage procedure | Merchant/provider | ☐ |
| Training | Open/close, returns, manager functions, support contacts, escalation | Merchant/provider | ☐ |
1. Prepare consistent application information
Use the same legal name, DBA, entity type, tax identification, ownership, address, and banking information across the application and supporting records. Explain differences before submission. The processing profile should accurately describe products, services, delivery timing, sales channels, average ticket, highest expected ticket, monthly volume, refunds, subscriptions, and card-not-present activity.
Do not reshape the business description merely to obtain easier approval. Inaccurate information can create delayed funding, reserves, requests for documents, or account problems later.
2. Review the complete agreement
Separate the merchant agreement from equipment, gateway, software, app, financing, and support terms. Record who provides each service and how it is canceled. Use the proposal comparison worksheet and the pricing-model guide.
3. Assign implementation ownership
Every item needs a named owner: hardware delivery, menu or catalog build, taxes, tipping, employee permissions, kitchen routing, inventory, ecommerce, accounting, gift cards, loyalty, internet, cabling, training, and live support. “The vendor handles setup” is not specific enough.
4. Inventory equipment
Record model and serial numbers, accessories, network requirements, power, stands, printers, scanners, cash drawers, scales, customer displays, and spare devices. Confirm ownership or lease status, replacement process, warranty, return address, and what happens after cancellation. Our lease-versus-purchase guide explains the contract questions.
5. Configure software from real workflows
Build representative products, variants, modifiers, taxes, discounts, tips, receipt text, manager approvals, employee roles, refund limits, and reports. Restaurants should test kitchen routing and online-order flow; retailers should test barcodes, returns, inventory adjustments, and purchase workflows. See the Clover restaurant implementation guide.
6. Complete controlled testing
- Run a small live sale and receipt.
- Void a transaction before settlement.
- Process a permitted refund after settlement.
- Test tips or adjustments where applicable.
- Close a batch and record the total.
- Match the settlement report to the bank deposit.
- Test each online or integrated channel.
- Document the internet and device failure procedure.
7. Train for exceptions
Staff need more than checkout training. Cover declines, duplicate-payment concerns, manual entry policy, refunds, manager overrides, offline behavior, receipt reprints, suspicious transactions, chargeback document retention, support escalation, and end-of-day reconciliation.
8. First-week review
Review deposits daily, check fees or billing start dates, confirm user permissions, examine voids and refunds, resolve catalog errors, and document support cases. Keep the prior system available during a processor change until the new environment has proven stable. Follow the processor-switching guide.
Organize your onboarding before equipment arrives
Process Rite can help a small business review its existing statement, proposed equipment, and implementation questions before go-live.
This checklist is general operational guidance. Approval, documentation, processing, compliance, and funding requirements vary.
Security and compliance handoff
Document who manages PCI questionnaires, device inspections, password and user administration, software updates, remote access, employee departures, and suspected payment incidents. Confirm that no employee is instructed to send card numbers, security codes, credentials, or unprotected statements through ordinary email. Save official support contacts separately from unsolicited calls or messages.
Ask how the provider validates support requests and remote sessions. Limit staff permissions to job needs, remove inactive users promptly, and schedule a post-launch review of access, refunds, manual entry, and manager overrides.