dynelight_unexpected

[hollow vale]

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.

• dynelight_api, 1 hour ago, 58 messages
• dynelight_unexpected, 4 days ago, 23 messages

[candid socket]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1239814356494057564

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[cursive rivet]

Hi there, are you referring to the pending_setup_intent ? https://docs.stripe.com/api/balance_transactions/list#balance_transaction_list-payout

[steady wraith]

I am not

I do:

subscription = Stripe::Subscription.create(payload)

Is the first event I see from my webhooks

but I am not specifying to create this setup intent

[cursive rivet]

Yup, that's the pending_setup_intent that I mentioned earlier.

You created a subscription on trial, so there's no payment required for the first invoice.

[steady wraith]

This is my payload:

      payload = {
        customer: entity.stripe_customer_id,
        items: items,
        metadata: {
          billable_id: entity.id,
          billable_type: entity.entity_type
        },
        trial_end: 1.year.from_now.to_i,
      }

[cursive rivet]

And that's why Stripe created a pending_setup_intent for you to collect a payment method, so that you can use this to pay invoices once the trial ends

[steady wraith]

What if I already have a setup intent and I want to use that one instead?

We can create trial subscriptions but the user might already have a default payment assigned

[icy steppe]

Then you can use the collected PaymentMethod inside your preivous SetupIntent, to set on the Subscription's default_payment_method

The Subscription will recognize you already have one, and won't prepare another new SetupIntent

[steady wraith]

This makes so much sense! Thanks so much. I will give it a try and if I have any other questions, I will open another thread.

I should only need one setup intent per customer right?

Is there a reason to needing more than one?

[icy steppe]

Technically yes, but for example if your customer's card expired and can't update, or their bank simply declined it and they need to add a new one, then you probably need to generate a new SetupIntent to re-collect a new card

SetupIntent = your attempt to collect a card from the customer

[steady wraith]

Card or bank right?

If I add three credit cards then I will need three setup intents?

[cursive rivet]

Yes you are right, one setup intent for one payment method