One store, full exposure
Connect a processor to the store that holds your catalogue and you have handed them the exact document that disqualifies you.
Checkout on your domain, with your real products. For WooCommerce when processors won't underwrite what you sell, including stores on bank transfer or crypto. No redirects, invoices, or another freeze.
What your customer sees
Your order
Embedded · payment store
What a reviewer sees
Cotton tote
$64.00
Ceramic mug
$38.00
The situation
Processors classify merchants by what they sell. A clean record, low chargebacks and years of history count for very little once a reviewer opens a product page and finds a category their policy excludes. The account is frozen, the balance is held, and the store stops taking cards on a Tuesday afternoon.
Connect a processor to the store that holds your catalogue and you have handed them the exact document that disqualifies you.
Payment links keep you trading for a while, but a reviewer asking to see the shop finds nothing to review, and conversion collapses in the meantime.
Sending a buyer to another domain to pay costs you the order, and the arrangement is obvious to anyone who looks at the flow.
Take cards at checkout
Many operators start with bank transfer, wire, or crypto because cards were not available for their category. Customers still expect card fields at checkout. TandemPay adds card payment on your domain while the charge runs on a payment store your processor can underwrite.
The architecture
Your sales store keeps your brand, your catalogue and your customers. A second WooCommerce store on its own domain holds the merchant account and a plain, processor-friendly catalogue that a reviewer can browse and test-buy. TandemPay connects the two so the customer experience stays on your side and the audit surface stays on the other.
Your domain, your products, your shipping and tax rules. The payment fields are embedded from the payment store, so the URL bar never changes.
Your processor's merchant account lives there. The charge is recorded against a mapped stand-in product with a clean descriptor.
Your store receives the order with the real line items, the real customer and the real totals, ready to pick and ship.
Payment history stays where the processor expects it. Fulfilment history stays where your operation needs it. Totals reconcile across both.
Who runs this
You need a storefront a reviewer can genuinely inspect, rather than hoping nobody reads your product pages.
You are live on wires or crypto but customers want card checkout. TandemPay adds cards on your domain without putting your catalogue on the processor's merchant account.
You already run a split setup, but it pushes customers off your domain and breaks whenever a processor looks closely.
You have been frozen once, you know exactly what it costs, and you are not willing to be exposed a second time.
Commercial terms
No public price list. Tell us what you sell and your predicted volume. We will reach out with competitive fees, setup scope, and billing terms. Ongoing fees are invoiced bi-weekly on payment-store checkout volume, due within three business days, or against a prepaid float where agreed.
What you sell, estimated revenue, and your current payment situation. Any category, any business. The form helps us quote accurately.
Usually within a few business days with setup scope, ongoing fees based on your predicted volume, and how billing works.
Payment store build, plugin install, product mapping, and a test checkout before you take real orders.
Questions
No. The payment fields are embedded into your checkout page, so the URL bar shows your domain for the whole purchase. There is no redirect and no third-party checkout page.
To the payment store only. Your merchant account is attached to that domain, and it is the store a reviewer sees. Your sales store never has a processor connected to it.
Not during a routine merchant review. They review the store on the merchant account. We are deliberate about the wording here: this addresses normal review, not a determined investigation.
WordPress with WooCommerce 8 or newer on both stores, and two domains. A headless sales storefront is fine so long as checkout itself runs on WooCommerce.
We read your application and reach out by email, usually within a few business days, with setup scope, competitive fees based on your predicted volume, and billing terms. Once you agree, we get you live.
Both plugins, the payment store playbook, and email support. One production store pair per licence.