TD

[dusty hinge]

Hi there!

Can you clarify what's your use case? Why do you want the subscription to stay incomplete for a week?

[manic spade]

ok Soma

so our scenarios is as below - you can suggest change as expert

We use mobile app with ACH - we collect create PI and ACH bank details and create subscription.

Subscription is incomplete and we get Micro amounts and code to verify bank

Generally we get in 24 hours and customer will provide us 6 digit code to verify account

but what if micro deposits added but customer wont checking bank details for 2-3 days?

So we want to increase subscription expire to one week

This is actually happening if we use check out session

but want to do same using API

https://stripe.com/docs/billing/subscriptions/overview#incomplete

You look our scenario here -

We may expect delay of more than 23 hours so want to increase it

[dusty hinge]

Sorry for the delay, having a look now.

[manic spade]

No issues 🙂 I am here

This is somehow possible - have look screenshot from our prod stripe where we used checkout session and time given is 10 days 🙂

but when we do API - it just give 23 hours

[twin fiber]

Hi! I'm taking over from my colleague. Please, give me a moment to catch up.

Could you please share the Subscription ID?

[manic spade]

ok where I can quickly find it?

[twin fiber]

On this page, it looks like sub_xxx

[manic spade]

sub_1NFF06INNTEta5UlUPwAPFHF

this is the one got expired before verfied

[twin fiber]

Taking a look

Could you please share a Subscription that was created via Checkout Session?

[manic spade]

sub_1NFxrVINNTEta5Ul3CqV5APy

I noticed one thing - when sub. created using check out session - payment seems initiated as well

That is not the case when we use API

Could this be a catch?

[twin fiber]

What do you mean by "payment initiated" exactly?

[manic spade]

look in invoice

and screenshot I sent above

"$1.55 payment was initiated which requires an additional user action"

[twin fiber]

I see, and that's from the Checkout-created Subscription?

[manic spade]

yes

[twin fiber]

Okay, for the Subscription created via API, are you planning to collect a new payment method or charge an existing one?

[manic spade]

new

[twin fiber]

Are you presenting the Payment Element (or PaymentSheet on mobile) to the customer?

[manic spade]

We create payment intent with ACH

Element

[twin fiber]

I don't see that the customer confirms the payment.

[manic spade]

ok you mean last step is somehow missing?

[twin fiber]

Yes

[manic spade]

We see mandate etc

we use payment element so what could be the reason we dont see confirm payment screen?

[twin fiber]

Could you please make a screen recording of your flow?

It seems like the payment flow is not completed.

[manic spade]

hmm can you wait for 10-15 mins?

yes I think so too

[twin fiber]

Sure

[manic spade]

I think we got the issue

We are not initiating verification

I am sharing video but need to know which API to call to begin payment verification

[wraith ridge]

Hi there 👋 catching up as my teammates needed to step away, are you doing manual or instant verification for your ACH flow?

[manic spade]

manual

[wraith ridge]

Gotcha, so are you doing anything mentioned in this section to trigger that verification?
https://stripe.com/docs/billing/subscriptions/ach-debit?platform=web#verify-with-microdeposits

[manic spade]

ok will havelook

what api to call?

We are creating payment intent and that's created successfully

what api we should call next?

so steps 1 : create payment intent - capture banke details

obtain client secret etc

2, whcih api?

3. create customer

4. give subscription

[wraith ridge]

I don't think you should be creating Payment Intents directly if you're working with Subscriptions. Subscriptions automatically create Invoices which automatically create Payment Intents for handling the Subscription's payments.

Can we take a step back and realign. What are you trying to do, what do you have so far, and where are you running into troubles?

[manic spade]

Sure

Any possibilities to screen share call?

or we have to continue chat

[wraith ridge]

We'll need to continue to chat

[manic spade]

ok so our scenarios

We have subscription to give

which has amount associated

we ask to pay either by card - which seems to work fine as we confirm payment of card and if we get success we create subscription so this is fine.

Now ACH - US bank account or manual

We are yet to check US bank account means instant

Now issue is with ACH Manual

this is where we need suggestions

we are doing like we said and can share video

[wraith ridge]

Let's focus on this for a second, as this doesn't sound right offhand. When you create the Subscription following the Payment Intent being completed, do you do so in such a way that the Subscription doesn't also immeidately process a payment for its first billing period?

[manic spade]

I think so

we create payment intent first, then customer and give them subscription

so I think payment is not initiating - I know there something where we need to join dots.

[wraith ridge]

Typically when you create a Subscription, it immeidately creates and finalizes an Invoices, which creates and confirms a Payment Intent to handle the first payment for the Subscription. So my fear is that if you're processing a Payment Intent and then creating a Subscription, that you are building a flow that may double charge your customers for the first billing period.

[manic spade]

No no - payment is one time only

but yes we need to think of this scenario whatever you told

ok using api I created subscription

but in sameI was given 23 hours

which is really we dont want

we want one week

see sub_1NG0QMINNTEta5UldgTLdIxH

how do we change this? and you can also see payment is also not initiated

so how do we initiate payment using api with just subscrition created

[wraith ridge]

As far as I know this is not possible, Subscriptions will expire after one-day rather than one-week.

[wraith ridge]

This Subscription created an Invoice that was finalized, but that Invoice was not paid because it was set to charge_automatically but there was no default payment method set on the Customer or Subscription objects.

To process this payment, you could use the client secret of the Payment Intent associated with the Invoice to render the Payment Element. Or you could use the Hosted Invoice Page URL from the Invoice object if you would prefer a hosted experience over an embedded one.
https://stripe.com/docs/api/invoices/object#invoice_object-hosted_invoice_url

[manic spade]

" you could use the client secret of the Payment Intent associated with the Invoice to render the Payment Element" this is our way

[wraith ridge]

Okay, and what problems are you running into when doing that?

[manic spade]

well so we need to do what with payment intent?

I mean do we need to confirm payment intent?

We are already creating payment intent

and getting secrets also

[wraith ridge]

You don't create a new Payment Intent, you use the one that is already being created by the Subscription and its Invoice.

[manic spade]

got it so

step 1 : create subscription and method is ACH US bank

get invoice and from same retrive payment intent

and then confirm or complete or something?

[wraith ridge]

Yes, have you looked through the guide that I linked before? It walks through the entire process (linking again for convenience):
https://stripe.com/docs/billing/subscriptions/ach-debit?platform=web#create-subscription