Each request has the same header data in the payload. Among other things, this header data is used to identify the customer via their card_id. In addition, the final flag is used to decide whether it is an article scan or a receipt completion. The accounting_id is important in order to be able to assign several requests to one checkout process. The accounting_id must not change within a checkout process.
The fields purchase_date and payment_method have no function and are used exclusively for data storage.
"purchase": {
"card_id": "42000007566795131965",
"accounting_id": "000501",
"purchase_date": "2021-08-11T10:23:24+2:00",
"payment_method": "cash",
"final": false,
// ...
}| Field name | Type | Field description | Use | Explanation |
|---|---|---|---|---|
card_id |
String | mandatory | Unique card number of the scanned customer card | In order to identify a customer account beyond doubt, the customer card must be scanned during the checkout process |
accounting_id |
String | mandatory | Unique ID of the checkout process | This ID must be generated by the POS system for each checkout process |
purchase_date |
mandatory | DateTime (ISO 8601) | Time stamp of the scan | Is currently only used for data storage |
payment_method |
String | Obligation | Payment method of the checkout process | Previously only used for data storage. Can contain one of the following values (can be combined using “,”): cash, creditcard, debitcard, mobileWallet, giftCard, bottleDeposit |
final |
Boolean | mandatory | Final checkout process or item scan | Used to identify the incoming request as an item scan or completion of the checkout process. |