NoahBundeling

[blissful solstice]

the initial payment uses iDEAL, and then the recurring payments are processed as SEPA Debits against the IBAN from the customer's iDEAL bank account

iDEAL can't be used for the recurring payments since it's a one-time method that requires actively authenticating each payment

see the docs at https://stripe.com/docs/billing/subscriptions/ideal

[pallid wigeon]

Yeah, I was thinking so. Just I got so confused.

So, if we have a separate option to add a payment method (before starting your subscription), it's better to just show SEPA Direct debit, right? Because there you'll add your iban and everything.

Instead of adding iDEAL and keep asking for authentication.

Thanks for your information though! And verification

[blissful solstice]

not 100% following you

you could ask for SEPA Debit from the start instead , yep, but one of the advantages of using iDEAL for the initial payment is that it can be more user-friendly and it has immediate confirmation of success instead of multiple days for SEPA

[pallid wigeon]

Hm alright

Yeah that does make sense.

Well, the thing is... I've made a checkout session with setup mode like this:

        'customer' => Core::app()->user->getClient()->getSubscriptionCustomerId(),
    'mode' => 'setup',
    'success_url' => 'https://xxxx,
    'cancel_url' => 'https://xxxx',
    'payment_method_types' => ['card', 'ideal'],
    'locale' => 'en'
]);```

And when you click on iDEAL, you can only select your bank and type in the name. Then you need to authorize. But I'm not quite sure how I can connect that method after that to the customer,?

[outer girder]

Hi 👋 jumping in as my teammate needs to step away soon. Since you're providing the Customer's ID when creating the Checkout Session, the resulting Payment Method should automatically be attached to that Customer. Are you seeing something different?

[pallid wigeon]

Don't worry, thanks for stepping in.

When I try to add iDEAL as a payment method and authenticate (in test mode), it always returns bank_code RABO with the same end numbers. Is that normal?

Because that's quite confusing.

[outer girder]

I believe so, a lot of our test flows use specific account numbers for testing purposes.

[pallid wigeon]

👍 Alright

So, just to get back to the flow question...

Our flow currently is like this (and all of it is separate steps by the way):

1. You are getting a trial subscription
2. You need to add your billing information (this will be send to Stripe)
3. You need to add a payment method (via a checkout session with setup mode
4. Then you can click on 'start subscription immediately' and the subscription trial date basically gets removed and because of the previous step to add a default payment method, it's automatically being charged.

So now I'm having kind of trouble adding iDEAL into these steps, because it looks like then the SEPA direct debit that's being generated when selecting iDEAL previously needs to be the default one and not the iDEAL that you selected in 'add a payment method'. Am I right?

I hope I'm explaining it correctly.

[outer girder]

It's been a while since I've worked with this flow directly (I'm going to work on standing up a test in parallel), but what are you seeing when the Checkout Session is completed and a Payment Method is being created? Are you seeing more than one Payment Method being created?

[pallid wigeon]

Actually no, I'm getting an error because the payment method is not being attached to the customer as a default method. So I'm not quite sure if that has to be the sepa direct debit that's being created or the ideal method.

[outer girder]

It's not expected for the above flow to automatically set the Customer's default Payment Method, you will need to make another request to set the newly created Payment Method as the default.

[pallid wigeon]

Alright, I'm gonna look into that

Thanks for your help