Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Billing Address accept accented characters without validation error

See original GitHub issue

General information

SDK version: Hosted Fields 3.53.0
Environment: Sandbox
Browser and OS Example: Chrome Version 77.0.3865.90 (Official Build) (64-bit) on Windows 10

Issue description

With the latest version of the Hosted Fields, I can’t trigger THREEDS_LOOKUP_VALIDATION error. I don’t want to accept accented characters in the Billing Address. This feature worked in the v3.52.0.

threeDSecure.verifyCard({
    challengeRequested: true,
    amount: '6.00',
    nonce: payload.nonce,
    bin: payload.bin,
    email: 'test@example.com',
    billingAddress: {
        givenName: $("#BillingAddress_FirstName").val(),
        surname: $("#BillingAddress_LastName").val(),
        streetAddress: $("#BillingAddress_StreetAddress").val(),
        locality: $("BillingAddress_Locality").val(),
        region: $("BillingAddress_Region").val(),
        postalCode: $("BillingAddress_PostalCode").val(),
    },
    //additionalInformation: {
    //    shippingGivenName: $("#BillingAddress_FirstName").val(),
    //    shippingSurname: $("#BillingAddress_LastName").val(),
    //    shippingAddress: {
    //        streetAddress: $("#BillingAddress_StreetAddress").val(),
    //        locality: $("BillingAddress_Locality").val(),
    //        region: $("BillingAddress_Region").val(),
    //        postalCode: $("BillingAddress_PostalCode").val()
    //    }
    //}
}, function (err, response) {
    if (err) {
        logError(err);
        if (err.code.indexOf("THREEDS_LOOKUP_VALIDATION") === 0) {

If I’m uncommenting the additionalInformation part, it will work and I get the proper error.

Issue Analytics

State:
Created 4 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

crookedneighborcommented, Oct 14, 2019

I assume you’re talking about this comment:

// a validation error occurred
// likely some non-ascii characters were included in the billing
// address given name or surname fields, or the cardholdername field

You are right, that comment is a little misleading. It shouldn’t say “or the cardholdername field” (though we’re looking into adding an additional field to the billing address options which is the cardholder name, and that would be subject to the same rules)

1reaction

crookedneighborcommented, Oct 8, 2019

This is fixed in 3.54.0, thanks for alerting us!

Top Results From Across the Web

Characters and symbols allowed in shipping and billing ...

Here is the official list with Special Characters NOT allowed in shipping and billing address by USPS. Click on the hyperlink provided above...

Prevent file import errors caused by special characters or ...

When you import a file of contacts, we recognize characters that are common to email addresses, such as: Capital letters (A - Z) ......

How to clearly state to the User what characters are valid

I'm trying to determine the best way to inform the User that an input accepts certain special characters. Alphanumerics ...

Why Won't My Address Verify / Validate? - Smarty

Sometimes, an address will not validate because the address is marked as "vacant" by the USPS. Additionally, a new address, an unregistered address, ......

Error when you create a user name that contains a special ...

The e-mail name contains invalid characters. Cause. This behavior occurs because certain special characters aren't permitted in user names that ...