#Min.K
vital laurelBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
pine isle
hi! I would expect it in last_payment_error yes.
do you have the example invoice or PaymentIntent ID you looked at?
void gale
pi_3OFCF4H7t32LLKQx1oQvdaTV
sub_1OEooBH7t32LLKQxUzBelQEI
Would you check this out please?
I used a testcard to test payment failures and the invoice generated by the subscription failed normally and is in the Retry state.
In addition, the invoice.payment_failed event was also issued normally.
However, even though the payment failed, the payment_intent has a null last_payment_error.
pine isle
pi_3OFCF4H7t32LLKQx1oQvdaTV
no payment attempt has happened on that yet. The related invoice was finalized 18 minutes ago, and we wait an hour before charging usually
in any case I think the failure here is different
I think it's that you don't have a default payment method set, so there wasn't actually a payment attempted. The failure is that here is no card to charge, basically.
void gale
no payment attempt has happened on that yet. The related invoice was finalized 18 minutes ago, and we wait an hour before charging usually
in any case I think the failure here is different
=> The invoice was created 1 hour and 30 minutes ago and has already attempted to pay and is retrying. Please see the image I posted.
pine isle
yeah I was wrong yes
the actual error here is an internal error that no CVC was provided (not sure if you can see https://dashboard.stripe.com/test/logs/req_Zh9p2fpmhS6Q5h)
when you added that customer's card, you did it in the Dashboard, and the Dashboard doesn't collect the CVC, and the CVC is actually required.
so overall that's a mess and our problem, but basically you should be testing all this using the API and your own payment pages that use Elements/Checkout, which do collect the CVC. "Keying-in" card details on the Dashboard isn't really a flow you'd do in production.
void gale
So, to clarify, it sounds like you're saying that in a real production customer flow, LAST_PAYMENT_ERROR would have a value. Am I understanding this correctly?
As an additional question, I would like to test that the last_payment_error field is not null, but has a value in it. How can I verify this in my test environment?
I'm a developer, so I have to validate that I'm getting real data, parsing it, and handling it.
pine isle
yes
use your payments integration(Elements, or Checkout in mode:"setup") to add the card to the customer instead and then do the same test