PDF Wallet Generation

This option is currently available for BitBayCoin (BAY), Bitcoin Cash (BCH), Bitcoin (BTC), Dash (DASH), Ethereum (ETH), Litecoin (LTC), Monero (XMR), and Ripple (XRP). Coins implemented via extensions with support for IPaperWallet can be edited to support PDF wallets as well (undocumented).

Overview:

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. The webhook you create here will be sent to your customers and will (essentially) be exposed to the public. Choose carefully.

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

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

   2. Any arbitrary path can be used, BUT

      1. it MUST be used consistently, and

      2. it cannot conflict with another path,

      3. e.g. https://yourcasdomain.com/terminals would conflict.

   3. The protocol must include (and 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/pdf_wallet

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

Open

• 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

  • test URL example: https://cas-rest-api.yourcasdomain.com/api/v1/crypto-wallets/test

  • the pdfWalletLinkUrl should match your adjusted test URL (without the “test” suffix), because

  • that is the link that will be sent to your customers.

• 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/pdf_wallet becomes: https://yourcasdomain.com/pdf_wallet/test

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

Open

Enable the Feature per Terminal

Navigate to your Terminal (or Template) and enable the option in Printing Settings.

Adjust the PDF text

Adjust the content & layout of the PDF document with this Custom String.

• The same variables are accepted from: printer_paper_wallet_template

  • See: Custom Strings | printer_paper_wallet_template.1

Navigate to the appropriate Crypto Setting - CUSTOM STRINGS:

Example BUY

1. The customer initiates a BUY.

2. Customer selects the button “DON’T HAVE A WALLET?”, or

   1. if the Travel Rule is employed, the “CREATE NEW WALLET” option may be offered.

3. The Customer chooses “DOWNLOAD WALLET AS PDF”.

4. The Customer downloads the PDF file from the link provided.

5. The Customer confirms that they have downloaded the PDF (by pressing the button).

   1. The link may only be used ONCE!

   2. After the link has been used, the message “Invalid key” will be displayed thereafter.

6. The Customer uses the Public Key in the PDF to receive their coin.

Example PDF:

NGINX Specific Details

Your settings should contain entries such as these.