Page Comparison

...

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

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

   2. The path /walletwallets is arbitrary and can be anything that doesn’t conflict with other CAS 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:

...

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

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

...

• Press CTRL-X to save the file and exit (choose “y”, and leave the filename unchanged).

...

• The setting will automatically be updated within CAS in approximately 30 seconds.

Expose the webhook

Now that 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

...

• : 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

Testing

Append “/test” to the end of the exposed URL. Navigate to the URL using a web browser.

• e.g. https://yourcasdomain.com/wallets becomes: https://yourcasdomain.com/wallets/test

• Navigating to that URL should result in a simple web page “Invalid key” result.

...

Enable the Feature per Terminal

...