Merchant software updates, improvements and signed downloads.
Update your installation
whollycrypto update --check
whollycrypto update
The updater verifies the pinned signature and archive hash. It preserves your configuration and keys; keep independent backups. Read the update guide.
Wholly Crypto 8.3.2
Latest stable
Console navigation uses a slim progress line and stable placeholders. Refresh keeps existing rows visible, and Store tabs load only the features they need.
Slow page loads offer Retry. Static-only prefetch helps upcoming navigation without reading private data. Payments, wallet keys, approvals and schema 141 are unchanged.
Console pages load on demand, with less initial JavaScript and fewer hidden wallet and sweep panels.
Background refresh focuses on the visible page. Lists keep their place and controls stay usable while data refreshes. Wallets, invoices and transfer approvals are unchanged.
Faster EVM fee reviews keep progress across retries. Native sends can explicitly deduct extra fees from the recipient amount or retain the exact amount with project-funded gas. Token amounts stay unchanged.
Configure extra EVM fee headroom per project. New grouped approvals include bounded funding speed-ups; old hashes stay tracked and confirmed funding is never duplicated. Schema 141 preserves existing approvals.
Review pending EVM transfers together in the background. One approval covers same-nonce fee replacements and required project-funded gas; recipients and amounts stay unchanged.
Automatic EVM fee caps have more headroom. Fix premature attention warnings after resuming old signed transfers. Schema 140 preserves history; updating does not approve funding or higher fees.
Manual sends prepare in the background. Review the exact destination, amount and maximum fees in Transfer activity, then approve once. Signing and sending continue after closing the browser.
Live counters, compact source lists and bounded parallel EVM requests make large transfers easier to follow. Cancel before signing or refresh an unsigned quote; changed quotes need a new approval.
Fix signed-transfer details failing with humanize is not defined. Existing signed transfers can explicitly continue using their retained bytes. Schema 139 preserves wallets and history; updating does not authorize old sends.
Mark all notifications as read from the bell popup or notification settings, across every accessible page and filter. Compact rows improve spacing and readability.
Inherited checkout appearance is clearly read-only. Show or hide the Return to merchant button per store, or override it with checkout_appearance.show_return_button when creating an invoice.
Existing designs keep the button visible; automatic success redirects remain separate. Schema 138, wallets, payment history and financial permissions are unchanged.
Recover eligible EVM token transfers in one review, including missing native gas from the same project and a higher-fee replacement with the original nonce.
One approval starts funding, confirmation checks and replacement in the background. Amount, destination and fee limits stay fixed; retries never create a second token payment.
Clear recovery errors and grouped progress. Schema 138 preserves existing wallets and transfers; updating does not approve gas funding or a speed-up.
Better EVM fee estimates and bounded retries of existing signed transfers. Fees never increase automatically.
Transfer details offers an approved same-nonce speed-up for eligible EVM sends. Destination and amount stay unchanged; sufficient native gas is required.
Invoice lists and details open incoming transactions in their blockchain explorer. Schema 137 preserves wallets; invoice settlement stays separate from sweep confirmation.
Installed API docs now show expandable nested fields, compact descriptions and separate request and response sections. Response examples start expanded.
Create-invoice examples offer Minimal and Full views in four languages. Search opens matching fields; direct links, copyable paths and mobile navigation make the reference easier to use.
Documentation-only update. Schema 136, API behavior, permissions, wallets and invoices are unchanged. Update, reload, then open Settings → API access → Documentation.
Commission changes now require financial permission. Vendors with unsettled obligations cannot be archived; restoring an archived vendor requires an audited approval.
Overpayments do not block quoted vendor payouts on Bitcoin, EVM coins or supported ERC-20 tokens. Vendor shares stay unchanged and the excess stays separate for reconciliation.
Payout recovery verifies on-chain reverts and keeps previous fees in the budget. Automatic policies skip paused accounts and isolate invalid invoices. Schema 136 preserves wallets, balances and payment history.
Marketplace adds one checkout for several vendors, exact shares, commission and controlled Bitcoin/EVM payouts. Project wallets receive customer funds first; vendors are paid afterwards.
Six console tabs, 45 scoped API endpoints, signed events and SDK clients. Vendor funds are protected from ordinary sends and sweeps; network fees and token gas need separate funds.
Schema 135 preserves existing data. Marketplace and automatic payouts stay off until configured. The existing processing fee applies once per original invoice, not again per vendor payout.
Fresh setup supports an exact signed release with --version X.Y.Z. Latest stable remains the default; resume and GitHub fallback retain the selected version.
Interrupted setup resumes completed phases safely, including after an administrator account has been created. Existing accounts, wallet keys and settings stay intact.
Earlier installation, port, memory, disk and HTTPS checks; stale local DNS can be checked with two public resolvers. PostgreSQL authentication edits are atomic, validated and recoverable. No database schema change.
Customer checkout, payment links and scheduled payment emails now support ten languages, including Brazilian Portuguese and Simplified Chinese. Payment instructions, warnings, errors and hosted previews are translated.
Choose the store checkout language or override it per invoice or payment tool. Emails and resends keep the invoice language. Merchant-written content stays unchanged; Merchant and Operator consoles remain English.
Schema 134 is unchanged. Existing wallets, invoices and exact payment amounts are preserved. The managed proxy update adds the same-origin language asset without changing active domains or authentication. Upgrading sends no emails or payments.
Project Payment tools adds reusable payment links, a point-of-sale screen and scheduled email requests. Choose fixed fiat with fresh crypto quotes, exact on-chain crypto amounts, or customer-entered amounts within your limits.
Scheduled requests run once, weekly or monthly in your chosen timezone. They create ordinary store invoices, never automatic wallet debits. Safe retries reuse an invoice; missed periods do not trigger a burst of requests.
Settings System adds encrypted outgoing SMTP with connection and test-email checks. Notification channels can opt into system SMTP. Existing settings and payments are preserved; upgrading does not enable tools or send email.
Notifications & alerts adds a permission-scoped inbox, verified email and Telegram channels, grouped operational alerts and 30-day history. Theme choices move to the settings menu; store IPN and webhooks stay separate.
Settings → Accounting adds reports, a searchable transaction journal, accountant ZIP exports and checks for missing evidence. Confirmed receipts and costs stay separate from transfers and prepaid credit purchases; invoice totals are deduplicated.
Missing historical rates and actual fees remain flagged, never replaced with current prices or fee estimates. Schemas 132–133 preserve existing keys, invoices, credits and settings. Updating does not enable external messages or automatic payments.
Operator processing fees now follow verified customer payments, including accepted underpayments. Manual invoice labels cannot waive a fee; genuine chain reversals remain supported.
Operator fee conversion and reports now use provider-aware rate freshness, so daily fiat rates remain usable over weekends. Stale live exchange quotes remain blocked.
Operator API reports exclude the owner's separate business. Schema 131 preserves wallets, keys, fee policies and ledger history. Updates do not enable automatic payments.
EVM scanners use bounded due queues instead of stopping above 10,000 monitored payment methods. New payments and retained history keep independent scanning slots, with durable cursors and receipts preserved.
Kraken ERC20 deposits match original transaction hashes, including aggregate receipts. A deposit cannot be counted twice or used to trade unrelated funds.
Auto top-up adds payment checks and confirmed recovery actions. Resume the same valid payment or close an independently verified failed Ethereum transfer and pause the rule. Uncertain payments stay protected; only the receiver confirms credits. Schema 130 preserves existing data and does not enable automatic payments.
Auto top-up adds prepaid credits from a selected receiving wallet when the balance falls below your threshold. Off by default, with explicit consent, daily purchase limits, a network-fee cap and duplicate-payment protection. Only the receiving credit service confirms credit.
Supports BTC, ETH and Ethereum USDC/USDT. Operator installation credits use dedicated Operator wallets; hosted merchants pay their Operator from their own wallets. Token sources need ETH for gas; automatic gas funding is not part of credit top-ups.
The native CLI adds scoped reset, read-only previews and recoverable uninstall, with confirmation and verified backups. Removal retains database, keys, configuration, credits and installation identity. Schema 129 preserves existing data and never enables automatic payments on upgrade.
Automatic sweeps wait for the previous transfer to confirm and for an updated balance before starting another cycle, avoiding attempts against funds already sent.
Obsolete unsigned preparation warnings clear automatically when confirmed sends leave nothing above the sweep threshold or retained amount. Completed transfers and an audit record remain available.
Real failures, pending transactions and uncertain confirmations remain protected. Wallet keys, sweep rules, fee limits, approvals and schema 128 are unchanged.
Faster EVM and Solana wallet refreshes focus on funded, changed and new addresses, with periodic audits of empty addresses. The last completed balance stays visible while updating; explicit Scan balances still performs a full scan.
Manual sends and automatic gas funding avoid repeatedly reading recent empty invoice addresses. Small read batches and bounded provider fallback reduce preparation delays while retaining live balance, fee, nonce and reserve checks.
Sweep shows unsigned preparation separately from on-chain transfers and keeps the last preparation error visible during retries. Fresh completed balances remain usable during background refreshes; stale or invalidated balances pause new automatic work. Schema 128 preserves wallets, keys, rules and approved transfers.
My business in Operator mode no longer shows an internal processing-credit top-up dialog. Installation credits remain in the Operator panel; hosted merchants keep their own credit accounts.
Operator receiving wallets are excluded from merchant projects, dashboards, search and direct access, including My business. Reserved projects cannot be used through merchant API credentials or MCP.
Existing wallets, addresses, top-ups and fee settings are preserved. No funds are moved and no keys are regenerated. Automation checks remain enforced; schema 127 is unchanged.
The Operator panel now has its own interface with dedicated wallets, sweep, chain nodes and settings pages. Each page loads only the tools it needs; My business opens the separate merchant console in a new tab.
Copy a merchant UUID directly from the Operator merchant list for use with the Operator API. Receiving wallets, transfer approvals and shared scanner safeguards stay unchanged.
Fixes checkout appearance autosave jumping back to the project menu. Existing accounts, keys, balances and permanent installation modes are preserved; schema 127 is unchanged.
A separate, opt-in Operator API manages hosted merchants, users, invitations, local credits, fee policies, projects, stores and merchant API credentials. Direct account creation and invitation-based onboarding are both supported.
Scoped keys support merchant access, source-IP restrictions, expiry and request limits. Writes require retry keys; signed lifecycle events support backend integrations. Wallet secrets, spending and global server changes are excluded.
Installed and website API references include cURL, JavaScript, PHP and Python examples. All three SDKs 2.6.0 add Operator clients and examples. Schema 127 preserves existing accounts, wallets, balances and permanent installation modes; the Operator API starts disabled.
Operator login is clearly labeled. The credit balance opens top-ups; the extra Top up button is removed. Hosted console custody notices are shown at invitation acceptance instead of repeated in the header.
Add merchant supports a one-time free starting credit, including zero, in the merchant's credit currency. Grants appear in credit history and merchants are listed newest first.
Send invitation by email is checked by default. Set up your SMTP provider in Operator Settings, or uncheck it to copy the private link. Email failures keep the account and credit. Schema 126 preserves existing accounts, wallets and balances; updates never enable email or grant existing accounts new credit.
Operator receiving wallets support Bitcoin, ETH and Ethereum USDC/USDT with separate Bitcoin and Ethereum recovery phrases. Guided setup verifies tokens and preserves existing receiving wallets.
Operator navigation now includes merchant top-ups, wallets, sweep, shared chain nodes and fees. The header shows separate installation credits and top-ups; My business opens in a new tab.
Clearer first-admin terms and privacy spacing, with Add merchant above the list. Updates never create wallets or enable automatic sends.
Operator Finances shows earned fees, verified installation charges, estimated margin and current merchant credits. Filter dates, merchants and reporting currency, or export CSV. Pending charges and missing fiat rates stay clearly marked.
Invite hosted merchants and staff with expiring, single-use links instead of sharing initial passwords. Replace or revoke invitations and password-reset links in User accounts. Share links privately; no email is sent automatically. Basic Auth and 2FA remain enabled.
Schema 125 adds reporting indexes and account-link state. Existing installation modes, passwords, wallets, fee policies and balances are preserved. Reports separate prepaid credits from revenue and do not send funds.
Operator mode uses a dedicated fourth hostname with its own Basic Auth login. Choose the subdomain and credentials in a resumable DNS and HTTPS wizard; merchant protection stays unchanged.
Operator administration opens directly at its own address, without a merchant-page URL or workspace query. Existing 7.0.0 operators complete address/protection setup after updating. Failed validation preserves live routes.
First-admin setup explicitly warns that mode selection cannot be undone; changing mode needs a new installation. Schema 124 preserves wallets, payments and balances. Pre-7 installations remain in merchant mode.
Fresh installations choose permanent Merchant or Operator mode during first-admin registration. Existing installations stay in merchant mode and cannot switch.
Operator mode hosts separate merchant accounts with their own projects, stores, wallets and integrations. Manage users, prepaid credits and percentage fees, or use the included own-business account.
Credit purchases require verified settlement. Fees use the original invoice amount with retained rate snapshots and reversal protection. Hosted hot wallets remain accessible to the server operator; keep independent backups and use an operator you trust. Schema 123 preserves existing merchant data.
Switching projects or stores no longer clears accepted payment methods during autosave. Slow or failed loads cannot overwrite another store's selection.
Removing the last payment method requires confirmation, with a server safeguard for older cached consoles. Schema 121, wallet data and custom confirmation policies are unchanged. Review any methods that were already disabled before updating.
Payment scanners, balances, fees, health checks and transfer requests share provider budgets and quota cooldowns. Active payments take priority, while idle chains and empty wallets poll less often.
Older invoices keep late-payment and reorg monitoring with slower background checks. Non-EVM scan cohorts reuse safe provider reads; configured EVM, Solana, XRP and Polkadot WebSockets can wake scans, with HTTP catch-up retained.
Schema 121 adds a scheduling marker only. Wallets, payment history, confirmation policy, provider quorum and spending permissions are preserved. Public-provider capacity is still limited.
Invoice Details shows metadata expanded below customer details. Search invoice lists or the whole console by metadata keys and values, including nested entries.
Project sidebars use the default store logo. Prepaid request badges are more compact. Exchange account cards show estimated totals in your regional currency, with missing prices and stale data clearly marked.
Schema 120 rebuilds the invoice search index for existing records. Large histories may need extra update time. Payment behavior, wallet keys and sweep rules are unchanged.
Manual sending and opt-in automatic sweeps now cover native coins on 29 chains. Monero remains view-only. Existing ERC-20 and classic SPL support is unchanged; other token standards and Lightning spending are not included.
New adapters check amounts, fees, reserves and transaction identities before local signing. Use a compatible submission provider. Zcash is transparent-only, DOT uses Asset Hub and outgoing memo/tag destinations are not supported.
Send and sweep setup show chain-specific guidance. Schema 119 is unchanged; the update enables no wallets, rules or permissions. Preview and test a small transfer with your provider before enabling automation.
Automatic sweep Setup opens a modal for the selected asset and chain. Choose a destination, retained balance and fee limits without expanding the list.
Closing keeps unsaved edits. Save errors stay inside the editor, and enabled rules still need confirmation. Includes the dashboard tabs below the revenue chart. Schema 119 and spending behavior are unchanged.
Dashboard tabs now sit below the revenue chart. Reporting filters, totals and charts stay visible while you browse Projects & stores, Invoices, Wallets or Sweeps.
Switching lists keeps the chart in place without reloading it. Reports and lists refresh independently. Payment behavior and schema 119 are unchanged.
New dashboard tabs bring invoices, wallets and sweep transfers from your accessible projects together. Projects & stores keeps the reporting charts and totals. Lists include search, filters, pagination and links to details.
Each automatic sweep rule has a Setup button beside its switch. Settings stay compact until opened, and saving an enabled rule still needs confirmation.
Transfer progress refreshes without F5, including after slow initial loads and while editing settings. Wallet lists use cached balances and regional-fiat estimates. Schema 119 and spending limits are unchanged.
Transfer activity shows real ongoing work and transfers needing attention. Idle sweep rules no longer appear as waiting transfers; completed sweeps stay in history.
Completion uses read-only blockchain confirmation checks, not a display timer. Search and status filters keep history compact, with verified gas funding grouped inside the related sweep's details.
Schema 119 adds display-only tracking. Existing wallets, signed transactions and spending limits stay unchanged. Historical transfers are checked gradually after the update; no public API or SDK changes.
Automatic token sweeps fund eligible addresses in bounded groups, with reserved balances and nonces plus parallel confirmation checks. Existing limits and signed-transaction recovery are preserved.
Transfer activity adds Gas funding badges, filters, grouped details and automatic sweep progress. Token transfers remain separate from native gas funding.
Sweep setup adds Active rules and Inactive tokens filters. EUR 1 per rule can be a starting allowance for light usage, not a daily charge. Schema 118; no new migration, public API or SDK changes.
Automatic token gas uses one daily funding limit in your project's reporting currency. The next sweep's gas is estimated automatically; technical controls and optional diagnostics are under Advanced.
Limits apply per token rule over a rolling 24 hours. Missing prices or exhausted limits pause funding without increasing your budget. Existing native limits and saved choices are preserved; enabled rules still require confirmation.
Automatic progress shows funding and waiting reasons. Exact budget reservations preserve signed-transfer recovery. Schema 118; no public API, SDK or manual-send approval changes.
New token sweep rules start with project-funded gas selected. Existing saved choices and draft opt-outs stay unchanged. Automatic sweeps still require saving and confirmation.
Clearer gas funding text identifies the project's native-coin wallet and its limits. Enable confirmation shows the per-address and 24-hour budgets. Removed the unchecked gas placeholder message; real check results and errors remain visible.
Schema 117; no new migration, public API or SDK changes. Update with whollycrypto update.
Automatic sweep rules can keep a minimum coin or token amount across the project wallet, separate from the sweep trigger. Existing rules keep zero; manual sends are unchanged. Fees come from the excess, with network dust and rent limits preserved.
Needs attention supports individual or current-page selection to mark reviewed, add a note or rescan. Per-invoice checks and audit history remain; failed requests can be retried without repeating successful actions.
Project navigation shows the default store's checkout logo when available. Schema 117; no public API or SDK changes.
Restored inner spacing around the Console language section on desktop and mobile, including a fresh visit before opening Fees.
Includes 6.2.1's Live domains management and separate Add/Manage flows, with change-only DNS and activation review. No new migration or public API changes.
Manage existing domains directly from one Live domains list. Add domain has its own editor, with cancellation, pending-change labels and safe draft review before publication.
DNS results and activation review focus on changed addresses. Unchanged live hosts are not queried or reissued certificates. Removal-only and primary-address updates skip temporary ACME/staging reloads; Nginx and retired-host safety checks remain.
Fixed Console language selector styling and alignment without depending on a prior visit to Fees. No new migration or public API changes.
Search projects, stores and invoices from the console header, with suggestions while typing and direct navigation. Search respects assigned project access. Logout moves into the gear menu; Ctrl/Cmd+K opens search.
Filter chain connections by scanner status, including verified, unverified, restricted, failed checks, cooldown and incompatible APIs.
The consolidated dashboard adds an active cryptocurrency filter after Store. Tokens are separated by network, and reports follow received payments rather than checkout options. Schema 116 adds an invoice search index; large histories may take longer to update. No public API or SDK changes.
Fixed a scanner worker stack overflow introduced in 6.1.0 that could repeatedly restart an active merchant backend, causing intermittent Bad Gateway and billing-status warnings.
Scanner task scopes now keep large async state on the heap. Regression tests cover normal-sized worker stacks, concurrent scans, cache isolation and cancellation. Wallets, payment history and verification policies remain unchanged.
Recommended stability update for installations running 6.1.0. Schema 115, no new migration or SDK upgrade. Update with whollycrypto update.
More native-payment scanner APIs: Algorand algod, Tezos Octez, Polkadot Asset Hub RPC, Stellar RPC and transparent Zcash Core/Zebra. Full retained history and exact payment evidence remain required; healthy node height alone is not enough.
Bounded in-memory block sharing, remembered EVM log-range limits and additional public-provider pacing reduce repeated work without storing a blockchain database. Existing node settings, priorities and independent-provider thresholds are preserved.
Safer raw/indexed failover preserves Tezos and Zcash receipt identities. Connection details explain API and token limitations; native support does not imply new token payment methods. Schema 115; no SDK upgrade required.
Additional native-payment scanner APIs for Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash and TRON. Compatible raw nodes supply complete decoded or solidified blocks; basic node health alone is not proof of payment-history access.
Bounded history windows, resumable cursors and independent raw/indexed verification preserve exact amounts and receipts during provider changes. Raw-node catch-up can take several cycles; indexed history remains preferable for volume.
Connection details explain unavailable scanner adapters and list accepted APIs. Core raw scanning needs 1–48 confirmations; zero-confirmation Bitcoin still needs Esplora. TRON is native TRX only. Schema 114 preserves node settings and the default two-provider policy.
Manual/API invoices keep configured on-chain methods during scanner cooldowns, pending checks or insufficient usable providers. Detection waits for verified recovery; confirmation and provider-independence rules stay unchanged. Wallet setup, trustworthy rates and external Monero/Lightning request creation are still required.
Wallets → Addresses adds Hide small balances, on by default, for combined holdings below EUR 0.20. Unknown prices and stale balances stay visible. Cached assets show their approximate value in the project reporting currency.
Inactive automatic sweep settings start collapsed; active rules stay expanded. All / Has balance filtering and roomier recommended-setup guidance make the list easier to use.
Supported manual token sends start with Use project native coin for gas selected. Merchants can turn it off; quote review and explicit approval remain required. Existing automatic rules and wallets are unchanged. Schema 113; existing SDKs remain compatible.
Zcash scans now accept the exact empty-history response for unused addresses. Cosmos checks bypass short-lived caches and explain stale network heads without weakening validation.
Current EVM payments have priority over background history. Shared provider pacing, adaptive native scan windows and local capability-aware routing reduce avoidable requests. Current-payment lag and history catch-up are shown separately.
Optional BlockCypher history support adds another provider choice for Litecoin, Dogecoin and Dash; free quotas remain limited. Monero setup now clearly asks for an external view-only wallet-RPC. Existing node settings, verification policies and wallets are preserved.
Fixed BNB Smart Chain scanning on large blocks with a bounded 16 MiB full-block response allowance, smaller retained transaction data and lower request concurrency. Ordinary RPC limits remain unchanged.
Ethereum and other EVM scanners share discovery for invoices at nearby block positions, reducing repeated requests across creation times. New invoices and older catch-up work retain progress and fair scheduling.
Added Bitcore address-history scanners for Bitcoin Cash and Dogecoin alongside Esplora, including spent outputs and canonical transaction/output checks. Incomplete or oversized histories fail safely.
Chain details and readiness diagnostics list compatible scanner APIs, including mixed independent-provider pairs. Two providers remain the default; existing policies, cooldowns, wallets and history are preserved. Migration 112; additive accepted_endpoint_roles diagnostics, no SDK upgrade required.
Wallets → Addresses starts with Has balance enabled, including positive cached native-coin and token balances. Turn it off to include empty or unchecked addresses. Search and Page X of Y pagination apply to the filtered list.
Disabled console buttons no longer suggest loading when nothing is running. Actual pending operations retain their loading feedback.
Automatic sweep rules can choose matching chain/network addresses from the address book or use a manually entered address. Search and pagination make saved destinations easy to find. Selection fills a draft only; saving and confirmation remain required.
Required memos/tags are never silently dropped, and exchange and other-wallet destinations remain mutually exclusive. Existing rules and spending approvals are unchanged. No database migration or public API/MCP change.
Reorganized Public node catalog with a compact table, consistent badges, clear Added / Not added views and prominent chain and qualification filters. Detailed probes and source metadata stay out of the main list.
Configured connections outside the public pool are labeled Merchant only. Their added status remains clear, and Details opens local diagnostics instead of showing a public-catalog qualification failure.
Chain connection badges distinguish scanner cooldowns, expired checks, failed checks and incompatible APIs. Open a badge to see the recorded scanner error and retry time alongside separate capability measurements.
Existing connections, qualification rules and verification policies are preserved. Capability probes do not clear scanner cooldowns; scanner response limits and retry behavior are unchanged. No database migration or public API change.
Public node catalog marks endpoints already added to Chain connections, with filters for added and not-added entries. Disabled connections still count as configured.
Connections outside the central catalog appear as local entries, even before the first catalog download. They stay on your merchant and are never uploaded to the public pool. URL credentials and paths are hidden; Details opens the connection's local capability checks.
Qualification status now explains missing requirements and shows the successful-check count. Passing every capability in one probe still requires a second successful observation. Clearer operator-attribution wording separates provider review from connection tests.
Existing connections, qualification requirements and scanner verification policies are preserved. No database migration or public API change; available through signed updates for native Linux and Docker.
New Public node catalog, linked from Settings → Chain connections. Search thousands of public mainnet endpoints and filter by chain, freshness and qualified candidates for native payments, token scanning or historical access.
The centrally maintained catalog refreshes regularly, with signed updates cached on your merchant. Source dates, operator information and capability checks show what has been verified and what remains unknown.
Connection status opens a capability-details dialog for network identity, head freshness, native payments, token logs and history access. View central measurements separately from local results and run a read-only check from your merchant.
Catalog browsing and diagnostics leave configured connections and one/two-provider verification policies unchanged. Automatic node selection and rotation are not enabled. No additional payment chains are introduced. Migration 111; available through signed updates for native Linux and Docker.
Adds NodeReal as a default BNB Smart Chain connection to help payment scanning when other public providers restrict transaction receipts or reach shared quotas.
New installations and upgrades add the connection when absent and preserve existing NodeReal settings. Verification by two independent providers remains the default. Includes the console refresh fix from 5.13.4.
Fixed intermittent project-loading failures after refreshing the merchant console. Project reads recover when background requests invalidate cached data, without requiring another refresh.
Temporary loading failures retry once, stalled requests time out and persistent errors offer a Retry button. Session and access checks remain enforced; changes and payment actions are never automatically retried. No migration or SDK upgrade required.
Internal gas top-ups no longer appear as customer payments or false underpaid, late, expired-method and ambiguous-payment warnings.
An audited migration repairs matched funding records while retaining valid settlements, genuine overpayments, original transactions and signed callback history. No funds are moved.
Payment totals, current payment history, new callback snapshots, refund limits and recent-payment lists exclude verified internal funding. A historical settlement that depended on internal funding is marked invalid for review. Wallet balances are unchanged. Migration 109; no SDK upgrade required.
Fixed gas-funded EVM token sends waiting unnecessarily after funding. Each source's approved fee budget can cover the send without adding the selected fee-tier buffer again.
Transfer progress now separates confirmed gas funding from the token-send stage and clearly explains fee-budget waits.
Review updated gas prepares an unsigned follow-up for the same unsent tokens, reuses existing gas and requires fresh approval for the remaining costs. Previous funding and signed transactions are preserved. No migration or public API changes.
Fixed USDT, USDC and other ERC-20 sends failing during signing. Token transfers correctly send zero native-coin value while keeping the requested token amount positive.
Resume remaining transfer safely refreshes an expired unsigned step within the original amount, destination and fee limits. Completed gas funding is kept; signed or uncertain transactions are never replaced.
A fresh explicit approval renews the one-hour sending window. Installing this patch does not resume paused payments or change sweep rules. No migration or public API changes.
Manual gas-funded sends need one approval. Pre-reserved funding transactions are submitted together, confirmations are checked as a group and tokens follow automatically. Temporary node errors retry the original approved transactions.
Transfer review shows source and transaction counts, maximum native and reporting-fiat fees, and fees as a percentage of the transfer value.
Optional automatic-sweep fee limits wait for lower fees or fresh verified prices. Existing rules and unique invoice addresses are unchanged; safety limits and approval expiry remain enforced. Additive migration.
Manual send now shows examples below the native-coin reserve: zero adds no extra reserve without spending the whole balance; 0.005 keeps that amount available for later, with funding and fees covered separately.
Examples use the selected chain's native coin. Display-only patch; defaults, approval requirements, automatic sweeps and wallet data are unchanged.
Manual token sends can fund missing gas from the same project's native wallet on supported EVM chains and Solana SPL. Review native funding, fee limits and an optional reserve, then approve once.
Gas funding confirms before tokens move. Durable progress and original-transaction recovery keep approved amounts bounded; higher costs pause. Existing automatic rules and sending gates stay unchanged.
Cleaner manual-send form and review. Successful broadcast or funding approval closes the modal and opens Transfer activity, with progress and explorer links. Missing gas shows an actionable error.
Exact SPL sends combine token accounts and gas funding retains required Solana account balances. Wallet destinations, up to 32 token-owning addresses per workflow; Token-2022 remains unsupported. Additive migration preserves data.
Save a chain/address once in Address book. Native coins and matched CoinGecko tokens are discovered automatically, with grouped holdings, regional-fiat estimates, search and paginated details.
Watch-only fungible-token readers cover 22 chains using existing connections. Private balances and token overlays requiring separate indexers remain explicitly unavailable.
Bounded background work shows progress and errors, preserves cached balances on failure and fences stale results after edits. Additive migration preserves existing entries; invoice methods, wallet keys and spending policy are unchanged.
Exchange sweeps check minimums and deposit fees for every outgoing transaction, including small remainders. Below-minimum deposits stop before sending.
Spending discovers all recorded receiving addresses. Native EVM and ERC-20 manual sends combine addresses while covering the full requested amount and each source's gas; large sweeps use bounded batches.
Wallet reservations prevent overlapping sends and nonce/input reuse. Lost responses recover by checking the exact transaction hash before retrying original signed bytes. Resume uncertain transfers instead of replacing them.
Additive migration preserves wallets, history, approval requirements and sending policy. No public API, MCP or callback contract changes.
Faster merchant console with on-demand features, active-section rendering and unchanged-row reuse. Project switching uses brief session-only read caching with duplicate-request reuse and cancellation.
Verified versioned browser assets are cached; HTML and private APIs remain no-store. Wallet balances, secrets, billing and sending checks stay outside the read cache.
Invoice lists fetch less metadata and avoid redundant counts on short pages. Activity queries load payment details only for the selected page. No migration, added index, policy change or fund movement.
Manual sending has two steps: prepare, then review and Approve & send. Approval, local signing and broadcast retain their audited checks; failed requests stop for a status refresh before continuing.
Sweep separates automatic setup, exchange destinations and transfer activity into tabs. A native-gas reminder explains fees at each sending address.
Compact paginated history opens transfer details, with public explorer links for submitted transactions. Broadcast is not confirmation. No migration, policy changes or transfers triggered by this update.
Fixed missing wallet fiat estimates for verified USDC/USDT when CoinGecko prices are stale or missing. Fresh quotes from enabled Kraken/Binance rate providers provide a fallback, primary provider first.
No assumed dollar peg or ticker-only custom-token pricing. Wallets distinguish missing market prices from current balance scans; reporting-currency conversion and partial totals stay accurate.
No migration, key changes or fund movement. Invoice quotes, payment amounts and transfer settings are unchanged.
Manual balance scans get reserved capacity and keep priority across address pages. Bounded parallel workers and provider timeouts prevent one slow chain from holding up every wallet.
Per-asset progress shows checked addresses, updated balances and clear errors. Lightweight polling avoids repeatedly loading all wallets; Manual Send retains your entered amount and destination.
Only complete scans publish fresh totals. Short leases recover interrupted scans safely; large wallets may continue in the background. Additive migration preserves keys, history and transfer policy.
New Settings → Address book with named chain/asset destinations, tags, descriptions, search, sorting, pagination, cached balances, regional-fiat estimates and explorer links.
Manual Send offers saved and recent project/asset destinations. Preview only defaults off; plans still require separate approval, signing and broadcast. Plans created from Wallets open Sweep for review.
Scan balances on wallets and inside Manual Send requests fresh native/token scans. Repeated requests are throttled and active scan cursors are preserved.
Public Monero balances remain private. Required memos/tags are never silently dropped. Additive migration preserves existing wallets, history and transfer policies; public API and callbacks are unchanged.
Per-node scanner eligibility badges distinguish usable payment sources from connectivity alone. Chain details can explicitly trust one provider; two independent providers remain the default.
Wallet estimates use the default store currency, falling back to the project currency, with real exchange-rate conversion and fiat-appropriate rounding.
Fourteen verified public fallbacks and three corrected Bitcoin scanner connections expand the install defaults. Same-operator aliases do not count as independent providers; existing custom settings and disabled nodes stay intact.
Single-provider mode removes independent cross-checking, not network, amount or confirmation checks. Some chains still need an own or credentialed history provider. Updated API diagnostics and documentation.
Console saves, toggles, uploads and delete actions use explicit POST endpoints, compatible with Cloudflare’s Not GET or POST rule without a WAF exception.
Login, CSRF protection, project permissions, validation and deletion confirmations remain enforced. No automatic retries or generic method override.
Public API, SDKs, checkout and MCP protocols are unchanged. Existing console methods remain available for already-open tabs.
New domain fields appear above existing editors without changing the primary domain. Store domains has a clean in-panel heading and consistent spacing.
Clearer server/proxy 403 errors with a safe Cloudflare Ray ID. Unsaved changes are preserved; normal authentication and CSRF protection remain enforced.
A Cloudflare rule blocking PUT requests still needs adjustment in Cloudflare. This patch does not bypass external security rules.
Show or hide project and store names on customer checkouts and previews, with default-store inheritance and per-invoice API overrides.
Choose active merchant, pay and API domains per store. Generated links prefer the store, then the default store, then system defaults; retired domains fall back safely.
Live domains appear first. Adding domains reuses unchanged live hosts and validates new ones before activation, then returns to the active overview.
Store-count badges, store-name and logo headers, and recent activity showing the received asset amount, token and network. Updated API docs and SDK 2.5.0 examples.
Shared receive-readiness checks explain missing wallet, scanner and provider requirements before invoice creation. Chain connections show scanner-ready, unavailable, unchecked and delayed states separately from node health.
Manual invoices keep unavailable methods visible with reasons, settings links and Check again. Store payment methods and wallets share the same receiving checks; balances and sending gas remain separate.
Structured API/MCP diagnostics identify the chain, asset and actionable blocker. PHP, Python and Node SDK 2.4.0 adds safe exception explanations and convenient payment-method issue helpers.
Invoice API/MCP selections ignore inactive or unaccepted choices, use store defaults if nothing matches, and include all active assets for a chain-only selection. Existing invoice methods and idempotent retries are preserved.
Chain-specific invoice errors explain wallet, scanner-provider and rate requirements, including TRON history-indexer readiness. Safety checks and ambiguous-ticker rejection remain enforced.
Manual Send reloads the current shared balance snapshot on opening. Wallets adds Active in stores filtering, including token-only chains. Store Payment methods uses smaller chain hints without repeated identifier boxes.
The consolidated dashboard defaults to Last 30 days, with Last 60/90/180 days, Last year and All time. Long histories use monthly or yearly chart points within the user's reporting scope.
Fixed Add destination remaining unavailable after returning from Exchange settings. Clear access checks and a more compact destination layout.
Connect/disconnect switches and safe deletion for saved exchange accounts. Unresolved jobs block deletion; saved credentials are removed without deleting exchange funds or historical records.
Estimated fiat values in exchange balances use your regional default currency. Sort any column, with highest fiat value first; unknown and stale prices remain clearly identified.
API and MCP invoices accept chain-scoped asset_tickers. Copy selections from Store → Payment methods. Ambiguous symbols require asset_ids; existing acceptance, readiness and idempotency checks remain enforced.
Search and page through receiving addresses from Project → Wallets → Addresses, with invoice links, order IDs, references, derivation indexes and exact cached asset balances.
Clearer base-address and aggregate wallet balances. Shared-account balances are not presented as separate invoice balances.
Chain-specific recovery help, selected-address reveal confirmation, backup cautions and practical Sweep recommendations. No automatic transfers or key disclosure.
Wallet keys, invoices, callback payloads and existing sending policies are preserved. Receiving and spending support remain separate.
Regional defaults in Settings → System, after Console language: searchable fiat currency and timezone for new projects and accounts.
The consolidated dashboard uses the system currency until you choose another. Existing projects, stores, invoices and prepaid-credit currency are unchanged.
Choose chains and assets for each manual invoice without changing store settings. API and MCP requests accept optional payment_methods selections, with Bitcoin Lightning chosen separately.
Selections can only narrow accepted, ready store methods. Invalid, disabled or unavailable choices are rejected, with no silent fallback to other assets. Existing idempotency, wallet keys and callbacks are preserved.
Faster invoice search and navigation, retryable checkout-appearance loading and better laptop layouts.
Wallet backups offer plain TXT or a searchable offline HTML file with embedded QR codes. Both contain unencrypted secrets: keep them private and offline.
Send shortcuts open the exact wallet asset in manual-send review. Dashboard currency persists after reload, charts show hover details and custom dates use a modal.
Checkout puts the fiat total under Amount due, shows the order description below its title and moves Return to merchant to the top-right. Improved logo borders, picker hover states and subtle waiting indicators. Existing payment rules, keys and callback payloads are unchanged.
Settings → API access puts AI connections · MCP below API credentials, with clearer spacing between the panels.
Wallet filters add Has balance and Has no balance, combinable with search and readiness. Native coins and tracked tokens count; unknown or stale zero balances are not classified as empty. Current badges now fit their text.
Project invoice rows show the order ID alongside the description, plus received crypto amounts and their chain/token. Batched cached summaries keep the list fast, with no per-invoice node calls.
IPN and webhooks now include paid_asset_amount for the full crypto quote and paid_asset_amount_received for actual receipts at settlement. Exact decimal strings preserve accepted shortfalls and overpayments without changing the invoice amount.
Settlement amounts stay frozen on retries. Older snapshots remain unknown, saved event bodies are unchanged, and payload version stays 2. Merchant/product documentation and all three SDK examples are synchronized.
Checkout hides the chain and asset chooser while payment confirmation is in progress. Payment details, progress and transaction links remain visible; partial payments keep their remaining-amount controls. Hosted previews match.
Built-in merchant MCP at your API domain’s /mcp endpoint. Connect an AI assistant without installing an extra service. MCP stays off until explicitly enabled.
Eight project-scoped read tools cover stores, payment methods, balances, invoices, delivery status and conversions. Invoice creation requires separate approval and keeps the existing validation and idempotency rules.
OAuth with administrator consent, S256 PKCE, rotating tokens and revocable connections. Optional bearer access, project permissions, IP restrictions and shared API rate limits remain enforced. No wallet-secret exports or fund-transfer tools.
New English/German MCP guides, homepage and feature information, plus synchronized merchant and product API references. Existing wallets, invoices, domains and REST integrations are preserved.
Top-level paid_chain, paid_asset and paid_payment_method_id identify the payment method that settled an invoice. Detailed payment_info remains available in IPN and webhooks.
settlement_exchange_rate saves the before-spread market rate at settlement with explicit units, currency, source timestamps and quality flags. It never changes the locked invoice amount.
Retries and further payments to the same method preserve the saved snapshot, including missing rates. Reorgs clear the current summary; re-settlement or a changed settling method gets a new snapshot. Historical event bodies are unchanged.
Updated merchant/product API references and PHP, Python and Node SDK examples. Existing SDK 2.1.0 and shop plugin 1.0.2 receivers remain compatible. Wallets, invoice amounts and store policies are preserved.
New quotes for recognized verified fiat stablecoins round up to at most two decimals, after spread. Paying the rounded amount in full works with zero tolerance; existing invoices keep their locked amounts.
QR codes, wallet links and copied checkout amounts request the full outstanding quote. Underpayment tolerance is no longer subtracted from the requested payment.
Tolerance only decides whether received funds count as paid. Accepted shortfalls do not show as underpaid or ask for more funds while network confirmations are pending.
The shared calculation covers all chains and tokens, including partial payments. Existing invoice totals, settlement policies, wallets and callback field meanings are preserved.
Richer IPN and webhook snapshots include used chain/token, exact received, confirmed and missing amounts, transaction links, customer metadata and signed event/project/store IDs.
Locked quote, spread, tolerance and upward rounding stay separate from advisory cached market rates. Retries preserve the original snapshot; unavailable historical rates remain unknown.
Delivery Details groups payment, rate and customer information. A read-only paginated payments API provides complete current transfer history when callback arrays are truncated.
Update strict nine-field receivers or whole-body duplicate checks. SDK 2.1.0 and shop plugins 1.0.2 support new and retained legacy callbacks. Existing wallets, invoices and queued payloads are preserved.
Breaking API response change: invoice_id replaces public_id in invoice creation, lists, detail and checkout, matching IPN/webhooks. Internal IDs remain id; invoice URLs and callback bodies do not change. Update custom integrations before upgrading.
Official PHP, Python and Node.js SDK 2.0.0 use invoice_id. WooCommerce and WHMCS plugin 1.0.1 support both new and older merchants; update the plugins first.
Each invoice has separate collapsed IPN and webhook histories. Compact store histories show order and invoice IDs, customer name/email, delivery status and time, with search and pagination.
Details opens a modal with the saved body, delivery result and timeline, separately from current customer metadata. Expired data is never recreated; wallets and payment history are preserved.
IPN and Webhook history Details now show the saved invoice status, exact JSON body and delivery result. Payloads load only when opened, with clear expiry messages.
Clearer callback documentation covers event selection, all invoice statuses, payload fields, separate signing secrets, retries and safe order fulfilment.
The customer checkout footer links to the official Wholly Crypto website in a new tab. Existing wallets, payments and invoice history are preserved.
More reliable Ethereum and EVM token scanning. Recent invoices are checked separately from older history catch-up.
Smaller token queries adapt to public provider limits. Historical-access restrictions and rate limits are handled separately, with scheduled retries and cooldowns.
Chain connections now highlight delayed payment scanning even when basic node health checks pass.
Existing payments, invoice history and wallets are preserved. Payments still require verification by two independent providers.
Accept Bitcoin Lightning through an external LND node or a compatible Nostr Wallet Connect wallet. Enable it independently of on-chain Bitcoin in each store.
Connection checks, project access and shared Lightning balances, with clear guidance on self-hosted, managed self-custodial and custodial wallets.
Lightning QR codes and wallet links, whole-satoshi quotes, exact millisatoshi payment records and restart-safe settlement tracking.
New English/German setup guides and updated API documentation, features and comparisons. Lightning receiving is opt-in; sending, refunds and channel backups stay in the external wallet.
See available, held and total balances for Kraken, Binance and Coinbase Advanced Trade accounts in Settings → Exchanges.
Search and paginate balances, include zero amounts and refresh. Exact values retain their timestamps and show a warning when cached results are stale.
Each chain/token sweep chooses either another wallet or a matching verified exchange destination, never both. Switching clears inactive destination settings.
Improved mobile balance layouts and exchange dialog cleanup. Balance checks are read-only; existing wallets, credentials and sweep rules are preserved.
New Exchanges settings for Kraken, Binance and Coinbase Advanced Trade, with encrypted credentials, connection checks and project access controls.
Search automatically refreshed spot markets, indicative rates and trading minimums for each exchange.
Send supported assets to verified exchange destinations from Sweep, manually or automatically. Optionally convert a matched, credited deposit to supported fiat or crypto.
Network, token and account checks, exact amounts and durable order tracking. Interrupted orders are reconciled without blind resubmission.
Exchange connections and trading stay off until configured. Exchange custody, KYC and fees apply; fiat stays in the exchange account. Test new routes with a small amount first.
Larger Intro and Outro checkout message fields, each with its own font size. Existing customer messages are preserved as the Intro.
Create-invoice API supports partial checkout appearance overrides, including same-project store logos and favicons. Each overridden invoice keeps its resolved design independently of future store edits.
Updated merchant and website API references with shared cURL, JavaScript, PHP and Python examples. Structured settings only; no custom HTML, CSS, JavaScript or remote image loading.
Fixed project-deletion confirmation handling for checked acknowledgments and pasted identifiers with surrounding spaces.
Clear identifier feedback and accurate loading states. Backup, switch-off and permanent-history safeguards remain in place; updating never deletes projects.
The setup reminder now says Project is currently disabled.
Project names, section titles and page actions align in one desktop header row.
Content starts level with the project enable/pause switch, removing the extra gap. Store and invoice actions remain on the right, with a responsive layout for narrow screens.
Project enable/pause switch moves above the section menu, including the mobile dropdown.
Section titles sit at the top left of the content, with store selection, New store, Create invoice and other section actions on the right.
Responsive spacing for long project names and narrow screens. Mobile project switching no longer triggers an unnecessary store save. Existing project status, wallets, payments and credit settings are unchanged.
Project sections move into a desktop sidebar, with a compact dropdown on small screens.
Four-step project deletion with wallet-backup acknowledgment, a switch-off step, permanent-history review and typed confirmation.
Completed invoice and payment history no longer blocks project deletion. Active work and known balances stay protected; processing fees, prepaid credits and existing backup files are unchanged.
Updates safely wait for running background jobs while checkout stays online. Timeout and cancellation restore timers without restarting the app.
Clearer console update progress and failure messages, with safe recovery when interrupted before installation.
A verified standalone updater lets older installations adopt the fix without manually pausing timers. Wallets, invoice history and credit rules stay unchanged.
Distinct enable and disable icons for chain connections.
Clearer prepaid-credit request badges and compact payment links in a separate column.
Simpler top-up payment screens. Quoted amounts and processing fees are unchanged.
Delete an unused, paused project after confirming your existing wallet backup. A fresh backup download is optional; balance and history protections remain.
Highlighted payment-received cards with confirmation progress. Fully received credit top-ups no longer show an expiry timer while confirmation is pending.
Instant credit-tab navigation with background history refresh and pending-request badges. Credit decisions remain server-verified.
Automatic release-versioned browser assets for the console, checkout and API reference, plus cleaner source-IP forms. Existing wallets, balances and quotes stay unchanged.
Faster console opening and refresh with earlier secure session verification and bundled assets.
Faster prepaid-credit loading, optional billing details in the background and automatic top-up availability updates without losing drafts.
Payment countdowns use authenticated server time, so an incorrect computer clock cannot falsely expire a valid quote. Existing quotes and payment verification are preserved.
Fee details and Refresh stay together on large and small screens.
Automatic credit activation after the first admin signup, with a one-time 10 USD equivalent welcome credit. No activation code or support request is needed.
Safe retries preserve the same credit account and never duplicate welcome credit. Existing balances, fee policies and wallet keys stay unchanged.
Fixed fresh installations stopping after HTTPS certificate issuance when TLS support files are missing. Resume keeps existing keys, credentials and certificates.
Clear setup progress with spinners, elapsed time, actual download percentage and success/failure markers. Redirected logs use plain-text status updates.
Fixed 3,000-token CoinGecko refreshes rejecting unusual provider IDs or blank display names. Existing cached data stays available while the next complete snapshot loads.
Consistent token registration and icons, updated API guidance and expanded catalog regression tests.
Add and edit custom ERC-20 contracts and classic Solana SPL mints in store payment methods, with on-chain verification.
Exact project-specific fixed USD prices for custom tokens, shared by that project’s stores and shown in wallet values. Existing invoice quotes stay unchanged.
Custom-token API documentation, responsive token dialogs and a simpler IPN layout.
Grouped wallet address/actions and chain-specific secret details with private-key QR support.
Installing a new version requires verified positive processing credit when fees are enabled. Update checks, backups, recovery and incoming payments stay available; fee-free accounts have no credit restriction. Updated English and German documentation.
Consolidated revenue dashboard across authorized projects and stores, with calendar presets, custom dates, currency/timezone filters, charts and CSV export.
Dashboard shortcut before project navigation and Create project at the right.
Per-host Let's Encrypt or Cloudflare proxy selection, with validated staged activation and strict origin TLS.
Exhausted-credit mode also pauses new project/store creation. Existing checkouts and incoming payments continue; fee-free accounts require no prepaid credits.
English-first product localization with a German homepage and documentation, plus a clearer degraded-mode guide. Existing keys, account policy and active domains are preserved.
