The Name-Value Pairs implementation relies on the .NET framework’s built in HTTP to SOAP translation layer. As a result, there are a few idiosyncracies that an integrator must be aware of when implementing using HTTPS.
1. The .NET framework is taking the HTTPS request and building a SOAP object using the fields that it receives.
2. As a result, regardless of whether or not a field’s VALUE is required, the field name must be sent along with the request.
3. Although this may seem counter intuitive, the .NET web service will simply build the SOAP object using only the fields that are passed to it.
4. If a field name is not included in the request, the SOAP object will be built without that parameter, thus resulting in an improperly formed SOAP object that will be rejected by the web service.
5. To avoid this, each field name must be sent even if you are not passing a value to the service. You must send the field EVEN if the API indicates that the field is not required, but send the field with a ‘NULL’ value. Eg; “CustomerName=”
6. Remember, the request MUST include all field names, but when deciding whether to send a value in a specific field you can rely on the API to indicate whether a specific field requires a value in order to return a valid result
When calling a service using HTTPS, you must also use a slightly different URL. This URL is displayed for each web service in the API under the heading ‘Service Location’. Please make sure that when implementing using Name-Value Pairs over HTTPS that you are sending the request to the URL labeld ‘For standard HTTPS connections’.
For additional detail regarding HTTPS GET or POST format, navigate to the service url labeled ‘For SOAP connections and scroll down to view properly formed GET and POST requests for each service.
Most integrators will only need to concern themselves with the ProcessCreditCard web service. However, if additional functionality is required, our web services have been labeled intuitively, and the functionality exposed in each service is implied in the title.
The API is broken up into categories according to functionality type to ease this further.
If you have any development specific questions, please contact our technical support center at the following email address:
Table of contents for test forms can be located at: https://<assigned domain>/ws/
<integration support email>