Laqira Payments for WooCommerce
| 开发者 | LaqiraProtocol |
|---|---|
| 更新时间 | 2026年6月17日 15:32 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0+ |
| 版权网址: | 版权信息 |
详情介绍:
Laqira Payments is a secure, efficient, and Fully Decentralized Asset-Agnostic Multi-Network Payment Gateway for WooCommerce, enabling businesses to accept digital payments seamlessly with advanced blockchain technology. It offers enhanced flexibility and security, transparent financial statements, and in-app wallet features for users.
Key Features:
- Fully Decentralized: Uses blockchain for secure, anonymous transactions without third-party oversight.
- Asset-Agnostic: Allows payments in any origin asset and provides stablecoin in destination to providers, minimizing risk and maximizing stability.
- Multi-Network Support: Supports diverse network payments, with user options dependent on provider acceptance and configuration.
- Chainlink Price Feeds: Automatic exact amount detection and stablecoin depeg detection for vendor settlement.
- Security: Utilizes HttpOnly cookies for JWT authorization and employs robust input hardening and sanitization throughout.
- Provider Registration: Register on LaqiraPayments and receive a dedicated smart contract address (API key) where transparent financial records are carved.
- Plugin Setup: Install the LaqiraPayments plugin, input your API key, and configure settings.
- Customer Payment: Customers select the LaqiraPayments method, choose a network and cryptocurrency, connect their wallet, and complete the transaction.
安装:
Step 1 - Prerequisite (WooCommerce):
Make sure WooCommerce is installed, updated to the latest version, and active on your WordPress site before you begin.
Step 2 - Install & activate the plugin:
Go to Plugins > Add New > Upload Plugin, upload the Laqira Payments .zip file, click Install Now, then click Activate.
Step 3 - Register on LaqiraPay:
Go to
https://laqirapay.com, connect your wallet, and create your provider account. (See screenshot 1)
Step 4 - Enable your networks:
On LaqiraPay, enable the blockchain networks you want your customers to be able to pay with (for example BNB Smart Chain, Ethereum, Polygon). Only enabled networks will be available at checkout. (See screenshot 2)
Step 5 - Copy your API Key:
Copy the API Key generated for your account on LaqiraPay. (See screenshot 3)
Step 6 - Configure the plugin settings:
Navigate to WooCommerce > Settings > Payments, open Laqira Payments, and fill in the fields exactly as below:
* API Key: paste the API Key you copied from LaqiraPay in Step 5.
* Laqira RPC Url: https://bsc-dataseed.binance.org
* Laqira Contract Address: 0x52ab753dd301e4fb5bf00d9bfeb55e356a44064d
* WalletConnect Project ID: 57c157d7249ecf6e78dc45ede079eb07
Then click Save. Below the API Key field the plugin shows which networks are active for your configuration (e.g. "BNB Smart Chain is Active"). (See screenshot 4)
Step 7 - Clear the Web3 cache:
Click the Clear Web3 Cache button so the plugin reloads your latest network and configuration data.
Step 8 - Enable the payment method:
Under WooCommerce > Settings > Payments, toggle Laqira Payments to Enabled. Your store is now ready to accept crypto payments. (See screenshot 5)
Minimum Requirements:
- PHP version: 8.1 or higher (as per validation report and plugin file)
- WordPress version: 6.3 or higher (as per validation report and plugin file)
- WooCommerce version: 8.2 or higher (as per validation report and plugin file)
屏幕截图:
常见问题:
Do I need SSL for my store to use LaqiraPayments?
Yes, using an SSL certificate (HTTPS) is strongly recommended for all e-commerce sites to ensure the security and integrity of payment transactions.
How do I get my API Key?
Your unique Laqira Pay Provider API Key (which acts as your provider address) can be obtained by connecting your wallet and registering as a Provider on the LaqiraPayments website (https://laqirapay.com).
What happens if a transaction fails?
LaqiraPayments includes robust Order Recovery features that help track and manage failed or pending transactions, including a dedicated section on the WooCommerce Order Editing page to repair orders by TXHash.
更新日志:
0.9.38
- Security - Escaped the order recovery shortcode output before returning it to WordPress.
- Security - Replaced manual AJAX nonce verification in checkout and transaction recovery handlers with
check_ajax_referer()calls that WordPress.org review tools can detect. - Security - Removed the nonce-less persistent tab option update from the Order Recovery admin redirect and now derive the active settings tab from the validated request state.
- Fixed - Replaced invalid Terms/Privacy URLs and expanded the external services disclosure for Laqira services, Consensys/Infura RPC endpoints, and remote CID/IPFS metadata requests.
- Fixed - Deferred Web3 cache cron scheduling until
initto avoid early WooCommerce translation loading notices during first activation. - Fixed - Updated test bootstrap coverage so the PHPUnit suite loads plugin files after defining
ABSPATH.
- Fixed - Migrated public WooCommerce payment identifiers, checkout block handles, AJAX actions, and custom helper functions to plugin-specific Laqira Payments names while preserving legacy settings compatibility.
- Fixed - Removed remote Google Fonts references from bundled and generated assets used by the release package.
- Security - Re-audited request input handling, nonce verification, and WooCommerce admin capability checks around AJAX, settings, and order metabox flows.
- Security - Removed the legacy whole-request fallback from the shared request input helper so only explicitly expected request keys are read.
- Fixed - Replaced hardcoded plugin path detection with WordPress-safe plugin APIs and plugin constants.
- Fixed - Hardened the GitHub Actions release build so production Composer dependencies are rebuilt with
--no-dev, generated assets are sanitized, and the final package is validated before zipping. - Fixed - Corrected distribution ignore rules so Composer runtime source files inside
vendorare preserved, preventing activation failures on clean WordPress installs. - Fixed - Excluded nested dependency lock files such as
vendor/**/package-lock.jsonfrom the release package. - Fixed - Restored WooCommerce order-pay rendering compatibility for retrying failed or interrupted payments in classic and block checkout contexts.
- Fixed - Split admin order recovery metabox behavior so recorded
tx_hashorders use the recovery status metabox while orders without a transaction hash use the failed transaction recovery form. - Changed - Refined WordPress.org documentation, explicit external service domain disclosures, screenshots text, and release strategy notes.
- Fixed - Prepared the WordPress.org release candidate after clean-install activation and transaction smoke testing.
- Fixed - Fix some issues (Remove plugin update class , readme.txt, vendor folder)
- Fixed - Updated the plugin distribution process so generated release zip files exclude development-only files and unnecessary vendor artifacts.
- Fixed - Expanded the external services documentation in the readme to clearly describe wallet connectivity, RPC, remote JSON metadata, and explorer links.
- Fixed - Replaced the remaining non-prefixed constants and the legacy recovery shortcode with plugin-specific names to improve WordPress.org compliance.
- Fixed - Added direct-access guards for the remaining PHP entry points, including generated asset PHP files.
- Security - Hardened AJAX/admin request handling with stricter unslash/validation flows and defensive order checks in transaction confirmation paths.
- Security - Improved SQL safety in legacy transaction persistence by using prepared SQL markers for table identifiers and IDs, and documenting unavoidable direct queries.
- Fixed - Replaced discouraged functions (
strip_tags,parse_url) with WordPress-safe alternatives and added missing translators comments for replacement strings. - Fixed - Reworked global function naming to plugin-prefixed names and synchronized bootstrap calls to match the new function names.
- Fixed - Added direct-access guards for remaining PHP entry files and aligned uninstall SQL handling with safer
$wpdb->prepare()usage. - Chore - Updated
readme.txttags.
- Fixed: Fix some language strings.
- Fixed: Optimize webpack bundle.
- Changed - Updated plugin display name to Laqira Payments for WooCommerce.
- Changed - Updated plugin slug to laqira-payments.
- Fixed: Restored the settings view by renaming the admin templates to the
laqira-payments-…filenames expected byAdminController. - Fixed: Deferred the activation log until
initto avoid_load_textdomain_just_in_timewarnings caused by loading translations too early. - Fixed: Prevented SQL syntax errors in the legacy AJAX confirmations by inlining the sanitized table name before preparing
SELECT COUNT(1)queries.
- Security: Added nonce enforcement for order recovery confirmations.
- Security: Restricted admin-only confirmation to users with WooCommerce management capabilities.
- Fixed: Guarded template entry points against direct access.
- Fixed: Switched the gateway icon to a bundled local asset.
- Fixed: Added missing
rel="noopener noreferrer"to external links opened in a new tab. - Fixed: Updated web3p/web3.php to 0.3.2.
- Fixed: Updated bundled Semantic UI assets to 2.5.0.
- Changed: Updated plugin display name to Laqira Payments for WooCommerce.
- Fixed: Removed dynamic translation usage for non-literal strings to comply with WordPress i18n standards.
- Fixed: Removed custom plugin update mechanism to meet WordPress.org repository guidelines.
- Fixed: Improved settings registration by adding sanitize callbacks for all registered options.
- Fixed: Ensured support for array and nested option values during sanitization.
- Fixed: Removed discouraged manual textdomain loading when using WordPress.org language packs.
- Fixed: General code cleanup and compliance improvements for WordPress.org review.
- Added support for additional blockchain networks: zkSync
- Added support for additional blockchain networks: Optimism
- Security - Prevent duplicate on-chain payments by locking orders during processing and rejecting additional transaction hashes once recorded.
- Fixed - Disable repeated payment submissions in the checkout modal while a payment request is processing.
- Changed - change plugin slug
- Security - rename and refactor the admin transactions list table to sanitize query parameters and replace debug output with escaped JSON.
- Changed - fix perg_replace #3 parameters to ensure not null (php 8.1+)
- Changed - update test environments
- Security - Reuse the shared
laqira_payments_filter_inputhelper for exchange-rate submissions so superglobals are unslashed before sanitization. - Security - Normalize request methods, option keys, and nonces prior to validation to eliminate PHP 8.1 deprecation warnings surfaced in QA.
- Security - Refactored the admin transactions list table to sanitize list-query parameters and remove debug output.
- Changed - Renamed admin/bootstrap/helpers to match WordPress
class-*.phpconventions and updated Composer autoloading. - Security - Hardened admin settings sanitization with enforced nonce/capability checks and consistent unslash/sanitize flows.
- Fixed - Added PHPCS-compliant documentation and normalized asset loading throughout the admin bootstrap and JWT utilities.
- Fixed - fix some warning:
- remove FILTER_SANITIZE_STRING constant (deprecated since PHP 8.1)
- fix webpack.js to solve Potential Leaked Secrets
- Added - Add README.TXT file based on woocommerce and wordpress structure
- Changed - Aligned exchange rate view config formatting and updated persistence tests.
- Changed - Refined admin settings sections to include dedicated exchange rate and order recovery tabs.
- Changed - Refactored order recovery admin settings and cleaned up the settings view.
- Security - Fixed PHPCS & semgrep issues.
- Security - Fixed PHPCS & semgrep issues.
- Fixed - Fixed INPUT_REQUEST.
- Enhanced - Ran PHPCS tests.
- Security - Hardened input handling and escaping for LaqiraPayments across AJAX controllers, logging, and helper utilities.
- Fixed - Improved CLI input handling and sanitization fallbacks.
- Changed - Allowed scripts in confirmation markup.
- Fixed - Guarded blockchain integrations until required settings (API key, contract address, RPC URL) are saved.
- Security - Locked down rendered templates and sanitized admin/front-end output.
- Security - Hardened transaction confirmation flows and replaced raw SQL with prepared statements.
- Security - Fortified logging and request sanitization.
- Security - Improved blockchain error handling and documentation hygiene.
- Fixed - Handled hex transaction statuses for PHP 8 compatibility.
- Fixed - Guarded WooCommerce cart reset when session is unavailable.
- Fixed - Removed leading newline before PHP tag in
LegacyAjax.phpto avoid header warnings. - Fixed - Handled null CID values in blockchain lookups.
- Fixed - Localized settings script data.
- Changed - Raised the minimum supported PHP version to 8.1 and updated project documentation.
- Fixed - Prevented plugin bootstrap from triggering activation and handled missing composer autoloaders gracefully.
- Security - Enforced secure cookies, default SSL verification and sanitized transaction metadata rendering in admin area.
- Fixed - Handled unavailable checkout data, stopped repeated cart refresh loops and restored Place order button behaviour.
- Fixed - Normalized stored transaction hashes, guarded against missing ABI data and ensured confirmations persist to the database.
- Fixed - Added multi structure permalink support.
- Fixed - Fetched Web3 data automatically and cleared its cache when any plugin settings option updated.
- Changed - Changed plugin name to LaqiraPayments from WooLaqiraPayments.