#nukesforbreakfast

1 messages · Page 1 of 1 (latest)

lapis marshBOT
#

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.

digital pendant
#

HI 👋

We are not experts on the dashboard here but we do know that we don't have parity between features in the Dashboard and in the API so that is expected.

#

We focus on the API and I think that behavior is correct

blissful cedar
#

hmmm, well the dashboard behavior is exactly what I need for my use case since I might not have an email yet when an invoice is generated.

#

so who would know the answer? Stripe support?

digital pendant
#

This is the behavior of the API. There isn't "an answer". If you want to create a Subscription with send_invoice as the collection method via the API you will need to wait until you have an email address for the Customer

blissful cedar
#

These are one off invoices, sorry. Not subscriptions

#

not sure if that makes a difference.

#

(but if the dashboard can make it happen, that indicates there exists an API method to bypass this verification and create the invoice anyways)

digital pendant
#

but if the dashboard can make it happen, that indicates there exists an API method to bypass this verification and create the invoice anyways
No, not really.

blissful cedar
#

the dashboard has to make requests to some back end API though, no?

digital pendant
#

But then it does stuff on it's own as well.

lapis marshBOT
blissful cedar
#

I mean I can see the initial post request to the invoices endpoint in the logs. 🤷

orchid hound
#

Right, but the dashboard has different capabilities from the API that our client libraries use unfortunately. I can put in a feature request to expose this on that API, I definitely see the value in it. But at the moment it doesn't support send_invoice subscriptions for customers without email address

blissful cedar
#

yeah, it must get some special treatment. There's a bunch of params that don't appear to exist on the public API.

#
{
  "customer": "cus_P0adhqP8YP75jo",
  "collection_method": "send_invoice",
  "include": [
    "available_payment_method_types"
  ],
  "pending_invoice_items_behavior": "exclude",
  "only_finalize": "true",
  "expand": [
    "default_tax_rates",
    "default_payment_method",
    "default_source",
    "from_invoice.invoice",
    "lines.data.tax_amounts.tax_rate"
  ]
}
#

send_invoice subscriptions for customers without email address

Again, to be clear, these are not subscription invoices. These are one offs.

#

I don't know how much of a difference that makes.

orchid hound
#

Yeah, dashboard exclusive params definitely exist. I don't think being subscription vs one off makes a difference here, if you are seeing this error in your testing with one-off invoices I think it is just a restriction there for the time being unfortunately