#skoshkarli-subscription-setupintent
1 messages · Page 1 of 1 (latest)
skoshkarli-subscription-setupintent
Hey @winter scaffold ! You seem to be mixing up multiple different concepts. A SetupIntent is here to collect payment method details without a payment. There's no description for this or anything you can control that would appear in the Dashboard. You also can't "pass the intent" to the Subscription creation (in theory it's the opposite, you create the Subscription first)
As for the description on the PaymentIntent for a given payment, it's controlled by the Subscription itself and it's not something you can set. You can change it after the fact if you want by updating the underlying Charge's description for example but that would be after the email receipt if sent (if any)
no, this is not how we do it, we use the setupIntent to render the payment form and validate payment before creating a subscription
Sure but that's also not the way we recommend doing this which is what I'm trying to explain while also trying to grasp what you are doing. The screenshot you sent is about a Subscription update not even the creation
Yeah i've had hours of conversations with you guys about whats recommended and what we need
right now thats not what i am trying to solve though
the screenshot is from the Payments tab on the dashboard
¯_(ツ)_/¯ I'm trying to help you, the way you framed the question confuses me so I'm trying to poke at it
What i would like to know is where this "Subscription update" description is coming from
and how do i override it
This is set by default when you update a Subscription which leads to an Invoice being cut. And you have no control over this and can't override it before creation. You can change it afterwards
so we have an integration through recurly as well on one of our Stripe accounts, and they are able to do it
here is an example:
they do it somehow
I want to do the same on my direct integration with stripe as well
what does "they are able to do it" mean though? As far as I can tell all the description says in this example is the Invoice + invoice number?
correct, instead of Subscription update
Okay sorry we're running a bit in circles
so however Recurly is integrated with you guys, they are able to create the subscription and have this description field show some specific data
can you give me a concrete example of the Subscription update one? I still don't understand what you're asking
okay so that is because you did a real subscription update right? Like you created the Subscription as a trial and then immediately ended the trial, which is a Subscription update
ok let me give you another one where i did not intervene
also it's 2 completely separate Stripe accounts, one is on a 2014 API version
they are separate accounts, correct
i am specifying a 2020 api version for all my api calls
on our new account which has the direct integration with Stripe
I'm also confused by the second example which seems to also have started with a trial subscription?
correct, most of our subscriptions start with a trial
Okay so yeah the main reason is the API version difference really. Your newer account is on a 2022 API version and it defaults to that string.
the fact that you force the API version is irrelevant in this case because the Invoice finalization/payment happens async and you basically can't control it
so on our older account, how does Recurly put in custom data into that description?
they don't. Your account just has a 9 years old API version and has the old behaviour
if i look at non-test users, they have a description of the products in them in that old account
its definintely customized
I mean no it's not
why is this different than the first test user i sent then?
it would be the same stuff if it wasn't custom
that one has nothing to do with Subscriptions. It's a normal PaymentIntent creation for a one-off payment
it is a subscription
no it's not
we don't have one-off payments, we dont offer products for one-off payments
all of our products are subscriptions
https://dashboard.stripe.com/logs/req_NKfmXX6xqfNfhJ
This is a call to POST /v1/payment_intents
and basically no
you offer a recurring payment option but that doesn't mean your integration uses Subscriptions (our Billing product) everywhere right?
I assume Recurly has their own recurring logic maybe?
at least that specific example you gave me is not related to a Subscription or an Invoice
i see whats going on here
yeah it looks like Recurly is doing the recurring logic itself and doesn't create an actual Subscription in Stripe
just doing payment intents every month
ok, so you are saying there is no way i can customize this field then ?
There is, after its creation. So it depends a lot on what your goal is
would that just be a matter of me calling update on teh payment intent tied to the user's subscription?
but i am guessing it wouldn't persist on a monthly basis for monthly subscriptions
correct, you'd write code to do this automatically for each Invoice