Services Plugins FAQs

Stripe Marketplace Express bug - hardcoded acct id?

Plugins
#1

Hi guys,
I posted this across on the bubble forum too, but thought it may get handled a little quicker here: 💳 Stripe Marketplace Express Checkout + SCA 3D Secure - New Plugin from Zeroqode - #61 by mattb - Showcase - Bubble Forum

Since updating to the latest version (1.10.0), I’m getting an account access issue. The account (acct_…) shown in the screenshot below does not appear as any of the accounts I’ve added to my Stripe dashboard.

I’ve checked Stripe Connect API keys and access - nothng has been revoked. This leads me to the conclusion that the acct_1Fz… id is being pulled directly from the plugin somewhere, rather from the bank account token creation. Is there a chance you may have a leftover hard-coded acct id?

Capture

#2

Hello @matt,

Unfortunately, yes the acct id is hardcoded in the plugin. We will fix that issue and update the plugin. I will let you know when the updated version will be published.

Meantime you can change the value in the Account ID field and make it Dynamic. Here you can find it:

image
image708×215 14.2 KB

Best Regards,
Alex

1 Like
#3

Hi Alex, I’m not really sure that’s an option in my current circumstance. I have the seller and customer id’s saved to a dataset (seller = user, customer = company), and the cards and bank accounts are linked to those datasets respectively (cards to customers, bank accounts to sellers).

If I start playing around with the API in that way it’s going to get tricky. The reason behind this is because I’m currently using a reusable element in a repeating group. The repeating group is taking the RG’s data and then displaying in a popup (inside the reusable element).

#4

Could you please share some screenshots and maybe some additional details, just to make everything clear? I am afraid I don’t get why in your case is not possible to use dynamic data in the field Account ID.

Looking forward to hearing from you.

Best Regards,
Alex

#5

Hi Alex,
As I’m still building the app it may be more prudent to wait until that bug is fixed (rather than changing things now, and having to change them to a more streamlined approach later). Do you have an ETA when that might happen?

#6

Ok, sure!

I cannot provide you exact timings but our team will do its best to provide the update ASAP.

#7

Hello @matt,

The issue with the hardcoded IDs was solved. Please update the plugin to the latest version to have access to the latest fixes.

Best Regards,
Alex