• A checkout that cannot reach the blockchain no longer skips one of your wallet’s receiving addresses, so a long outage cannot push a customer’s payment past what your wallet looks for. Bitcoin, Ethereum, Polygon, Base, Arbitrum and the Ethereum test network now fall back to a second public data source when the first is down.

• At checkout, the recipient check shows the receiving address on its own line, on one line where there is room and evenly wrapped where not, without breaking words. The Copy button no longer covers labels, and the amount and status stay whole on narrow screens. Choosing a different coin no longer waits on a slow network check.

• At checkout, a token payment can now switch its QR code between a payment link, which fills in the amount and coin, and the receiving address only, for wallet apps that mistake the link. The page shows the recipient to check. Choose which shows first in the gateway settings. A token’s own address is never accepted as your receiving address.

• On WHMCS 9.1 a refund is now recorded the way WHMCS’s own refund does it, so a fully refunded invoice shows Refunded with its credit note, and a part refund leaves the invoice Paid. A refund on an invoice paid in several parts is booked against each payment in turn.

• On an address you reuse, a payment is credited even when your first blockchain provider has forgotten older transactions — the next provider is asked. A refund is no longer pre-filled with an earlier customer’s address while the paying address is still being read.
• Healthy providers are no longer shown as failing when they don’t support transfer history, and your providers are no longer asked for it on every payment check.

• After a partial refund you can refund the rest of the payment from the same place later. The form shows what was already refunded and never lets you send more than is left, and the refunds recorded on the invoice add up to what the customer paid.

• Current prices lists every coin you accept in every currency you bill in, including any that has no price yet, so you can see at a glance what checkout is missing and why.
• Stability improvements.

• Security fix for USDT and other tokens on Tron: a payment is now recognised only from a real transfer of that token made after the invoice was opened.

• Stability improvements.
• A wallet set to a list of addresses you provide now records what each address already holds when a payment request is created, and counts only what arrives afterwards. That means you can build the list from accounts you already hold funds on, instead of needing empty ones.
• Each payment is credited to the invoice it was sent for. If you receive to one shared address, a payment that arrived just before an invoice was raised is no longer counted towards it.
• New: choose your address type. Bitcoin wallets can show addresses starting bc1, 3 or 1. Pick the one your own wallet displays, the wallet screen now previews the first address of each type from your key, so you can match it before saving.
• New: tidy up. Payment requests that expired or were cancelled without ever receiving anything can be removed in one click. Anything that took money is left untouched.
• New: Check the network now. If a customer says they have paid but the invoice is still open, open the payment and check again on demand, it credits whatever has actually arrived, whenever it arrived. Available on any payment that is not yet settled.
• Mark as settled now re-reads the network first, so it credits the exact amount received and tells you plainly if nothing has arrived yet.
• Better handling of wallets that use a single receiving address for every invoice: only payments made after an invoice was raised count towards it.
• The Payments list now warns you when a customer has opened the same invoice several times in a few minutes without completing it.
• Payments can be searched by receiving address, so a customer who tells you which address they paid can be matched to their invoice.

Stable Release