The fastest way to accept payments on a website is a payment link, which takes about 15 minutes, needs no code, and works even if your site is a single page. A pay button on your own page takes an afternoon. Checkout built into the site takes longer but gives you the most control. Which one you want depends on how many different things you sell and how often.
Omar runs a three-person junk removal service. Most jobs come from phone calls and run $180 to $600. He wanted customers to pay a $60 booking fee online and the rest on the day. Here is how each of the three ways would work for him, what each costs, and the test to run before you send a real customer to pay.
Before any of the three: what you need ready
Every option needs the same short list. A business bank account to receive money. Your legal name or business name and address. An ID number for tax purposes (an EIN or, for a sole proprietor, a Social Security number). And a processor account, such as Stripe, PayPal or Square. Opening one takes about 15 minutes of forms. The slow part is the first payout: Stripe says it typically schedules a new account's first payout within 7 to 14 days after the first live payment, so open the account a couple of weeks before you need cash.
Way one: a payment link, about 15 minutes
A payment link is a web address that opens a checkout page hosted by your processor. You create it in your dashboard, name what it is for, set the price, and copy the address. Stripe's pricing page lists Payment Links as included with its payment processing, so you pay only the card fee. At Stripe's published online rate of 2.9% plus 30 cents (as published on their site, October 2026), a $60 booking fee costs you $2.04.
- Open your processor's dashboard and find payment links (2 minutes).
- Create one product per thing you sell, such as "Junk removal booking fee, $60" (5 minutes).
- Turn on the receipt email, and add your phone number to the confirmation page (3 minutes).
- Paste the link on your website as a button, put it in your email signature, and send it by text after a phone quote (5 minutes).
This is the right start for Omar. The links work with customers who call first. The drawback is that you create one link per price, and nothing connects the payment to a job record, so you check the dashboard when a payment arrives.
Way two: a pay button or embedded form on your page, a few hours
Here the customer stays on your site. Your processor gives you a snippet of code, or your website platform has a built-in payments block, that shows a pay button or card fields on your own page. You can set an amount from a form field, such as a quote the customer picks.
The cost is the same card fee plus your time, or a plugin fee if your platform charges one. The important detail is where the card number is typed. Use fields or a checkout hosted by the processor so the number never touches your own server. That is the simplest way to meet the card networks' security standard, PCI DSS, because the processor handles the sensitive part. Never build your own form that collects card numbers.
This option fits a site with a handful of services and a customer who often pays right when they decide. Allow two to four hours the first time, mostly for testing on a phone.
Way three: checkout built into the site, days
A custom checkout stores an order, takes the payment, emails the customer, and tells you a job needs doing. It uses the processor's API, a server that confirms payments, and a database. It can be built by a developer, or you can start from a builder that ships with payments included. In Rocketship, the $12-a-month Builder (site or app only) connects to your own Stripe account through Stripe Connect, so customers pay you directly and the money goes to your account, not ours. Our look at whether you need a website or an app helps with that choice, and the $12 Builder plan explains what that plan includes.
Pick this one when you sell many items, need customer accounts, or want the order recorded automatically. If you only sell three services, it is more than you need.
A decision chart: link, button or checkout
| Way | Time to live | Costs on top of the card fee | Best when |
|---|---|---|---|
| Payment link | 15 minutes | None listed | Customers call or text first, a few prices |
| Pay button or embedded form | 2 to 4 hours | Your time, or a plugin | Customers decide on the site |
| Checkout built into the site | Days | A developer, or a builder plan | Many items, accounts, automatic records |
Read it as four questions, in order. Do customers talk to you before they pay? Start with a link. Do they decide on the page, for a handful of set prices? Add a button. Do you sell more than a handful of items, need customer accounts, or want each order recorded without typing? Build the checkout. Spending more than an hour a week matching payments to jobs by hand? That is the signal to move up a step.
What goes on the payment page
People pay when they trust the page. Show the price in dollars, what it covers, your business name as it will appear on a card statement, your refund rule, and a phone number. A customer who sees a statement line they don't recognize is the customer who files a dispute, and Stripe lists $15 for each one. For a deposit-style payment, paste in the four-sentence rule from deposits for appointments.
Test it with a real card in five minutes
- Pay your own link with a real card, on your phone, on mobile data instead of Wi-Fi (2 minutes).
- Check that the receipt email arrives and the amount is right (1 minute).
- Check that the payment shows in the dashboard with the right label (1 minute).
- Refund it, and look at which fee stayed behind (1 minute).
Where it goes wrong
The most common failure is a customer who pays and nobody notices. A success page on the customer's screen is not a record on your side. Turn on payment notifications, or in a custom checkout confirm payments from the processor's server message instead of the browser redirect. The second is a payment link left in a text thread with an old price. Archive links you stop using. The third is a business that offers only one payment method. Offer cards, and add a wallet button such as Apple Pay if your processor supports it. If you also want a PayPal button, compare costs in Stripe vs PayPal for a small business, or see Stripe vs Square if you also take payments in person. Matching payments to jobs by hand is the admin described in the four hours nobody invoices for, and why the website is not the product explains why the payment page is only one part of getting a customer.
Getting paid is the last step of getting a customer. Rocketship finds the buyers, emails them from your own Gmail, follows up, and books the meeting on its own. Plans that get you customers start at $24.99 a month (Launch), and every monthly plan starts with a 7-day free trial, card required.