Skip to content
Contact
Support Troubleshooting

Troubleshooting

Common issues and quick fixes.

Checkout shows HTTP 502 or checkout_creation_failed

Section titled “Checkout shows HTTP 502 or checkout_creation_failed”
Retry once from Settings > Subscription & Billing.
If it repeats, capture the timestamp and contact support.
Click Refresh Billing.
Wait 30 to 60 seconds and retry.
Webhook updates can be asynchronous.
The page may not auto-refresh immediately after checkout completion.

Restricted key save fails with mode mismatch

Section titled “Restricted key save fails with mode mismatch”

If you see a message like:

The selected mode does not match the key.
Selected mode is live, but key belongs to test mode.

Do this:

  1. Verify selected mode in Settings, Test versus Live.
  2. Verify the key prefix:
    • Test uses rk_test_...
    • Live uses rk_live_...
  3. Generate or copy the key from the same Stripe dashboard mode.
Click Refresh Status.
Re-run Connect Stripe.
Confirm you used the intended mode, test versus live.
Retry from Settings > Subscription & Billing.
Click Refresh Billing to confirm the latest provider state.
If you still see an HTTP error, capture the timestamp and contact support.
Compare active customer count to the plan limit in Settings.
Upgrade plan if active count exceeds your current tier.

Use monetizationapps.com/contact and include:

Timestamp with timezone.
Account email.
Stripe account ID if applicable.
Screenshot of the error.

Help us improve MonetizationApps

Accepting analytics cookies lets us see what's working on our site. We don't use them for ads or share your data.

See our Privacy Policy for details.