#stantastic_
1 messages · Page 1 of 1 (latest)
not mandatory no
that looks like Lavarel Cashier though, so check their docs since maybe it has other requirements or modes
It is, yes. They just sent me here 🙂
in the API itself you create incomplete subsciptions and add the payment method on the frontend https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements , I don't know what Cashier does or how it wraps the functionality
to be clear anyway you can't use the Stripe Billing Portal to create a new subscription
Okay. I'll have another look. I just tried to avoid having any payment related data on my front-end really. I thought it's possible to just create the subscription, redirect to stripe and have users select their payment method of choice there.
it's meant for managing a Customer's existing Subscriptions. You create the Subscriptions either using a CheckoutSession, or with a custom payment form with Elements and an incomplete initial Subscription
I thought it's possible to just create the subscription, redirect to stripe and have users select their payment method of choice there.
well you can just use Checkout for that. You don't create the Subscription first, you just create a CheckoutSession and redirect the user to its URL, and they enter details there and it creates the subscription
It does create an incomplete subscription since there's no default payment added beforehand.
yeah but I mean you as the person calling the API never 'create a subscription' or call the /v1/subscription API endpoint, you just create a CheckoutSession with the /v1/checkout/sessions API can redirect to its URL
again, no idea how Lavarel wraps this