#codyl-achdebit-mandate

1 messages · Page 1 of 1 (latest)

sick bison
#

Easiest is to do a new SetupIntent for that existing payment method and confirm it client-side

wind hinge
#

Ah ok.

#

Still feels like an issue that we can't see the status or the id of a mandate attached to a payment method.

#

but I submited a write up to support on that earlier today

#

thanks

sick bison
#

yeah in theory you track the mandate in your database and listen to events

wind hinge
#

so by design you would have one mandate per customer then?'

#

seems like you should be able to lookup mandates by customer but can't do that either.

sick bison
#

it depends on your integration, but in most cases either you only have one, or you have to track those and explicitly pass the right id per payment already

wind hinge
#

I was under the impression that once the mandate was attached to the payment method it would not need to be referenced again for individual payments

#

if the mandate was not attached to the payment methond then that would make sense to me

sick bison
#

that's what I said!

#

We can choose one automatically, you don't have to pass the id, but if you have more than one you would pass the right id since we can't know which one you want

#

Overall: you, as the developer, should keep track of those mandates and listen to the corresponding events when they get revoked

wind hinge
#

ok

sick bison
#

I do agree with your original point though that being able to list mandates would make this easier

wind hinge
#

Yeah it's early on those

#

I'm guessing there will be some iterations in the api

#

anyway I'll just look at storing one mandate per customer in our db and see how that looks

#

thanks again

sick bison
#

happy to help!

wind hinge
#

the payment method

#

sorry back to the original quesiton on the invalidated mandate

#

passing the same payment method back to a new setup intent with a new mandate

#

should just yield a payment method with the same id right?

sick bison
#

yes