Live checkout troubleshooting

How to read the live checkout monitor and distinguish normal abandonment from SDK, iframe, webhook or store-integration issues.

The Live checkout monitor helps you understand what is happening while traffic is coming in: users on product pages, users on checkout, payment attempts, completed orders and possible technical issues.

Not every checkout without an order is a bug. Customers abandon because of price, shipping, payment method availability, declined cards, closed wallets or normal hesitation. Use this page to separate normal abandonment from technical signals.

1. Quick reading

Signal	Meaning	Action
Active user on product	The customer clicked or opened the cart/store	No action
Active user on checkout	The customer reached WooshPayment checkout	Watch whether they continue to payment
Completed order	Whop/COD completed correctly	No action
Low conversion rate without technical errors	Likely commercial abandonment	Review price, shipping, trust and payment methods
Repeated technical events	Possible SDK/iframe/integration issue	Follow the checklist below

2. Technical issue vs normal abandonment

Treat as normal:

customer closes wallet or 3DS;
card is declined by the bank;
customer expects PayPal/Klarna and leaves;
user opens checkout and never fills the form;
session expires after inactivity.

Treat as technical:

Whop iframe never becomes ready;
payment not ready, iframe null/ref, or SDK submit unavailable;
init-payment or prepare-payment fails before submit;
Pay click gets stuck without sheet, iframe, visible decline or Whop payment;
Whop shows paid but WooshPayment remains pending because the webhook did not arrive.

3. Checklist when you see technical events

Open Dashboard → Orders and filter technical orders.
Check whether the session has iframe/SDK events before the Pay click.
If the payment never started, the customer can retry: there is no double-charge risk.
If Whop shows an open, incomplete or pending payment, wait or refresh status before asking the customer to retry.
If Whop shows paid but WooshPayment does not complete, ask support for a backfill with session token and Whop payment id.

4. Shopify

On Shopify, the cart redirect runs through the ScriptTag.

If checkout does not open:

Dashboard → Settings or Integrations → verify Shopify installation.
If the status is red, click Reinstall or complete OAuth again.
Open the Shopify theme and click Checkout from both normal cart and cart drawer.
If it still does not intercept, use Script tag debug.

5. WooCommerce

On WooCommerce, the cart redirect runs through the official WooshPayment Checkout plugin.

If checkout does not open:

WordPress → Plugins → verify WooshPayment Checkout is active.
WordPress → Settings → WooshPayment → check the health page.
Dashboard → Integrations → WooCommerce → verify store URL and REST keys.
Test both classic cart and block cart.
If the REST API fails, regenerate Consumer Key + Consumer Secret with Read/Write permissions.

6. When not to use hosted fallback

Hosted fallback is a technical parachute, not a second checkout to use all the time.

Do not use it when:

card is declined;
3DS or wallet is closed by the customer;
customer abandoned by choice;
a payment already exists on Whop.

It only makes sense when the payment truly did not start and the preflight confirms there is no double-charge risk.