paulhilt

Hilt

<p>Hilt Pay uses X-Hilt-Key authentication, checks the connection with GET /v1/products?limit=1, lets merchants choose Hilt checkouts from GET /v1/products, and creates hosted checkout handoffs through POST /v1/products/{product_id}/handoff-link. Mapped Hilt templates should use the configured WooCommerce identity type, which defaults to CUSTOM.</p>
<p>Support and landing page: https://www.hilt.so/woocommerce</p>
<p>The plugin is free. There is no WooCommerce surcharge. Standard Hilt plan pricing and transaction fees apply.</p>
<p>Includes:</p>
<ul>
<li>WooCommerce offsite payment gateway.</li>
<li>Admin settings for API base, API key, Hilt identity type, webhook signing secret, webhook URL, and connection health check.</li>
<li>Minimum API key scope guidance: read + execute only.</li>
<li>Product and variation selector for choosing the Hilt checkout/template that should fulfil each WooCommerce product.</li>
<li>Hosted checkout handoff creation through POST /v1/products/{product_id}/handoff-link.</li>
<li>Webhook receiver at /?wc-api=hilt_pay.</li>
<li>HMAC verification with X-Hilt-Signature and X-Hilt-Timestamp.</li>
<li>Event-id deduplication.</li>
<li>Order notes for Hilt success and failure events.</li>
<li>Visible admin/order states for Hilt API failures and 429 rate limits.</li>
<li>Customer user-meta sync for Hilt membership status and expiry when present.</li>
</ul>
<h3>Checkout Blocks</h3>
<p>The plugin declares Cart and Checkout Blocks compatibility and registers a no-build Checkout Blocks payment method bridge. It delegates processing to the WooCommerce payment gateway and expects WooCommerce to follow the returned offsite redirect URL.</p>


Hilt Pay for WooCommerce

Accept USDC on Solana through hosted Hilt checkout for WooCommerce digital products, memberships, gated downloads, and paid community access.

Invizo

<p>Invizo Cart helps you sell digital files, software products, e-books, design assets, templates, and licensed downloads from your WordPress site.</p>
<p>You can use it to create products, collect payments, generate license keys, deliver download links, manage orders, and give customers a frontend account area for their purchases.</p>
<p>The plugin is built for site owners who want a focused digital commerce workflow without turning every page into a large shop catalog. It includes product management, checkout shortcodes, customer order records, license records, tax settings, coupons, and a React-powered admin interface.</p>
<h4>Highlights</h4>
<ul>
<li>Digital product management with pricing, sale pricing, product media, file lists, and product descriptions.</li>
<li>Software license generation for paid orders.</li>
<li>Frontend shortcodes for product grids, checkout, order success pages, account dashboards, and single product displays.</li>
<li>Stripe, PayPal, and Paddle payment gateway integrations.</li>
<li>Tax rate management for country and state-level tax rules.</li>
<li>Coupon and discount management.</li>
<li>Customer and order management inside WordPress.</li>
<li>Download logging for delivered files.</li>
<li>React-powered admin screens for products, orders, customers, licenses, taxes, discounts, exports, and settings.</li>
<li>Custom database tables for digital product, order, license, tax, download, and coupon records.</li>
</ul>
<h4>Shortcodes</h4>
<p>Use these shortcodes on normal WordPress pages:</p>
<ul>
<li><code>[invizocart_products]</code> – show a frontend product grid.</li>
<li><code>[invizocart_cart]</code> – show the cart page with quantity controls and checkout link.</li>
<li><code>[invizocart_single_product]</code> – show a single digital product layout.</li>
<li><code>[invizocart_checkout]</code> – show the checkout page.</li>
<li><code>[invizocart_checkout_success]</code> – show the post-payment success page.</li>
<li><code>[invizocart_account_dashboard]</code> – show the customer account and downloads area.</li>
</ul>
<p>You can also link directly to checkout with a product query string, for example <code>/checkout/?add=123</code>.</p>
<h4>Who is this for?</h4>
<p>Invizo Cart is useful for:</p>
<ul>
<li>Developers selling licensed plugins, themes, templates, or software.</li>
<li>Designers selling UI kits, graphics, presets, or downloadable assets.</li>
<li>Creators selling e-books, guides, courses, or resource files.</li>
<li>Agencies that need a lightweight digital product checkout for client assets.</li>
<li>Site owners who want a focused digital store without a full physical-product catalog.</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to external payment services outside your site.</p>
<ul>
<li><strong>Stripe API</strong> is used to create payment intents, confirm payment status, and process webhook events.</li>
<li><strong>PayPal checkout services</strong> may be used to redirect customers to PayPal and confirm checkout status.</li>
<li><strong>Paddle checkout services</strong> may be used to redirect customers to Paddle and confirm checkout status.</li>
</ul>
<h4>What data is sent to Stripe?</h4>
<p>When Stripe checkout is used, the plugin may send the order ID, customer email address, purchase amount, product metadata, payment intent IDs, and related payment metadata needed to create and confirm payment.</p>
<p>Payment card details are handled by Stripe.</p>
<ul>
<li>Stripe Services Agreement: https://stripe.com/ssa</li>
<li>Stripe Privacy Policy: https://stripe.com/privacy</li>
</ul>
<h4>What data is sent to PayPal?</h4>
<p>When PayPal checkout is used, the plugin may send the order reference, customer/payment context, and payment amount needed to initialize and confirm checkout.</p>
<ul>
<li>PayPal Legal Agreements: https://www.paypal.com/us/legalhub/paypal/home</li>
<li>PayPal Privacy Center: https://www.paypal.com/us/privacy-center/home</li>
</ul>
<h4>What data is sent to Paddle?</h4>
<p>When Paddle checkout is used, the plugin may send the order reference, customer/payment context, and payment amount needed to initialize and confirm checkout.</p>
<ul>
<li>Paddle Terms: https://www.paddle.com/legal/terms</li>
<li>Paddle Privacy Policy: https://www.paddle.com/legal/privacy</li>
</ul>
<h3>Build and source files</h3>
<p>The plugin includes generated browser assets for performance and the human-readable source files needed to review and rebuild them.</p>
<h4>Admin app assets</h4>
<ul>
<li>Generated files: <code>assets/admin-build/index.html</code> and <code>assets/admin-build/js/app.js</code>.</li>
<li>Source directory: <code>admin-ui/src/</code>.</li>
<li>Important source files: <code>admin-ui/src/main.jsx</code>, <code>admin-ui/src/App.jsx</code>, <code>admin-ui/src/*.jsx</code>, <code>admin-ui/src/App.css</code>, and <code>admin-ui/src/index.css</code>.</li>
<li>Build files included for review: <code>admin-ui/package.json</code>, <code>admin-ui/package-lock.json</code>, <code>admin-ui/vite.config.js</code>, and <code>admin-ui/index.html</code>.</li>
<li>Rebuild command: <code>cd admin-ui && npm install && npm run build</code>.</li>
</ul>
<h4>Frontend templates</h4>
<p>Frontend shortcode and template output is generated from PHP source files, including:</p>
<ul>
<li><code>src/Shortcodes.php</code></li>
<li><code>src/PublicFacing/Template_Manager.php</code></li>
<li><code>public/templates/single-digital-product.php</code></li>
</ul>
<h4>PHP dependencies</h4>
<p>Stripe’s PHP SDK and PayPal HTTP classes are installed with Composer and prefixed with Mozart into <code>InvizoCartVendor\</code> under <code>vendor_prefixed/</code>.</p>
<p>Stripe’s own SDK contains a cURL-based HTTP client. Those cURL calls are part of the third-party Stripe library, not plugin-specific HTTP code. Plugin-specific HTTP requests should use WordPress APIs.</p>
<p>The root <code>vendor/</code> and <code>node_modules/</code> folders are not included in the release package. The reviewable React source is included, but <code>admin-ui/node_modules/</code> is not.</p>


Invizo Cart

Sell digital downloads, software licenses, and digital products with checkout pages, customer account pages, download delivery, and payment gateways.

Hilt Pay for WooCommerce vs Invizo Cart