#jayvir
wraith bear
timid dew
hello! you would probably want to listen for the invoice.paid event : https://stripe.com/docs/billing/subscriptions/webhooks#events and check. the billing_reason : https://stripe.com/docs/api/invoices/object#invoice_object-billing_reason
subscription_cycle indicates an invoice created by a subscription advancing into a new period.
fast geyser
ok @timid dew
another questions:
paymentLinks generate links
- how have i can bind email & make it not editable?
- it always creates new customer based on same email how can i stop it.
@timid dew ?
i am using 9.13 version FYI in nodejs
timid dew
you'll need to use Checkout Sessions and implement your own unique email verification check logic - you would create a Customer with a specific email. Then always pass that same Customer Id into the Checkout Session when creating it : https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer. Right now PaymentLinks will always generate a new Customer, even if the email is the same.
fast geyser
@timid dew
session vs paymentIntents
which is good
- usecase for recurring payments
- usecase for one type payments
timid dew
you can use Checkout Sessions for Subscriptions or one time payments
fast geyser
bcz we have implemented based on paymentIntents
paymentIntents is not good solution ?
timid dew
can you share more about your business model? That'd help me be able to advise you better
fast geyser
we just have
- subscription based for products on stripe which is monthly recurring
- one time fees for some other usecase
timid dew
Are you using the Subscriptions API?
fast geyser
paymentLinks - automatically creates Subscriptions for us
as of now.
timid dew
I suggest you stick to using Checkout Sessions then. It'd be easier to implement than building your own one time payment flow with PaymentIntents.
fast geyser
ok @timid dew
another question for connected account
customers should be created in main account or connected account
timid dew
what kind of fund flow are you using - direct charges, destination charges, or separate charge and transfers? You can see how to implement each of these charge types by clicking o the relevant link : https://stripe.com/docs/connect/charges
fast geyser
paymentLinks - transfer_data: {
destination: config.connectedAccountId,
},
using above
timid dew
that would be destination charges then. The customer should be created on the platform
fast geyser
platform meaning main account or connected account ?
timid dew
platform refers to the main account