DSmart SOAP Node

Make SOAP web service requests with authentication for DSmart services

Actions17

Overview

The node enables making authenticated SOAP web service requests specifically for DSmart services. It supports multiple operations related to banking and payment management, such as setting payment cancellations, retrieving bank agreements, direct debit info, invoices, and more.

For the SetPaymentCancel operation, the node sends a SOAP request to cancel a payment by providing details like bank code, subscriber number, invoice number, and cancellation date. This is useful in scenarios where automated cancellation of payments is required within financial or billing workflows.

Practical examples:

  • Automatically cancel a payment when a refund is processed.
  • Integrate with DSmart's payment system to update payment statuses based on external triggers.
  • Manage payment cancellations programmatically without manual intervention.

Properties

Name Meaning
SOAP Service URL The URL endpoint of the SOAP web service to which requests are sent. Default is http://dstahsilat.dsmart.com.tr/DsmartOnlinePaymentSystem.asmx?WSDL.
Authentication Source How authentication credentials are provided: either using stored API credentials or manual input. Options: "Use Credentials", "Manual Input".
Authentication When manual input is selected, this collection allows entering the username and password for SOAP authentication.
SOAP Envelope The full SOAP envelope XML template for the request. Supports variable placeholders like {{username}}, {{password}}, and other parameters that get replaced dynamically. For SetPaymentCancel, it includes fields like bankCode, subscriberNo, invoiceNo, cancelDate, username, and password.

Output

The node outputs JSON data containing:

  • response: The parsed SOAP response body relevant to the executed operation (e.g., the result of SetPaymentCancel).
  • rawResponse: The raw XML response string from the SOAP service.
  • statusCode: HTTP status code of the SOAP request.
  • statusText: HTTP status text of the SOAP request.

This structured output allows downstream nodes to easily access both the parsed data and raw response for logging or further processing.

The node does not output binary data.

Dependencies

  • Requires an active internet connection to reach the specified SOAP service URL.
  • Needs valid authentication credentials either via stored API credentials or manual entry.
  • Uses the axios library for HTTP requests.
  • Uses the xml2js library to parse XML SOAP responses into JSON.

Troubleshooting

  • Common issues:

    • Incorrect SOAP Service URL or network connectivity problems can cause request failures.
    • Invalid or missing authentication credentials will lead to authentication errors.
    • Malformed SOAP envelope XML or incorrect variable substitutions may cause the SOAP service to reject the request.
    • Timeout errors if the SOAP service is slow or unresponsive (timeout set to 30 seconds).

  • Error messages:

    • Errors include HTTP status codes and messages from the SOAP service.
    • If the node is configured to continue on fail, error details are included in the output JSON under error.
    • To resolve errors, verify the SOAP URL, credentials, and ensure the SOAP envelope XML matches the expected format for the operation.

Links and References

Discussion