How to Charge Card on Stripe, Ask Payment in Credit Cards Easily 2026

A payment link suits a fixed amount you want paid now: freelance deposits, one-off products, event tickets. An invoice suits work with terms attached, where the customer needs a document with a number and a due date for their own bookkeeping.

Charging a saved card directly is for repeat customers who've already paid you once and agreed to have their card stored. The distinction that matters most is who types the card number.

With links and invoices, the customer enters it on Stripe's own page, which keeps card data out of your systems entirely. Default to those two.

In the dashboard's left navigation, Payment Links sits under Payments, and it's also pinned in the Shortcuts group at the top. The page lists every link you've made with its name, price, and creation date; a link you no longer want live can be deactivated instead of deleted, which stops it accepting payments but keeps its history.

Click New to build one. Stripe supports two pricing models here: a fixed product or subscription, the common case, and "customers choose what to pay", meant for tips or donations, where you can set a suggested amount plus an optional minimum and maximum (the default cap is $10,000; Stripe support can raise it on request). Either way, Stripe generates a URL you paste anywhere, and the same link can be reused by any number of customers.

Invoices live under Billing in the left navigation, filtered along the top by All, Draft, Open, Past due, and Paid. Each row carries the total, frequency, invoice number, customer name and email, due date, and creation date: everything you'd need to chase a late payment.

Creating one attaches a customer record, line items, and a due date, and Stripe emails a hosted invoice page with a Pay button. First-time accounts get card, Link, bank transfers, Cash App Pay, and WeChat Pay enabled by default for invoices; add more in Payment methods settings if you need them. The advantage over a link is the audit trail: the invoice number, the status, and automatic reminders once the due date passes.

Whichever route you use, the checkout page shows only the payment methods you've enabled, each with its own toggle in settings. Card needs to be on for this task; alongside it you'll typically find wallets, bank debits, Cash App Pay, and others, all switched independently.

A customer only sees Apple Pay or Google Pay if they've activated that wallet on their own device, and what's shown also depends on their browser, so an empty-looking checkout isn't necessarily a setting you got wrong. Leaving too many methods on clutters the page and can push the card fields below the fold; leaving too few costs you conversions from wallet-only customers. Enable card plus the one or two alternatives your own customers use, and check the result on a phone.

For a returning customer, open Customers, find their record, and charge the payment method stored on it. This is the closest thing to the classic "charge a card from the dashboard" workflow, and it works because the customer entered the card themselves and agreed to it being kept on file.

Typing a card number read to you over the phone is different: it needs manual card entry enabled on your account and puts you inside card-data compliance rules (PCI). Unless you genuinely run an in-person or phone-order business, send a link instead. It's faster, and it moves the security burden to Stripe.

Stripe's dashboard runs in a sandbox until you switch it to live, and a banner across the top says so; nothing there touches your real account, and any invoice or link you build is a test object. Use it to send yourself an invoice and click through the payment page as a customer would before anything real goes out.

Some payment methods, bank debits and vouchers among them, take Stripe two to fourteen days to confirm a payment instead of clearing instantly like a card, so don't assume a pending charge has failed. Set up a webhook if you need to know the exact moment a payment clears.