Edgars V

Looks like it will be hard to get an answer from their support for us as we don’t know the product structure.

Hi ???Edgar,

 

Thanks for reaching out! Mariana here with Braintree Technical Support – happy to assist.

 

I understand you have questions about additional data fields for 3D Secure authentication. To ensure you’re set up to handle the switch in October, it’s important to review your current 3DS integration to make sure 3DS 2.0 is properly configured. An incorrect implementation could result in a poor customer experience and impact the success of your transactions.

 

A common issue merchants may have with 3DS implementations is ensuring that the <a href="https://braintree.github.io/braintree-web/current/ThreeDSecure.html#~additionalInformation" rel="noopener" target="_blank">additional data fields</a> are correctly formatted. These fields need to be strictly formatted as per the length requirements and if applicable, the ISO requirements. Any issue with these fields would result in a fallback to 3DS 1.0, but with the deprecation, this will now result in direct errors for the customer or the 3DS challenge failing completely.

 

This limit you are seeing is for each field. You can check the <a href="https://braintree.github.io/braintree-web/current/ThreeDSecure.html#~additionalInformation" rel="noopener" target="_blank">complete list here</a> for field requirements.

 

I hope this information was helpful. Let us know if you have any other questions.

• This reply was modified 2 years, 4 months ago by Edgars V.

Actually, after checking the code I found out that the error message

The address data passed to the 3D Secure provider was in an invalid format. Address fields can have a maximum length of 50 characters.

comes from the plugin.

The real error code is THREEDS_LOOKUP_VALIDATION_ERROR and in Braintree documentation, it says

Occurs when a validation error occurs during the 3D Secure lookup.

.

So the plugin message is misleading, and the real issue could be somewhere else.
Will open a ticket with Braintree to figure out what’s wrong.

Any news here?

Yes by combining all the fields we get 64. Here is a sample

Xxxxxx Xxxxxxx
45 Xxxxxx St
Xxxxxxxx Xxx Xxxxx Xxxxx 4563
Xxxxxxxxx

And addresses like this get the error that they are too long.

Hi!

Actually, the full address is 64, not a specific field. Maybe that’s the problem? Maybe you need to limit the shippingAddress to 50

Yes, there are multiple, the last one we checked had an address with 64 characters.

We are using version 3.2.39 for a time already, but still we receive complaints from the customers that they get this error.

Thanks for confirming!

Thank you! ??

Hi!

Yes in this case the address was 87 chars

Hi!

Thank you for your feedback! It really means a lot for us!

Before I get to your problem I would like to clarify one thing, that hiding a version from script and style src won’t make your site safer, because the version of plugins, WordPress, and themes still can be easy detected inside multiple JS files, even if you will remove versions from all JS files, then there still is a possibility to compare the JS files and version will be detected.

Just wanted to let you know this before we go further.

Related to your snippet, it removes the versions from style and script srcs, I tested it locally, and it worked fine also with our plugin. I could open the editor, create/edit pages. The downside is that this snippet can create some unwanted cache issues after plugin updates. So I would recommend not to remove the version, but if you really want to hide it, then just replace it with a random string.

Here is a sample snippet for that:

add_filter('script_loader_src', 'mydomainUpdateScriptsStylesVer', 10, 2);
add_filter('style_loader_src', 'mydomainUpdateScriptsStylesVer', 10, 2);

function mydomainUpdateScriptsStylesVer($src, $handle)
{
    $parsedSrc = parse_url($src, PHP_URL_QUERY);
    $src = remove_query_arg('ver', $src);
    parse_str($parsedSrc, $queryArgs);
    if (isset($queryArgs['ver'])) {
        $salt = 'customSalt';
        $hashedVer = substr(sha1($queryArgs['ver'] . $salt), 0, 5);
        $src = add_query_arg(
            [
                'ver' => $hashedVer,
            ],
            $src
        );
    }

    return $src;
}

As you will update the $salt to your custom, then nobody will know the version anymore ??

If you’re still facing some issues, please let us know.

• This reply was modified 4 years, 3 months ago by Edgars V. Reason: Updated code tags

Hi @irina9645!

Really sad to hear that, but related to your described situation, looks like you’re thinking about a completely different product -WPBakery Page Builder, not Visual Composer Website Builder.

Visual Composer Website Builder: https://visualcomposer.com/ and WPBakery Page Builder: https://wpbakery.com/ are two independent products. Having said that, one can’t be replaced by another.
You can find more info here: https://visualcomposer.com/docs/faq/visual-composer-website-builder-vs-wpbakery-page-builder/

Hi @yashfox !

By the code, you shared looks like it is built using WPBakery Page Builder. Visual Composer Website Builder: https://visualcomposer.com/ and WPBakery Page Builder: https://wpbakery.com/ are two independent products. Having said that, one can’t be replaced by another.
You can find more info here: https://visualcomposer.com/docs/faq/visual-composer-website-builder-vs-wpbakery-page-builder/

Hi!

Looks like your talking about WPBakery, not Visual Composer Website builder. To receive WPBakery support you will need to visit: https://support.wpbakery.com

But I can recommend double-checking all the plugins and themes, mostly the issue after updating WordPress to the 5.5 version is there.

Glad that it helped you!

Feel free to leave a review for our plugin after you have get know it closer. ??