Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

XML parse exception is thrown when subsequentAuth tag is passed in TransactionProcessor request for Cybersource

Open
  • Is something wrong?
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
api, payments

Research direction

Start by tracing how the PHP SDK serializes TransactionProcessor requests and handles the subsequentAuth field. Reproduce the supplied request against the Cybersource test endpoint, comparing it with the same request without subsequentAuth. Done means a request containing subsequentAuth is accepted without the XML parse fault while existing requests remain functional.

Written by the indexing model from the issue text.

Description

Iam getting SOAP fault exception : XML parse error when passing subsequentAuth tag in the XML payload.

Endpoint used: https://ics2wstesta.ic3.com/commerce/1.x/transactionProcessor/

XML request used:

<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Header>
      <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsse:UsernameToken>
            <wsse:Username>steelbrickbilling</wsse:Username>
            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">**MASKED**</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
   </s:Header>
   <s:Body>
      <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.161">
         <merchantID>steelbrickbilling</merchantID>
         <subsequentAuth>true</subsequentAuth>
         <merchantReferenceCode>steelbrickbilling</merchantReferenceCode>
         <purchaseTotals>
            <currency>USD</currency>
            <grandTotalAmount>5</grandTotalAmount>
         </purchaseTotals>
         <recurringSubscriptionInfo>
            <subscriptionID>**MASKED**</subscriptionID>
         </recurringSubscriptionInfo>
         <ccAuthService run="true">
            <authType>AUTOCAPTURE</authType>
         </ccAuthService>
         <ccCaptureService run="true" />
      </requestMessage>
   </s:Body>
</s:Envelope>

Response:

HTTP/1.1 500 Internal Server Error
Server=Apache-Coyote/1.1
X-OPNET-Transaction-Trace=a2_79ec7399-e512-4ccd-b261-c1085012c3de
Strict-Transport-Security=max-age=31536000
X-Frame-Options=DENY
X-Content-Type-Options=nosniff
X-XSS-Protection=1; mode=block
v-c-response-time=1580829613
Content-Type=text/xml
Content-Length=773
Date=Tue, 04 Feb 2020 15:20:13 GMT
X-Cnection=close

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Timestamp-216660870"><wsu:Created>2020-02-04T15:20:13.702Z</wsu:Created></wsu:Timestamp></wsse:Security></soap:Header>
<soap:Body>
<soap:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:c="urn:schemas-cybersource-com:transaction-data-1.0">
<faultcode>soap:Client</faultcode>
<faultstring>
XML parse error.
</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

However, the same request works when subsequentAuth tag is removed from the request. Please suggest a fix.

Dominant language
PHP
Stars
60
Forks
59
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CyberSource/cybersource-sdk-php

All issues in CyberSource/cybersource-sdk-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.