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

When Entering Invalid test credit cards, drop-in throws and error #403

Closed
jmannau opened this issue May 25, 2018 · 8 comments
Closed

When Entering Invalid test credit cards, drop-in throws and error #403

jmannau opened this issue May 25, 2018 · 8 comments

Comments

@jmannau
Copy link

jmannau commented May 25, 2018

General information

  • SDK/Library version: 1.11.0
  • Environment: Sandbox
  • Browser and OS: Chrome Version 66.0.3359.181 on MacOs 10.13.4

Issue description

Thanks for the great library!

I am using the Drop-In to accept credit cards and was testing cards from (https://developers.braintreepayments.com/guides/credit-cards/testing-go-live/php#card-numbers-for-unsuccessful-verification) to check for invalid cards.

In the sandbox account settings, I have enabled 'Card Verification' prior to storage in the Vault.

When using test cards '4000...1115' or '5105...5100' there is an error when trying to add a credit card.

Uncaught TypeError: Cannot read property 'creditCard' of null
    at p.t.exports [as _adapter] (hosted-fields-frame.min.html:1)
    at p.adaptResponseBody (hosted-fields-frame.min.html:1)
    at XMLHttpRequest.O.f.onreadystatechange (hosted-fields-frame.min.html:1)

This is cased as the post to https://payments.sandbox.braintree-api.com/graphql response returns

{
  "data" : {
    "tokenizeCreditCard" : null
  },
  "extensions" : {
    "requestId" : "..."
  }
}

This then leaves the UI in a locked 'loading' state. (see screenshot).

screen shot 2018-05-25 at 2 51 06 pm

Can the Drop-In UI Handle verification of invalid cards?

@crookedneighbor
Copy link
Contributor

Can you provide the request id so we can look up the request on our end?

@crookedneighbor
Copy link
Contributor

I can't reproduce on my end. I get this view as I'd expect:

screen shot 2018-05-25 at 9 56 17 am

@jmannau
Copy link
Author

jmannau commented May 25, 2018

Hi,
Here is a request id where it occurred

{
  "data" : {
    "tokenizeCreditCard" : null
  },
  "extensions" : {
    "requestId" : "be1da38e-84c9-430b-8675-ef0f9abd6f97"
  }
}

@crookedneighbor
Copy link
Contributor

I was able to reproduce this. We'll work on getting it fixed. Thanks for the report!

@alexgenco
Copy link

@jmannau We have a fix for this in the pipeline, however if you want a quick fix, I believe you can just enable cvv or avs rules in your sandbox control panel: https://articles.braintreepayments.com/guides/fraud-tools/basic/avs-cvv-rules. Let us know if that helps.

@jmannau
Copy link
Author

jmannau commented May 31, 2018

Thanks Team. @alexgenco you beat me to it. Thanks for the work around. Out of curiosity, once fixed, will I need to update the drop-in library or is it a server fix?
Thanks very much for your quick response! :D

@crookedneighbor
Copy link
Contributor

It's a fix that will happen on the server, so no need to upgrade.

@demerino
Copy link
Member

The server side fix for this should be out. Let us know if there are any other issues.

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

4 participants