Bitcoin Jason News | Merchant education and technology | 7 November 2026. One of the frustrations of merchant adoption is asking a shop to place another tablet beside the checkout just to accept Bitcoin Cash. Paytaca’s new-generation Payment Hub raises an interesting possibility: keep the existing point-of-sale (POS) workflow and let Bitcoin Cash be an additional payment option. Here’s what is available, what still requires integration work, and how a merchant can start safely.
The short answer: Paytaca Payment Hub supports BCH invoices, payment links, an API and signed payment-status webhooks. This makes integration with an existing POS technically feasible. It does not mean every checkout can enable BCH with one switch; the POS software must support custom payments, a compatible plugin or a developer-built connector.
Following a recent conversation about rebuilding BCH merchant hotspots in Townsville, the Paytaca team pointed me toward Payment Hub as their invoicing and payment-gateway approach for systems that wish to integrate. This is worth exploring because the simplest merchant experience is often the one that changes the least about how staff already work.
What is Paytaca Payment Hub?
Payment Hub is a Bitcoin Cash payment service for one-off invoices, hosted payment pages and recurring-payment plans. It lets a business request a payment, share a checkout link or QR code and detect the outcome. Under its non-custodial model, the merchant’s BCH is paid directly to a receiving wallet rather than held in a processor account awaiting payout. Read the official Payment Hub overview.
Importantly, this product is different from Paytaca POS. Paytaca POS is a dedicated point-of-sale application. Payment Hub is the payment-link and integration layer intended to connect into other selling systems.
The goal: one checkout, more ways to pay
Imagine a café in Fairfield or a restaurant on The Strand. Staff take an order in their usual register and select Bitcoin Cash as a payment method. Their checkout software sends an order reference and amount to Payment Hub, receives a payment link, and displays the customer’s payment QR on a compatible screen or sends it to the customer’s phone. When payment is made, a signed notification reaches the merchant’s integration, which updates the sale in the original POS.
That is a proposed integration workflow, not an existing feature confirmed for a particular till brand. Each POS provider would need to confirm it can trigger an external payment request and accept a verified payment result. Some merchants may require a small custom connector.
Three realistic ways to start
1. Manual invoices: easiest first test
A business can use Paytaca’s direct-invoice feature to make a BCH request and share the payment page. This proves the customer’s payment experience, but staff may still need to create or share the invoice manually. It does not automatically mark the existing till receipt as paid.
2. Existing POS plus API: the ideal integrated option
For a POS with an extensible checkout or backend, a developer can create store-linked invoices, pass along a unique order reference, present the payment URL and process signed webhooks for paid, expired and cancelled invoices. Staff may be able to keep using the normal register, with no permanently attached BCH-only tablet. This depends on the POS provider’s supported integration methods.
3. E-commerce plugin: check availability before relying on it
Paytaca’s newer Payment Hub site currently labels WooCommerce, Shopify and additional one-click plugins as coming soon. Some older Paytaca pages describe a WooCommerce plugin differently. Do not assume a verified, supported plugin is available for your store until Paytaca provides the current download, compatibility details and installation instructions.
Installation guide: Set up a merchant in the Paytaca Wallet
The following is the wallet-side process documented by Paytaca. A merchant can set up its store without operating a server. Connecting an external POS automatically is a separate stage.

- From the official Paytaca website, install or update the Paytaca Wallet on a trusted device.
- Create a merchant-controlled BCH wallet, or prepare an existing compatible one. Make a secure offline backup of its recovery phrase, enable a strong device lock, and do not share the phrase with staff or POS vendors.
- Open Apps → Payment Hub inside the Paytaca Wallet.
- Select Add Store (some documentation calls this Create Store) and enter the shop’s details.
- For a basic merchant demonstration, start by creating a low-value, one-off invoice and viewing the payment page. Confirm the receiving wallet and the amount before sharing.
- If an external checkout will receive automatic payment notifications, the developer supplies an HTTPS webhook URL and the merchant enters it into the store’s configuration.
- Open the store’s Settings → Webhook Verification to obtain the Ed25519 public key used by the integration to validate messages. Keep store API credentials protected and rotate them through the wallet when necessary.
- Make a small live test transaction between two wallets. Verify the customer sees the correct invoice, the merchant receives the expected BCH amount and the original sale is reconciled correctly.
No webhook endpoint? You can still explore manual direct invoicing. Do not invent a webhook address or point a live business at an unverified endpoint. Automatic callbacks require a properly implemented, reachable HTTPS receiver.
Technical guide for a POS developer
A developer should use the interactive API reference and webhook documentation linked from the current Payment Hub site. Its integration demonstration supports store-associated invoices and returns a payment page and status that can be checked or handled through webhooks.
- Map order to invoice. On checkout, send a unique POS sale ID, an amount/currency and the destination receiving wallet to Payment Hub. Store the returned invoice ID and payment link against that sale.
- Present the payment. Show the hosted payment page or QR through the existing customer-facing display, a QR on the till screen, or a secure link sent to the buyer, depending on POS capabilities.
- Receive a payment event. Configure store webhooks for paid, expired or cancelled invoices. Paytaca’s new documentation uses events such as
invoice.paidand includes an invoice ID and BCH transaction ID. - Verify, then reconcile. Verify the Ed25519 signature exactly as Paytaca documents; check invoice ID, store association, requested amount, payment status and duplicates. Mark the correct sale as paid only when your agreed payment-verification policy is met.
- Keep an audit trail. Record the original AUD sale amount, conversion rate, BCH amount received, fees, transaction ID, invoice ID and date. Handle failed, expired and duplicate callbacks safely.
The current webhook guide states that notifications are signed with Ed25519, require HTTPS and should be processed idempotently. Some older Paytaca pages on payment-hub.paytaca.com refer to HMAC-SHA256. Those are different verification methods. Do not mix old sample code with the newer integration without checking the exact version with Paytaca.
What does Payment Hub cost?
Paytaca’s current published terms describe a 1% processing fee, waived when the calculated amount is below US$0.01 and capped at US$1 per transaction. Normal BCH miner fees are separate. The service also advertises no monthly platform fee. These are provider-published terms as checked on 7 November 2026, not a quotation for a particular POS integration. A POS vendor or developer may charge separately. Check Paytaca’s current terms.
What about Australian pricing and GST?
The newer Payment Hub interface supports fiat-priced invoices with conversion to BCH at a live exchange rate. Before rolling out to a Townsville merchant, test its AUD pricing, how long a quotation is valid and whether its fee presentation suits the checkout.
For Australian businesses, a BCH payment does not remove ordinary sales-record obligations. The ATO explains that GST on taxable supplies paid in digital currency must be accounted for in Australian dollars. Preserve the invoice’s AUD value, GST, BCH quantity and transaction details, and confirm the approach with the merchant’s accountant.
Before installing it in a real shop: our pilot checklist
- Identify the POS product and version. Ask the vendor whether it supports custom tender buttons, checkout APIs, customer payment links and third-party payment callbacks.
- Keep custody with the merchant. Never put a recovery phrase or private key in POS software, a website plugin or a support chat.
- Test the entire sale. Run a small invoice, pay it, verify the merchant’s wallet and confirm that the original receipt is closed just once.
- Test failures. Try an expired invoice, incorrect amount, cancelled sale, duplicate webhook and interrupted internet connection.
- Set a clear payment policy. Low-value in-person purchases and higher-value transactions may require different confirmation and risk controls.
- Prepare the team. Train staff to verify status inside their merchant systems, never rely solely on customer screenshots and follow an approved refund process.
- Promote only after verification. Update the merchant map and create a promotional video once the system is functioning reliably.
The Bitcoin Cash City opportunity
My goal is to rebuild practical Bitcoin Cash hotspots around Townsville, including The Strand and Fairfield. Reusing a merchant’s existing checkout could reduce hardware clutter, staff confusion and the ongoing maintenance burden that has often accompanied BCH adoption.
The first step will not be to promise every merchant a turnkey solution. It will be to select a willing business, document its current POS, confirm integration options with the provider, and test an end-to-end BCH sale with the merchant’s approval. Then we can develop a repeatable onboarding method for other businesses.
Bitcoin Cash adoption succeeds when it fits the way a real business operates. Payment Hub may become an important bridge between the familiar checkout and direct peer-to-peer electronic cash.
Official links and further reading
- Paytaca Payment Hub: current service overview, invoices, fees and API documentation
- Payment Hub webhook setup and Ed25519 verification
- Paytaca Wallet: official installation links
- Paytaca POS: separate merchant point-of-sale product
- Paytaca Wallet source and release information
- Australian Taxation Office: GST and digital currency payments
- Bitcoin Jason: Bitcoin Cash wallet comparison and self-custody guide
- Bitcoin Jason: History of the Bitcoin Cash City merchant economy
Editorial note: This article is independent Bitcoin Jason reporting and merchant education, not a paid Paytaca announcement. Product features, fees and plugins may change. We have not yet tested a live integration with any particular Townsville POS vendor. Technical guidance is educational and must be validated against Paytaca’s current API docs and the merchant’s own equipment before deployment.



