torotil-testing | Stripe Developers | Page 1

plain linden Mar 9, 2022, 9:01 AM

#

nope, that is normal and how it works

#

only the 3155 card simulates being set up. And it only works for exemptions on off-session payments, not all payments

scarlet pilot Mar 9, 2022, 9:19 AM

#

Ok. There are real cards though that seem to fail with the same error (example seti_1Kak99ISFtZjFMJ3xTPgLMyp). Is this just a regular occurrence of an error? If so how should we best report it to the user?

plain linden Mar 9, 2022, 9:22 AM

#

yes real cards do that

#

the way it works is you accept a card and set it up. That then allows for future payments to potentially qualify for exemptions : https://stripe.com/ie/guides/strong-customer-authentication#merchant-initiated-transactions-including-variable-subscriptions

#

the 3155 card tests the happy path where you get the exemption, other cards test the unhappy path where you don't. In production, it's up to the bank

scarlet pilot Mar 9, 2022, 9:26 AM

#

Ok, thanks for pointing me in the right direction.

So in order to make this work more reliably (with only one user interaction and knowing the details of the subscription upfront) I’d need to create a mandate right when completing the setup intent, did I get this right?

plain linden Mar 9, 2022, 9:27 AM

#

no, not really

#

this is just part of how it works, sometimes you confirm the SetupIntent and it requires authentication, that's 100% normal and what they're supposed to do. You're supposed to create the SetupIntent on the backend, then confirm it on the frontend with our libraries, which takes payment details from the customer and prompts for 3D Secure if required.

#

I don't understand also why you'd create a SetupIntent and then immediately a Subscription, that's not the intended integration. What guide are you following exactly?

scarlet pilot Mar 9, 2022, 9:33 AM

#

The implementation is already ~2 years in production so at the moment I’m following no particular guide (… and I’d need to ask the colleague who implemented it for more details). It seems we’ve got our exemptions just fine for up to now.

The use case is mainly about accepting one-off and recurring donations:

For one-off we create a payment intent and mark the payment as success once it is completed.
For recurring donations we create the setup intent and then after that’s completed the subscription.

This seemed to be the simplest way to get both working at the time.

What would be the recommended way to set up recurring payments?

plain linden Mar 9, 2022, 9:35 AM

#

using Checkout https://stripe.com/docs/billing/subscriptions/checkout is the most recommended way

Build a subscriptions integration

Create and manage subscriptions to accept recurring payments.

scarlet pilot Mar 9, 2022, 9:35 AM

#

Ok, does this also work with user-defined amounts (that’s where donations are different than usual subscriptions)?

plain linden Mar 9, 2022, 9:35 AM

#

but when not using Checkout the idea is you

create subscription
get the subscription.latest_invoice.payment_intent
confirm that on the frontend, which handles 3D Secure and starts the subscription by paying the first invoice
(https://stripe.com/docs/billing/subscriptions/build-subscription?ui=elements)

plain linden Mar 9, 2022, 9:36 AM

#

scarlet pilot Ok, does this also work with user-defined amounts (that’s where donations are di...

in various ways yes, there's for example https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-line_items-price_data you could look into

scarlet pilot Mar 9, 2022, 9:37 AM

#

Ok, thanks very much for your help!

#torotil-testing