#kylemarlin - incomplete subscriptions

1 messages · Page 1 of 1 (latest)

tall flume
#

You'll generally want to use the 0341 test card for testing various subscription renewal failures, you can attach it to a customer but all payments will decline

#

How are you creating these subscriptions?

#

This is necessary to handle payment authentication

wanton shale
#

It would appear we create the customer via the API, and then create the subscription via the API (sending the customer, plan, quantity, cancel_at_period_end (false), default_tax_rates and proration_behavior).

tall flume
#

Sure -- you still need to manage payment authentication for indian cards

tall flume
wanton shale
#

Is there any documentation to handle this from the backend? We handle all our communication with Stripe using the node.js API.

tall flume
#

Handle what, exactly?

#

authentication need to be done client-side with the customer on session

wanton shale
#

After reading more about the India changes, it sounds like we couldn't use our backend only solution, as the customer wouldn't be on the site, if I'm understanding this correctly.

tall flume
#

Yes, error_if_incomplete should have the response error instead, if that's what you want, but I was trying to explain how you can go about resolving the incomplete status to get the subscription active

#

Correct - authentication is required by regulation, the customer must be online to authenticate payment in your client app, currently

wanton shale
#

Ah okay, that was the part I wasn't understanding. I'll pass along the information here to my higher-ups. You've been very helpful. Thanks so much!