#christian_pw

1 messages · Page 1 of 1 (latest)

spring solsticeBOT
gleaming steeple
#

Hi there! Sorry for the delay

#

The request ID can be shared here. It's not sensitive on its own

brazen quartz
#

Sure, then the id is req_LFP241XnQnsnsB

gleaming steeple
#

Yikes, sorry for the delay!

#

I see some setup intent permissions have been granted to the platform on this account. Digging in a bit more

#

One other thing I noticed about this request: the card number used appears to be a test card number, but the request was made using live mode keys.

#

I see the platform is connected to this account in test mode as well. Are you able to create and confirm a Setup Intent in test mode using a test card number?

brazen quartz
#

Yeah I just put in a test number because I didn't want it to accidentally work and charge a real card. An organic request with the same result would be req_P9vHFM8yMpZT92

#

If they have connected to us in test mode I can't easily get the keys to try that out

#

This is a widespread problem for us, not just with this connected account, so I don't think it is an isolated incident

next iris
#

Hi there, jumping in for roadrunner as they had to step away. Please give me a few minutes to get caught up.

next iris
#

I'm stumped here so asking a teammate to help me out, thank you for your patience.

#

Can you share the permissions array of their stripe-app.json file?

brazen quartz
# 
"permissions": [
        {"permission": "balance_transaction_source_read", "purpose": "..."},
        {"permission": "event_read", "purpose": "..."},
        {"permission": "balance_read", "purpose": "..."},
        {"permission": "charge_write", "purpose": "..."},
        {"permission": "checkout_session_write", "purpose": "..."},
        {"permission": "connected_account_read", "purpose": "..."},
        {"permission": "coupon_write", "purpose": "..."},
        {"permission": "credit_note_write", "purpose": "..."},
        {"permission": "customer_write", "purpose": "..."},
        {"permission": "dispute_write", "purpose": "..."},
        {"permission": "invoice_write", "purpose": "..."},
        {"permission": "payment_intent_write", "purpose": "..."},
        {"permission": "payment_links_write", "purpose": "..."},
        {"permission": "payment_method_write", "purpose": "..."},
        {"permission": "plan_write", "purpose": "..."},
        {"permission": "product_write", "purpose": "..."},
        {"permission": "quote_write", "purpose": "..."},
        {"permission": "setup_intent_write", "purpose": "..."},
        {"permission": "source_write", "purpose": "..."},
        {"permission": "subscription_write", "purpose": "..."},
        {"permission": "token_write", "purpose": "..."},
        {
            "permission": "user_email_read",
            "purpose": "Allows a ProfitWell account to be created if none already exists"
        }
    ]
next iris
#

Thank you, still digging. I'll let you know as soon as I have more information.

next iris
#

Are you using Stripe Elements in your app?

brazen quartz
#

yes we are. We use a card element

next iris
#

I see, then you'll need to add the elements_write permission. Are you able to this and see if you're still the same error?

brazen quartz
#

I can't reproduce this locally because I can't simulate an app being installed onto a separate account with certain permissions, but that seems likely at least. I'll have to just submit a new version of the app with that permission and see if it fixes it.
It seems strange that the card details get sent to the API seemingly fine though, I would have expected an earlier error

next iris
#

Yeah, the team has flagged this to be included in our public document in the near future. Thank you for writing in here.

brazen quartz
#

Thanks for your help