#Rafal_theConstruct-guest-customers

1 messages · Page 1 of 1 (latest)

wanton flume
#

Hey there! Can you share your account ID?

silent sierra
#

k

#

acct_19BaCcHYW0GgASNt

wanton flume
#

Checking something

#

They can't be deleted, no. Is there a specific reason why you'd want to delete them?

silent sierra
#

nope just asking 🙂 but it could be related to my second question. Could you look at this customer -> cus_KwCTKxbU0LdEFs and check my payments? Why have he two payments?

#

Am I doing something wrong?

wanton flume
#

Taking a look

#

If that was unexpected then there's likely some strange behaviour in your integration

silent sierra
#

hm, I looked at stripe docs to build subscriptions, and before creating a subscription, I create paymentIntent or setupIntent to collect additional setpts like 3ds etc

wanton flume
#

You won't need to create a separate Payment Intent as well as the Subscription. The Subscription will create the necessary Payment/Setup Intent and it'll be returned on the object for you to action

#

Which docs/guide are you following?

silent sierra
#

I used it because the flow for creating subscriptions was quite weird. Create customers and subscriptions before submitting the payment form.

hollow fox
#

yep but that is the recommended/documented flow

#

anyway if you're going to do your own PaymentIntent and then create a Subscription, you need to use a trial period on the subscription to avoid double-charging the customer essentially

silent sierra
#

ok, ok

silent sierra
#

hey,@hollow fox could you look at this customer -> cus_KwDpdOqsCVuB0K why he doesn't have payments? I have created setupIntent, a subscription with a trial as you said. 🙂

hollow fox
#

will look in a bit

hollow fox
#

ok looking

#

yeah so you just ran a SetupIntent(no payment, it's just saving a card), and then you created a Subscription with a trial period(no payment either). So that seems normal?

#

earlier you said

Could you look at this customer -> cus_KwCTKxbU0LdEFs and check my payments? Why have he two payments?
that one had two payments because you used a PaymentIntent with setup_future_usage to accept/charge the card, and also created a subscription

#

my answer assumed you were still using that PaymentIntent with setup_future_usage approach, in which case you want a trial so the subscription doesn't also charge the card

#

as I said last week though, I really suggest just using Checkout overall!

silent sierra
hollow fox
#

it's still valid yes

#

but this is all talking about the integration you said is "weird" and seem to have chosen to not use? It's all about 'create the subscription, then look at the latest_invoice.payment_intent or pending_setup_intent 'and you seem to not want that flow, you want to create the Intents object upfront and then create the Subscription(which I understand, and you can do that yes, but as I think I said last week, there won't be any specific docs for those exact flows, but it can work fine).
I'd still just use Checkout, or our documented 'incomplete' subscription flow if you'd like to host the payment elements on your page, overall.

silent sierra
#

Yep, you have 100% right, I wanted to create an intents object 🙂 but It seems that going to resign from creating the Intents object. It is too complicated. 🤨

wanton flume
#

Let me know if you've any follow-up questions about the recommended integration path

silent sierra
#

ah okey, okey 🙂

silent sierra
wanton flume
#

You'd also use confirmSetup from Stripe.js when collecting the payment info

#

That's because there's no immediate payment due in cases of a trial, so instead we create a Setup Intent to carry out any required auth on the payment method to ensure future off-session, recurring payments are successful without having to bring your customer back on-session

silent sierra
#

cool thx 🙂

#

and what about "PaymentBehavoir" should It be the same as in subscription without trial DEFAULT_INCOMPLETE ?

stuck marten
#

That's going to depend on how you want the subscription to behave. This page helps break down the various options for payment_behavior and how each behaves:

Apologies, since you're going down a flow where you first create the subscription on the backend, then yes.
https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior

Stripe API reference – Create a subscription – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

Edited above message.

silent sierra
#

Okay thanks for the answer, but what if the customer abandons the payment form. We have created a customer and subscription which is in Trial status and after trial subscription transit to ACTIVE, how to cancel abandoned subscriptions? @stuck marten

#

Here you have an example -> cus_KwHPbpOAm1qz2s

stuck marten
silent sierra
stuck marten