Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnexpectedException for umlaut in cardholdername #85

Closed
marlonbosse opened this issue Mar 15, 2016 · 3 comments
Closed

UnexpectedException for umlaut in cardholdername #85

marlonbosse opened this issue Mar 15, 2016 · 3 comments

Comments

@marlonbosse
Copy link

I got a problem with cardholdernames containing umlaut like 'ä' .

CardBuilder cardBuilder = new CardBuilder()
                .cardNumber(creditCard.cardNumber)
                .expirationDate(creditCard.expirationDate.toMMYYWithSeparator())
                .cardholderName(creditCard.ownerName)
                .cvv(creditCard.cvc);
            braintreeFragment = BraintreeFragment.newInstance(this, clientToken.getClientToken());
            Card.tokenize(braintreeFragment, cardBuilder);

In the onError-Callback I get the mentioned UnexpectedException with a empty message. Since I don't get an ErrorWithResponse this doesn't seem to be an issue with umlaute in cardholdername.

The braintree reference website indicates a bug with the client library.

@lkorth
Copy link
Member

lkorth commented Mar 16, 2016

@marlonbosse: thanks for submitting this issue. This error is being generated from a 400 HTTP response because of the special character. We're currently looking into if we want to allow special characters in the cardholder name. Either way, we will make sure to update this issue, update the reference docs with the allowed character set, and improve the error message or accept the characters.

Note: the reference section is referring to braintree_java and not this SDK.

@marlonbosse
Copy link
Author

@lkorth thanks for the quick reply. So the quick fix will be sanitizing the input. Looking forward to the update.

@lkorth
Copy link
Member

lkorth commented Apr 13, 2016

@marlonbosse: We've fixed this issue. The fix will go out in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants