Important: SOAP Toolkit Update

Available Environments

Java Prerequisites

C# Prerequisites

PHP Prerequisites

C++ Prerequisites

Java Migration Steps

Add these dependencies to the

pom.xml

file:

<dependencies>
  <dependency>
    <groupId>jakarta.xml.ws</groupId>
    <artifactId>jakarta.xml.ws-api</artifactId>
    <version>4.0.2</version>
  </dependency>
  <dependency>
    <groupId>com.sun.xml.ws</groupId>
    <artifactId>jaxws-rt</artifactId>
    <version>4.0.3</version>
    <scope>runtime</scope>
  </dependency>
  <dependency>
    <groupId>com.sun.xml.ws</groupId>
    <artifactId>jaxws-ri</artifactId>
    <version>4.0.3</version>
    <type>pom</type>
  </dependency>
  <dependency>
    <groupId>org.bouncycastle</groupId>
    <artifactId>bcprov-jdk15to18</artifactId>
    <version>1.78</version>
  </dependency>
  <dependency>
    <groupId>org.apache.santuario</groupId>
    <artifactId>xmlsec</artifactId>
    <version>4.0.3</version>
  </dependency>
</dependencies>

Add this plugin to the

pom.xml

file:

<build>
  <plugins>
    <plugin>
      <groupId>com.sun.xml.ws</groupId>
      <artifactId>jaxws-maven-plugin</artifactId>
      <version>4.0.3</version>
      <configuration>
	  <wsdlUrls>
           <wsdlUrl>https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_1.219.wsdl</wsdlUrl>
        </wsdlUrls>
        <keep>true</keep>
        <packageName>com.cybersource.stub</packageName>
        <sourceDestDir>src/main/java</sourceDestDir>
      </configuration>
    </plugin>
  </plugins>
</build>

Check the value that is set in the

wsdlUrl

tag, and update the version if necessary. The latest version of the WSDL that can be supported is 1.219.

Run this command in your terminal:

mvn clean jaxws:wsimport

Find these lines in your existing code:

TransactionProcessorLocator service = new 
    TransactionProcessorLocator();

URL endpoint = new URL(SERVER_URL);

ITransactionProcessorStub stub = 
    (ITransactionProcessorStub) service.getportXML
    (endpoint);

stub._setProperty(WSHandlerConstants.USER, request
    .getMerchantID());

Replace them with these lines:

TransactionProcessor service = new TransactionProcessor();

service.setHandlerResolver(portInfo - >{
  List < Handler > handlerList = new ArrayList < >();
  handlerList.add(new BinarySecurityTokenHandler());
  return handlerList;
});

ITransactionProcessor stub = service.getPortXML();

Copy these files to your project directory:

BinarySecurityTokenHandler.java
PropertiesUtil.java
SecurityUtil.java

Add a

toolkit.properties

file in the

src/main/resources

folder in your project. The

toolkit.properties

file must contain this content:

MERCHANT_ID = <your_merchant_id>
LIB_VERSION = 4.0.3
KEY_ALIAS = <your_certificate_key_alias>
KEY_FILE = <your_certificate_file>
KEY_PASS = <your_certificate_password>
KEY_DIRECTORY = src/main/resources

If you want to use your own properties file, you can make these changes in the

PropertiesUtil.java

file.

Add your P12 certificate to your key directory.

Run these commands in your terminal:

mvn clean install

java -jar target\JavaSoapToolkit.jar

(Optional) You can confirm that your configuration is updated successfully by checking that your request was authenticated using a Bearer token. To confirm, add this command after line 54 in the

src\main\java\com\cybersource\BinarySecurityTokenHandler.java

file:

System.out.println( soapMessageContext ); 

C# Migration Steps

Add the following service URL as a service reference to your project:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_N.NNN.wsdl

where

N.NNN

is the latest server API version.

This will generate a Connected Services section in your project. It will also generate an

app.config

file for your project.

Add the following sections to the top of your

app.config

file:

<configuration>
   <configSections>
      <section name="toolkitProperties" type="System.Configuration.NameValueSectionHandler"/>
   </configSections>

   <toolkitProperties>
      <add key="MERCHANT_ID" value="<your_merchant_id>"/>
      <add key="KEY_ALIAS" value="<your_certificate_key_alias>"/>
      <add key="KEY_FILE" value="<your_certificate_file>"/>
      <add key="KEY_PASS" value="<your_certificate_password>"/>
      <add key="KEY_DIRECTORY" value="<path/to/certificate/file>"/>
   </toolkitProperties>
</configuration>

The

<configSections>

tag must be the first section inside

<configurations>

.

In the generated

app.config

file, leave the

<binding>

section as it is.

The

<binding>

section must look like this:

<bindings>
   <basicHttpBinding>
         <binding name="ITransactionProcessor">
         <security mode="Transport"/>
         </binding>
   </basicHttpBinding>
</bindings>

Add this dependency to the

packages.config

file:

<packages>
   <package id="Portable.BouncyCastle" version="1.9.0" targetFramework="net472" />
</packages>

Install the dependency:

nuget install packages.config -OutputDirectory packages

Add this package reference to your

.csproj

file:

<Reference Include="BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942, processorArchitecture=MSIL">
   <HintPath>packages\Portable.BouncyCastle.1.9.0\lib\net40\BouncyCastle.Crypto.dll</HintPath>
</Reference>

The steps for adding a new dependency can also be done through Visual Studio Package Manager.

Add your P12 certificate to the

KEY_DIRECTORY

.

This

KEY_DIRECTORY

location must be accessible to your code. Ensure that your code has permission to read this location.

Copy these files to your project directory and import them to your project:

CertificateCacheUtility.cs
InspectorBehavior.cs
PropertiesUtility.cs
SecurityUtility.cs
SoapEnvelopeUtility.cs

Find these lines in your existing code:

TransactionProcessorClient proc = new TransactionProcessorClient();

proc.ChannelFactory.Credentials.UserName.UserName =  request.merchantID;
proc.ChannelFactory.Credentials.UserName.Password =  TRANSACTION_KEY;

ReplyMessage reply = proc.runTransaction(request);

Replace them with these lines:

TransactionProcessorClient proc = new TransactionProcessorClient();

proc.Endpoint.EndpointBehaviors.Add(new InspectorBehavior());

ReplyMessage reply = proc.runTransaction(request);

Find your installation of .NET Framework.

This is often located at one of these locations:

C:\Windows\Microsoft.NET\Framework\v4.0.30319
(32-bit)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
(64-bit)

Use

msBuild.exe

to compile your project.

<path_to_framework>\msBuild.exe <name_of_project>.csproj

Run the project executable:

bin\<configuration>\<project_name>.exe

(Optional) You can confirm that your configuration is updated successfully by checking that your request was authenticated using a Bearer token. To confirm, add this command after line 59 in the

CSharpSoapToolkit\InspectorBehavior.cs

file:

Console.WriteLine(request.ToString()); 

PHP Migration Steps

Update the following service URL (

WSDL_URL

) in your code:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_N.NNN.wsdl

N.NNN

is the latest server API version.

Copy these files to your project directory:

ExtendedClientWithToken.php
PropertiesUtility.php
SecurityUtility.php

Locate these lines in your existing code:

$soapClient = new ExtendedClient(WSDL_URL, array());

Replace them with these lines:

$soapClient = new ExtendedClientWithToken(
    WSDL_URL,
    array(
        'SSL' => array(
                'KEY_ALIAS' => 'YOUR KEY ALIAS',
                'KEY_FILE' => 'YOUR CERTIFICATE FILE',
                'KEY_PASS' => 'YOUR KEY PASS',
                'KEY_DIRECTORY' => 'PATH TO CERTIFICATES'
            )
        )
);

Update the necessary values for these fields in your code:

MERCHANT_ID
KEY_ALIAS
KEY_FILE
KEY_PASS
KEY_DIRECTORY

Add your P12 certificate to the

KEY_DIRECTORY

.

This

KEY_DIRECTORY

location must be accessible to your code. Ensure that your code has permission to read this location.

Run the code:

php <sample_PHP_file>

(Optional) You can confirm that your configuration is updated successfully by confirming that your request was authenticated using a Bearer token. To confirm, add this command after line 109 in the

ExtendedClientWithToken.php

file:

print_r($request);

C++ Migration Steps

Update your existing Makefile.

Change the

cybsdemo

target from:

cybsdemo:     sample.cpp $(SOAPH) $(SOAPCPP) ../gsoap/dom.cpp wsseapi.o smdevp.o
		$(CPP) $(CFLAGS) -o cybsdemo sample.cpp soapC.cpp soapClient.cpp ../gsoap/dom.cpp $(SOAPCPP) wsseapi.o smdevp.o $(LIBS)

To:

cybsdemo:	sample.cpp $(SOAPH) $(SOAPCPP) ../gsoap/dom.cpp wsseapi.o smdevp.o
		$(CPP) $(CFLAGS) -o cybsdemo sample.cpp soapC.cpp ../gsoap/dom.cpp stdsoap2.cpp ../gsoap/import/custom/struct_timeval.cpp ../gsoap/plugin/threads.c ../gsoap/plugin/mecevp.c ../gsoap/plugin/wsaapi.c wsseapi.o smdevp.o soapITransactionProcessorProxy.cpp ../gsoap/import/gsoapWinInet.cpp PropertiesUtil.cpp BinarySecurityTokenHandler.cpp $(LIBS)

If you do not have an existing Makefile, you can use one of the following Makefiles:

UnixBuildAllCommented.Makefile
UnixQuickBuild.Makefile
WindowsBuildAllCommented.Makefile
WindowsQuickBuild.Makefile

Cybersource

recommends that you use UnixBuildAllCommented.Makefile or WindowsBuildAllCommented.Makefile. If you need to make changes to individual targets,

Cybersource

recommends that you use UnixQuickBuild.Makefile or WindowsQuickBuild.Makefile, as each target can be built individually.

CyberSourceTransaction WSDL and XSD version 1.224 are available here:

CyberSourceTransaction_1.224.wsdl
CyberSourceTransaction_1.224.xsd

If you want to use a different version, download your preferred version to the project directory and update the versions in the

header

target of your makefile. For example, change:

header:	CyberSourceTransaction_1.224.wsdl
		$(GWSDL) -t ../gsoap/WS/WS-typemap.dat -s -o cybersource.h CyberSourceTransaction_1.224.wsdl

to:

header:	CyberSourceTransaction_1.219.wsdl
		$(GWSDL) -t ../gsoap/WS/WS-typemap.dat -s -o cybersource.h CyberSourceTransaction_1.219.wsdl

Add gsoap to the compile path. You can do this by using one of these methods:

Copy the gsoap directory, including the header files, to one level above the project directory.
Update all paths in the Makefile that reference 'gsoap' to point to where gsoap is located.

Update your sample.cpp file to match your test credentials:

const char *MERCHANT_ID = "your_merchant_id";
const char *TRANSACTION_KEY = "your_transaction_key";

If you do not have an existing sample.cpp file, you can use the version that is provided here: sample.cpp.

If you are using an existing sample.cpp file from a previous C++ SOAP Toolkit, you must refer to all "upgrading from previous versions" comments throughout sample.cpp to see what has changed.

Include these new source files in your project:

BinarySecurityTokenHandler.cpp
BinarySecurityTokenHandler.h
PropertiesUtil.cpp
PropertiesUtil.h
stdsoap2.cpp
stdsoap2.h

Edit the toolkit.properties configuration file to match your test credentials:

MERCHANT_ID=
KEY_ALIAS=
KEY_FILE=
KEY_PASS=
KEY_DIRECTORY=

The toolkit.properties configuration file is read from the same location as the executable at run time.

You must make sure that there are no spaces at the start and end of the lines, or either side of

=

.

Run this command in your terminal:

make header

This generates the cybersource.h file.

Insert this text in the Import section of cybersource.h:

#import "WS-Header.h"

Run this command in your terminal:

make source

This generates these files:

soapITransactionProcessorProxy.cpp
soapITransactionProcessorProxy.h
ITransactionProcessor.runTransaction.req.xml
ITransactionProcessor.runTransaction.res.xml
ITransactionProcessor.nsmap
soapStub.h
soapH.h
soapC.cpp

Run these commands in your terminal:

make wsseapi.o
make smdevp.o
make cybsdemo 

This generates the cybsdemo.exe executable.

Add your P12 certificate to the

KEY_DIRECTORY

.

Run the cybsdemo.exe executable in your terminal.

A successful console output consists of the

keyFile

full path, followed by the response from the web service and no errors. For example:

keyFile full path: C:/keys/test_p12_file.p12
decision = APPROVED
reasonCode = 0
requestID = 6017349752184504643266
requestToken = Axxd6DCgJoj77wSTjm5pe7DwFPfjpNDMyadDIZ/u1Pfje7D9IGU1ogwAGkmXoDc3JoZmTToZDIAAvxSz
ccAuthReply.reasonCode = 0

Java Implementations

Change your communication protocol from HTTP (port 80) to HTTPS (port 443)

Non-Java Implementations

Rewrite your code to use the REST API using the REST SDK.
Rewrite your code to use the Simple Order API using the SO SDK.
If you are using C++ or C#, we have provided sample code that enables you to minimize the transition between SCMP to SO. See: Enable SCMP to SO Conversions For Non-Java Clients.

Prerequisites

Establish the Simple Order Payload Conversion

Add the SCMP sample client program to your payment system. These files can be found in the GitHub resource referenced above.
Update the
app.config
file. The following list is of values must be updated:
merchantID
: Set this to your production merchant ID used for commerce.
keysDirectory
: The file path to the P12 certificate generated previously.
password
: The P12 certificate password.
keyAlias
: The name of your MID.
Other values may be set at your discretion. Use the comments within the file to determine which values you wish to change.
After the SCMP payment software creates a request payload, run the
processRequest
method found in the
Util.cs
file against that payload.
This method converts the SCMP payload into an Simple Order payload and forwards the Simple Order payload to the correct Simple Order endpoint. When the Simple Order reply payload is received, the method will then convert the payload back into an SCMP payload for normal processing within the system.

Prerequisites

Java Migration Steps

Add these dependencies to the

pom.xml

file:

<dependencies>
  <dependency>
    <groupId>jakarta.xml.ws</groupId>
    <artifactId>jakarta.xml.ws-api</artifactId>
    <version>4.0.2</version>
  </dependency>
  <dependency>
    <groupId>com.sun.xml.ws</groupId>
    <artifactId>jaxws-rt</artifactId>
    <version>4.0.3</version>
    <scope>runtime</scope>
  </dependency>
  <dependency>
    <groupId>com.sun.xml.ws</groupId>
    <artifactId>jaxws-ri</artifactId>
    <version>4.0.3</version>
    <type>pom</type>
  </dependency>
  <dependency>
    <groupId>org.bouncycastle</groupId>
    <artifactId>bcprov-jdk15to18</artifactId>
    <version>1.78</version>
  </dependency>
  <dependency>
    <groupId>org.apache.santuario</groupId>
    <artifactId>xmlsec</artifactId>
    <version>4.0.3</version>
  </dependency>
</dependencies>

Add this plugin to the

pom.xml

file:

<build>
  <plugins>
    <plugin>
      <groupId>com.sun.xml.ws</groupId>
      <artifactId>jaxws-maven-plugin</artifactId>
      <version>4.0.3</version>
      <configuration>
	  <wsdlUrls>
           <wsdlUrl>https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_1.219.wsdl</wsdlUrl>
        </wsdlUrls>
        <keep>true</keep>
        <packageName>com.cybersource.stub</packageName>
        <sourceDestDir>src/main/java</sourceDestDir>
      </configuration>
    </plugin>
  </plugins>
</build>

Check the value that is set in the

wsdlUrl

tag, and update the version if necessary. The latest version of the WSDL that can be supported is 1.219.

Run this command in your terminal:

mvn clean jaxws:wsimport

Find these lines in your existing code:

TransactionProcessorLocator service = new 
    TransactionProcessorLocator();

URL endpoint = new URL(SERVER_URL);

ITransactionProcessorStub stub = 
    (ITransactionProcessorStub) service.getportXML
    (endpoint);

stub._setProperty(WSHandlerConstants.USER, request
    .getMerchantID());

Replace them with these lines:

TransactionProcessor service = new TransactionProcessor();

service.setHandlerResolver(portInfo - >{
  List < Handler > handlerList = new ArrayList < >();
  handlerList.add(new BinarySecurityTokenHandler());
  return handlerList;
});

ITransactionProcessor stub = service.getPortXML();

Copy these files to your project directory:

BinarySecurityTokenHandler.java
PropertiesUtil.java
SecurityUtil.java

Add a

toolkit.properties

file in the

src/main/resources

folder in your project. The

toolkit.properties

file must contain this content:

MERCHANT_ID = <your_merchant_id>
LIB_VERSION = 4.0.3
KEY_ALIAS = <your_certificate_key_alias>
KEY_FILE = <your_certificate_file>
KEY_PASS = <your_certificate_password>
KEY_DIRECTORY = src/main/resources

If you want to use your own properties file, you can make these changes in the

PropertiesUtil.java

file.

Add your P12 certificate to your key directory.

Run these commands in your terminal:

mvn clean install

java -jar target\JavaSoapToolkit.jar

(Optional) You can confirm that your configuration is updated successfully by checking that your request was authenticated using a Bearer token. To confirm, add this command after line 54 in the

src\main\java\com\cybersource\BinarySecurityTokenHandler.java

file:

System.out.println( soapMessageContext ); 

C++ Prerequisites

Migration Steps

Update your existing Makefile.

Change the

cybsdemo

target from:

cybsdemo:     sample.cpp $(SOAPH) $(SOAPCPP) ../gsoap/dom.cpp wsseapi.o smdevp.o
		$(CPP) $(CFLAGS) -o cybsdemo sample.cpp soapC.cpp soapClient.cpp ../gsoap/dom.cpp $(SOAPCPP) wsseapi.o smdevp.o $(LIBS)

To:

cybsdemo:	sample.cpp $(SOAPH) $(SOAPCPP) ../gsoap/dom.cpp wsseapi.o smdevp.o
		$(CPP) $(CFLAGS) -o cybsdemo sample.cpp soapC.cpp ../gsoap/dom.cpp stdsoap2.cpp ../gsoap/import/custom/struct_timeval.cpp ../gsoap/plugin/threads.c ../gsoap/plugin/mecevp.c ../gsoap/plugin/wsaapi.c wsseapi.o smdevp.o soapITransactionProcessorProxy.cpp ../gsoap/import/gsoapWinInet.cpp PropertiesUtil.cpp BinarySecurityTokenHandler.cpp $(LIBS)

If you do not have an existing Makefile, you can use one of the following Makefiles:

UnixBuildAllCommented.Makefile
UnixQuickBuild.Makefile
WindowsBuildAllCommented.Makefile
WindowsQuickBuild.Makefile

Cybersource

recommends that you use UnixBuildAllCommented.Makefile or WindowsBuildAllCommented.Makefile. If you need to make changes to individual targets,

Cybersource

recommends that you use UnixQuickBuild.Makefile or WindowsQuickBuild.Makefile, as each target can be built individually.

CyberSourceTransaction WSDL and XSD version 1.224 are available here:

CyberSourceTransaction_1.224.wsdl
CyberSourceTransaction_1.224.xsd

If you want to use a different version, download your preferred version to the project directory and update the versions in the

header

target of your makefile. For example, change:

header:	CyberSourceTransaction_1.224.wsdl
		$(GWSDL) -t ../gsoap/WS/WS-typemap.dat -s -o cybersource.h CyberSourceTransaction_1.224.wsdl

to:

header:	CyberSourceTransaction_1.219.wsdl
		$(GWSDL) -t ../gsoap/WS/WS-typemap.dat -s -o cybersource.h CyberSourceTransaction_1.219.wsdl

Add gsoap to the compile path. You can do this by using one of these methods:

Copy the gsoap directory, including the header files, to one level above the project directory.
Update all paths in the Makefile that reference 'gsoap' to point to where gsoap is located.

Update your sample.cpp file to match your test credentials:

const char *MERCHANT_ID = "your_merchant_id";
const char *TRANSACTION_KEY = "your_transaction_key";

If you do not have an existing sample.cpp file, you can use the version that is provided here: sample.cpp.

If you are using an existing sample.cpp file from a previous C++ SOAP Toolkit, you must refer to all "upgrading from previous versions" comments throughout sample.cpp to see what has changed.

Include these new source files in your project:

BinarySecurityTokenHandler.cpp
BinarySecurityTokenHandler.h
PropertiesUtil.cpp
PropertiesUtil.h
stdsoap2.cpp
stdsoap2.h

Edit the toolkit.properties configuration file to match your test credentials:

MERCHANT_ID= 
KEY_ALIAS= 
KEY_FILE= 
KEY_PASS= 
KEY_DIRECTORY=

The toolkit.properties configuration file is read from the same location as the executable at run time.

You must make sure that there are no spaces at the start and end of the lines, or either side of

=

.

Run this command in your terminal:

make header

This generates the cybersource.h file.

Insert this text in the Import section of cybersource.h:

#import "WS-Header.h"

Run this command in your terminal:

make source

This generates these files:

soapITransactionProcessorProxy.cpp
soapITransactionProcessorProxy.h
ITransactionProcessor.runTransaction.req.xml
ITransactionProcessor.runTransaction.res.xml
ITransactionProcessor.nsmap
soapStub.h
soapH.h
soapC.cpp

Run these commands in your terminal:

make wsseapi.o
make smdevp.o
make cybsdemo 

This generates the cybsdemo.exe executable.

Add your P12 certificate to the

KEY_DIRECTORY

.

Run the cybsdemo.exe executable in your terminal.

A successful console output consists of the

keyFile

full path, followed by the response from the web service and no errors. For example:

keyFile full path: C:/keys/test_p12_file.p12
decision = APPROVED
reasonCode = 0
requestID = 6017349752184504643266
requestToken = Axxd6DCgJoj77wSTjm5pe7DwFPfjpNDMyadDIZ/u1Pfje7D9IGU1ogwAGkmXoDc3JoZmTToZDIAAvxSz
ccAuthReply.reasonCode = 0

Prerequisites

PHP Prerequisites

Migration Steps

Add the following service URL as a service reference to your project:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_N.NNN.wsdl

where

N.NNN

is the latest server API version.

This will generate a Connected Services section in your project. It will also generate an

app.config

file for your project.

Add the following sections to the top of your

app.config

file:

<configuration>
   <configSections>
      <section name="toolkitProperties" type="System.Configuration.NameValueSectionHandler"/>
   </configSections>

   <toolkitProperties>
      <add key="MERCHANT_ID" value="<your_merchant_id>"/>
      <add key="KEY_ALIAS" value="<your_certificate_key_alias>"/>
      <add key="KEY_FILE" value="<your_certificate_file>"/>
      <add key="KEY_PASS" value="<your_certificate_password>"/>
      <add key="KEY_DIRECTORY" value="<path/to/certificate/file>"/>
   </toolkitProperties>
</configuration>

The

<configSections>

tag must be the first section inside

<configurations>

.

In the generated

app.config

file, leave the

<binding>

section as it is.

The

<binding>

section must look like this:

<bindings>
   <basicHttpBinding>
         <binding name="ITransactionProcessor">
         <security mode="Transport"/>
         </binding>
   </basicHttpBinding>
</bindings>

Add this dependency to the

packages.config

file:

<packages>
   <package id="Portable.BouncyCastle" version="1.9.0" targetFramework="net472" />
</packages>

Install the dependency:

nuget install packages.config -OutputDirectory packages

Add this package reference to your

.csproj

file:

<Reference Include="BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942, processorArchitecture=MSIL">
   <HintPath>packages\Portable.BouncyCastle.1.9.0\lib\net40\BouncyCastle.Crypto.dll</HintPath>
</Reference>

The steps for adding a new dependency can also be done through Visual Studio Package Manager.

Add your P12 certificate to the

KEY_DIRECTORY

.

This

KEY_DIRECTORY

location must be accessible to your code. Ensure that your code has permission to read this location.

Copy these files to your project directory and import them to your project:

CertificateCacheUtility.cs
InspectorBehavior.cs
PropertiesUtility.cs
SecurityUtility.cs
SoapEnvelopeUtility.cs

Find these lines in your existing code:

TransactionProcessorClient proc = new TransactionProcessorClient();

proc.ChannelFactory.Credentials.UserName.UserName =  request.merchantID;
proc.ChannelFactory.Credentials.UserName.Password =  TRANSACTION_KEY;

ReplyMessage reply = proc.runTransaction(request);

Replace them with these lines:

TransactionProcessorClient proc = new TransactionProcessorClient();

proc.Endpoint.EndpointBehaviors.Add(new InspectorBehavior());

ReplyMessage reply = proc.runTransaction(request);

Find your installation of .NET Framework.

This is often located at one of these locations:

C:\Windows\Microsoft.NET\Framework\v4.0.30319
(32-bit)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
(64-bit)

Use

msBuild.exe

to compile your project.

<path_to_framework>\msBuild.exe <name_of_project>.csproj

Run the project executable:

bin\<configuration>\<project_name>.exe

(Optional) You can confirm that your configuration is updated successfully by checking that your request was authenticated using a Bearer token. To confirm, add this command after line 59 in the

CSharpSoapToolkit\InspectorBehavior.cs

file:

Console.WriteLine(request.ToString()); 

PHP Prerequisites

PHP Migration Steps

Update the following service URL (

WSDL_URL

) in your code:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/CyberSourceTransaction_N.NNN.wsdl

N.NNN

is the latest server API version.

Copy these files to your project directory:

ExtendedClientWithToken.php
PropertiesUtility.php
SecurityUtility.php

FInd these lines in your existing code:

$soapClient = new ExtendedClient(WSDL_URL, array());

Replace them with these lines:

$soapClient = new ExtendedClientWithToken(
    WSDL_URL,
    array(
        'SSL' => array(
                'KEY_ALIAS' => 'YOUR KEY ALIAS',
                'KEY_FILE' => 'YOUR CERTIFICATE FILE',
                'KEY_PASS' => 'YOUR KEY PASS',
                'KEY_DIRECTORY' => 'PATH TO CERTIFICATES'
            )
        )
);

Update the necessary values for these fields in your code:

MERCHANT_ID
KEY_ALIAS
KEY_FILE
KEY_PASS
KEY_DIRECTORY

Add your P12 certificate to the

KEY_DIRECTORY

.

This

KEY_DIRECTORY

location must be accessible to your code. Ensure that your code has permission to read this location.

Run the code:

php <sample_PHP_file>

(Optional) You can confirm that your configuration is updated successfully by confirming that your request was authenticated using a Bearer token. To confirm, add this command after line 109 in the

ExtendedClientWithToken.php

file:

print_r($request);

RM-32750

Description

There was an error in processing a transaction because the amount field (CP01 - TCR9) in the TC33 file could not accommodate the value, as it exceeded the field's 8-digit limit. We have updated our system to prevent such an error from occuring again.

Audience

SMCC DCC acquirers and other VPC Japan acquirers.

Benefit

This update improves the reliability and accuracy of the batching process, reducing the likelihood of missed transactions and ensuring smoother operations.

Technical Details

None.

Important Dates

Released to Production January 21, 2024.

Payments

| EPS-30773

Description

Voided transactions performed soon after the batching time might still be batched, despite receiving confirmation that the void occurred in the API Response.

Audience

Merchants using Visa Platform Connect and GPX processors for payment transactions.

Technical Details

Merchants should see the error DNOTVOIDABLE rather than SOK when the void call was performed close to the daily set batching time.

Workaround

Perform void calls before the set batching time setup for your merchant ID during the boarding of your account to prevent any overlap.

Payments

| EPS-30820

Description

An intermittent DINVALIDATA error is sometimes returned in the

ics_bill

(settlement) call rather than during the

ics_auth

(authorization) call.

Audience

Merchants who use Visa Platform Connect for payment transactions.

Technical Details

None.

Workaround

If this scenario occurs, perform an authorization reversal to remove the ring fencing of the funds induced by the generation of the authorization code by the issuer. Prompt your customer to enter a valid value based on our documented validations. The addition of restrictions in your checkout page will also assist in preventing this scenario.

REST API

| EPS-30637

Description

A defect is causing the

consumerAuthenticationInformation.token

field to be returned in the

processorInformation

object instead of the

consumerAuthentication

object.

Audience

Merchants using the REST API.

Technical Details

None.

Workaround

None.

Invoicing

| EPS-30538

Description

When an invoice has been partially paid at least once, the remaining balance provided within the webhook response might not return a correct value.

Audience

Merchants using invoicing.

Technical Details

None.

Workaround

Real-time data is available in the Business Center's Invoicing and Reporting pages to help you track the payment status of orders processed using invoicing.

Payment

| EPS-30491

Description

Merchants using digital payments such as Apple Pay and Google Pay, in conjunction with Discover or Diners Club cards will see the following error:

DINVALIDDATA "Unsupported ECI type. e_commerce_indicator=DIPB"

.

Audience

Merchants processing Discover or Diners Club card transactions using Vantiv on Visa Platform Connect.

Technical Details

Our implementation with Vantiv is preventing the usage of the

e_commerce_indicator

value

dipb

, indicating the passing of a cryptogram from an authenticated transaction.

Workaround

You can replace the value

dipb

with the value

internet

to bypass the current validation. However, you risk losing the liability shift and incurring increased rejections downstream.

API Testing

| EPS-30041

Description

The API testing trigger 5001.00, which tests AVS response codes, is not producing the correct responses for Discover cards.

Audience

Global.

Technical Details

The test amount of 5001.00 should trigger a processor response of

processorInformation.avs.code=Y

. Instead, it is returning

processorInformation.avs.code=A

.

Workaround

None.

Business Center

| EPS-30657

Description

Some users logging into the Business Center's testing environment are not receiving the One-Time Password if it is sent using SMS.

Audience

Users of the Business Center's testing environment.

Technical Details

None.

Workaround

You can use email instead of SMS.

Reporting

|

EPS-30677

Description

When you use the REST API

GET reporting/v3/reports

request to query the

reportName

parameter, and the length of the report name is too long, the affected report is not returned in the response.

If the query parameter

reportName

is not specified, then it does successfully return the report details.

Audience

Users of the Reporting REST API.

Technical Details

None.

Workaround

Merchants can omit the

reportName

query parameter in the API call or recreate the report with a shorter name.

Merchant Boarding

| EPS-30718

Description

Resellers are currently unable to enable Secure Acceptance for new merchant accounts.

Audience

Resellers.

Technical Details

None.

Workaround

None.

Payments

|

EPS-30784

Description

An intermittent error sometimes prevents transactions from being recorded in the Business Center even though a response was received by the merchants. In some cases, this can result in the cardholder being charged twice.

Audience

Merchants using the Cielo and Rede processors in Latin America.

Technical Details

None.

Workaround

None.

Transaction Search and Details

|

EPS-30810

Description

Some resellers are experiencing slow loading or timeouts in the Business Center's testing environment when using the Transaction Search and Transaction Details pages.

Audience

Resellers.

Technical Details

None.

Workaround

None.

Reporting

| RITM18309968

Description

An intermittent issue can cause the Purchase and Refund report to display duplicate rows.

Audience

Merchants who use the Purchase and Refund report.

Technical Details

None.

Workaround

None.

Payments

| 1694196

Description

Due to an intermittent issue, credit authorizations (online credit) might be processed as standard credits (offline credit). This issue can affect compliance in some mandated regions.

Audience

Merchants who use credit authorizations to refund customers.

Technical Details

None.

Workaround

None.

Payments

| RITM18769444

Description

Due to an intermittent issue, when merchants on the GetNet gateway cancel a credit using the Cancel Transaction API, an internal error sometimes occurs.

Audience

Users of the Cancel Transaction API on the GetNet gateway.

Technical Details

None.

Workaround

None.

Fraud Management Essentials

| 1672469

Description

Search results for Fraud Managerment Essentials in the Business Center are currently prevented from being exported.

Audience

Users of Fraud Management Essentials.

Technical Details

None.

Workaround

Try using the Reporting feature or copy and paste from the user interface.

Custom Roles on VAP

| 1641831

Description

When a reseller account uses the Visa Analytics Platform (VAP) to create a custom role for a merchant-level user, the role is not applied, and the user does not inherit the permissions for the custom role.

Audience

Users of VAP who use custom roles.

Technical Details

None.

Workaround

To add the custom role:

Navigate to the newly created account's user profile.
From the User Role drop-down menu, select CUSTOM.
Create the custom role.