Things that usually vary:
- Fees: Often a percentage per transaction; sometimes an extra fee for international cards or currency conversion.
- Payout time: Money might reach your bank in anywhere from the same day to several days, depending on the provider and your account history.
- Features: Some platforms add invoice tracking, reminders, partial payments, and recurring billing.
Best suited to:
People who don’t need to charge customers face-to-face on the spot, or who can wait while the customer pays from their phone.
2. Virtual terminals (card-not-present, typed-in payments)
What it is:
A virtual terminal is an online version of a card machine. Instead of inserting or tapping a card, you type the card details into a secure webpage.
Typical use cases:
- Taking orders over the phone 📞
- Handling mail orders or manual billing
- Small offices or clinics that don’t want a countertop terminal
How it works:
- Customer gives you their card number, expiry, CVV, and billing details (usually over the phone).
- You log in to the virtual terminal in your browser.
- You key in the card details and amount.
- The system processes it through the regular card network.
- Customer gets a receipt (usually by email), and you see it marked as paid.
Key differences vs. in-person card machines:
- The card is not physically present, so:
- There’s usually a higher risk of fraud.
- Fees can be higher than for “card-present” transactions.
- You bear more security responsibility (e.g., not writing card details on Post-its, keeping systems secure).
Best suited to:
Businesses that often take phone orders, have an office environment, or need a backup option when in-person payments fail.
3. “Tap to Pay” on a smartphone (phone as the card reader)
What it is:
Some payment providers let you use your smartphone itself as a card reader using contactless (NFC) technology. The customer taps their card or phone on your smartphone to pay — no extra hardware.
Typical use cases:
- Market stalls, pop-up shops
- Delivery services and on-site work
- Mobile professionals (beauty, fitness, consulting)
How it works:
- You install a Tap to Pay–enabled app on a compatible smartphone.
- You enter the amount and select contactless payment.
- The customer taps their card, phone, or watch against yours.
- The transaction is processed like a normal in-person card payment.
Things to check carefully:
- Device compatibility: Not all phones or operating systems support this yet.
- Transaction limits: Some setups may have lower limits for contactless without PIN.
- Security standards: Reputable providers follow strict PCI and device security rules.
Best suited to:
People who want in-person card payments without carrying a separate card machine, and who have a modern smartphone.
4. Online checkout or “pay on your website”
What it is:
You add a checkout to your website so people can pay with a credit or debit card (and often digital wallets). This works whether you sell physical products, digital items, or services.
Typical use cases:
- Online shops
- Service providers who take bookings online
- Event organizers selling tickets
How it works:
You sign up with a payment gateway or platform.
You integrate it with your site (directly, via plugins, or no-code tools).
Customers:
- Add items to a cart or choose a service
- Go to checkout
- Enter card details or use a saved payment method
- Receive confirmation
Funds flow into your merchant/platform account, then to your bank.
Key variables:
- Technical setup: Can be very simple (plug-in) to quite advanced (custom integration).
- Control: You usually get more control over branding, taxes, shipping rules, and customer data.
- Compliance: Card details must be handled in a compliant way. Using a hosted checkout page helps reduce your direct responsibilities.
Best suited to:
Businesses that want to scale online sales and don’t mind a bit of setup.
5. Email money requests and “pay by link” from banks or wallets
Some banks and digital wallets offer money request tools, which can function as a simple alternative to card machines.
What it is:
- You send a payment request (by email, text, in-app link).
- The recipient pays. Depending on the system, they may:
- Use their bank account directly, or
- Use a card stored in the wallet or app.
How it works:
- You create a request (amount, description).
- Share the link or request format.
- The customer pays from their bank app or wallet.
- You receive confirmation and see the funds in your account or wallet balance.
Important distinction:
In some systems, this is basically a bank transfer rather than a “card payment” in the technical sense — but to your customer it often feels similar (they click and pay digitally).
Best suited to:
Individuals, micro-businesses, or side gigs where you’re okay with a simple request-and-pay setup and don’t need deep invoicing or reporting features.
6. Bank transfers and other non-card alternatives
Some people choose to skip cards entirely and use:
- Bank transfers (domestic or international)
- Real-time payment systems (where available)
- Direct debits or standing orders for recurring amounts
These aren’t card payments, but they’re common substitutes when you don’t want a card machine.
Pros:
- Often lower fees (or flat fees) compared with card processing
- No card disputes in the same way as chargebacks, though disputes can still occur
- Useful for larger or recurring payments
Cons:
- Customer friction: they must log into banking, set up the transfer, and may make mistakes entering details.
- Harder to connect automatically to your sales or booking system.
- Less familiar to some customers for small, everyday purchases.
Best suited to:
Higher-value services, B2B work, or customers who are comfortable with transfers and prefer to avoid cards.
Comparing your main options at a glance
| Option | Card present? | Hardware needed | Typical use | Speed of payment action for customer |
|---|
| Payment links / online invoices | No (card-not-present) | Phone / computer | Remote services, ad hoc | Medium (click link, fill form) |
| Virtual terminal (keyed-in) | No (card-not-present) | Computer / tablet | Phone orders, offices | Medium–fast (you handle typing) |
| Tap to Pay on smartphone | Yes (card-present) | Smartphone only | In-person, mobile trades | Fast (tap-and-go) |
| Website checkout | No (card-not-present) | Website + gateway | Online shops, bookings | Medium (standard online checkout) |
| Bank/wallet “pay request” links | Sometimes card-backed | Phone / computer | Small or informal sales | Medium (depends on bank/wallet) |
| Bank transfers (non-card) | No | None (banking only) | Larger or recurring sums | Slow–medium (manual action) |
Key factors that shape which option might fit you
Because the “right” answer depends on your situation, it helps to look at a few core questions:
1. Are your customers with you in person or remote?
2. How often do you need to take payments?
- Occasional or side gig:
- Simple tools like payment links, wallet requests, or basic online checkout may be enough.
- Regular, high volume:
- You might care more about fee structure, settlement times, and reporting.
3. How important is speed at the point of sale?
- Need to move a line quickly (cafés, events, markets):
- Tap-based options are usually faster than asking every customer to open their email or banking app.
- Longer, one-on-one services (consulting, home repairs):
- Customers may be fine taking a minute to pay via link or transfer.
4. How sensitive are you to fees vs. convenience?
- Card payments (of any type) usually involve:
- A percentage fee
- Sometimes extras for international or premium cards
- Bank transfers may have:
- Lower or flat fees
- Less built-in protection for the payer in some regions, which can affect customer comfort
No method is free of trade-offs. People often accept slightly higher fees in exchange for simpler, faster payments.
5. What kind of records and reporting do you need?
- If you need invoices, tax-friendly reports, and easy reconciliation with your accounting:
- Payment platforms and online invoicing tools tend to help.
- If you just need to know “money came in”:
- Simpler bank or wallet transfers might be enough.
Security and compliance: what to keep in mind
Whatever method you use, some basics apply:
- Never store full card numbers, CVVs, or photos of cards on your phone, computer, or on paper.
- Use tools that clearly state they comply with card security standards (often called PCI DSS).
- Protect your own account access:
- Strong passwords
- Two-factor authentication
- Up-to-date devices and software
- Be clear with customers about:
- Who they’re paying
- What they’re paying for
- How refunds or disputes are handled
What you need to evaluate for your own situation
To decide which non-machine method to use, you’d typically weigh:
- How you interact with customers (face-to-face vs. remote)
- Your sales volume and typical transaction size
- Your comfort with tech setup (apps and basic tools vs. website integration)
- Your tolerance for fees, and whether you prefer predictable costs or flexibility
- How quickly you need access to funds in your bank
- How important detailed records and invoices are to you
- Customer expectations in your line of work (for example, some industries lean heavily on bank transfers, others on instant card payments)
You don’t have to pick just one option. Many people combine them — for example:
- Tap to Pay on a phone for in-person work
- Payment links or online invoices for follow-up work or remote clients
- Bank transfers for larger, pre-agreed projects
Understanding the range of tools available lets you choose the mix that fits your own way of working, without ever needing a traditional card machine on the counter.