Question about new Visa Secure Data Fields rules #481
-
Hi, we use drop-in SDK in both our Android and iOS apps to collect payment card information. I was notified by business, that there are new Visa Network changes - Updates to Visa Secure Data Fields mandate which they want us to integrate into our mobile application. Is this something that will be automatically handled by Drop-In SDK, or do we need to do something on application-side? I found related issue with web drop-in but that was not really helpful to me: braintree/braintree-web-drop-in#922 This is how we essentially collect payment card information right now: dropInClient.launchDropIn(
DropInRequest().apply {
this.isGooglePayDisabled = true
this.isPayPalDisabled = true
}
)
// And then send payment method nonce to backend on success Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi @matejsemancik - Yes you should include the fields listed in the Updates to Visa Secure Data Fields mandate by passing a custom For a list of all fields available for customizing the request, see ThreeDSecureRequest or BTThreeDSecureRequest and specifically the ThreeDSecureAdditionalInformation classes. |
Beta Was this translation helpful? Give feedback.
-
Hi @sarahkoop an additional question you maybe will know answer to. I wasn't really able to find more additional info for this and description in documentation is not very specific -- do we need to pass a local IP address that can be easily retrieved using system APIs, or do we need to send a public IP address of device obtained by calling some 3rd party service such as https://www.ipify.org/ ? |
Beta Was this translation helpful? Give feedback.
Hi @matejsemancik - Yes you should include the fields listed in the Updates to Visa Secure Data Fields mandate by passing a custom
ThreeDSecureRequest
to yourDropInRequest
(Android) orBTThreeDSecureRequest
to yourBTDropInRequest
(iOS). The fields outlined in the table linked above can be set through theThreeDSecureRequest
object.For a list of all fields available for customizing the request, see ThreeDSecureRequest or BTThreeDSecureRequest and specifically the ThreeDSecureAdditionalInformation classes.