A website order, a confirmed payment and a fiscal receipt are separate records. Integrating Checkbox or Vchasno.Kasa links them under agreed rules. The goal is traceability and correct handling of service responses. A successful payment alone does not mean a receipt has already been issued.
First agree the receipt trigger
Describe payment and fulfilment methods: prepayment, partial fulfilment, payment on delivery and returns. For each, an accountant or specialist adviser determines the appropriate fiscalisation procedure. The technical team implements it; one universal order-created event cannot replace that decision.
Record the sources of item names, quantities, discounts, payment types and tax parameters. Values must come from agreed accounting data. Check the meaning of similarly named CRM and cash register fields rather than mapping them automatically.
Separate testing and live operation
Both services provide official integration documentation. Before development, check current authentication and testing arrangements. Keep test registers and credentials separate; tests must not accidentally use live credentials. Secrets must not enter browser code.
Transfer keys and permissions through an agreed secure channel. Assign responsibility for replacement and revocation. Document which system issues receipts: independent submissions from both the website and CRM can duplicate an operation.
Handle retries and uncertain outcomes
If a request times out, the receipt may exist even though its response was lost. Check the result through the service’s documented mechanism before creating another. Retain the relationship between the order, payment and receipt identifier.
Operators must distinguish pending, confirmed success and failure. A retry queue must not submit the same operation uncontrollably. Unresolved cases need notifications and instructions as well as a technical log.
Test refunds and daily reconciliation
Using test data, run a sale, discount, partial scenario and refund under agreed rules. Verify amounts and receipt delivery to the customer. Correct product data errors at their source or they will recur on the next order.
Hand over an operation list for reconciling orders, payments and receipts. A record without a receipt, or a receipt without a clear order, needs investigation. A specialist confirms legal suitability for the specific arrangement; technical testing demonstrates the agreed algorithm works.
Sources and further reading
