Payments that do not go through

1. Locate the existing attempt.

   Open the payment provider dashboard in the environment used by the app. Find the attempt by time and the test customer. Record its status and id. With Stripe, check whether you are viewing live activity or test activity before concluding that a payment is missing.

2. Check where checkout stops.

   For a new test attempt, open Chrome Inspect, then Network. Click the app’s checkout button once. Read the response from your app’s checkout-creation request. If it fails before opening the provider, record that response rather than blaming the customer’s card.

3. Inspect delivery to the app.

   If the provider records success but access is missing, open its event or webhook delivery view. For Stripe, select the configured destination and inspect the relevant event’s delivery attempt, HTTP status and response. Note whether the destination is your current production endpoint.

4. Check the purchased result.

   Sign back into the test customer’s account and reload the purchased feature. Compare the provider’s payment id with the order or entitlement stored by your app. Do not create another charge just to refresh a missing entitlement.

WORKSThe provider confirms payment and the correct account receives exactly the purchased access.

BROKENCheckout fails or a confirmed payment has no matching fulfillment.

Ranked in the order to investigate, not by claimed frequency.

1. Checkout creation fails in your backend.

   Use the failed response to correct the server’s provider configuration, product reference or validation. Keep secret credentials on the server and repeat only in test mode until checkout opens.

2. The payment is incomplete or in another environment.

   Follow the provider’s recorded status and compare account and mode. Test activity cannot prove live payment processing. Never mark an order paid merely because a browser reached a success URL.

3. The payment succeeds but fulfillment fails.

   Repair the verified server-to-server event handler and reconcile the existing paid order. Ensure processing an event again cannot grant the same purchase twice.

• Some payment methods complete later. A return from checkout may happen before the provider reports a final successful payment.
• A failed webhook response does not prove the payment failed. Keep the payment record and the delivery attempt as separate evidence.

When to stop and hand it over

Hand over immediately for an unexplained real charge, repeated charges or mismatched customer access. Provide the payment and event ids through an appropriate private channel. Do not send card details or secret keys in the contact form.