DSmart SOAP Node

Make SOAP web service requests with authentication for DSmart services

Actions17

Overview

This node enables making authenticated SOAP web service requests specifically tailored for DSmart services. It supports various operations related to banking and payment systems, such as setting payment information, retrieving bank agreements, managing direct debits, and canceling payments.

A common use case is automating interactions with the DSmart online payment system, for example:

  • Submitting payment details to record a transaction.
  • Querying invoice or direct debit information.
  • Canceling payments or direct debit agreements.

By allowing custom SOAP envelopes with dynamic variable injection, it provides flexibility to adapt to different SOAP operations and payloads within the DSmart ecosystem.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests are sent. Default points to the DSmart online payment WSDL.
Authentication Source Method to provide authentication credentials: either "Use Credentials" (from stored API credentials) or "Manual Input" (enter username and password directly).
Authentication When using manual input, this collection holds the username and password for SOAP authentication.
SOAP Envelope The full SOAP envelope XML string to send in the request body. Supports placeholders like {{username}}, {{password}}, and other variables that get replaced dynamically per execution. This allows customizing the SOAP request for each operation.

For the SetPayment operation, the default SOAP envelope includes these variables (used as placeholders):

  • username: Authentication username.
  • password: Authentication password.
  • bankCode: Bank code (default "24").
  • subscriberNo: Subscriber number (optional).
  • invoiceNo: Invoice number (optional).
  • paymentAmount: Amount paid (optional).
  • paymentDate: Date of payment (defaults to current date).
  • bankRefNo: Bank reference number (optional).
  • bankBranchNo: Bank branch number (optional).
  • paymentChannel: Payment channel (default "Internet Banking").

Output

The node outputs an array of items where each item contains:

  • json.response: Parsed JSON object representing the SOAP response result specific to the invoked operation.
  • json.rawResponse: Raw XML response string from the SOAP service.
  • json.statusCode: HTTP status code returned by the SOAP service.
  • json.statusText: HTTP status text message.

If an error occurs and "Continue On Fail" is enabled, the output will include:

  • json.error: Error message.
  • json.statusCode: HTTP status code if available.
  • json.statusText: HTTP status text if available.
  • json.rawResponse: Raw response data if available.

The node does not output binary data.

Dependencies

  • Requires access to the DSmart SOAP web service endpoint.
  • Needs valid authentication credentials either via stored API credentials or manual username/password input.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses into JSON.

Troubleshooting

  • Authentication errors: Ensure correct username and password are provided either via credentials or manual input. Incorrect credentials will cause SOAP faults.
  • Timeouts: The node has a 30-second timeout for SOAP requests; slow network or service issues may cause timeouts.
  • Malformed SOAP envelope: The SOAP envelope must be well-formed XML and correctly use placeholders for variables. Invalid XML or missing required fields can cause errors.
  • Unexpected response structure: If the SOAP response format changes or differs from expected, parsing may fail or return empty results.
  • Network errors: Verify the SOAP service URL is reachable and correct.

To resolve errors, check the raw SOAP response (rawResponse) in the output for detailed fault messages from the service.

Links and References

Discussion