atanas-ach

[crystal creek]

Hello! Starting up a thread for you!

[neat bone]

Thanks

There's also a failure_code under charges. That should be easier to map things as a side-note, though I'd still need to know what the original messages look like.

[crystal creek]

Unfortunately I don't believe we have an exhaustive list of messages (you could try writing into support https://support.stripe.com/contact and asking if you want to double-check). With that said, I do believe that you can surface those messages to your users - when we say "card error" we actually mean the card_error error type. If you look at our docs on error handling here (https://stripe.com/docs/error-handling?lang=ruby#payment-errors) we call them "card errors" for legacy reasons, but they apply more broadly to payment errors in general (even for non-card payments)\

[neat bone]

Thank you - Is there a differentiation between the charges object and last_payment_error? When would one use one vs the other? Or does not not make much of a diff

[crystal creek]

I don't think it really matters, it just depends on what works for your integration