AnsweredAssumed Answered

How to test an "invalid" card number?

Question asked by shanon@qbc.com on Jun 17, 2019
Latest reply on Jun 26, 2019 by tboumil

Like • Show 0 Likes0
Comment • 5

I've got a connection to the cnpAPI sandbox via https://www.testvantivcnp.com/sandbox/communicator/online, and have been first playing with getting a response via the registerTokenRequest function.

I've come across multiple differing documents with examples of card numbers to use for testing features, and my issue that I seem to be running into is that no matter what number I put in for the card, the response always comes back as 801 - Account Number was successfully registered.

I've tried using the "invalid" card numbers from the cnpAPI reference guide, as well as trying to "build" a card number for the desired response using the data here: http://vantiv-ecommerce.github.io/sandbox/

Does anyone have any tips on this?

tboumil Jun 17, 2019 2:14 PM

Correct Answer

OK. Thanks for the info. I'll have someone check the simulator code for the registerTokenRequest to see what's wrong.

Tom

See the reply in context

No one else had this question

Outcomes

tboumil Jun 17, 2019 11:26 AM

Hi Shanon,

First, the card numbers from the cnpAPI guide apply to our Pre-Live certification environment, but not the Sandbox. Each of these environment use different simulators, so yield different results for most, if not all, the tests.

You were taking the correct approach in attempting to build your own card number with the info shown on http://vantiv-ecommerce.github.io/sandbox/. The second example in the Available Features section should return an 801 code.

4100280140123000002Vault/Tokenization5-7 - Token response code

It is possible that there is something wrong with the simulator for the register token transaction. I will ask someone to check that it returns the expected results, but in the meantime, could you try it again with the number shown in the example. Could you also try it with either a Sale or Authorization transaction, which should return a <tokenResponse> element with the <tokenResponseCode> child element and a value of 801.

Tom

Actions

shanon@qbc.com @ tboumil on Jun 17, 2019 12:58 PM

Hi Tom,

Upon further testing, it does appear that running a Sale transaction with the tokenization feature returns the correct "820 - Invalid Card Number" response if I send that in the card number. It seems to be only the standalone registerTokenRequest that is adamant about returning 801.

Actions

tboumil @ shanon@qbc.com on Jun 17, 2019 2:14 PM

OK. Thanks for the info. I'll have someone check the simulator code for the registerTokenRequest to see what's wrong.

Tom

Actions

tboumil @ shanon@qbc.com on Jun 24, 2019 12:00 PM

We have verified that there is indeed a bug in the Sandbox Simulator. There is a team working on the fix. I will post here once we have verified the fix is in.

Sorry for any inconvenience this may have caused,

Tom

Actions

tboumil Jun 26, 2019 1:09 PM

Hi Shanon.

The engineer working on the bug just informed me that it has been fixed. If you are still testing, Sandbox should now generate the expected responses.

Tom

Actions

5 Replies

tboumil Jun 17, 2019 11:26 AM
Mark Correct
Correct Answer
Hi Shanon,

First, the card numbers from the cnpAPI guide apply to our Pre-Live certification environment, but not the Sandbox. Each of these environment use different simulators, so yield different results for most, if not all, the tests.
You were taking the correct approach in attempting to build your own card number with the info shown on http://vantiv-ecommerce.github.io/sandbox/. The second example in the Available Features section should return an 801 code.

4100280140123000 002 Vault/Tokenization
5-7 - Token response code

It is possible that there is something wrong with the simulator for the register token transaction. I will ask someone to check that it returns the expected results, but in the meantime, could you try it again with the number shown in the example. Could you also try it with either a Sale or Authorization transaction, which should return a <tokenResponse> element with the <tokenResponseCode> child element and a value of 801.

Tom
Like • Show 0 Likes0
Actions
- shanon@qbc.com @ tboumil on Jun 17, 2019 12:58 PM
  Mark Correct
  Correct Answer
  Hi Tom,
  
  Upon further testing, it does appear that running a Sale transaction with the tokenization feature returns the correct "820 - Invalid Card Number" response if I send that in the card number. It seems to be only the standalone registerTokenRequest that is adamant about returning 801.
  Like • Show 0 Likes0
  Actions
  - tboumil @ shanon@qbc.com on Jun 17, 2019 2:14 PM
    Unmark Correct
    Correct Answer
    OK. Thanks for the info. I'll have someone check the simulator code for the registerTokenRequest to see what's wrong.
    
    Tom
    Like • Show 1 Like1
    Actions
  - tboumil @ shanon@qbc.com on Jun 24, 2019 12:00 PM
    Mark Correct
    Correct Answer
    We have verified that there is indeed a bug in the Sandbox Simulator. There is a team working on the fix. I will post here once we have verified the fix is in.
    
    Sorry for any inconvenience this may have caused,
    
    Tom
    Like • Show 0 Likes0
    Actions
tboumil Jun 26, 2019 1:09 PM
Mark Correct
Correct Answer
Hi Shanon.

The engineer working on the bug just informed me that it has been fixed. If you are still testing, Sandbox should now generate the expected responses.

Tom
Like • Show 0 Likes0
Actions

How to test an "invalid" card number?

Outcomes

Related Content

Recommended Content