WHMCS Payment Gateway
Accept card payments for WHMCS invoices with Smart Card2Crypto Hosted and receive payouts to your own USDC Polygon wallet.
Package: October 2026 release · Hosted checkout · USDC Polygon payouts
Requirements
- A supported WHMCS and PHP installation with PHP cURL enabled.
- A public HTTPS WHMCS System URL that can receive payment callbacks and access the Card2Crypto API.
- A self-custodial USDC Polygon payout wallet. Database permission is needed to create mod_card2crypto on first use; include this table in backups.
Installation
- Back up the current gateway files and WHMCS database.
- Extract card2crypto-whmcs-gateway.zip and merge the enclosed modules directory into the WHMCS root beside configuration.php. Include modules/gateways/card2crypto/lib.php and callback.php, together with the gateway and callback modules.
- Open WHMCS Payment Gateways and activate Smart Card2Crypto Hosted. Card2Crypto Custom is available for a chosen provider; existing direct provider modules can also be retained.
- Enter USDC Polygon Wallet Address. Keep Custom Domain at pay.card2crypto.org and API Domain at api.card2crypto.org unless dedicated endpoints have been configured. An empty API Domain uses the API default.
- Review Description and Fees Tolerance, then save changes. In custom mode also check Custom Provider Tag and Minimum Invoice Amount (USD).
- Pay a staging invoice and confirm it becomes Paid. Review the Gateway Log before relying on automatic service activation.
Recommendations
Use Smart Card2Crypto Hosted as the starting gateway; choose custom or direct modes only for the provider and region you intend to support.
Keep the checkout and API domain settings separate. The API domain does not inherit a custom checkout domain.
Review Fees Tolerance as an amount-acceptance threshold, not a processing fee. Keep amount detection enabled where available and choose the threshold deliberately for your workflow.
For Card2Crypto Custom, select a currently available provider identifier and review Minimum Invoice Amount (USD). Do not rely on the inherited moonpay default. Your configured invoice minimum also applies.
Preserve mod_card2crypto and existing settings in database backups and updates; test a new invoice payment after changes.
Use your own payout wallet
Use a self-custodial 0x wallet you control for USDC payouts on Polygon. Confirm the address and receiving network.
Check provider limits
Set an order or invoice amount above the selected provider’s minimum and allow for fees. Country availability, payment methods and customer verification requirements depend on the provider.
Provider minimums
Reference minimums checked on 27 October 2026. Limits, fees, payment methods and regional availability may change. The selected provider confirms the final amount and any customer verification requirements during checkout.
| Payment provider | Minimum amount |
|---|---|
| Stripe (US/EU) | $2 |
| Stix | $6 |
| Coinbase Pay | $2 |
| PayPal (USA) | $5 |
| Robinhood (USA) | $5 |
| Revolut (EU/EEA) | €6 |
| Meld (Multi) | $30 |
| Topper | $10 |
| Transak | $30 |
| Google Pay | $10 |
| Apple Pay | $10 |
| Binance Connect | $20 |
| Banxa | $11 |
| Blockchain.com | $20 |
| particle.network | $30 |
| Cash App (USA) | $2 |
| Venmo (USA) | $2 |
| Sardine.ai (USA) | $30 |
| Klarna | 125 SEK |
| iDEAL (NL) | €46 |
| UPI/IMPS | ₹1600 |
| Interac | CA$100 |
Troubleshooting
Gateway is missing
Verify files were merged into the WHMCS root, including modules/gateways/card2crypto/, then activate Smart Card2Crypto Hosted under Payment Gateways.
Invoice payment cannot start
Check the payout wallet, Custom Domain, API Domain and PHP cURL connectivity. In custom mode review the provider tag and Minimum Invoice Amount (USD).
Invoice stays unpaid
Review the Gateway Log and confirm the HTTPS System URL and payment callback are publicly reachable. Preserve the mod_card2crypto table and verify the actual payment before marking an invoice paid manually.
Support
Need help with WHMCS setup? Contact Card2Crypto support with your platform version, integration version, order or invoice reference and the error message.
Review current pricing before accepting live payments.