Provide Receipts

 

Card Network Rules On Card Present Receipts

Merchants/platforms must provide transaction receipts in either electronic or paper format at the time of transaction. Card network rules require that:

  • Merchants must provide receipt if requested by customer (in other words cardholders should be presented with the option to get a receipt).
  • Receipt must be provided if merchant has return, refund or exchange policy, or requires receipt for return or refund.
  • Receipt can be paper or electronic. However merchant must provide paper receipt if paper receipt requested by customer unless transaction is ecommerce or at contactless-only POS device.
  • A merchant must retain a transaction receipt for 13 months.

For Link, WePay delivers electronic receipts.

Clear partners must adhere to the following receipt protocols:

  1. Inform the payer of transaction receipt delivery method (i.e. email, text message, etc) and when it will be sent. Read more about required notifications that you, the platform, must deliver in our Platform Setup article.
  2. Provide the receipt in a static format that cannot easily be manipulated after it has been created.
  3. If a link to the receipt is provided, outline clear instructions for accessing the receipt, as appropriate.
  4. Make the receipt available to the cardholder for at least 24 hours after the transaction.
  5. Not store or use personal information provided by the cardholder to receive a receipt (such as email address or phone number) without the express consent of the cardholder.
  6. Include the following in the title of the email or first line of the text message:
  • the merchant name
  • language indicating that the email or text message contains the transaction receipt or a link to the transaction receipt.

A merchant/platform must retain a transaction receipt for 13 months.

Transaction Receipt Data Requirements

For Card Not Present transactions (i.e. eCommerce), the following data points must be included on receipts:

  1. Merchant name or DBA (or merchant website)
  2. Merchant location: address, city, country, phone number
  3. Transaction type (retail sale, cash disbursement, refund)
  4. Descriptions (and price) of goods and services
  5. Total amount
  6. Transaction date (and time if possible)
  7. For recurring transactions: the words “Recurring Transactions”, frequency of recurring transactions, duration of recurring transaction period
  8. Card network name
  9. PAN (in truncated form)
  10. Transaction authorization approval code returned by issuer
  11. Refund and return policies
  12. Customer service contact information such as email address or phone number
  • Recommended to reduce the likelihood of cardholder dispute/chargeback:
    • For merchants located in the US: “This charge will appear on your credit card statement as WPY*description.”
    • For merchants located in Canada: "This charge will appear on your credit card statement as description."

To implement the above recommendation, fetch the statement_description value from the associated merchant account to insert as the "description." For instance, if you have a merchant where "statement_description": "Joe's fundraiser", then the description that you should show payers on the receipt would be "WPY*Joe's fundraiser" (payments to US-based merchants) or "Joe's fundraiser" (payments to Canada-based merchants).

Reference: Visa Core Rules and Visa Product and Service Rules, April-2016

Card Present Receipts

In addition to the above receipt protocols (not to be confused with data requirements), card present receipts also require that:

  • Merchants must provide receipt if requested by the customer (in other words cardholders should be presented with the option to get a receipt)
  • A receipt must be provided if merchant has return, refund or exchange policy, or requires receipt for return or refund.
  • Receipts can be paper or electronic
  • Merchants must provide paper receipt if paper receipt requested by customer unless transaction is ecommerce or at contactless-only POS device.

The following data points must be included on Card present receipts:

  1. Merchant name
  2. Merchant Location (city & state/province)
  3. Merchant Number (must NOT be on Debit Receipts)
  • Omitting the merchant number from the receipt for US merchants is optional
  1. Transaction Type (abbreviation allowed)
  • Purchase or Sale; Credit, Refund or Return; Prior Sale or Voice Authorization; Void; Reversal; Incremental Authorization; etc.
  1. Local date and time
  2. Entry Mode
  • Swipe, chip, NFC, etc.
  1. Card Issuer Name / Card Brand Name OR Payment method (debit vs. credit)
  • Discover and Visa must appear in full on the receipt; all other payment brand names may be abbreviated
  1. Card Type
  • Always print "CREDIT"
  1. Masked PAN
  2. Truncated Expiration Date
  • Must be omitted or fully truncated (XXXX or **)
  1. Total Amount
  • If the transaction was partially-approved, the partially-approved amount must be presented on the receipt as the total transaction amount
  • It may be helpful to print the request amount on the receipt if it differs from the total transaction amount
  1. Approval or Authorization Code
  2. Application ID
  • Required on EMV only
  1. Application Preferred Name
  • Required on EMV only
  • Recommended to reduce the likelihood of cardholder dispute/chargeback:
    • For merchants located in the US: “This charge will appear on your credit card statement as WPY*description.”
    • For merchants located in Canada: "This charge will appear on your credit card statement as description."

To implement the above recommendation, fetch the statement_description value from the associated merchant account to insert as the "description." For instance, if you have a merchant where "statement_description": "Joe's fundraiser", then the description that you should show payers on the receipt would be "WPY*Joe's fundraiser" (payments to US-based merchants) or "Joe's fundraiser" (payments to Canada-based merchants).


Compile Receipts

DataRequired?Find in API vs. SDKResource/Class & Parameter
Merchant nameRequiredAPIAccounts; name
Merchant Location (city & state/province)RequiredAPILegal Entities; address
Transaction Type (abbreviation allowed)RequiredN/AOption to always print "Pre-Authorization," or build logic to identify transactions as pre-authorizations vs. sale and print the appropriate string.
Local date and timeRequiredSDKpaymentDate
Entry ModeRequiredSDKPayment Method; inputSource -- print in uppercase
Card Issuer Name / Card Brand NameRequiredSDKPayment Method; cardBrand -- print in uppercase
Card TypeRequiredN/AAlways print "CREDIT"
Masked PANRequiredSDKPayment Method; maskedPAN
Truncated Expiration DateRequiredSDKPayment Method; expirationMonth & expirationYear
Transaction AmountRequiredSDKAuthorization Info; amount
Total AmountRequiredSDKAuthorization Info;
- amount+tipAmount (tip on terminal)
- amount (no tip)
- blank (tip on receipt)
Authorization Code (including offline)RequiredSDKAuthorization Info; authorizationCode
Application IDRequired on EMV onlySDKEMC Info: applicationIdentifier
Application Preferred NameRequired on EMV onlySDKEMV Info: applicationLabel
Transaction OutcomeRecommendedSDKAuthorization Info; authorizationResult
MERCHANT COPY / CARDHOLDER COPYRecommendedN/APrint "Merchant Copy" or "Cardholder Copy"

Deliver Receipts

Once a receipt has been compiled, the merchant can provide either an electronic or a paper receipt to the payer. The delivery method may be restricted, depending on the hardware that the merchant is set up with.

Terminals

Merchants using the VeriFone V400m can leverage the receipt printer included with the terminal itself. For these cases, simply inject any custom or required information needed into the customer receipt text blob returned by the SDK on the Payment Info class. These merchants can also provide electronic receipts.

Merchants using the VeriFone P400 must either exclusively offer electronic receipts or procure their own external receipt printer, compatible with the terminal being used.

Mobile Card Readers

Merchants using the Ingenico Moby 5500 must either exclusively offer electronic receipts, or procure their own bluetooth receipt printer to offer paper receipts as well.