설명
MixPay for WordPress – The Ultimate Crypto Payment Solution for Merchants
MixPay (https://mixpay.me) is a Web3-based payment protocol that brings a secure, privacy-focused crypto payment solution to your WordPress store. Say goodbye to costly fees and complex integrations, and start accepting a wide range of cryptocurrencies with ease.
Quick Start
- Installation
- Register an account & Get your UUID – MixPay Dashboard
- Tutorial
Why Choose MixPay?
- Privacy First: No KYC required for customers, ensuring complete user privacy.
- Seamless Settlement: Instant settlements in USDT, reducing exposure to crypto market fluctuations.
- Cost-Effective: Zero integration fees, zero service fees.
- Broad Crypto Support: Accept payments from 15+ blockchains and 50+ cryptocurrencies, including BTC, ETH, DOGE, SOL, LTC, and more.
- Full Asset Control: MixPay never holds your funds—you stay in control.
- Simple Integration Options: Choose from APIs, WordPress Plugin, and Shopify Plugin to integrate with your store effortlessly.
With MixPay, give your customers a flexible and secure way to pay, while you enjoy reliable and fast settlements, zero hidden fees, and robust protection against high-risk transactions. Install the MixPay plugin today and empower your business with secure, hassle-free crypto payments!
Business cases:
Contact
- Business: bd@mixpay.me
- Customer support: customer@mixpay.me
Social
- Official: https://mixpay.me
- LinkedIn: https://www.linkedin.com/company/mixpay
- Twitter: https://twitter.com/MixPayProtocol
스크린샷
설치
Plugin installation
- Please make sure PHP BCMath installed in your server.
- Upload the mixpay-woocommerce-plugin directory to the /wp-content/plugins/directory.
- Activate the plugin through the “Plugins” menu in WordPress.
After the plugin is activated, MixPay Payment will appear in the WooCommerce>Payments section.
Plugin configuration
After you have installed the MixPay Payment plugin, the configuration steps are:
- On the WooCommerce “Settings” page, go to the “Payment Gateways” tab, then click “MixPay Payment”.
- Check “Enable MixPay Payment”.
- Register an account https://dashboard.mixpay.me and activate your account.
- Specify your Payee Uuid And Settlement Asset
- Click “Save changes” and the gateway will be active.
Callback IP security
The callback endpoint accepts MixPay’s documented source IP, 52.198.117.57. Behind Cloudflare, it also accepts that source when REMOTE_ADDR is within Cloudflare’s published IP ranges (https://www.cloudflare.com/ips/) and Cloudflare’s single CF-Connecting-IP header matches the MixPay IP. The bundled Cloudflare ranges must be checked against the official list when releasing an update.
For another reverse proxy, first make the proxy verify its own upstream and overwrite a dedicated X-MixPay-Verified-Client-IP header (discard any client-supplied value). Then configure its exact trusted CIDRs with the woocommerce_mixpay_callback_trusted_proxy_cidrs filter. Otherwise callbacks remain blocked. Never add a shared proxy IP to woocommerce_mixpay_callback_allowed_ips: that filter is only for MixPay’s actual callback IPs. Never trust an unverified X-Forwarded-For header.
Tutorial
https://help.mixpay.me/en/articles/6836912-mixpay-wordpress-plugin-deployment-tutorial
후기
기여자 & 개발자
“MixPay Crypto Payment Gateway for WooCommerce”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.
기여자
변경이력
1.1.13 – 2026-10-19
- Security: Bound payment results to the original WooCommerce order, MixPay payee, currency, and amount; invalid or mismatched results leave the order unchanged
- Security: Verified payment-code details before saving the order’s payment binding, and rejected malformed or unrelated callback order identifiers
- Security: Verified callback source IPs for direct connections, trusted Cloudflare connections, or explicitly configured reverse proxies; unverified forwarded headers are no longer accepted
- Reliability: Serialized payment creation and callbacks per order, with short throttling for repeated upstream result lookups
- Fix: Allowed failed orders to retry only after MixPay confirms the previous attempts failed, using a separate payment attempt ID
- Fix: Reused reserved attempt IDs after interrupted requests and recovered incomplete retry activation without replacing an active payment
- Fix: Prevented callbacks for older attempts from changing the current attempt; unexpected late payments on older attempts are flagged for manual review
- Fix: Kept confirming and underpaid payments on hold, including during retry recovery; successful payments still move to processing
- Fix: Loaded the configured payment title and description in Blocks checkout and removed an uninitialized-variable warning in classic checkout
- Maintenance: Aligned plugin and package version metadata to 1.1.13; no dependency upgrades
1.1.12 – 2026-03-23
- Removed legacy cron polling mechanism for payment status checks
- Added one-time cleanup to remove accumulated cron events from previous versions
- Improved callback handler with better error handling and input validation
- Made order status updates idempotent for terminal states
1.1.11 – 2025-11-21
- Improved order status mapping with WooCommerce standards
- Enhanced payment validation and error logging
- Fixed order status overwrite issues
1.1.10
- Previous stable version