Transaction Receipt Rules: What Must Appear

A transaction receipt has a required contents list and a prohibited contents list. Most merchants have seen some version of the required list. Almost nobody has read the prohibitions, which is where the real exposure sits, and one of them carries a deadline in October 2027 that will catch terminals and gateways still in service today.

Here's both lists, plus the separate rules that apply when you email the receipt instead of printing it.

What a receipt has to include#

Table 5-33 of the rules lists eleven required elements (ID# 0027843, last updated April 2026). Ten apply to an ordinary electronic sale. The eleventh, other details embossed on the card, applies only to the merchant copy of a manually imprinted receipt.

• The payment credential, with everything except the final 4 digits disguised or suppressed on the cardholder's copy
• The authorization code, for transactions the issuer authorized
• The card network name, which must contain "Visa"
• A description of the goods or services
• The merchant or marketplace location, meaning the city and state or province of the outlet. For an ATM, the location or street address
• The merchant name, being the name the merchant uses to identify itself to its customers
• Return and refund policies
• The transaction amount and currency symbol
• The transaction date
• The transaction type, from a fixed list: ATM cash disbursement, cash-back with no purchase, credit, manual cash disbursement, load transaction, or purchase

That transaction type list is closed. "Payment," "order," and "charge" aren't on it. If your receipt says something else, it isn't using the vocabulary the rule specifies.

The name element also connects to your billing descriptor, and the refund policy element to your disclosed return policy. The receipt isn't a standalone artifact. It's where several other obligations have to show up in one place.

What a receipt must not contain#

Shorter list, sharper edges (ID# 0026206).

Promotional language preferring a non-Visa card. If the receipt bears the Visa program marks, it must not carry promotional, advertising or similar language conveying a preference for a competing payment card. A "pay by bank and save 3%" banner on a Visa-marked receipt is the shape of the problem.

More information than is embossed or printed on the card. With exceptions for a token, a card showing only a partial account number, and a card showing no account number at all.

Full merchant or terminal identification numbers on the cardholder's copy. This is the one with a date attached.

The October 2027 deadline#

The cardholder's copy must not show the full card acceptor identification number, the full merchant identification number, or the full terminal identification number. Right now that applies to POS acceptance devices and payment gateways deployed on or after 15 October 2022. Effective 16 October 2027, it applies to all of them.

So a terminal installed in 2019 is outside the rule today and inside it in October 2027. If you run older estate, that's a receipt template change with a fixed date on it, and it's the kind of thing that gets discovered late.

Two carve-outs worth knowing. The restriction doesn't apply where the device or gateway connects to a processor host using PCI-validated point-to-point encryption or cryptographic keys for all host connectivity. And an acquirer may show only the last 4 digits on the cardholder's copy while showing all digits on the merchant's copy, which is usually the practical fix rather than removing the field.

Email receipts have extra rules#

If you deliver the receipt by email or wireless message, three more requirements attach (ID# 0027837, updated October 2025).

The message has to carry the merchant name as it will appear in the clearing record and on the cardholder's billing statement. Not your trading name if that differs. The name they'll see on the statement, so the receipt and the statement line match.

It has to include language indicating that the message contains the cardholder's copy of the receipt, or a link to it. The customer should not have to infer what the email is.

And the receipt has to be in a static format that cannot be easily manipulated after it has been created. An HTML email that renders live from a template, or a link to a page you can edit afterwards, is the thing this rule is aimed at. A PDF is the obvious answer.

That last one is quietly the most-breached rule on this page, because almost every ecommerce platform emails a dynamic receipt by default.

The currency symbol trap#

The amount element requires the total of all goods and services sold to the cardholder at the same time, including applicable taxes and fees and any adjustments or credits. Then it requires the currency symbol, but only if the transaction currency isn't the local currency of the transaction country.

Here's the catch in the footnote. If the currency symbol or identification isn't on the receipt, then the transaction currency is the local currency of the transaction country.

Omitting the symbol isn't neutral. It's an assertion. If you're billing a US customer in euros and your receipt shows a bare number, the rule reads that as dollars. Anyone doing cross-border pricing or currency conversion should treat the symbol as mandatory rather than cosmetic.

Who gets named when there's a middleman#

The merchant name element has a set of exceptions that all work the same way: when someone sits between the seller and the acquirer, both names appear.

• A payment facilitator transaction names the facilitator and the sponsored merchant, or an abbreviation
• A marketplace transaction names the marketplace and the retailer
• A consumer bill payment service names the service and the biller
• A back-to-back transaction through a digital wallet operator names the operator and the retailer
• An up-selling merchant must be named in a way that clearly differentiates it from the initial merchant

That's why aggregator receipts look the way they do. It isn't branding, it's a rule.

What to check on yours#

Pull up a real receipt your system sent yesterday and check four things.

• Is the transaction type one of the six permitted words?
• Does the merchant name match your billing statement descriptor exactly?
• Is there a currency symbol, and is it the right one?
• Is the emailed artifact static, or does it render live?

If you deliver refunds or run advance payments, those carry additional receipt content requirements of their own on top of this list.

Source: Visa Core Rules and Visa Product and Service Rules, 18 April 2026.