Help for owners
Customers cannot pay in my app, or payments do not show up
Short answer
A payment has three parts: the app, your server and the payment provider. Failures come from an expired or wrong key, a webhook the provider cannot deliver, a server error, or a store rule that requires its own billing for digital items. Check the provider's dashboard first, change nothing, and get the flow traced.
Does this sound like your situation?
- Customers see an error at the payment step.
- Money is taken from the card but the order or subscription is not activated.
- Payments work in testing but not for real customers.
- The payment provider's dashboard shows failed webhook deliveries.
- The app was rejected or flagged because of how it takes payment.
Why does this happen?
A key or mode is wrong
Payment providers give separate test and live keys. A live app using a test key, or a key that was replaced or expired, fails at the payment step.
The provider cannot tell your server about the payment
After a payment, the provider sends a message called a webhook to your server so the order can be marked as paid. If the server rejects the message because of a secret mismatch, money moves but your system never hears about it.
Technical detail: Stripe webhook: no signatures found matching the expected signature
The server is failing or timing out
If the server behind the app is down, overloaded or returning errors, the payment screen cannot complete.
Technical detail: AxiosError Network Error with code ERR_NETWORK in a React app
Google requires its billing for digital items
Google's payments policy says paid app downloads and in-app purchases of items such as virtual items, subscriptions, app features or content must use Google Play's billing system unless an exception applies. Payments for physical goods or services are excluded.
Confirmed by support.google.com
Apple requires in-app purchase for unlocking features
Apple's guidelines say that to unlock features or functionality in an app, such as subscriptions, in-game currencies, levels, premium content or a full version, you must use in-app purchase and not your own mechanisms.
Confirmed by developer.apple.com
What can I do about it today?
- Open your payment provider's dashboardLook at recent payments and any errors or failed webhook deliveries. Take screenshots. This shows whether the problem is the card step or your server.
- Do not change keys or webhook settings yourselfReplacing a key or secret in one place without the other can break payments completely. Wait for a person who can change both.
- List affected customersNames, times and amounts of payments that were taken but not activated. You may need to fix these orders by hand.
- Do not refund everything in a panicMatch each payment to an order first. Some payments may have worked and only the confirmation is missing.
- Check what you sellDigital content inside the app and physical goods follow different store rules. Write down which one you sell, since it decides how you may take payment.
- Put a short notice on your siteSay you know about the problem and how people can reach you to complete a purchase.
When should I bring someone in?
- Payments are taken but orders are not recorded.
- The app was rejected for how it handles payments.
- You are not sure which account or key the payment set-up uses.
How do I handle it?
- Trace one payment end to endI follow a payment from the app screen to the provider and back to your server, and find where it stops.
- Compare keys and secretsLive and test keys and webhook secrets are checked against what the server uses, without printing them anywhere.
- Repair and replayThe fault is fixed, and missed webhook events are replayed so orders catch up, after a backup of the data.
- Check the store rules for your caseIf the app sells digital items, I compare the flow with the store's billing rule and tell you what must change.
- Add a payment alertA check warns you when payments fail or webhooks are not delivered.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is the customer's money safe?
Card details are held by the payment provider, not by me. The provider's dashboard shows what was charged.
Can I use my own payment page inside the app?
It depends on what you sell. Google excludes physical goods and services from its billing requirement, and Apple's rule covers unlocking features and content. Check your case before building.
Can missed payments be recovered?
Where the provider recorded them, their events can often be replayed to your server. I check what the provider allows.
Do you need my provider password?
No. I work through invited access with limited roles, which you can remove afterwards.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Webhook signature verification failed. Err: No signatures found matching the expected signature for payload.Stripe webhook: no signatures found matching the expected signatureAxiosError {message: 'Network Error', name: 'AxiosError', code: 'ERR_NETWORK'}AxiosError Network Error with code ERR_NETWORK in a React appJsonWebTokenError: jwt malformedjsonwebtoken rejects a token: invalid signature, jwt expired or jwt malformed