Hospitality Receipt Generation

Hospitality provides formatted text only receipts either on a socket or a file. In attended mode two receipts are returned: the Merchant and the Customer receipts. In case of a Kiosk or Semi-Attended mode only a Customer receipt is returned.

Below are the attributes of an EFT receipt.

Note: These are subject to change in future releases of Hospitality in compliance with requirements from UK APACS.

UK APACS Receipt Format

Mandatory (APACS)FieldsProperty
1Merchant/Outlet NumberMerchantID
2Merchant NameMerchantName
3Merchant AddressMerchantAddress1,
MerchantAddress2,
City,
State, ZipCode
4Transaction Type e.g. SALE / REFUNDTransactionType
5Card Number (PAN) - TruncatedApplPAN
7Transaction Data Source e.g. ICC, SWIPE, KEYEDChipStripeorKeyed
8Date of TransactionTransactionDate
9Terminal Number (TID)TerminalID
10Transaction NumberTransactionSeqNo or TransactionReference
11Transaction Response e.g. Auth CodeAuthCode
12Amount of Transaction (Inc. currency symbol)Amount
13Request for Signature (not required for PIN Transactions replaced by 17)N/A
14Space for Signature (nor required for PIN Transactions replaced by 17)N/A
15Declaration e.g. Please debit my accountN/A
16Retention ReminderN/A
17Amount of Cash (for Purchase With Cashback transaction)AmountOther
18PIN Verified StatementN/A
19Application IdentifierapplID
20Gratuity Amount (where a gratuity amount is added to the original amount)AmountGratuity
21Diagnostic MessageN/A
23Card Issue No / Sequence No - App PAN Sequence No for ICC TransactionsApplPANSeqNo
24Time of TransactionTransactionTime
25Application Preferred Name*ApplPreferredName
  • If the Application Preferred Name is not provided, or not readable from the card, the Application Label is provided on the receipt.
OptionalProperty
1Card Scheme NameApplLabel
2Courtesy MessageN/A
3Receipt Number (not transaction number)N/A
4Goods AmountN/A
5Goods DescriptionN/A
6Hot Card File Version NoHotCardVerNo
7Term Software Version NoTermSoftVerNo

Hospitality provides receipts in two text files in the receipt folder as configured in the YESEFTConfig:

  • Merchant receipt - Named as MerchantReceiptXXXXXmmss.txt where XXXXX are first five initials of 'Transaction Reference' and 'mmss' refers to transaction time in minutes and seconds.

  • Customer receipt - Named as CustomerReceiptXXXXXmmss.txt where XXXXX are first five initials of 'Transaction Reference' and 'mmss' refers to transaction time in minutes and seconds.

Hospitality also provides receipts on a socket connection, if configured in YESEFTConfig.

Hospitality provides a configuration option to suppress Merchant receipts. If this option is chosen then Merchant receipts are not issued except where signature verification is needed.

In case of signature verification, the Merchant receipt is received first from Hospitality. There is a possibility that the POS application may receive another Merchant receipt if the attendant rejects the signature verification on the Hospitality prompt. The Customer receipt follows the Merchant receipts.

This is the sequence that needs to be followed for receipt printing if the POS application is printing the receipts:

  1. Check for Merchant Receipt

  2. On receiving Merchant Receipt, print the receipt

  3. Check for Merchant Receipt or Customer Receipt

  4. If Merchant Receipt, print the receipt and then wait for Customer receipt

  5. If Customer receipt, print the receipt and wait for response

The Hospitality transaction response is issued at the end of the transaction. There will be no more receipts after the response message is issued.

The receipts are validated as compliant EMV receipts as part of the accreditation process that Hospitality undergoes with the acquiring banks. All the information contained in the Hospitality Customer receipt should be printed by the EPOS application. The Customer receipt text should be at least 2.55mm in height and not narrower than 15 characters per inch. The EPOS application should print Customer receipts from all transactions where Hospitality issues such a receipt.

The examples below show typical Merchant and Customer receipts generated by Hospitality for a Chip and PIN transaction.

  1. Receipts in Text Files MainReceipt.txt and CustomerReceipt.txt

    Copied!
    CUSTOMER RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET HERTS EN4 8QZ
     06/11/2013 01:47:34
     RECEIPT NO.: 3
     MID:XXX49873                         TID:XXXX0012
     AID:A0000000041010
     MASTERCARD
     XXXX XXXX XXXX 0020
     PAN SEQ NO. : 00
     ICC
     SALE                                       GBP100.00
     TOTAL                                      GBP100.00
     PLEASE DEBIT MY ACCOUNT
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS
     AUTH CODE: 007054
    Copied!
    MERCHANT RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET HERTS EN4 8QZ
     06/11/2013 01:47:34
     RECEIPT NO.: 2
     MID:21249872                         TID:22980012
     AID:A0000000041010
     MASTERCARD
     XXXX XXXX XXXX 0020
     PAN SEQ NO. : 00
     ICC
     SALE                                       GBP100.00
     TOTAL                                      GBP100.00
     PLEASE DEBIT MY ACCOUNT
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS
     AUTH CODE: 007054
  2. Receipts from the Receipt Socket port

    Receipts issued on the Receipt Socket port are prefixed by labels CUSTOMER: and MERCHANT: so that their start point may be readily identified in the stream of data from the socket. These labels should be removed from the receipt data and not printed.

    Copied!
    CUSTOMER:CUSTOMER RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET HERTS EN4 8QZ
     06/11/2013 01:47:34
     RECEIPT NO.: 3
     MID:XXX49873                         TID:XXXX0012
     AID:A0000000041010
     MASTERCARD
     XXXX XXXX XXXX 0020
     PAN SEQ NO. : 00
     ICC
     SALE                                       GBP100.00
     TOTAL                                      GBP100.00
     PLEASE DEBIT MY ACCOUNT
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS
     AUTH CODE: 007054
    Copied!
    MERCHANT:MERCHANT RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET HERTS EN4 8QZ
     06/11/2013 01:47:34
     RECEIPT NO.: 2
     MID:21249872                         TID:22980012
     AID:A0000000041010
     MASTERCARD
     XXXX XXXX XXXX 0020
     PAN SEQ NO. : 00
     ICC
     SALE                                       GBP100.00
     TOTAL                                      GBP100.00
     PLEASE DEBIT MY ACCOUNT
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS
     AUTH CODE: 007054
  3. Receipts of Account Verification (zero auth) transaction

    Copied!
    CUSTOMER:CUSTOMER RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET , EN4 8QZ
     10/04/2019 13:08:01
     RECEIPT NO.:156
     MID:XXX49873            TID:XXXX0018
     AID:A0000000043060
     MAESTRO
     XXXX XXXX XXXX XXX 0507
     ICC
     ACCOUNT VERIFICATION
     YOU WILL NOT BE CHARGED FOR THIS
     TRANSACTION
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS
    Copied!
    MERCHANT:MERCHANT RECEIPT
     YESPAY DEMO
     153 CHECKNET HOUSE EAST BARNET ROAD
     BARNET , EN4 8QZ
     10/04/2019 13:08:01
     RECEIPT NO.:156
     MID:21249873            TID:22980018
     AID:A0000000043060
     MAESTRO
     XXXX XXXX XXXX XXX 0507
     ICC
     ACCOUNT VERIFICATION
    
     PIN VERIFIED
     PLEASE KEEP THIS RECEIPT FOR YOUR
     RECORDS