dmp_error | Stripe Developers | Page 1

agile windBOT May 8, 2026, 11:01 AM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1502264217858867322

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

prime mountain May 8, 2026, 11:04 AM

#

hey there 👋 does this issue happen when your customer tries to open a Payment Link from within the Facebook app, or does this issue happen when redirecting from your site/app?

can you share any relevant screen recordings and example payment IDs to help us investigate?

twin wolf May 8, 2026, 11:14 AM

#

As far as I understand from the logs. User goes to our web. It does the whole QUIZ, then completes our checkout and after pressing "order now" the whole magic happends and it MUST redirect an client to the STRIPE PAYMENT screen. But logs do not even show any "tries" of loading. Some of them who comes not from FACEBOOK - as this gives an idea that IN-APP facebook browser blocks the "call out" of the stripe.

#

There is no payment ID or anyhthing to show because the CLIENT do not even REACH the stripe payment window

prime mountain May 8, 2026, 11:22 AM

#

Facebook's in-app browser (WebView) is known to sometimes have restrictions that interfere with Stripe integrations - it restricts cross-origin navigations and can silently block redirects to external domains like checkout.stripe.com. Since your logs show no Stripe session creation attempts from these users, the call is being blocked before it reaches Stripe

the simplest fix would be to detect the Facebook in-app browser via the User-Agent, and prompt users to open in their native browser - alternatively, you could switch your integration to use Stripe's Embedded Checkout / Elements so payment collection happens on your own domain without a redirect

twin wolf May 8, 2026, 11:43 AM

#

What could be the best fix?
I guess I can not force via fb ads to not open in in in-app browser but in their external browser?

prime mountain May 8, 2026, 11:46 AM

#

yeah if it's possible for you to force that via Facebook ads then that would work

your website could also detect when the in-app browser is used via the User-Agent, and prompt the user to open in an external browser

agile windBOT May 8, 2026, 11:59 AM

#

twin wolf May 8, 2026, 11:59 AM

#

Okayyy, added to my logs this idea, to detect which browser is the person using. Thanks

#

Then maybe this will be easier to detect the main problem

twin wolf May 8, 2026, 12:37 PM

#

Have you heard maybe some clients had some problem using RedTrack tracker with your payments? Maybe this caused them the BLOCKS or maybe the LINK is tooo long because of the URL parameters and it flags something?

zealous warren May 8, 2026, 12:51 PM

#

Hey there. I took a quick look, but I don't see any report of issues with RedTrack

#dmp_error