#piercy

1 messages · Page 1 of 1 (latest)

iron oysterBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

  • piercy, 17 hours ago, 4 messages
  • piercy, 2 days ago, 25 messages
  • piercy, 2 days ago, 4 messages
tired plume
#

Hi, let me help you with this.

stuck drift
#

To note, I am using the platform accounts keys, i dont have keys for the connected account, and I am not using stripeAccount in the request options

#

main goal I am trying to do is remove the state metadata field, as you can see the POST body doesn't contain the state field, yet it remains after the call.

So 1, i am not sure why it remains, and 2, I am not sure why this is happening on the connected account and not the platform account

tired plume
#

I see, I am not sure why it's the case. I think when you update the account itself, it's kind of a gray zone, the Connected account doesn't "live" on the Platform, but on it's own, unlike any other objects, e.g. PaymentIntents.

#

But to remove the field, you should send it with an empty value, e.g. "state": ""

stuck drift
#

ah, i tried null, undefined but I didn't try blank. Let me try that and see.

#

Yep that did it, thanks!

tired plume
#

Happy to help.