​

Changelog

​

Common questions

​

What changes appear here?

​

Where is the public developer contract?

​

June 2026

• Native Solana USDC subscriptions are live across the merchant builder, Get Started wizard, merchant template docs, and Hilt Pay API docs
• SDK and developer assets are updated to version 1.1.0, including structured errors, request ids, idempotency handling, webhook helpers, sandbox helpers, recurring examples, and refreshed Postman assets
• Merchant renewal models are now clearer: one-off payments and native automatic renewals
• Native automatic renewals are described as buyer-approved Solana USDC subscriptions, not generic background charging
• Hilt’s native collection path keeps the operating layer intact: collection evidence, receipt records, membership period extension, webhook delivery, support context, analytics, and audit history
• Native cancellation semantics are period-aware: future collection stops immediately while access can remain available through the paid-through date before post-period revoke or close handling
• The quick-start wizard, Product Studio, and docs now present one-off and native automatic renewal products as distinct setup paths

​

May 2026

• Hilt Pay API is now the primary developer and agent-facing surface for AI tools, APIs, bots, datasets, paid software, and private products
• The Developers page now leads with Hilt Pay API, Agent Bootstrap, setup intents, x402 protected-resource protocol flows, Solana USDC settlement, SDKs, Postman, OpenAPI, and GitHub developer assets
• Added an Agent setup guide covering sandbox setup intents, manifests, owner approval, rail settings, setup readiness, payment sessions, x402 HTTP 402 requirements, and entitlement checks
• Pricing now separates Hilt Pay Workspace from Hilt Pay API, with API tiers for Sandbox, Starter, Growth, Scale, and Enterprise plus an API-specific estimator up to $1m/month
• Hilt LLM files now describe the Workspace/API split, exact API pricing, x402 protocol boundary, Solana USDC settlement, and the current public settlement scope
• Hilt Pay for WooCommerce is now approved on WordPress.org at wordpress.org/plugins/hilt-pay-for-woocommerce
• WooCommerce docs now install from WordPress.org first, with the direct ZIP retained as a fallback
• Merchant Operating Layer V1 is live: merchant Analytics now has clearer revenue-by-day reporting, date ranges, product lenses, checkout-funnel reporting, and day-level summaries
• Starter-and-above operating tools now include merchant analytics, buy notifications, CSV/PDF exports, and tax/export records, with public receipt proof kept privacy-conscious
• Support ticket workflows now send email updates around ticket creation and replies, while ticket context can stay linked to payment, receipt, member, or checkout details
• Billing now exposes the Stripe customer portal more plainly when a Stripe customer record exists, so merchants can manage payment methods, invoices, and cancellation in Stripe
• Launch Wizard V1 is live for new merchants, covering link-only, embed, WooCommerce, Telegram, Discord, redirect, download, and custom handoff setup paths
• The launch checklist now stays visible in the merchant dashboard until the first setup steps are complete
• Discord setup now surfaces the Hilt Connect invite path before merchants rely on Discord role automation
• Hilt Pay for WooCommerce first shipped as a self-hosted plugin ZIP before the later WordPress.org approval
• The WooCommerce page now explains order handoff, hosted Hilt checkout, signed webhook confirmation, buyer return, and merchant-owned payout flow
• Embed checkout is now live, so merchants can add a Hilt checkout button to external pages and keep a direct checkout link as the fallback
• Zapier public V1 has been narrowed to event, reporting, and lookup workflows for review readiness, with checkout-link creation kept private and deferred unless Zapier explicitly approves it
• Zapier template planning now covers common merchant operating workflows such as Sheets reporting, Slack alerts, Gmail follow-up, CRM notes, Mailchimp segmentation, and support tasks
• Checkout now supports a unified multi-wallet flow across desktop and mobile, reducing the old Phantom-only buyer path
• The homepage has been simplified into six clearer sections that explain who Hilt serves, how checkout works, and why the custody model matters
• Learn is now the home for buyer education, articles, FAQ, and release updates, with navigation cleaned up around merchant-facing discovery
• The public FAQ has moved into Learn so merchants and buyers can find product answers alongside guides and articles
• Public site pages now use a cleaner white-background presentation and tighter title treatment where that improves readability
• Official JavaScript and Python SDKs now install from npm and PyPI respectively, with dedicated public GitHub repos for each package
• Approved OpenAPI snapshots, Postman imports, and example webhook payloads now also live in a public developer-assets GitHub repo
• The public CLI now covers webhook endpoints, delivery logs, re-send flows, sandbox sessions, recurring recovery, delivery diagnostics, and direct receipt proof sending
• Hilt now provides sandbox API testing without claiming a separate fake settlement rail
• Public merchant and developer playbooks now turn webhook launch, delivery rescue, recurring recovery, proof handling, and go-live checks into dedicated guides
• Official TypeScript and Python SDK download artifacts are now published from Hilt alongside a first-party Postman collection and environment
• Developer docs and the public Developers page now point to real Hilt SDK and Postman install paths instead of telling teams to generate their own first
• Merchant analytics now shows a real checkout funnel with hosted checkout opens, payment session starts, confirmed payments, and daily open → connect → confirmed reporting
• Product reporting now combines take-home, fees, renewal pressure, delivery-failed rate, and support load so merchants can see what needs attention without stitching together multiple screens
• Admin analytics now includes merchant-operations reporting with workspace attention signals, product heat, and cross-platform renewal, delivery, and support pressure
• Hosted checkout opens are now recorded as a first-class analytics signal instead of being inferred from broader website traffic
• Webhook operations now include signed test events, payment or membership event timelines, and a stronger merchant delivery-log workflow around self-serve Re-send webhook
• Telegram and Discord access recovery now includes live provider diagnostics plus support-linked escalation actions in merchant workflows
• Recurring operations now expose expiring-soon cohorts, collection timing, cancellation state, recent renewal events, and product-level renewal reporting for native recurring flows
• Receipt proof now has a richer public proof page, PDF generation, invoice metadata, receipt search filters, and direct “send proof link” actions from merchant and admin workflows
• Support tickets can now carry structured payment, membership, and receipt context so retry delivery, proof sharing, and renewal recovery actions stay tied to the case
• Recurring access flows are now cleaner across checkout, members, support, admin operations, and public pricing
• One-off payments and native recurring flows are now treated as separate commercial modes instead of one fuzzy recurring setup
• Recurring access keeps buyer approval explicit while Hilt records collection, receipt, access, webhook, support, and audit state
• Merchant webhook delivery logs now include a self-serve Re-send webhook action for retry-scheduled and dead-letter deliveries in the dashboard
• Tightened the public pricing ladder so one-off payments and native automatic subscriptions are described more plainly
• Updated the pricing calculator, comparison cards, and Developers page so the plan story stays consistent across the site
• Reworked the webhook docs into a first-class integration surface with quickstart, event catalog, signature verification, delivery behavior, idempotency, and migration guidance
• Template renewal modes are now explicit: one-off payment versus native recurring flows instead of one fuzzy recurring setup
• Updated the merchant builder, pricing language, and developer examples so payment model and renewal model are clearer before launch
• Access automation rescue is now queue-backed for failed membership delivery and failed expiry revoke paths
• Added a dedicated Delivery operations desk in admin with due-job sweeps, manual-review visibility, readiness gaps, and recent attempt history
• Updated the merchant and developer docs so post-payment delivery now reflects automatic rescue plus manual retry controls
• Native Hilt webhooks are live for payments, memberships, receipts, failed delivery, and support ticket creation
• Added signed outbound delivery with retry scheduling, dead-letter handling, and replay controls in the Hilt admin workspace
• Updated the developer docs so webhook integrations are now first-class, while payment polling remains a valid fallback during active checkout flows

​

April 2026

• Rebuilt the public docs around merchant and developer audiences only
• Tightened the public language so merchant and developer workflows stay clearer throughout the docs
• Clarified the relationship between dashboard templates and API or CLI products
• Refocused the public developer guidance on the live Hilt API