Page Comparison

...

1. CAS version 20241001 (or newer) must be installed.

2. A one-time CAS setting must be deployed by the Administrator.

3. The feature is enabled for each BATM in Terminal details.

4. Your customers will have the option to complete a purchase using the PDF wallet.

5. The customer is then forced to scan and receive their coin to the new PDF wallet.

...

Configure CAS

Create/edit webhooks

The CAS base configuration must be changed to offer PDF wallets.

1. Determine the URL path. In this example we’ll use: https://yourcasdomain.com/wallet

   1. It must be the domain for your CAS (e.g. yourcasdomain.com).

   2. The path /wallet is arbitrary and can be anything that doesn’t conflict with other paths.

   3. The protocol must include (and must support) HTTPS.

2. Create/edit the /batm/config/webhooks file and place the URL path as a setting:

sudo nano /batm/config/webhooks

• Add the setting pdfWalletLinkUrl=https://yourcasdomain.com/wallet

  • Replace the example URL with the one you decided upon in Step 1.

...

• Press CTRL-X to save the file and exit (leave the filename unchanged).

Finally, restart CAS to place the changes into effect.

Expose the webhook

Now the configuration has been created, you must expose this URL to the world. Installation (or modification) of NGINX is described in this article: https://generalbytes.atlassian.net/wiki/x/AQBlrw

It’s also possible to do it via Cloudflare (instead): https://generalbytes.atlassian.net/l/cp/VLSWb0XA

Yet another (undocumented) option: ngrok Secure Tunnel: https://ngrok.com/product/secure-tunnels

The URL path in any case must translate/point to: https://{master_bind_ip}:7743/api/v1/crypto-wallets

...

Enable the Feature per Terminal

...