Incorrect transfer of the technical_return variable to the check box API by the action "Creating a sales receipt, fiscalizing it and delivering it to the client by email"

[quote] variable technical_return (Default: false) [/quote] This parameter does not appear in the current integration implementation. [quote] the parameter defines the type of the fiscal check operation, sale or return. But there is also such a factor as the lack of transmission at all by default, which affects its display in the html check image - when the checkbox is set in the action "Creating a sales receipt, fiscalizing it and delivering it to the client by email", transaction type is not displayed in html receipt image [/quote] You can ask this question to Checkbox technical support. They probably have the type of operation of the fiscal check that you write about - it appears only for payments with type=CARD, and in the case of "Payment" - payment with type=CASH is transmitted. [quote] 1. please fix it so that everything is the same, for example, the inscription was always displayed. [/quote] From our side, I see only a refinement so that "Pіslyaplata" is transmitted with the CARD type (if it is normally accepted by the Checkbox API) - the implementation of the setting will take 1 hour [quote] 2. and then complete the checkbox that will turn off the display of the transaction type in the receipt. [/quote] If there is such a parameter in the API - provide information about it - we can finalize the corresponding setting in 1 hour. In the current documentation https://docs.google.com/document/d/1Zhkc4OljKjea_235YafVvZunkWSp6TCAKeckhgl8t2w/edit#heading=h.prhyp31urzzb I don't see an explicit setting that allows this. [quote] 3. when there are two payments in the html image, the operation type is displayed twice - According to the representatives of the check box, the "transaction type" refers to the check and not to the payment, so I think the conclusion of the check operation type twice is a mistake. please check and correct. [/quote] You can similarly address this claim to Checkbox API technical support. We do not pass any parameters to them regarding these signatures - accordingly, the entire check output is generated on their side.