· Published by Small Business Tool Lab
Opening week needs a payment system that reaches the right bank account, presents a clear invoice and handles a failed payment without confusion. Set up those three paths before taking customer money. A low headline fee cannot rescue a checkout that sends the wrong amount or a launch that starts before required registrations are complete.
Use this seven-day sequence as a setup plan, not a promise that every bank or state will approve an application within a week. If a required permit or verification is still pending, keep working in test mode and move the sales launch. The schedule follows dependencies: permission and banking first, payment channels next, then testing and reconciliation.
Day 1: Clear the Prerequisites and Open the Bank Account
List the business’s legal name, structure, tax ID requirements, operating location and the goods or services it will sell. Check the state revenue department and local licensing authority for registrations that must be completed before trading or collecting sales tax. Costs and processing times vary. An application receipt is not necessarily permission to begin.
Apply for an EIN through the IRS if your business needs one. The IRS application is free; a paid filing service is a separate optional service. Bring the documents your bank requests and use an account suited to your business structure. A sole proprietor and a corporation need not have identical account requirements.
Compare cash deposit charges, transfer limits, monthly fees and the records available for bookkeeping. Keep business activity separate from household spending so payouts and refunds are easier to reconcile. Confirm the account number through the bank’s own secure interface; never rely on details copied from an unexpected email.
Day 1 deliverable: a prerequisite checklist with each item marked required, completed or pending, plus the bank account selected for settlement. Pending legal requirements remain launch blockers. Bank verification can continue while you configure the processor.
Day 2: Choose a Processor Using Your Actual Payment Mix
Start with the sales channel. A shop counter needs reliable in-person acceptance; a service business needs invoices and deposits; an online seller needs a checkout customers can use. Square, Stripe and PayPal can all be candidates, but compare the specific product rather than the brand name alone.
Fee model: $8,000 monthly sales, 70% paid through the modeled channels, means $5,600 processed. Half is in person and half online: $2,800 each, with 35 transactions per channel at an $80 average ticket. U.S. domestic pricing below was checked against provider schedules during the October 11 revision. It excludes equipment, foreign cards, disputes, instant payouts, subscriptions and optional software.
| Setup modeled | In person/month | Online/month | Total/month | Annualized |
|---|---|---|---|---|
| Square Free: standard in-person + online card | $78.05 | $102.90 | $180.95 | $2,171.40 |
| Stripe: reader transactions + online Payments | $77.35 | $91.70 | $169.05 | $2,028.60 |
| Stripe: Tap to Pay + online Payments | $80.85 | $91.70 | $172.55 | $2,070.60 |
| PayPal: QR + standard online card | $67.27 | $100.87 | $168.14 | $2,017.68 |
The rates used are Square 2.6% + $0.15 in person and 3.3% + $0.30 online; Stripe 2.7% + $0.05 in person and 2.9% + $0.30 online, with $0.10 extra per Tap to Pay authorization; PayPal 2.29% + $0.09 QR and 2.99% + $0.49 standard online card. PayPal Checkout is a different channel at 3.49% + $0.49. Square’s plans and API channels also differ.
Every fee cell uses channel volume × percentage + transaction count × fixed fee. For example, Square online is $2,800 × 0.033 + 35 × $0.30 = $102.90. Stripe’s phone-based acceptance adds 35 × $0.10 = $3.50 to this scenario. The distinction matters because a reader fee and a phone authorization fee are not the same product.
The table models online Payments, not the full cost of issuing invoices. Stripe Invoicing Starter adds 0.4% per paid invoice. If all $2,800 of the modeled online volume instead goes through that product, add $11.20 to the Stripe row. Do not apply the separate post-payment-invoice $2 cap to ordinary Invoicing Starter fees.
Treat a difference of a few dollars as a prompt to test fit. Consider checkout usability, receipt wording, integrations and support. A processor that saves $10 but forces a monthly hour of manual reconciliation may be the more expensive operational choice. Conversely, an extra product fee becomes meaningful when invoice volume grows.
Day 3: Configure the In-Person Channel
Check the supported device, OS version, country and app or integration for your chosen Tap to Pay product. NFC hardware alone is not enough. Stripe Terminal may require a compatible application or integration; access to a Stripe account does not automatically turn every phone into a ready terminal.
If a reader better suits the counter, confirm compatibility, connectivity and the current purchase price before ordering. Consider where it will sit, how it will remain powered and what happens when the internet drops. Do not promise a customer that offline payments work unless the provider supports that feature and you understand its risk.
Set the business display name and receipt details. Decide which staff can accept payments, issue refunds or edit payout settings. Give employees only the permissions they need and enable the available account security controls. A phone passed around without a lock is not a launch procedure.
Day 4: Create One Clear Online Payment Path
Build a hosted link for one product or service first. Show the exact amount, what is included, customer contact details and any applicable cancellation or refund terms. Confirm tax treatment before publishing. Add custom-amount links only when the payment purpose and customer agreement remain clear.
Place the link where a customer already makes the decision: a booking confirmation, a quote acceptance or a relevant website page. Test the mobile view and the browser’s back button. A successful payment should lead to a useful confirmation, while a failed attempt should not leave the customer believing they paid.
For telephone orders, send the hosted link rather than asking customers to dictate card numbers into a message or notebook. A virtual terminal is a separate channel with different pricing and responsibilities. Do not describe a keyed payment as though it were the hosted checkout used in the cost model.
Day 5: Make the Invoice Match the Agreement
- Use a consistent invoice sequence, legal business details and a description the customer recognizes. Starting at 001 or 1001 is an administrative choice, not evidence of experience.
- State the agreed due date. Net 15 and Net 30 are options; the contract, customer and applicable rules determine what is appropriate.
- Use deposits only where the contract and applicable law permit them. Do not make a 50% deposit the universal rule for home-service work.
- Add a late fee only after checking legal limits and agreeing clear terms. A percentage printed on an invoice does not automatically make it enforceable.
- Offer bank payment when the product supports it, explain timing and confirm settlement before treating funds as available.
For a $2,000 invoice, PayPal Pay by Bank’s listed 1% fee capped at $10 produces a $10 charge. Its standard card fee would be $2,000 × 2.99% + $0.49 = $60.29. That is a $50.29 fee difference in this channel-specific example, before other applicable charges. Square ACH fees depend on plan, invoice versus API and settlement arrangement; verify the exact account schedule.
Day 5 deliverable: an invoice template approved against the real contract and a clearly identified payment product. Record whether the cost model includes invoice software fees. Do not send yourself a live bill just to create a test transaction.
Day 6: Test Without Artificial Live Charges
Stripe’s official testing guidance prohibits testing in live mode with real payment-method details. Use its sandbox or test mode and the supported test payment methods. For other providers, follow their documented testing route. Do not generalize a “charge your own card $1 and refund it” instruction across processors.
| Test case | Evidence to save |
|---|---|
| Successful payment | Correct amount, order/invoice reference and confirmation. |
| Declined payment | No false success message; customer can retry safely. |
| Refund simulation | Correct test record and refund status. |
| Duplicate submission | One intended order, with a clear handling rule for repeated attempts. |
| Payout configuration | Verified destination and access permissions; sandbox payments do not prove live settlement. |
Test the customer-facing name and receipt, not just the technical success flag. Check whether an invoice can accidentally be paid twice and how a staff member finds the original payment. An unexplained duplicate is easier to prevent before the counter opens than to refund during a queue.
Keep simulation and live money separate in your records. Sandbox transactions do not prove that a bank account is verified or that a production payout will arrive on a particular day. Confirm those settings through the provider, then reconcile the first legitimate customer transaction when sales begin.
Day 7: Reconcile a Real Sale and Set the Weekly Routine
Go live only after required approvals, verification and the test checklist are complete. The first transaction should be a genuine purchase. Record gross sale, tax, processing charge and net payout separately. The deposit into your bank is not necessarily the amount that belongs in the revenue column.
Set a weekly reconciliation appointment. Match processor transaction IDs to invoices and orders, list refunds separately and compare the payout report with the bank statement. Keep tax collected distinguishable from sales revenue. If a payout includes several days of transactions, reconcile the batch rather than inventing a single sale equal to the deposit.
The current IRS Form 1099-K guidance distinguishes payment-card reporting from TPSO reporting. For TPSOs, the federal required-reporting threshold is more than $20,000 and more than 200 transactions. Payment-card transactions have no minimum reporting threshold. Lower state rules or voluntary forms may apply; taxable business income is not exempt merely because no form arrives.
Confirm that the account’s tax name and ID are correct. Retain the underlying transactions so a year-end information return can be reconciled. Separately ask your processor about PCI responsibilities and the assessment appropriate to your setup. Hosted checkout reduces card-data exposure but does not make every configuration automatically identical.
Finally, budget for exceptions. Stripe lists a $15 received-dispute fee and a separate $15 fee for a manually countered dispute, with the countered fee returned when the dispute is won. Dispute response, refunds and payout timing deserve their own notes; they are excluded from the simple monthly table.
Frequently Asked Questions
- Can I start with a phone instead of a reader?
- Possibly, if the chosen processor, device, OS and application support Tap to Pay. Verify the product requirements and any authorization surcharge before relying on it for opening day.
- Is an invoice automatically included in online processing pricing?
- No. Payment processing and invoice software can carry separate charges. Identify the exact invoice product and add its fee to the transaction model.
- Should I make a small real payment to test the setup?
- Use the provider’s authorized testing tools. Stripe specifically prohibits live-mode testing using real payment-method details. A sandbox simulation and a first genuine customer sale serve different purposes.
- Does staying below the 1099-K threshold eliminate tax?
- No. Information-reporting thresholds do not determine whether business income is taxable. Reconcile your records and confirm filing requirements with the IRS or a qualified tax professional.
Business disclosure: This is an educational setup plan and fee model, not personalized legal, tax or financial advice. Provider fees, device support and registration rules can change. Confirm the applicable product schedule and jurisdiction before launching.
Related Reading
- 7 Card Payment Processing Mistakes Costing Your Small Business Money
- Square vs. Stripe for Service Businesses: Invoice, ACH, and Recurring Payment Fees
- Card Sales vs. Bank Deposits: Reconcile a Payout Step by Step
Keep this checklist: Save the relevant comparison and return to it when your actual terms or project scope change.
Sources and Further Reading
- Square official processing fees
- Stripe official pricing
- Stripe authorized testing guidance
- PayPal business fees
- IRS Form 1099-K general FAQs
- IRS employer identification numbers
Next step: Complete the prerequisite checklist, then test each payment channel before accepting genuine customer orders.
Published by Small Business Tool Lab · Editorial revision: October 11, 2026.