How all seven methods compare
This is a planning comparison, not a guarantee of suitability.
| Integration route | Fit | Status | Reason | Limitation |
|---|
First five setup steps
Before accepting payments
How to choose a crypto payment integration
Start from your sales flow, not API complexity
Crypto payment integration should solve a real business workflow. A freelancer sending invoices, a WooCommerce store, a SaaS product and a platform funding customer accounts have different needs. Compare how each method handles customer checkout, order matching, payment status and support, not merely the number of APIs.
How to interpret the result
The fit score is a relative planning signal based on twelve answers. It is not a probability, a safety rating or verification that a plugin supports your exact software version. Review the highest-ranked option and the alternatives, especially when scores are close.
How all seven methods compare
This is a planning comparison, not a guarantee of suitability.
Payment Link
Send a hosted payment request without code Fits manually shared sales and fast pilots without engineering.
Manual reconciliation becomes difficult at high volume.
Donation Service
Collect contributions with a reusable donation link or button Designed for campaigns, communities and open-ended contributions.
Not a standard checkout or order-fulfillment flow.
Pre-built Plugin
Connect a supported store using an OxaPay extension Uses existing platform orders and checkout, reducing custom work.
Verify exact platform version and extension compatibility.
Merchant Invoice API
Create an OxaPay-hosted invoice for every order Gives custom systems order-level references, statuses and hosted payment pages.
Secure backend code and verified webhooks are necessary.
White Label API
Build a branded payment experience using White Label API Fits embedded payment journeys where interface control matters.
Adds significant frontend, backend and exception-handling work.
Static Address API
Assign a reusable deposit address to each account Fits account top-ups and repeat deposits better than order-specific checkout.
Requires address-to-customer reconciliation and wrong-network policies.
Custom API Integration
Coordinate several OxaPay payment methods in one system Suitable for complex platforms with multiple flows and engineering resources.
The highest engineering and monitoring overhead of the options.
What to verify before launching
Confirm the latest OxaPay documentation, supported plugins and fees. Keep API credentials server-side, authenticate webhooks, process duplicate notifications idempotently and reconcile payments with orders before irreversible fulfillment. Test in staging first.
Frequently asked questions
Does a high score guarantee that a method works?
No. A high score only ranks the configured scenario against other routes; it does not verify actual platform availability or legal and technical readiness.
Do recurring payments need static addresses?
No. Recurring schedules, renewals and failed payments belong to your application. Static Address is mainly useful for deposits and repeated account funding.
Can I use multiple methods?
Yes. Complex platforms may use different OxaPay methods for different flows, but must coordinate status, reconciliation and customer records.