Duplicate Receipts

By default, the API rejects receipts posted with a duplicate transaction_id.

If desired, duplicates may be posted by setting the duplicate flag.

POST /receipts HTTP/1.1
Accept: application/json
Content-Length: ...
Content-Type: application/json
Host: api.ereceipts.co.uk

{
    "transaction_id": "0011120008",
    "duplicate": true,
    "...": "...",
}

Setting the duplicate flag has the following effect:

• The receipt will not be rejected due to a duplicate transaction_id,

• A random suffix will be appended to the transaction_id, e.g. 0011120008-duplicate-etxv,

• Internally, specific rules apply to processing of duplicates. By default, duplicate receipts are not included in statistics, data exports, etc. However, this can be adjusted for a particular retailer.

Using duplicates to resend receipts

While it’s possible to resend a previously posted receipt, this may not always be practical in a POS environment. Alternatively, a POS system may re-post a receipt with the duplicate flag set.

The re-posted receipt may include specific email and messaging settings. For example, this can be used to send the receipt to the customer’s preferred channel only.