Review receipt requirements in the Card Network Rules resource.
|Data Requirement||Find in API vs. SDK||Resource/Class & Parameter|
|Merchant Location (city & state/province)||API||Legal Entities;
|Merchant Number (must NOT be on Debit Receipts; USD is optional)||N/A||Not required as Card Present currently only supports USD.|
|Transaction Type (abbreviation allowed)||N/A||Defined by merchant in your UI prior to authorization.|
|Local date and time||SDK||paymentDate|
|Entry Mode||SDK||Payment Method;
|Card Issuer Name / Card Brand Name OR Payment method (debit vs. credit)||SDK||Payment Method;
|Masked PAN||SDK||Payment Method;
|Truncated Expiration Date||SDK||Payment Method;
|Total Amount||SDK||Authorization Info;
|Approval or Authorization Code||SDK||Authorization Info;
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!