Since each POS station gets its own identity in the Secure Receipt Wallet platform and for obvious security reasons, we highly recommend to run an independent node server for each POS station and avoid sharing the “Secure Receipt Wallet Receipt Digitization Server for Node” among multiple POS stations.
The merits of using the Secure Receipt Wallet Receipt Digitization Server for Node include the followings:
1. Universal compatibility: Providing seamless and similar end-to-end encryption SDKs and APIs for different languages is a challenge. Using a locally-exposed node-based server to abstract the underlying complexities is helpful in making the Secure Receipt Wallet platform available for almost any POS system, developed using any technology stack or language.
The demerits of using the Secure Receipt Wallet Receipt Digitization Server for Node includes the followings:
188.8.131.52 Integration Steps
184.108.40.206.1 Getting the POS Station Registered in Secure Receipt Wallet Issuer’s Portal
220.127.116.11.2 Generating and Delivering Smart Receipts
18.104.22.168.3 Demonstrating the results