#bmizerany-Subscription

1 messages · Page 1 of 1 (latest)

fickle dagger
#

Hi there, can you share with me the subscription ID?

solar marten
#

lookup that up, but in the meantime the accountID is acct_1KiXCTRJ4T2Doxgn

#

The sub id is sub_sched_1KiY1RRJ4T2DoxgnninbwUoZ

#

looking for sched id

#

hrm. That sub_sched isn't showing up in my dash

#

when I search for it

#

No such subscription schedule: 'sub_sched_1KiY1RRJ4T2DoxgnninbwUoZ'

#

it's in my logs, though

fickle dagger
#

Switch to test mode

solar marten
#

I did. I just realized I needed to view the dash as the connected account

#

found it

#

sub_1KiY1RRJ4T2DoxgnuXf5lz8w

fickle dagger
#

Thanks.

Stripe automatically creates SetupIntents for subscriptions that don’t require an initial payment. The authentication and authorization process also completes at this point, if required. If both succeed or aren’t required, no action is necessary, and the subscription.pending_setup_intent field is null.

#

Your subscription requires initial payment and the payment was succeeded, that's why the pending_setup_intent is null

solar marten
#

The reason it did not require payment was because the initial total was $0?

#

If I want to present a customer with a payment info screen, and my initial subscription is $0, then I need to manually create a payment intent?

fickle dagger
#

Hi, thanks for the waiting. Yes you can to use SetupIntent to collect the payment method from your customer before creating the subscription schedule.

solar marten
#

Thank you for your help! If you don't mind, could you help me understand why the setup_intent wasn't created as the docs say it is (I have read the docs you linked to a few times and still can't find an answer). The product/price I subscribed the customer to has a flat fee meaning the initial payment is >$0, and the customer has not entered any payment info. I understand I can create a setup intent before the subscription, but it would be helpful for the furture to understand the reason stripe isn't returning one give then above scenario

#

The recent request ID I have showing the error regarding being unable to "expand" is req_CZCkUnYX8LmUiF

fickle dagger
#

Thanks, let me take a look.

#

Hmm wait, you are expanding on the subscription schedule object, not the subscription itself.

#

There's no pending_setup_intent hash in subscription schedule object.

solar marten
#

I am. I will fix that, however I still see 0 payment intents when I list via the cli: ```stier % stripe payment_intents list
{
"object": "list",
"data": [

],
"has_more": false,
"url": "/v1/payment_intents"
}

#

Is the payment intent not created if the subscription is created as a side-effect of creating an initial sub_sched?

#

I guess the best thing to do is create the intent before I create the sub_sched

fickle dagger
#

There's no paymentIntent for the invoice because the amount = 0.

solar marten
#

Understood. How do I collect payment info if the amount is 0 when I create the first sub_sched? Do I need to create the intent manually first, then create the sub_sched?

fickle dagger
#

I'd recommend you to use SetupIntent to collect the payment method before creating the subscription schedule, so you have full control over the flow.

solar marten
#

Okay. Thank you.

#

If we decide to wait to ask for info, we can start the flow using SetupIntent after the sub_sched creation?

fickle dagger
#

Yes you can, just make sure you update the default_payment_methed of the subscription with the collected payment method.

solar marten
#

Wonderful. Thank you!

fickle dagger
#

Or you can set the invoice_settings.default_payment_methed of the customer

solar marten
#

You've been very helpful, thank you so much!

fickle dagger
#

Happy to help!