WooCommerce
Add cryptocurrency as a payment option for a WordPress store and keep order status tied to the corresponding crypto invoice.
Beta integrationCrypto Payment Integrations
Connect Paxlivo to the commerce systems you already use.
Use a ready-made commerce workflow where it fits, or connect directly through APIs and webhooks when your application needs more control over invoice creation and fulfillment.
WHMCS
Connect hosting, SaaS or service invoices to crypto checkout and use payment events as part of the normal service-provisioning workflow.
Beta integrationREST API
Create invoices, retrieve payment status and connect custom applications to the merchant payment engine using scoped credentials.
Developer overviewWebhooks
Receive server-to-server payment notifications so your application can react to invoice and transaction state changes.
Webhook guidancePayment Links
Share a hosted payment request directly when you need an invoice URL rather than a shopping cart integration.
Merchant toolQR Payments
Display payment addresses and invoice amounts in a format that is convenient for customers using mobile crypto wallets.
Hosted checkoutWooCommerce workflow
Add crypto without replacing the rest of your store.
A WooCommerce merchant can keep their existing product catalog, taxes, shipping and order management while adding crypto as an additional checkout method. The payment integration creates a corresponding crypto invoice and uses its state to update the ecommerce order.
Before going live, merchants should test successful payments as well as expired or incomplete invoices so staff understand how each status appears inside the store.
WHMCS workflow
Useful for hosting, SaaS and service billing.
WHMCS merchants can use crypto payment status alongside their normal invoice and provisioning process. This can reduce manual checking when a customer pays a hosting or service invoice in BTC, LTC or a supported stablecoin network.
The billing system should only mark an invoice paid when the configured payment state is appropriate for the merchant's risk policy.
API & webhook integrations
Build Paxlivo into your own application.
For custom platforms, the merchant application can create an invoice programmatically, redirect the customer to checkout and receive payment events server-to-server. This is the cleanest route when your business already has its own order database or account system.
Use scoped credentials
Give each integration only the permissions it needs, store API secrets outside public source code and rotate credentials if exposure is suspected.
Verify events
Treat webhook signatures and invoice identifiers as part of the security boundary. Do not trust a browser redirect alone as proof of payment.
Handle retries safely
Design fulfillment logic so receiving the same event more than once does not create duplicate orders, credits or service actions.
Before going live
Test the complete order lifecycle, not only the happy path.
A production integration should be tested from invoice creation through payment detection, confirmation and final merchant action. It should also have a defined response to expiration, partial payment, customer cancellation and temporary connectivity problems.
01Create a low-value test orderVerify amount and checkout URL
02Send the exact supported asset/networkConfirm detection and status changes
03Verify webhook processingCheck logs and signature validation
04Confirm fulfillment happens onceTest idempotent order handling
Custom integration
Talk to us Building something that is not listed?
Tell us about your stack and the payment flow you need. During beta we can use that feedback to improve documentation and merchant onboarding.