#imaliveagain

1 messages · Page 1 of 1 (latest)

jolly pebbleBOT
proven oracle
void elbow
#

It is however this particular use is an integration where payments are being run by a batch on previously inputted payment methods for a subscription(not stripes) model. So the user isn't present and I want to store on a field when some type of decline happens so that this seller can go look and see enough information on why it was decline and decide what to do or automate off of an error code.

#

I don't want to duplicate info or confuse the seller so I'm just trying to make sure I understand the message and codes coming in from the paymentintent and what's on the outcome of the charge.

proven oracle
#

yeah, you should not need to surface last_payment_error then