Update digital-receipt-implementation.md

doc/digital-receipt/implementation/digital-receipt-implementation.md

@@ -682,7 +682,7 @@ This chart shows the required data fields to visualize the hole dataset of the d
 | Amount  | 3.2  | mandatory  | yes  | Gross total price of service(s). The gross individual price, net total price, and net individual price, have to be calculated using the amount and either VAT rate or VAT amount  |
 | VATRate  | 20  | mandatory  | yes  | VAT rate as percentage  |
 | ftChargeItemCase  | 0x4154000000000003  | mandatory  | no  | Type of service or item according to the reference table in the appendix. It is used in order to determine the processing logic for the corresponding business transaction  |
-| ftChargeItemCaseData  | "{\"ftChargeItemCaseData\":[\"Mit Hafermilch\\r\\nund Zucker\"]}"  | optional  | currently not*  | Additional data about the service, currently accepted only in JSON format  |
+| ftChargeItemCaseData  |"ftChargeItemCaseData": "{\"ftChargeItemLines\":[\"Mit Hafermilch\\r\\nund Zucker\"]}"  | optional  | currently not*  | Additional data about the service, currently accepted only in JSON format  |
 | VATAmount  | 0.5333333333333333  | optional  | yes  | If the VAT amount is indicated, it can be used to calculate the net amount in order to avoid rounding errors which are especially likely to appear in row-based net price additions  |
 | AccountNumber  | 1234  | optional  | no  | Account number for transfer into bookkeeping  |
 | CostCenter  | 1  | optional  | no  | Indicator for transfer into cost accounting (type, center, and payer)  |
@@ -701,7 +701,7 @@ This chart shows the required data fields to visualize the hole dataset of the d
 | Quantity  | 1  | mandatory  | no  | Number of payments. This value will be set to 1 in most of the cases. It can be greater than 1 e.g. when paying with multiple vouchers of the same value  |
 | Description  | Hobex   | mandatory  | yes  |Name or description of payment  |
 | Amount  | 3.2  | mandatory  | yes  | Total amount of payment  |
-| ftChargeItemCase  | 0x4154000000000003  | mandatory  | no  | Type of service or item according to the refer-ence table in the appendix. It is used in order to determine the processing logic for the corresponding business transaction  |
+| cbPayItemCase  | 0x4154000000000003  | mandatory  | no  | Type of service or item according to the refer-ence table in the appendix. It is used in order to determine the processing logic for the corresponding business transaction  |
 | ftPayItemCaseData  | "ftPayItemCaseData":<br/>"{\"cbPayItemLines\":[\"* *  Kundenbeleg  * *\\r\\nTest\\r\\nMusterstr. 1\\r\\n5020 Salzburg\\r\\nDatum: 05.07.2023\\r\\nUhrzeit: 08:46:26 Uhr\\r\\nBeleg-Nr. 0001\\r\\nTrace-Nr. 000123\\r\\nKartenzahlung\\r\\nContactless\\r\\ngirocard\\r\\nNr.\\r\\n###############7123 0000\\r\\nGenehmigungs-Nr. 880123\\r\\nTerminal-ID 52051123\\r\\nPos-Info 00 075 01\\r\\nAS-Zeit 05.07. 08:46 Uhr\\r\\nWeitere Daten 0000000001\\r\\n/////1F0312//\\r\\nBetrag EUR 8,60\\r\\nZahlung erfolgt\\r\\nBitte Beleg aufbewahren\\r\\n\"]}","Moment":"2023-08-09T07:12:46.0000000Z"}]}"  | optional  | yes  | Additional data about the payment transaction data, only accepted in JSON format. This can be the transaction data from card payment data from your PSP or the remaining value of a voucher  |
 | CostCenter  | 1  | optional  | no  | Indicator for transfer into cost accounting (type, center and payer)  |
 | MoneyGroup  | 1  | optional  | no  | This value allows the logical grouping of payment types  |