Receipt upload with Nexi Engage presentation
As a merchant I want to make our receipts available digitally, but I do not wish to make them available through our own app or website.
APIs involved
Partners involved
Flow
Receipt upload
Uploading receipts to Nexi Engage is a two step process. Initially a receipt id is created, followed by the actual receipt upload. This receipt id should be stored in case the receipt has to be updated later.
Create receipt id Upload receipt
It is best-practice to put receipt upload behind a queue and retry the upload if it should fail for some reason.
Optional user lookup
All receipts can be delivered to Nexi Engage since Nexi Engage acts a data processor for the merchant. Nexi Engage will then be in charge of deleting the non-matched receipts.
It is preferred that Nexi Engage received all the receipts, since it is possible for Nexi Engage to assist the merchant in tracking support about receipts that were not matched to a user. There can be a lot of reasons why a receipt is not matched to a user, but if we do not receive a complete dataset, we have no way to help with that.
However if a merchant chooses to only send receipts for existing Nexi Smart Receipt usersa lookup can be done before sending the receipt using relevant user identifier. These operations are found here: