Application_fee_amount is only working with Chrome

[toomas.partin]

Hi everyone,

I’m facing an issue with Stripe’s application_fee_amount when processing payments in my Bubble app. The fee is applied correctly when using a PC browser like chrome, but when I try the same process on a mobile browser the fee disappears, and the connected account receives the full amount. (Also this issue is with PC Edge, so works only in chrome)

What I’ve Checked:

I use the same API setup for both PC and mobile (no changes in workflows).
Stripe logs show that application_fee_amount is missing only on mobile transactions.
Tested on different mobile browsers, same issue.
No mobile-specific payment method like Apple Pay or Google Pay is involved—just a normal Stripe checkout.
The Stripe API version is the same for all requests.

Questions:

Has anyone else experienced this issue?

When doing mobile payment, this line just goes away, everything else is same

Any help would be greatly appreciated! Thanks in advance.

[toomas.partin]

No privacy issues as well

[moon]

try fetching the json in the backend and the push it to the frontend via the Database that usually works

[toomas.partin]

Hi, Moon!

Thanks for reply, Uhhh, it went a few steps too complicated - is there some tutorial or sth? I’m relatively newbie on Bubble.

[toomas.partin]

Getting interesting, i did Edge vs Chrome testing and in Chrome it finds “current” user, but in edge, it doesnt find any info.

API, version, links all are the same.

Pictures, one is in Chrome where it finds current user, second is in Edge, and 0 info about user and thats why it fails, it will not take fee %…

Any idea how to fix it?

[moon]

Okay that’s really weird.

First make sure to log out of the current account when switching browsers, that can potentially cause issues cause your app thinks these two browsers are two separate devices.

activate account/lastname showing up on one browser and not on the other points out to privacy issues maybe some kind of issue how maybe some sort of session token is passed or issued and this could then point to privacy rule issues what makes one browser to display certain values and one not

what are your privacy rules for User? How are you getting the subscription plans site fee? Is this a (Data from API Connector) in your Database?