Academy › Build › Payments

What customers check before they enter their card

By the end, you'll know what your customer needs to read before they pay: who's really charging them, only the payment methods you actually accept today, and the full total, with not a single dollar hidden until the last click.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

5 min read

A customer adds your service to the cart, decides to buy, gets to the payment screen... and closes the tab without paying. The price hasn't changed, the offer was still good. What changed is what they see in that last step: a screen they don't recognize, a name that isn't yours about to charge them, no clue about what happens to their card details.

That last step decides whether the money comes in or gets stuck halfway there. What's left to figure out is what the customer needs to see there so they don't back out right before confirming.

The padlock icon doesn't convince anyone anymore

Years ago, the browser padlock and the "https" in front of the website were a trust signal people noticed. Today every site has it, including the ones that scam people. Showing it off like an achievement doesn't add anything: it's the bare minimum, like a restaurant having a clean floor.

What a customer does notice, even if they can't quite name it, is consistency: that the business they see on the payment screen is the same one they saw on the website, in the email, and in the WhatsApp conversation. The moment the name changes without explanation, doubt creeps in, even if everything else checks out.

The name that's going to show up on their bank statement

The thing that worries a customer most isn't the padlock, it's not knowing who's actually going to charge them. If your website says "Marta's Studio" but the charge on their bank statement later shows up as some initials they don't recognize, you've already planted doubt, even if the charge is completely legitimate.

The fix isn't technical, it's about giving a heads-up: if the name that's going to show up on the bank statement doesn't match your business name, tell them before they pay, on your site, in plain view, or in the message where you send the payment link. One line is enough: "this charge will show up on your bank statement as [name]." You explain it before it surprises them, not after they call to dispute it.

The charge nobody recognizes

A customer who sees a charge on their bank statement with a name they don't recognize doesn't think "oh, that's the payment processor," they think "I got charged without permission" and asks their bank to reverse it. That bank-side reversal, the chargeback, costs more than a regular refund: time, a dispute fee, and if it happens too often, trouble with your merchant account. You avoid it with one line before checkout, not with any paperwork afterward.

Payment methods: show what you accept, not everything that exists

Slapping on logos for every card brand, plus Venmo, plus PayPal, plus Apple Pay, even though you only process two of them, is a common mistake. It looks generous, but it's just template filler: anyone who's ever shopped online recognizes that row of logos as decoration copied from another site, not as real information about what's about to happen when they pay.

Show everything that exists, or show what you actually accept

Every logo you can find

Looks like a very professional checkout at first glance
The customer might pick an option that turns out not to work when they try it
It reads as copied the moment anyone looks twice

Only the methods you actually process

Two or three icons, the ones you can charge today
The customer knows what they'll pay with before they even pull out their card
When you add a new method, you add it the day it's actually working

Which one do I pick: Only show the methods you accept today. Add a new logo the day that method is actually live, not before. Which methods to offer and which ones to drop is the next decision in the course.

The total, no surprises at the last step

Nothing breaks trust faster than watching the price go up on the last click. If you charge a processing fee or extra shipping insurance, say so on the same screen where the price shows, not in the final confirmation. And if you're selling to individual consumers, the price you show should already include sales tax where that's how your state handles it: consumer protection rules call for showing the full final price, with any added fees broken out. The customer needs to reach the pay button knowing exactly what amount is coming out of their account, with no one moving the number on them halfway through.

This goes for the fine print too: if your service comes with conditions (a deadline, something it doesn't include), it's better to say so before the card is charged than after, when you're stuck handling a complaint.

What your customer should read before paying

Total due: $45 (includes processing, no surprises later). Charged by: Marta's Studio LLC; the charge will show up on your bank statement under this same name. Accepted methods: card and Venmo.

What you'll walk away with

Before paying, the customer knows who's charging them and what name the charge will show under on their bank statement
Only the payment methods you actually process today show up, not the ones you might accept someday
The price the customer sees before paying is the same amount that comes out of their account, no last-minute add-ons
The next decision: which payment methods to offer and which ones to cut

In Yodai the store comes with the Free plan, with a catalog, a cart and orders. See how to create your online store for free.

NextCard always; Venmo only if your customers buy from their phone