Review receipt requirements in the Card Network Rules resource.
|Data||Required?||Find in API vs. SDK||Resource/Class & Parameter|
|Merchant Location (city & state/province)||Required||API||Legal Entities;
|Transaction Type (abbreviation allowed)||Required||N/A||Option to always print “Pre-Authorization,” or build logic to identify transactions as pre-authorizations vs. sale and print the appropriate string.|
|Local date and time||Required||SDK||paymentDate|
|Entry Mode||Required||SDK||Payment Method;
|Card Issuer Name / Card Brand Name||Required||SDK||Payment Method;
|Card Type||Required||N/A||Always print “CREDIT”|
|Masked PAN||Required||SDK||Payment Method;
|Truncated Expiration Date||Required||SDK||Payment Method;
|Transaction Amount||Required||SDK||Authorization Info;
|Total Amount||Required||SDK||Authorization Info;
- blank (tip on receipt)
|Authorization Code (including offline)||Required||SDK||Authorization Info;
|Application ID||Required on EMV only||SDK||EMC Info:
|Application Preferred Name||Required on EMV only||SDK||EMV Info:
|Transaction Outcome||Recommended||SDK||Authorization Info;
|MERCHANT COPY / CARDHOLDER COPY||Recommended||N/A||Print “Merchant Copy” or “Cardholder Copy”|
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.
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
Questions? Need help? Visit our support page!