AnsweredAssumed Answered

Can't send TransactionQuery request (Express Interface API)

Question asked by eegorov on Sep 14, 2017
Latest reply on Oct 23, 2017 by kmartin

Like • Show 0 Likes0
Comment • 6

I am trying to implement Hosted Payment Page method for Web store (The configuration is Web browser - My Server - https:// certtransaction.hostedpayments.com gateway).

My workflow is :

1. Client (web browser) sends /payment request (our internal method) to Server.

2. Server sends successfully TransactionSetup xml request to https:// certtransaction.hostedpayments.com., got the TrasactionSetupID and reply it to the client.

3. Client redirects to Hosted Pay Page form, user populates the form and the gateway redirects back with HostedPaymentStatus=Complete status and other params.

4. Client sends /payment_complete request (our internal method) to confirm the transaction (sends TrasactionSetupID).

All is ok before the next step:

5. Server have to be sure that the operation is completed successfully (then it will create the payment record in our DB). I am trying to send TransactionQuery requests as it's described in your Express Interface API v2.8.4.pdf document: "The POS can now programmatically query Element’s real-time reporting API, TransactionQuery, using the TransactionSetupID for the specific purchase, to obtain the asynchronous result of the payment transaction."

I've sent the request by analogy to TransactionSetup one:

<AccountToken>account_token_is_here</AccountToken>

<AcceptorID>acceptor_id_is_here</AcceptorID>

</Credentials>

</Application>

<TransactionSetupID>transaction_id_is_here</TransactionSetupID>

</Parameters>

</TransactionQuery>

the request params are:

url: "https://certtransaction.elementexpress.com/",

method: "POST",

headers: {

"content-type": "text/xml;charset=\"utf-8\"",

"accept": "text/xml"

}

It replies with the body message:

<Response xmlns='https://transaction.elementexpress.com'><Response><ExpressResponseCode>103</ExpressResponseCode><ExpressResponseMessage>The 'https://transaction.elementexpress.com:TransactionQuery' element is not declared.</ExpressResponseMessage></Response></Response>

What am I doing wrong? Thanks in advance.

No one else has this question

Outcomes

d.meneghello Sep 18, 2017 6:25 AM

Queries are in https://reporting.elementexpress.com/ namespace not https://transaction.elementexpress.com'

But i'm getting a lot of comunication errors ( http 405 )

Actions

eegorov @ d.meneghello on Sep 18, 2017 10:08 AM

Yes, If I use "https://reporting.elementexpress.com" namespace and send the request to https://reporting.elementexpress.com/ server host then it returns a non XML response like <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r\n<html xmlns="http://www.w3.org/1999/xhtml">\r\n<head> ...

and communication code Status: 405

Then I've changed a test account to:

AccountID = "1048414";

AccountToken = "476F62A9170CD688D4758D7B937BFA64263D748EC9213A780F5B697548A35DBE8152A501";

ApplicationID = "8569";

AcceptorID = "3928907";

For this account it replies another error:

<TransactionQueryResponse xmlns='https://reporting.elementexpress.com'><Response><ExpressResponseCode>102</ExpressResponseCode><ExpressResponseMessage>Invalid AccountToken</ExpressResponseMessage></Response></TransactionQueryResponse>

i.e. "Invalid AccountToken"!

The request body was

It's unexpected behavior, I've taken AccountToken, AccountID, AcceptorID, ApplicationID from the email from Vantiv.

Regards,

Evgeniy

Actions

eegorov @ eegorov on Sep 18, 2017 10:19 AM

... and sometimes for the same request it replies:

<html><head><title>Request Rejected</title></head><body>The requested URL was rejected. Please consult with your administrator.<br><br>Your support ID is: 17235608497004737769</body></html>

very weird.

Actions

kmartin @ eegorov on Oct 2, 2017 11:43 AM

Evgeniy,

Your AccountID and AcceptorID are correct for our Cert platform for testing and development, but your URL is pointed at the production server for live processing. This causes the "Invalid Account Token" error you cited. Try again using this URL for the endpoint:

https://certreporting.elementexpress.com

The namespace can remain as-is. Keep us posted if you continue to encounter errors.

- Kevin Martin

kevin.martin2@vantiv.com

Actions

mamoen @ kmartin on Oct 23, 2017 11:30 AM

I'm having the same issue:

This is the xml I send over to https://certreporting.elementexpress.com

<AccountToken>token</AccountToken>

<AcceptorID>accptid</AcceptorID>

</Credentials>

<ApplicationID>appid</ApplicationID>

</Application>

</Parameters>

</TransactionQuery>

and I get back:

Error 103

"Invalid TargetNamespace: https://reporting.elementexpress.com/"

Actions

kmartin @ mamoen on Oct 23, 2017 1:54 PM

Martin,

Try removing the slash at the end of the namespace in your <TransactionQuery> tag. I was able to replicate your error and resolved it by using the namespace "https://reporting.elementexpress.com".

Keep us posted if the error persists.

- Kevin Martin

Actions

6 Replies

d.meneghello Sep 18, 2017 6:25 AM
Mark Correct
Correct Answer
Queries are in https://reporting.elementexpress.com/ namespace not https://transaction.elementexpress.com'

But i'm getting a lot of comunication errors ( http 405 )
Like • Show 0 Likes0
Actions
- eegorov @ d.meneghello on Sep 18, 2017 10:08 AM
  Mark Correct
  Correct Answer
  Yes, If I use "https://reporting.elementexpress.com" namespace and send the request to https://reporting.elementexpress.com/ server host then it returns a non XML response like <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r\n<html xmlns="http://www.w3.org/1999/xhtml">\r\n<head> ...
  and communication code Status: 405
  
  Then I've changed a test account to:
  AccountID = "1048414";
  AccountToken = "476F62A9170CD688D4758D7B937BFA64263D748EC9213A780F5B697548A35DBE8152A501";
  ApplicationID = "8569";
  AcceptorID = "3928907";
  
  For this account it replies another error:
  <TransactionQueryResponse xmlns='https://reporting.elementexpress.com'><Response><ExpressResponseCode>102</ExpressResponseCode><ExpressResponseMessage>Invalid AccountToken</ExpressResponseMessage></Response></TransactionQueryResponse>
  
  i.e. "Invalid AccountToken"!
  
  The request body was
  <TransactionQuery xmlns="https://reporting.elementexpress.com">\n <Credentials>\n <AccountID>1048414</AccountID>\n <AccountToken>476F62A9170CD688D4758D7B937BFA64263D748EC9213A780F5B697548A35DBE8152A501</AccountToken>\n <AcceptorID>3928907</AcceptorID>\n </Credentials>\n <Application>\n <ApplicationID>8569</ApplicationID>\n <ApplicationVersion>1.0</ApplicationVersion>\n <ApplicationName>Web</ApplicationName>\n </Application>\n <Parameters>\n <TransactionSetupID>20FEBF10-BBD7-4468-B986-190540D6CE64</TransactionSetupID>\n </Parameters>\n </TransactionQuery>
  
  It's unexpected behavior, I've taken AccountToken, AccountID, AcceptorID, ApplicationID from the email from Vantiv.
  
  Regards,
  Evgeniy
  Like • Show 0 Likes0
  Actions
  - eegorov @ eegorov on Sep 18, 2017 10:19 AM
    Mark Correct
    Correct Answer
    ... and sometimes for the same request it replies:
    <html><head><title>Request Rejected</title></head><body>The requested URL was rejected. Please consult with your administrator.<br><br>Your support ID is: 17235608497004737769</body></html>
    very weird.
    Like • Show 0 Likes0
    Actions
  - kmartin @ eegorov on Oct 2, 2017 11:43 AM
    Mark Correct
    Correct Answer
    Evgeniy,
    
    Your AccountID and AcceptorID are correct for our Cert platform for testing and development, but your URL is pointed at the production server for live processing. This causes the "Invalid Account Token" error you cited. Try again using this URL for the endpoint:
    
    https://certreporting.elementexpress.com
    
    The namespace can remain as-is. Keep us posted if you continue to encounter errors.
    
    - Kevin Martin
    kevin.martin2@vantiv.com
    Like • Show 0 Likes0
    Actions
    - mamoen @ kmartin on Oct 23, 2017 11:30 AM
      Mark Correct
      Correct Answer
      I'm having the same issue:
      This is the xml I send over to https://certreporting.elementexpress.com
      
      <TransactionQuery xmlns="https://reporting.elementexpress.com/">
          <Credentials>
              <AccountID>id</AccountID>
              <AccountToken>token</AccountToken>
              <AcceptorID>accptid</AcceptorID>
          </Credentials>
          <Application>
              <ApplicationID>appid</ApplicationID>
              <ApplicationName>JS test</ApplicationName>
              <ApplicationVersion>0.0.1</ApplicationVersion>
          </Application>
          <Parameters>
              <TransactionID>tid</TransactionID>
          </Parameters>
      </TransactionQuery>
      
      and I get back:
           Error 103
           "Invalid TargetNamespace: https://reporting.elementexpress.com/"
      Like • Show 0 Likes0
      Actions
      - kmartin @ mamoen on Oct 23, 2017 1:54 PM
        Mark Correct
        Correct Answer
        Martin,
        
        Try removing the slash at the end of the namespace in your <TransactionQuery> tag. I was able to replicate your error and resolved it by using the namespace "https://reporting.elementexpress.com".
        
        Keep us posted if the error persists.
        - Kevin Martin
        Like • Show 0 Likes0
        Actions

Can't send TransactionQuery request (Express Interface API)

Outcomes

Related Content

Recommended Content