Introduction

The Smart Receipt, or the online commercial document, replaces the issuance of a receipt via a telematic cash register. While the telematic cash register remains the optimal solution for retail sales from physical points of sale, a Smart Electronic Receipt fits perfectly in contexts where the sale occurs online.

The main difference between issuing a Smart Electronic Receipt and an e-invoice B2C is that the Smart Electronic Receipt does not require sending the fiscal ID (codice fiscale) of the customer.

A-Cube's Smart Receipt API service is a RESTful API that allows you to issue a Smart Electronic Receipt for a sale. The service interacts directly with Government Tax Portal Fatture e Corrispettivi (cassetto fiscale) acting as a proxy for the user.

Read more about how to onboard a new company on the A-Cube Smart Electronic Receipt here

Sandbox environment

In the sandbox environment, A-Cube will simulate the generation of the Smart Receipt identifiers. Please note that the PDF file generated in the sandbox environment will contain a standard text, regardless of the data provided to the receipt.

It is not necessary to provide real credentials for the sender BusinessRegistryConfiguration, while this is something you will need to complete for the production environment. Read the Onboarding documentation for more information.

First of all you have to set up a Business Registry Configuration, which represents the "Partita IVA" sending receipts. (Remember to set "receipts_enabled": true in the body of the request.) Then you can test the Smart Electronic Receipt API in the sandbox environment by using the following endpoints.

Send a receipt

POST https://api-sandbox.acubeapi.com/receipts

See the documentation

Void a receipt

DELETE https://api-sandbox.acubeapi.com/receipts/{uuid}

See the documentation

Return items on a receipt

POST https://api-sandbox.acubeapi.com/receipts/{uuid}/return

See the documentation