3D Secure integration v2

[tonic20]

Hi! We discover some problems with 3DS integration. Since the beginning of April some banks in Europe start rejecting transactions without full 3DS v2 info.

It turns out Braintree expect 2 more extra attributes:

• device data
• 3DS authentication id

Here is the solution:
whitespectre@d0c44cd

Also more information here:
https://developers.braintreepayments.com/guides/3d-secure/server-side/ruby

[iba-1]

Thank you, I was actually going mad about 3ds v2 failed transaction!

[kennyadsl]

Thanks @tonic20 ! Would you mind submitting a PR for this?

[iba-1]

hey @tonic20, we tried your integration but it keeps failing every transaction, would you mind share some details on the integration?
@kennyadsl implementing this would be so helpful as it seems like every bank it's transitioning to 3ds V2, maybe we could work together on a release supporting 3DSV2 if needed.

[kennyadsl]

@iba-1 Sure, we are currently not using this extension in any European store but I'm available to support anyway if someone wants to work on this.

[iba-1]

@iba-1 Sure, we are currently not using this extension in any European store but I'm available to support anyway if someone wants to work on this.

A bit OT but maybe could help someone landing here to solve some 3ds issues: what are you using to handle 3ds transaction?

[kennyadsl]

That's the point, 3ds is only required for European merchants transacting with European customers, as for Braintree doc:

3DS2 satisfies the Strong Customer Authentication (SCA) requirements coming into effect for European merchants transacting with European customers.

And we don't have any European customers at the moment. Anyway, I think that the Stripe extension has some code for it.