Cregis Payment for WooCommerce
| 开发者 | |
|---|---|
| 更新时间 | 2026年7月31日 17:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Cregis Payment for WooCommerce is an extension of the Cregis Payment Engine (https://support.cregis.com/payment-engine/introduction), allowing your WooCommerce store to accept cryptocurrency payments through the Cregis payment gateway.
Supported Cryptocurrencies
USDT, USDC, BTC, SOL, ETH, TRX, BNB
Features
- Accept cryptocurrency payments (USDT, USDC, BTC, SOL, ETH, TRX, BNB)
- Support for multiple blockchain networks
- Configurable underpayment and overpayment tolerance
- Automatic order status synchronization via webhook
- Partial payment and overpayment handling with dedicated return pages
- Debug mode for troubleshooting
- Compatible with WooCommerce Blocks
- WordPress 5.0+
- WooCommerce 3.0+
- A Cregis merchant account with Project ID and Secret Key
安装:
- Upload the
cregis-paymentfolder to/wp-content/plugins/or install via the WordPress Plugins screen - Activate the plugin through the 'Plugins' menu in WordPress
- Go to WooCommerce > Settings > Payments > Cregis Payment
- Enter your Cregis Project ID and Secret Key
- Configure underpayment/overpayment tolerance as needed
- Enable the gateway and save
常见问题:
Do I need a Cregis account?
Yes, you need to register at Cregis (https://cregis.com) and obtain your Project ID and Secret Key.
Which cryptocurrencies are supported?
USDT, USDC, BTC, SOL, ETH, TRX, BNB.
What happens if a customer pays less than the order total?
Please refer to the Cregis Payment Engine product manual (https://support.cregis.com/payment-engine/introduction) for detailed information on underpayment handling and tolerance settings.
What happens if a customer overpays?
Please refer to the Cregis Payment Engine product manual (https://support.cregis.com/payment-engine/introduction) for detailed information on overpayment handling and refund processes.
更新日志:
1.4.0
- Fixed: CSS/JS enqueue using WordPress best practices
- Fixed: XSS vulnerabilities in return page handling
- Fixed: Generic prefix naming to avoid conflicts
- Fixed: Direct file access security
- (Initial release after review fixes)
- Initial release