How to Choose an Online Payment Service for One-Time Sales, Monthly Memberships, and In-Person Payments

A convenient payment method should not create more places to check

“We want customers to pay online. But what if payment confirmation, monthly memberships, and in-store sales all end up in different screens and create more missed updates?”

Some online payment services let you accept payment by sending a URL.

Others handle recurring billing or combine online sales with in-store checkout.

They may all look like ways to “accept cards.”

The difficult work, however, usually sits before and after the payment screen.

• Staff cannot tell which order or booking a payment belongs to
• A successful payment is not reflected in the working order list
• A failed monthly payment or scheduled cancellation is missed
• Product names or stock differ between the store and online channels
• An order or membership remains active after a refund

The short answer

Choose online payments in this order:

1. For the same one-time item agreed by phone, LINE, or email, test a reusable payment link
2. For monthly memberships or recurring services, test failure, retry, and cancellation as well as successful billing
3. For both in-store and online sales, compare connections to the POS, products, stock, and booking tools you already use
4. If price and delivery conditions change by customer, review the order or booking entry point, not only the payment page

First, write the payment flow in one sentence.

This sentence shows whether a payment page is enough or whether the order or membership record must also be connected.

Add who updates what after a refund or cancellation.

30-second check: where should online payments start?

Four questions provide a provisional starting point: a one-time payment link, recurring billing, unified in-store and online sales, or preparation of sales terms.

The result is not a final decision.

Use it to choose a sales situation to test and prepare what to ask a service provider or development partner.

Look at where the amount is decided before looking at what you sell

The same product can need a different setup depending on where its amount is determined.

A fixed-price trial class can use one reusable payment link for many customers.

A repair priced after inspection needs a customer-specific amount and an order reference.

Online sales with multiple items need product selection, totals, delivery details, and stock before payment.

A monthly membership depends less on the first payment than on the next bill, failure, pause, and cancellation.

Write these five points for one real sale:

1. Which guidance leads the customer to apply?
2. When are the item, quantity, and amount decided?
3. Where can the customer review the terms and cancellation conditions before paying?
4. Which screen or notification does staff check after payment?
5. Who delivers the item, confirms the booking, or activates the membership?

Compare service names only after this flow is visible.

Compare Square, Stripe, and STORES by sales method

The table is not a ranking.

It compares one-time sales, recurring billing, in-store use, and connections to current tools.

Transaction and monthly fees change, so fixed prices are not reproduced here.

Before signing up, check the official pricing page and the conditions that apply to your products and business.

What official information tells you to verify

Square Payment Links supports reusable links, buy buttons, QR codes, customer-entered amounts, and recurring payments, and describes connections to Square POS and other Square products (reference).

Stripe Payment Links provides a Stripe-hosted page that can be shared by email or on a website and can accept one-time or recurring prices (reference).

STORES presents in-person payments, POS, online stores, booking, invoices, and payment links as services that can be combined under one account (reference).

None of these statements means that signing up automatically organizes the way your business works today.

For one-time sales, test matching after the link is sent

A payment link can test one-time sales before building a full online store.

It suits a fixed-price trial class, consultation, event ticket, or repair deposit.

A link alone, however, may not show which working order it belongs to.

Collect only the details required to match the payment.

• Show the product or service name
• Attach one order or booking reference
• Confirm the customer name or contact route
• Show the amount and delivery timing
• Decide which staff member receives the payment notification
• Decide which detail staff use to search for the transaction

Square states that link payments can create notifications and be reviewed with transactions, orders, and customer details in Square Dashboard.

Stripe also lets staff confirm payment in the dashboard and offers event notifications for later work (reference).

Start without a large automated connection. Confirm that one responsible person can match one payment and mark the order paid.

Compare monthly payments using the month that does not succeed

Monthly memberships require more than successful card registration.

The following states appear during normal operation:

1. Initial payment is pending and access has not started
2. This month's payment succeeded and service is available
3. Payment failed and repayment guidance was sent
4. Membership is paused and billing and access are stopped
5. Cancellation is accepted but the contract end date has not arrived
6. The contract ended and future billing and access are stopped

Stripe supports recurring prices through Payment Links and describes a customer portal for managing payment details and subscriptions.

Square also describes recurring payment options from its payment links and subscription products.

Ask these questions while comparing services:

• When are the first and later billing dates?
• Who receives a failed-payment notice, and through which channel?
• Does access return after a successful retry?
• What are the pause and cancellation deadlines?
• What are the final billing and service-end dates after cancellation?
• Where does staff review payment status?

Test one failed payment and one cancellation, not only a successful charge.

For in-store plus online sales, avoid adding product and refund review locations

A business may use a terminal in store, a payment link for preorders, and an online store for delivery.

That can be convenient for customers while leaving staff to compare three screens.

For one product, identify where each of these details is maintained:

• Product name and price
• Quantity available in store and online
• Payment result and expected deposit
• Customer contact details
• Pickup or delivery status
• Cancellation and refund record

Square describes reviewing online and in-person transactions in Square Dashboard.

Stripe in-person payments use Terminal, where a business chooses supported devices, locations, and an implementation method (reference).

STORES allows businesses to combine POS, online-store, and cashless-payment products.

The word “connected” does not guarantee that product, stock, customer, and refund status all update together.

Test one in-store sale and one online sale for the same item.

Separate payment completion from a deposit in your bank

A completion message on the customer's screen may not always mean staff should immediately provide the item.

A successful payment in the service also occurs before the provider transfers proceeds to the business bank account.

Use separate terms for each state:

1. Order received: the customer submitted an order or booking
2. Payment pending: payment started but final confirmation is pending
3. Paid: the payment service shows a successful payment
4. Provided: the product, booking, or access was delivered
5. Deposited: proceeds reached the business bank account
6. Refunded: the refund was processed and recorded

Stripe explains that some payment methods take longer to confirm and should use separate completion events.

Choose the state staff rely on before releasing a product or activating access.

For refunds, check the order and membership updates beyond the button

A service can support refunds without restoring the original order, stock, booking, or membership state.

Square explains that full and partial refund availability and timing vary by payment method (reference).

Stripe also documents full and partial refunds from its dashboard.

Verify this complete flow:

• Show the customer when a refund is available
• Find the correct order and payment
• Limit which staff members can issue refunds
• Issue a full or partial refund
• Tell the customer what to expect next
• Update the order, stock, booking, or membership state
• Record the reason and responsible staff member

Some refund actions cannot be undone.

Confirm testing methods and staff permissions before handling live payments.

A provider-hosted payment page does not replace your sales terms

Even when the payment provider supplies the payment page, the selling business defines what is sold, the amount, and when it will be provided.

Japan's Consumer Affairs Agency explains the information customers must be able to review at the final confirmation step for online sales (reference).

The guidance includes applications made through social media or chat.

It also explains that when a separate provider page collects only card details, the preceding order-confirmation page may be the final confirmation screen.

Before payment, make at least these items easy to review:

• Product or service content, quantity, and period
• Total amount, payment timing, and payment method
• Delivery or service-provision timing
• Return, cancellation, and termination terms and contact method
• Application deadline when one applies
• For recurring contracts, each delivery or service period, billing timing, and contract period

For monthly payments, a button labeled only “purchase” may not communicate that billing continues.

Keep the product description, final confirmation, confirmation email, and cancellation guidance consistent.

Read the pricing table vertically through one sale

Comparing only transaction fees can hide differences in terminals, monthly functions, deposits, refunds, and staff controls.

Record these points for one sale in the same table:

1. Setup, monthly, and per-payment costs
2. Required payment terminal and replacement support
3. Supported cards, wallets, transfers, and other methods
4. Application and merchant-review lead time
5. Deposit cycle and any required action
6. Full and partial refunds and disputed payments
7. Plans required for recurring billing, invoices, and in-person use
8. Connection conditions for POS, online store, booking, and accounting
9. Staff permissions for viewing and refunds
10. How active recurring payments and past records are handled when leaving the service

Run one real sale from top to bottom instead of reading feature names across a page.

Five signs to discuss a focused connection

When several of these conditions apply, discuss the connection to orders or membership records before replacing the payment provider:

1. Quotes, discounts, or extra charges differ by customer
2. Staff must confirm stock, booking capacity, or eligibility before payment
3. One payment must be allocated across several products, locations, or responsible teams
4. Payment status controls booking, membership access, or learning materials
5. A refund requires staff to correct orders, stock, bookings, and memberships in several screens

This does not mean building your own card-entry page.

Use a provider-hosted payment page and consider only the connection between the order reference, payment status, and next staff action.

Start with one product, one sales route, and one responsible team

The following is a practical Ready Mock guideline.

Do not switch every sale at once. Use this first scope:

Do not stop testing after a successful payment.

Also test a customer who leaves midway, pays twice, or cancels.

Six preparations before consultation

1. Collect three recent sales

Collect one real example from one-time, recurring, and in-store sales.

Skip any sales method your business does not use.

2. Gather pre-payment guidance

Place product descriptions, quotes, LINE messages, application forms, and cancellation guidance together.

Check whether the same product has conflicting amounts or terms.

3. Write the work after payment

Record who sees the notification and where they update the order, booking, or membership.

Separate any later confirmation of the bank deposit.

4. Prepare one exception of each type

Test payment failure, duplicate payment, cancellation, full refund, and partial refund.

For monthly billing, add pause and termination.

5. Run one complete sale in representative services

Go beyond pricing pages. Register one item and test payment, notification, search, and refund.

For in-store plus online sales, sell the same item once in each channel.

6. Use remaining review and re-entry as consultation material

Do not immediately convert every unsupported operation into a development feature.

Explain who checked which screen and what they had to enter again.

Online payment service comparison checklist

Select only what you can answer today.

Unselected items become questions for a trial or consultation.

Copyable consultation note

Use this note before choosing a payment service.

Write “confirm during consultation” for anything that is still unknown.

What we want to discuss about online payment services:

Current sales routes:
Example: storefront, phone, LINE, email, and booking page

First product or service to test:
Example: one baked-goods set for in-store pickup

When the amount becomes final:
Example: fixed before ordering, or confirmed by staff after reviewing the request

Current payment methods:
Example: in-store card payment, bank transfer, and cash

How payment is checked today:
Example: one staff member matches the order sheet with the payment dashboard each morning

Recurring payment conditions:
Example: the same amount each month; reception contacts the customer after a failed payment

Information to share across storefront and online sales:
Example: product, stock, customer, and refund status

Payment states we need to distinguish:
Example: instructions sent, awaiting payment, paid, and refunded

Work after a refund or cancellation:
Example: cancel the order, restore stock, and contact the customer after the refund

Terms the customer must confirm before paying:
Example: product, quantity, total, delivery date, and cancellation terms

Required payment methods:
Example: prioritize cards and confirm customer demand before adding other methods

What we need to verify about deposits:
Example: when sales reach the bank account and what fees are deducted

Services currently in use:
Example: point-of-sale system, online store, booking service, and accounting software

Providers compared or tested:
Example: reviewed the official Square, Stripe, and STORES screens, but not the failed recurring payment flow

First test scope:
Example: test one product, one sales route, and one responsible team through the full flow

Materials we can share:
Example: order notes, payment instructions, refund procedure, and monthly summary sheet

Your next step

Choose the most recent customer to whom you sent payment instructions.

Write one line for what you sold, where the amount was decided, where payment was confirmed, and what staff updated afterward.

This sentence is enough for a first consultation:

Further reading

• Block, Inc., Square, Square Payment Links. Checked reusable links, customer-entered amounts, recurring payments, POS connections, and transaction review. No publication or update date shown. Accessed August 9, 2026.
• Block, Inc., Square Help Center, Create and share payment links. Checked link creation, sharing, regional conditions for Japanese accounts, and when a full online store is more appropriate. No publication or update date shown. Accessed August 9, 2026.
• Block, Inc., Square Help Center, Manage refunds to customers. Checked full and partial refunds, payment-method restrictions, staff permissions, and refund records. No publication or update date shown. Accessed August 9, 2026.
• Stripe, Inc., Stripe Documentation, Accept payments online without writing code. Checked Stripe-hosted payment pages, sharing, receipts, and dashboard refunds. No publication or update date shown. Accessed August 9, 2026.
• Stripe, Inc., Stripe Documentation, Create a payment link. Checked one-time products, recurring prices, and customer-entered amounts. No publication or update date shown. Accessed August 9, 2026.
• Stripe, Inc., Stripe Documentation, After a Payment Link payment. Checked payment review, notifications, connections, customer subscription management, receipts, and refunds. No publication or update date shown. Accessed August 9, 2026.
• Stripe, Inc., Stripe Documentation, How Terminal works. Checked in-person payments, devices, locations, and no-code or custom implementation methods. No publication or update date shown. Accessed August 9, 2026.
• STORES, Inc., STORES. Checked the combination of cashless payments, POS, online store, booking, invoices, and payment links, including plan differences. No publication or update date shown. Accessed August 9, 2026.
• STORES, Inc., STORES online store. Checked online sales, recurring sales, preorders, digital products, and plan differences. No publication or update date shown. Accessed August 9, 2026.
• Consumer Affairs Agency, Japan, Guidelines for displaying information at the application stage of mail-order sales. Checked final-confirmation screens, social and chat applications, required information, and recurring-contract presentation. Revised as an attachment to the November 19, 2024 directive. Accessed August 9, 2026.