Title: Vaultion Payments Author: Jay Published: September 22, 2026 Last modified: September 22, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/vaultion-payments.svg) # Vaultion Payments By [Jay](https://profiles.wordpress.org/troysteele/) [Download](https://downloads.wordpress.org/plugin/vaultion-payments.1.0.0.zip) * [Details](https://wordpress.org/plugins/vaultion-payments/#description) * [Reviews](https://wordpress.org/plugins/vaultion-payments/#reviews) * [Installation](https://wordpress.org/plugins/vaultion-payments/#installation) * [Development](https://wordpress.org/plugins/vaultion-payments/#developers) [Support](https://wordpress.org/support/plugin/vaultion-payments/) ## Description Vaultion Payments connects your store to the Vaultion hosted payment service. It includes a fixed-price shortcode and WooCommerce classic and Checkout Blocks gateway. A Vaultion merchant account and reviewed store connection are required. The plugin is free software; the hosted service charges transaction fees. Direct checkout supports ETH and USDC on Base mainnet. Merchants can offer direct payment, let buyers choose, or require USDC escrow. Escrow requires at least 50 USDC. No other networks or ordinary address deposits are supported by this integration. The hosted merchant dashboard provides email-code sign-in, payment items, receiving- wallet settings and escrow policy. Existing orders keep their original terms when settings change. The plugin retrieves authenticated payment status; returning to the store or supplying a transaction hash alone never marks an order paid. Escrow funding leaves WooCommerce orders on hold. Only a verified full merchant allocation can mark the order paid. Disputed, refunded, split, late and duplicate payments need review. A finalized escrow credit still needs withdrawal through the escrow interface. The plugin does not initiate refunds, release escrow, rule disputes or withdraw funds. Escrow checkout quotes last up to 60 minutes, capped by the order session expiry, with up to one additional minute for transaction inclusion. Funding after that deadline is labelled late and stays on hold for manual review. The on-chain escrow is still active: its seven-day buyer review period runs from funding, and the seller can claim after that period under the contract rules. A store hold does not pause the contract. Contact both parties promptly, inspect the escrow deadline and agree fulfilment or a separately authorized refund; do not ask the buyer to pay again. Vaultion-assisted human arbitration is not decentralized: you are trusting Vaultion’s reviewers. The guardian can pause a ruling but never redirect funds. Review the existing escrow terms before funding. Direct payments have no escrow protection. Service operator: Vaultion Group Inc., registered in Seychelles. Support and privacy requests: service@vaultion.org. * [Merchant service](https://checkout.vaultion.org/account/login) * [Payments service terms](https://vaultion.org/payments/terms) * [Payments privacy](https://vaultion.org/payments/privacy) * [Escrow terms](https://vaultion.org/terms) ### External services and data This plugin needs the hosted Vaultion service to create checkout sessions, quote token amounts, verify blockchain receipts, reconcile orders and deliver signed status notifications. Administrators explicitly configure the service connection. No connection credentials are bundled and no third-party executable code is downloaded into WordPress. When checkout is requested, the WordPress server sends product/order references, a description, order-derived USD pricing and payment preferences to Vaultion. WooCommerce sends the order number and total, not billing names, customer emails, postal addresses or cart line items. Merchant-written product descriptions should not contain unnecessary personal information. The browser is redirected to the hosted checkout, which processes public wallet addresses, amounts, attempt and transaction references. Payment-linked escrow also records agreement, fee and settlement references. Cloudflare supplies hosted Workers, D1 storage, request protection, operational logs and merchant sign-in email. Wallet and RPC providers process blockchain requests. Blockchain records are public and permanent. Escrow agreement metadata and evidence can be published to IPFS through Pinata and reviewed through the escrow process; do not publish confidential material. Kraken public Trades supplies ETH/USD and USDC/USD prices without receiving account, order or wallet identifiers in price requests. Stale prices are refused and no fixed USDC dollar peg is assumed. The separate escrow form asks for party names, contact emails and agreement details. These are entered in that form, not read from WooCommerce billing. The existing escrow notification service stores pending invitations, subscriptions and delivery state in Cloudflare KV and delivers through Resend. Invited parties confirm their own subscriptions before ongoing updates are enabled. Direct-payment fees are 0.75%, deducted from the merchant amount by default or added for the buyer when configured. Escrow uses its existing fee instead: the buyer pays 4% below 500 USDC, 3% from 500 to below 5,000 USDC, or 2% from 5,000 USDC, separately before funding. Network gas is additional. Exact amounts and expiry are shown before wallet authorization. The plugin cannot reverse a separately paid escrow creation fee if creation is abandoned. WordPress stores connection options and Vaultion session, network, amount, transaction and status metadata with orders. Checkout saves recovery hints in local storage. Payment-linked escrow also stores fee/creation transaction hints on vaultion.org. Merchant sign-in uses ten-minute challenge and eight-hour session cookies. Plugin removal does not erase orders, connection settings or hosted records. Hosted payment/ account records have no general automatic deletion schedule; verified access, correction and deletion requests go to service@vaultion.org. Blockchain and replicated IPFS records cannot be erased by Vaultion. See the linked payments privacy notice for retention and service-provider details. ## Installation 1. Install and activate Vaultion Payments. WooCommerce is required for the gateway; the shortcode works without it. 2. Sign in to the merchant service and contact service@vaultion.org to review the store domain, receiving wallet and callback address. Email verification alone does not approve a merchant connection. 3. Open Settings > Vaultion connection as a WordPress administrator. Verify and save the assigned merchant API key and optional signed-callback secret. The production service is fixed to https://checkout.vaultion.org. 4. For WooCommerce, use USD store currency and enable Vaultion under WooCommerce > Settings > Payments. For a fixed-price button, create a merchant payment item and use [vaultion_pay product=”your-item”]. 5. Review the suggested disclosure in Settings > Privacy > Policy Guide and publish your store’s own policy. Verify a complete order and recovery flow before accepting customer orders. Keep credentials on the server, never in page content or browser JavaScript. Server constants VAULTION_PAYMENTS_API_KEY and VAULTION_PAYMENTS_WEBHOOK_SECRET take precedence over saved options. Saved credentials are non-autoloaded and are not displayed. Separate verify-and-activate forms support prepared replacement API keys and callback secrets for the same merchant. Existing orders and callback overlap are preserved. The integration has been tested with WordPress 7.1, WooCommerce 11.1.0 and PHP 8.3.33, including HPOS and Checkout Blocks. This is not exhaustive coverage of every version combination. #### Existing test installations Explicit VAULTION_STAGING_ORIGIN and legacy VAULTION_TEST_* configuration remain restricted to controlled staging or local WordPress environments. Base Sepolia test credentials cannot silently become mainnet credentials. Orders and credentials remain bound to their original service and network. Existing vaultion-local-testnet installations use the separate same-folder compatibility ZIP supplied by the operator. Do not activate the old test plugin alongside the public plugin. Review any migration of an existing store rather than switching its origin or deleting its orders. ## FAQ ### Is this a wallet or exchange? No. Buyers authorize transactions in their own wallets. Vaultion does not collect wallet private keys or recovery phrases. Direct payments split the merchant and service amounts in one transaction; escrow funds are held by the existing escrow contract. ### What happens if checkout closes? Return to the existing checkout or order before paying again. The service rechecks submitted evidence and current status. Signed callbacks also trigger authenticated reconciliation; neither a callback payload alone nor a redirect completes an order. ### Can a staging order become a real payment? No. The plugin checks the service origin and network recorded with the order. A mainnet connection refuses to reconcile an old test order as a real payment. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Vaultion Payments” is open source software. The following people have contributed to this plugin. Contributors * [ Jay ](https://profiles.wordpress.org/troysteele/) [Translate “Vaultion Payments” into your language.](https://translate.wordpress.org/projects/wp-plugins/vaultion-payments) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/vaultion-payments/), check out the [SVN repository](https://plugins.svn.wordpress.org/vaultion-payments/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/vaultion-payments/) by [RSS](https://plugins.trac.wordpress.org/log/vaultion-payments/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 Add Base mainnet ETH/USDC checkout, optional USDC escrow, explicit network-bound order recovery, production connection settings and service/privacy disclosures. Preserve controlled staging connection and same-folder upgrade support. ## Meta * Version **1.0.0** * Last updated **19 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.9 or higher ** * Tested up to **7.1.2** * PHP version ** 8.1 or higher ** * Tags * [cryptocurrency](https://wordpress.org/plugins/tags/cryptocurrency/)[escrow](https://wordpress.org/plugins/tags/escrow/) [payments](https://wordpress.org/plugins/tags/payments/)[woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/vaultion-payments/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/vaultion-payments/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/vaultion-payments/reviews/) ## Contributors * [ Jay ](https://profiles.wordpress.org/troysteele/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/vaultion-payments/)