#k3davis-paymentmethod

1 messages · Page 1 of 1 (latest)

proven kraken
#

hi! I don't think you can, in the backend API itself that route doesn't take any parameters or metdata, it's a HTTP DELETE verb

#

what's the use case exactly? You could update the PaymentMethod first and then detach it I suppose(but then you can't ever retrieve that PaymentMethod to look at the metadata if you don't have the pm_xxx ID directly so I don't quite follow the use case)

rustic tree
#

I was hoping I could identify which application was requesting the deletion (eg., a donor portal vs an internal application) so that the appropriate event listener could use that to know if it should act on the event or not

#

i do have the pm_xx id so your idea would probably work, though it adds another api request of course

#

i didn't realize until now that the metadata returned is for the payment method itself and not the request

proven kraken
#

yep, metadata is stored on the object you're interacting with

#

but yeah the webhook point is interesting, really all I can think of is setting the metadata in an update first and then detaching .