Hi,
I am needing to attach a Stripe payment method to a customer and hitting an error when using the parameter ’ invoice_settings.default_payment_method’ under the ‘Advanced Options’ section.
The error message is “Received unknown parameter: invoice_settings.default_payment_method”. This is a valid and accurate parameter as stated in Stripe API documents.
Both the customer ID and payment method ID are being retrieved within the same workflow in prior steps so no issue there.
Regards.
Hello @silisolutionist,
May I ask if you’re using Pipedream built-in Stripe action or a code step? Could you share a screenshot of your action facing the error?
It’s a built-in action.
This is a screenshot of the action:
And a screenshot of the error:
Hi @silisolutionist,
Could you check Stripe document on the Advanced Options props for a list of supported options? I suspect that the option you passed in is not supported
I’d appreciate it if you replied with a solution instead of asking to “check” things which anyone in their right mind would have done so before posting such a thread. All you have done so far is ask for screenshots - did you check it yourself before posting such a reply?
Are you part of Pipedream’s support team? I am looking for a response from Pipedream about this as this forum seems to be the only method of reporting a technical issue about their service.
@silisolutionist I’m a founder and engineer here. Leo is clearly trying to help, and is an amazing member of our team. He doesn’t deserve such a rude response.
The root invoice_settings param is an object, so when Stripe refers to invoice_settings. default_payment_method, try passing something like this in the Advanced Options field:
{{
{
invoice_settings: {
default_payment_method: steps.retrieve_payment_intent.$return_value.... (your specific value)
}
}
}}
That will correctly evaluate to the object Stripe expects. You can see we spread the value of the data passed in that field here.
Thanks,
Dylan
Considering he is a member of Pipedream’s team, we are shocked at the level of support that was provided by @vunguyenhung.
Instead of apologising about a member of your team providing support on a public forum without first doing due diligence, we have instead received a derogatory remark for highlighting the obvious - the poor level of support that is being offered on a forum that is supposed to be about helping your customers who are facing technical issues with your service.
I’m not sorry about my observations or my comments. What I am sorry about is that we considered using your service. Based on this experience, we have decided not to proceed with putting our payment processes in the hands of Pipedream.
Leo asked:
Could you check Stripe document on the Advanced Options props for a list of supported options?
That’s a valid question given the error. We deal with users from across the technical spectrum. When you said:
I’d appreciate it if you replied with a solution instead of asking to “check” things which anyone in their right mind would have done so before posting such a thread.
This might be obvious for you, but not everyone does due diligence before reaching out on our support channels. Asking these questions is just part of our triage process. In response, most of our users would gladly share a link to the relevant Stripe docs. And in response, I believe Leo would have given a similar answer that I did.
We provide the most generous support we can to free users here. You can upgrade for dedicated email and Slack support. I remember we had a long back and forth here, and I think you’d agree that we came to a good resolution?
Just try to remember that we’re all humans doing our best to help.