Currency Expectations: What US Customers See When They Pay a Jamaican Business
Charge US customers as a Jamaican business without checkout surprises. What they see in JMD vs USD, what their statement shows, and how to remove doubt.
An aunt in New Jersey clicks through to pay for her niece's birthday cake from a Kingston bakery, and the checkout asks her for J$18,000. She has no idea what that is in money she understands, the number looks like a car payment, and the tab quietly closes. The bakery never learns why. When you charge US customers as a Jamaican business, the sale is decided by what shows up on their screen and later on their card statement, and both are easy to get wrong without noticing.
This post walks through the payment from the American customer's side of the glass, because that view explains the abandoned carts, the "is this right?" messages, and the occasional dispute from a buyer who genuinely did not recognize the final amount.
Charging US customers: what they see at checkout
Customers pay in whatever currency the checkout states, and the currency you price in is the experience they get. A US buyer facing a J$ amount must either know the rough rate, trust you, or leave to do math, and every second spent converting is a second spent reconsidering. Large unfamiliar numbers also trip a primal alarm, since J$18,000 reads as eighteen thousand of something to a nervous first-timer.
None of this means JMD pricing is wrong, and for your local buyers it is exactly right. It means the currency on the page should match the audience the page serves. A diaspora-facing offer priced in US dollars answers the aunt's question before she asks it.
Watch a US buyer meet a JMD price in real time and the sequence is always the same. Pause, open a new tab, type the conversion query, squint at a result they only half trust, return, and re-decide whether the purchase is still worth the bother. Every step of that loop is a chance to leave, and none of it happens when the page simply says US$120. The strongest checkout is the one that never sends anyone away to do math.
What lands on their card statement
Here is the part merchants rarely see. If you charge in Jamaican dollars, the customer's card network and bank convert the amount into US dollars at their own rate, and the figure that finally posts can differ slightly from any estimate they saw or calculated. Depending on their card, their bank may also add its own charge for a foreign transaction, and those terms vary from card to card. As of this writing, such fees are common on basic US cards and waived on many travel-oriented ones, but the details belong to their bank, not to you.
Days later, a line appears on their statement with your business name on it. If that name does not match the shop they think they bought from, the memory has to do the work, and memory is what fails. Statement confusion is a quiet driver of "I didn't recognize the charge" disputes, which our chargebacks guide covers from the merchant's side. The kindest thing you can do for a future statement reader is a recognizable name and a receipt they kept.
It also helps to say the quiet part in your order message, telling the customer what name the charge will appear under. One sentence today saves a confused phone call in three weeks.
JMD or USD: the same sale, two experiences
| What happens | Priced in JMD | Priced in USD |
|---|---|---|
| At checkout | A J$ figure most US buyers must convert in their head | A US$ figure they recognize instantly |
| On their statement | Converted by their bank at its rate, so the posted amount differs from their estimate | The same US$ figure they agreed to, though their own bank's card terms still apply |
| Surprise risk | Higher, since two numbers never quite match | Low, since the quote and the charge are one number |
The pattern is simple to state. Pricing in USD moves the uncertainty from the customer's statement to your business planning, where you can manage it deliberately, and our guide to handling USD and JMD covers that side, including when JMD remains the right choice.
The bank check that surprises them
One more moment in the flow belongs to their bank rather than to you. US issuers increasingly verify online purchases, so your customer may see a prompt to approve the payment in their banking app or enter a one-time code, particularly for a first purchase from an overseas business. On a checkout where every card payment is authenticated, that step is guaranteed rather than occasional.
Prepare them for it and it reads as safety. Surprised by it, some buyers assume something went wrong and abandon. A single line in your order conversation converts the check from friction into reassurance. The full mechanics are in our plain guide to 3-D Secure, which works as a link to send the curious.
Word the heads-up plainly and keep it to one line. Something like: "When you pay, your bank might pop up a quick approval, that's them confirming it's really you." Buyers hear their own bank being careful on their behalf, which is the most reassuring sentence in online shopping. The same line works pasted into a product page, an order confirmation, or the chat right before you send the link.
Removing every surprise, step by step
The fix list is short and almost free. Price diaspora-facing offers in US dollars with the currency written explicitly, US$85 rather than a bare $85. Tell the customer the exact amount before the link, in the same currency the link will charge. Warn them once about the possible bank approval step. Then make sure what posts later is explainable: a business name they will recognize and a receipt in their inbox that states the amount and currency.
Timing helps too. Send the exact-amount message while the buyer is still deciding rather than after they have committed, since a surprise tolerated grudgingly at checkout becomes a dispute remembered sharply at statement time. For repeat diaspora customers, consistency is its own communication, because the person who bought in March expects April to work the same way, in the same currency, from the same recognizable name.
Your payment setup either supports this or fights it. On Inkress, you can hold prices and take payment in USD or JMD with multi-currency wallets keeping each straight, the hosted checkout states the amount and currency on its face, and every order produces a receipt and an order page the customer can revisit when their statement eventually asks the question. The aunt in New Jersey sees US$120, approves it in her banking app, and gets a receipt naming the bakery she actually bought from, which is the entire experience working as designed.
Sell to the diaspora like you can see their screen. Quote in their currency, match the charge to the quote, flag the bank check, and leave a paper trail their memory can lean on. If your current checkout cannot do those things, an Inkress account takes minutes to open and handles the currency side out of the box.
Common questions
What does a US customer see when paying a Jamaican business?
Whatever currency the checkout charges. A JMD price must be mentally converted, while a USD price reads instantly, and the posted statement amount matches only when the charge was in USD.
Why did my US customer's statement show a different amount?
Charges made in JMD are converted to USD by the customer's card network and bank at their own rate, so the posted figure can differ from any checkout estimate, and their card's own terms may add charges.
Do US banks add fees for paying Jamaican businesses?
Some cards apply a foreign-transaction charge and others waive it, and terms vary by card. The merchant does not control or receive this, so a brief heads-up to customers is the practical courtesy.
Why was my US customer asked to approve the payment in their banking app?
That is 3-D Secure authentication, where the customer's own bank verifies them before money moves. On checkouts that authenticate every card payment it is a standard step, not an error.