Stripe Integration : array params

Hi
The stripe resource is not interpreting array params correctly.
Let me explain with an example
default_tax_rates (in the invoices endpoint) is a param which expects an array. The following screenshot shows how I am populating it in the UI.

But with this, stripe throws an error, complaining about an "Invalid Array". And if you look at the request that was sent, it has the following snippet.

"body":"customer=cus_J66p7t6N0UEGn1&default_tax_rates=txr_1IZCF7BTm0Wy4mM2eyC38Eqq"
Stripe is expecting something of the form
"body":"customer=cus_J66p7t6N0UEGn1&default_tax_rates[0]=txr_1IZCF7BTm0Wy4mM2eyC38Eqq"

Interestingly, if you specify TWO tax rates in the UI (hardcode the other one), the request goes through perfectly.
(Cannot attach a screenshot because new users are allowed only one media item)

APOLOGIES for the multiple self-replies, could not find a way to attach multiple screenshots

Also, please ignore tax_rates vs default_tax_rates, they are from different queries, but they behave the same


This is a screenshot of having two tax rates, which works fine

This is how the ERROR case looks when expanded

This is how the NON_ERROR case looks when expanded

UPDATE:
I can make it work by using the following in the param field

[
  {0:"txr_1IZCF7BTm0Wy4mM2eyC38Eqq"}
]

This also works

{0:"txr_1IZCF7BTm0Wy4mM2eyC38Eqq"}

But, I cannot find a way to make it use the variable
For example, this does not work

[
  {"0": {{stripeTaxRateID}}}
]

or this

{0:{{stripeTaxRateID}}}

I am passing the stripeTaxRateID as additionalScope to the query

Hi! Thanks for bringing this to our attention. As we dug deeper, it does seem to be an error on our end. This has been added to the bug report, and we will update this thread when the issue has been resolved.

1 Like

Hey there! I just wanted to circle back around here on this, our engineers were able to ship a fix for this so Stripe queries should now be properly passing arrays rather than strings. Could you check to see if this works on your end now?

2 Likes

Hi,I am facing the same problem.... (create a subscription via the customers route)

UPDATE :
the POST route /customers/XXX/subscriptions does not accept "default_tax_rates".
Are you sure this route is not Deprecated ?

I used instead the /subscriptions route which is ok.