Mytras

[verbal crag]

Hi, could you share some id for us to look further into?

[bleak musk]

sure

we_1Myru8KavdtumQQG7iq1r5tO

that is the webhook id

the only response I got is from a subscription that started today

but the 2 test schedule subscirption that i setup yesterday to start today

they started but did not appeared in the webhook information

[hazy monolith]

Is the Subscription actually released from the Schedule?

Just because the Subscription has started doesn't necessarily mean they're released from Schedule control

[bleak musk]

I will give you some context of what I am trying to do, I want to set up a trigger/endpoint in Zapier where I receive information about scheduled subscriptions that started, once that trigger receive the information the zapier flow will create a payment link and subsequently send it to the customer

[hazy monolith]

Sure, then you'd listen for customer.subscription.created event, not subscription_schedule.released

[bleak musk]

this will only be applied to schedule subscriptions for customers that have subscription that start in the future

[hazy monolith]

subscription_schedule.released will only fire once the the end date of the Schedule is hit, or the phases have ran their course

It doesn't fire immediately when the Subscription is created at X date in future

The Subscription will be under the Schedule control until you either release it manually, or the phases/iterations defined on the Schedule have been completed

If you simply want to know when a Schedule creates/starts the actual Subscription then use customer.subscription.created

[bleak musk]

customer.subscription.created doesnt this fire the sending of the payment link in the moment that the subscription schedule is created in stripe, lets say i create the schedule subscritpion to start charging the customer 21 of april 2024, would that work?

[hazy monolith]

customer.subscription.created doesnt this fire the sending of the payment link
Not sure what you mean
lets say i create the schedule subscritpion to start charging the customer 21 of april 2024, would that work?
Would what work?

[bleak musk]

ok give me a moment

ill explain everything

[hazy monolith]

Please!

If you have any example Subscriptions or Schedules, share them

[bleak musk]

So I need the webhook to send information to the Zapier endpoint for subscriptions schedule for the future

that will trigger the Zapier flow to create a paymentlink and after that send to the customer for payment to the correct date

[hazy monolith]

When do you want the Payment Link to be sent? When you create the Schedule, or when the Schedule starts the Subscription?

[bleak musk]

when the schedule start the subscription, that is the moment that the customer needs to start paying

for example look at this customer cus_NHvItzUjNGNXwA

She has a 1 time payment that led to a subscription starting the february 2024

the day that subscritpion starts I the payment link needs to be created and sent to the customer

[hazy monolith]

Then you should utilise the customer.subscription.created event. But I'm unsure why you need a Payment Link in this instance. Assuming you've already collected payment details, the Subscription will automatically bill the customer

[bleak musk]

because for 1 time payment BACS DD are not implemented and we want to give the customer the choice to pay via Bank and paymentlinks are the way that my company can do it since we do not have a checkout on the website

[hazy monolith]

BACS DD are not on which surface? Payment Links?

[bleak musk]

1 time payment invoices

[hazy monolith]

But via a Payment Link or via Invoicing (they're different)

[bleak musk]

I have been told from Stripe support, that for 1 time payment invoices BACS DD are not a solution not even via payment link

[hazy monolith]

Should be if you enabled this checkbox when creating your Payment Link

(we're working on removing that requirement)

[bleak musk]

So what you are saying is that for customers that have 1 time payment to send them the payment link that will save the payment details that than in the future will be automatically used to charge the subscriptions

that solves (maybe) one of my problems

we also offer subscriptions only, that start NOW() and start on a future date

that is where I need to send the customer the payment link to the exact date that the subscritpion starts

and I want to automate the process without the need for customer service to do it manually

[hazy monolith]

Yes, it's a quirk of BACS DD with Checkout/Payment Links that is something we want to address soon. One-time sessions/payments require the setup_future_usage parameter, which that checkbox provides: https://stripe.com/docs/payments/bacs-debit/accept-a-payment?platform=checkout#:~:text=You must include the payment_intent_data.setup_future_usage parameter with a value of off_session when creating a payment mode Session for Bacs Direct Debit.

[bleak musk]

But what about:
we also offer subscriptions only, that start NOW() and start on a future date
that is where I need to send the customer the payment link to the exact date that the subscritpion starts
and I want to automate the process without the need for customer service to do it manually

[hazy monolith]

You mean you create the Payment Links via the API?

[bleak musk]

yes

[hazy monolith]

There's a parameter: https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-setup_future_usage

[bleak musk]

my idea was to get the information from the webhook on when the subscription starts and the API will create the paymentlink and send it to the customer, but not sure which event to use

[bleak musk]

This is what I need at the moment

can you help me in finding the right event, please?

[hazy monolith]

You need customer.subscription.created based on what you've told me. That will fire when the Schedule creates the Subscription, based on the start date you provide

[bleak musk]

so let's say Subscrition X starts 6th june 2023 for customer Y, the webhook will send the information to the endpoint about the subscription starting the 6th of June 2023, than my API flow will create paymentlink and send it to the customer

correct?

so the customer will receive the payment link the 6th of june and not earlier or later, correct?

[hazy monolith]

Sounds about right yep

[bleak musk]

ok, I will set this up and test it

thank you so much

[hazy monolith]

Again, you want customer.subscription.created which is the event that will fire on 6th June in your example