#adam.williams
1 messages · Page 1 of 1 (latest)
Hello! As far as I know we don't expose liability shift information in the API.
This was previously discussed here: #1138104771274879116 message
The consensus seemed to be that:
if
payment_method_details.three_d_secure.resulton the intent isauthorizedthen you can be confident the liability has very likely shifted
That's good enough for me
Okay. I wouldn't rely on that personally but it's entirely up to you if you want to go with that approach.
If there's an alternative more reliable approach I can look into within the API, I'd be interested - but cynically the support here appears rather .. limited compared to other PSPs like Braintree, with the intent of upselling Radar.
Let's stick to the technical aspects though - is my understanding of the charges and payment intent lifecycle accurate? Should I be able to retrieve a charge as soon as my payment intent enters the requires_capture state?
Yes, you can retrieve the Charge when the Payment Intent enters requires_capture state.
And the three_d_secure field will be populated at that point in time?
Yes, that happens after the 3D Secure process.