I am surely missing something obvious, but can someone share how the 3DS is implemented?
I've read the docs for this, which explain adding new data to the charge payload, but where do you get these values? Do you need a 3rd party service to perform the callout for 3DS verification?
There seems to be a gap in the document that assumes we've already done / implemented the 3DS service and are now sharing the successful validation keys for the transaction.
I've tried passing over blank values for threeds > authentication_result but that throws a generic JSON invalid error, so clearly there's some way to acquire these values before making the charge request.
The documentation alludes to each card provider using a different 3DS middleware but doesn't talk about how those are engaged.
Use 3-D Secure for e-commerce transactions (clover.com)
I'm using iframe fields to get a token and passing that over with the charge request. The basic charge is working fine, but looking to resolve some chargeback issues we've been having.
Anyone done this successfully?
Thanks in advance!
