#eleonored_45012

1 messages · Page 1 of 1 (latest)

fiery citrusBOT
hot hull
spring trench
#

we want to initiate this first setupIntent to do recurring paymentIntent. So i don't think Payment on hold is the right solution for that. Do you agree ?

#

(and we don't want to use Stripe subscription)

hot hull
#

You can set setup_future_usage on the Payment Intent to set up the Payment Method for future use (the same setup a Setup Intent performs).

spring trench
#

ok we saw it. But we can't use it for SEPA and less then 0,5€ payment (which can happen in case of discounts)

hot hull
#

Err, wait, that's above that minimum, but you're saying there's a minimum on SEPA separately, right?

#

I didn't think it did...

spring trench
#

is SEPA working with payment Intent without doing a setup intent before ?

#

about first question, can you confirm that with our current approach (setupIntent + async paymentIntent) the user might see a first screen to allow a 0€ payment and validate 3DSecure with this first setupIntent and then been charge of the actual amount ?

hot hull
#

Yes? I recommend you try this out in test mode to see if it will work for your use case or not.

#

Yes, with a Setup Intent followed by a separate Payment Intent some customers will see two separate items on their statements or get two separate notifications.

#

You should not use a Setup Intent followed by a Payment Intent. You should use only a Payment Intent with setup_future_usage and separate authorization and capture.

spring trench
#

ok thanks.
so only issue is for our < 0.5€ fees.

hot hull
#

Well, it should only be an issue for < 0.3€ as far as I know.

#

But yes. In that case you would use a Setup Intent and not charge anything, because you can't charge an amount that small.

spring trench
#

ok thanks 👍

hot hull
#

Happy to help!