AnsweredAssumed Answered

Index Key Missing - BIN Table

Question asked by rahul.jacob on Apr 27, 2018
Latest reply on Jun 19, 2018 by Chris Jennings

Like • Show 0 Likes0
Comment • 2

Hi,

We had implemented Vantiv integration with our POS last year.

All was well but now there is an issue with few POSs. We are getting "Index Key Missing" on the reader device and below is the result of the logs:

<Title>SaleTransaction</Title>
<Message>Response</Message>
<StackTrace><?xml version="1.0"?>
<RStream>
<CmdResponse>
<ResponseOrigin>Client</ResponseOrigin>
<DSIXReturnCode>003328</DSIXReturnCode>
<CmdStatus>Error</CmdStatus>
<TextResponse>TRANSACTION NOT COMPLETE - No Service Code Found.</TextResponse>
<SequenceNo>0010010000</SequenceNo>
<UserTrace></UserTrace>
</CmdResponse>
</RStream>
</StackTrace>

We checked the following:

Ingenico : Reader config is correct.
Data Cap: Processing correctly
Vantiv : Account setup was also done correctly.

We were informed by vantiv that everything now leads to BIN table. There were no details of implementing BIN tables in the sdk provided during integration.

Is this an issue with BIN table? Do we need to implement BIN table? If yes, need info on what it is and how to implement it.

Thanks

Rahul

No one else has this question

Outcomes

rahul.jacob Jun 19, 2018 6:26 AM

Does anyone know why we are getting this error on the reader?

Actions

Chris Jennings @ rahul.jacob on Jun 19, 2018 4:37 PM

Hi Rahul,

The response message <ResponseOrigin>Client</ResponseOrigin> indicates that is being generated from the dsiClient, which would means it is not being sent through to our hosted NETePay, so it is failing locally either at the device level or client.

Have you been able to reproduce within our test environment? Considering the examples are from a production account, utilizing our technical support team will be the best resource to resolve this, because we may need to review the merchant account details.

Are you able to share any details around the TStream Request? Does this happen on every transaction or just certain cards? Are you attempting to run an EMV request or Credit magnetic stripe request. Do you have any background related to the dsiclient version running or the in-store NETePay?

Regards,

Chris

Actions

2 Replies

rahul.jacob Jun 19, 2018 6:26 AM
Mark Correct
Correct Answer
Does anyone know why we are getting this error on the reader?
Like • Show 0 Likes0
Actions
- Chris Jennings @ rahul.jacob on Jun 19, 2018 4:37 PM
  Mark Correct
  Correct Answer
  Hi Rahul,
  
  The response message <ResponseOrigin>Client</ResponseOrigin> indicates that is being generated from the dsiClient, which would means it is not being sent through to our hosted NETePay, so it is failing locally either at the device level or client.
  
  Have you been able to reproduce within our test environment? Considering the examples are from a production account, utilizing our technical support team will be the best resource to resolve this, because we may need to review the merchant account details.
  
  Are you able to share any details around the TStream Request? Does this happen on every transaction or just certain cards? Are you attempting to run an EMV request or Credit magnetic stripe request. Do you have any background related to the dsiclient version running or the in-store NETePay?
  
  Regards,
  Chris
  Like • Show 0 Likes0
  Actions

Index Key Missing - BIN Table

Outcomes

Related Content

Recommended Content