AnsweredAssumed Answered

request contained an undetectable format with batch register token request

Question asked by kabele on Feb 21, 2018
Latest reply on Feb 22, 2018 by kabele

Like • Show 0 Likes0
Comment • 5

I am currently trying to create a Batch Register Token Request. Here is the XML I am using:

<litleRequest version="9.13" xmlns="http://www.litle.com/schema" id="12345" numBatchRequests="1">
<authentication>
<user>testuser</user>
<password>winteriscoming</password>
</authentication>
<batchRequest id="12345" numTokenRegistrations="1" merchantId="1149094">
<registerTokenRequest id="12345" reportGroup="1149094">
<orderId>12345</orderId>
<accountNumber>4176227725064295</accountNumber>
</registerTokenRequest>
</batchRequest>
</litleRequest>

I am sending it to: https://payments.vantivprelive.com/vap/communicator/online

The response I get is:

Error, the request contained an undetectable format <<litleRequest version="9.13" xmlns="http://www.litle.com/schema" id="12345" numBatchRequests="1">
<authentication>
<user>testuser</user>
<password>winteriscoming</password>
</authentication>
<batchRequest id="12345" numTokenRegistrations="1" merchantId="1149094">
<registerTokenRequest id="12345" reportGroup="1149094">
<orderId>12345</orderId>
<accountNumber>4176227725064295</accountNumber>
</registerTokenRequest>
</batchRequest>
</litleRequest>
>.

I am at a loss for what I am doing wrong? Thanks in advance.

tboumil Feb 21, 2018 2:29 PM

Correct Answer

Kurt,

Your XML looks ok to me. I believe your problem is where you are sending it. The endpoint: https://payments.vantivprelive.com/vap/communicator/online is only for Online transaction processing and won't accept Batches. Try sending the transaction to https://payments.vantivprelive.com:15000 . Also, please note, I believe that the Pre-Live Batch URL is behind a firewall, so access requires white-listing your IP. If your Implementation Consultant has already set this up for you, you should be fine. If no, you should contact your Implementation Consultant to get you up and running for Batch submissions to the Pre-Live environment.

Tom

See the reply in context

No one else had this question

Outcomes

tboumil Feb 21, 2018 2:29 PM

Kurt,

Tom

1 person found this helpful

Actions

kabele @ tboumil on Feb 22, 2018 5:50 AM

That solved my issue. I notice in my response that I got version 8.31 back when I was sending 9.13. Do you see any issues there?

Actions

kabele @ kabele on Feb 22, 2018 5:50 AM

And thank you for your quick response.

Actions

tboumil Feb 22, 2018 5:48 AM

Kurt,

I'm not sure about you getting back V8.31 in the response message. Have you always bees on V9.13 or did you just upgrade? Anyway, I'm just guessing here, but it is likely that you are configured for V8.x for Batch in our system. For various reasons we sometimes allow different a version for Batch versus Online. Ask your Implementation Consultant about your setting for Batch and they can change it. If it isn't this setting, then I am as mystified as you are, but it would only impact your transactions if you try to use a feature/element that was added in the V9.x or above stream. If that happens, you'll get an XML validation error response, because our system would e validating against the V8.x stream.

Tom

Actions

kabele @ tboumil on Feb 22, 2018 6:37 AM

Cool, I will check with my consultant. Thanks again for your assistance!

Actions

6 Replies

tboumil Feb 21, 2018 2:29 PM
Unmark Correct
Correct Answer
Kurt,

Your XML looks ok to me. I believe your problem is where you are sending it. The endpoint: https://payments.vantivprelive.com/vap/communicator/online is only for Online transaction processing and won't accept Batches. Try sending the transaction to https://payments.vantivprelive.com:15000 . Also, please note, I believe that the Pre-Live Batch URL is behind a firewall, so access requires white-listing your IP. If your Implementation Consultant has already set this up for you, you should be fine. If no, you should contact your Implementation Consultant to get you up and running for Batch submissions to the Pre-Live environment.

Tom
1 person found this helpful
Like • Show 0 Likes0
Actions
- kabele @ tboumil on Feb 22, 2018 5:50 AM
  Mark Correct
  Correct Answer
  That solved my issue. I notice in my response that I got version 8.31 back when I was sending 9.13. Do you see any issues there?
  Like • Show 0 Likes0
  Actions
  - kabele @ kabele on Feb 22, 2018 5:50 AM
    Mark Correct
    Correct Answer
    And thank you for your quick response.
    Like • Show 0 Likes0
    Actions
tboumil Feb 22, 2018 5:48 AM
Mark Correct
Correct Answer
Kurt,

I'm not sure about you getting back V8.31 in the response message. Have you always bees on V9.13 or did you just upgrade? Anyway, I'm just guessing here, but it is likely that you are configured for V8.x for Batch in our system. For various reasons we sometimes allow different a version for Batch versus Online. Ask your Implementation Consultant about your setting for Batch and they can change it. If it isn't this setting, then I am as mystified as you are, but it would only impact your transactions if you try to use a feature/element that was added in the V9.x or above stream. If that happens, you'll get an XML validation error response, because our system would e validating against the V8.x stream.

Tom
Like • Show 0 Likes0
Actions
- kabele @ tboumil on Feb 22, 2018 6:37 AM
  Mark Correct
  Correct Answer
  Cool, I will check with my consultant. Thanks again for your assistance!
  Like • Show 0 Likes0
  Actions

request contained an undetectable format with batch register token request

Outcomes

Related Content

Recommended Content