WooCommerce, WooPayments and the merchant account are different.
WooCommerce is the storefront software. WooPayments is a payment service with its own restrictions: its published policy lists peptides, research chemicals and supplements with unsubstantiated claims among excluded activities. A working WooCommerce store does not establish eligibility for WooPayments or another provider.
Ask the proposed processing partner to confirm your complete catalog, entity and markets first. Then identify the specific gateway and merchant-account configuration. A gateway brand or plugin listing by itself is not approval to process a product.
Ask for the exact extension and checkout compatibility.
List your WooCommerce version, theme, checkout type and any plugins that modify checkout or order handling. Ask who maintains the proposed extension, which checkout it supports and how compatibility is checked when the store updates.
Define the functions you need: immediate or delayed capture, full and partial refunds, saved cards, customer payment updates and the currencies actually charged and settled. Ask whether each action works inside WooCommerce or requires a separate dashboard. A purchase demo should show the real customer journey, including redirects if used.
Treat subscriptions as a separate acceptance test.
WooCommerce’s gateway comparison distinguishes manual and automatic renewals and shows feature differences between extensions. Confirm support for the exact functions you use, including changing payment methods, adjusting renewal dates and changing plan amounts.
Before moving existing subscribers, ask whether saved payment tokens can be migrated through a supported process. Identify any customer action required and schedule the change around renewals. Do not export raw card details or assume installing the new plugin moves stored payment credentials.
Test orders and settlements before the cutover.
Use the provider’s supported test setup to follow a successful purchase, a decline, an abandoned payment, a refund and an asynchronous payment update. Confirm that repeated notifications do not create duplicate fulfillment and that staff can investigate a payment against the correct order.
Keep access to the former account for earlier refunds and disputes. After activation, reconcile the first live orders with the gateway and payout reports. A paid order status and money arriving in the bank are different checkpoints. Alderwell provides guidance and referrals; the processing partner operates the account and sets its terms.
Your preparation checklist
- Written provider acceptance for the full catalog and entity
- Exact gateway extension, maintainer and checkout compatibility
- Capture, refund, saved-card and currency requirements
- Subscription functions and a documented migration path
- Staging tests, cutover timing and first-settlement reconciliation
Common questions
Do I need to move away from WooCommerce for high-risk processing?
No. Stay on WooCommerce. We connect a gateway that fits the catalog. The partner approves the products. You do not rebuild the shop to get card payments.
Can I use a merchant account I already have?
Ask that account provider which ecommerce gateways and configurations it supports. An existing in-person account does not automatically establish the intended online arrangement.
Why does a plugin work in testing but my account is not approved?
A test connection demonstrates software behavior. Merchant approval is a separate review of the business and live processing configuration.
Can I keep manual bank-transfer payments alongside cards?
Plan how customers choose a method and how staff confirm it. Keep unpaid transfer orders distinct from confirmed card payments, and prevent duplicate payment when a customer changes methods.