Configure notifications for Adobe Commerce

  Last updated: 

  Magento Commerce is now Adobe Commerce

The Trust Payments extension will continue to support both Magento Open Source and Adobe Commerce environments going forward. In our documentation, we will refer to this extension exclusively using the Adobe Commerce branding, but all instructions also apply when integrating using Magento Open Source.

Click here to learn more about Adobe Commerce.

 

  Unfortunately, the product documented here is currently only available in English.

 

  The following steps are only applicable when configuring the API solution (they are not applicable when configuring the Payment Pages solution).

Follow the steps provided below to configure and enable URL notifications in MyST, to ensure the Adobe Commerce extension is updated when transactions have been processed on your Trust Payments account. This updates the status of the order in Adobe Commerce.

  It is imperative that you follow and complete the steps described below when configuring the module. Failure to do so will prevent orders from being processed.

  1. Sign in to MyST.

  2. Search for your Trust Payments sitereference using the search box found at the top of the page.

  3. When viewing your site details, click “Rule manager“.

    webhook-2010-01-en.png

  4. Select the action type “URL notification” from the drop-down and your browser will be redirected.

    webhook-2010-02-en.png

  5. Create a new URL notification rule:

    Add new condition
    (A) Click “Add new condition” and specify the circumstances in which the URL notification is to be triggered following a transaction. Ensure the following options are ticked:

    webhook-2010-03-en.png
    • In the Accounts box displayed, ensure "ECOM" and "MOTO" are ticked.
    • In the Requests box displayed, ensure "ACCOUNTCHECK" and “AUTH” are ticked.
    • In the Error codes box displayed, ensure "0 - Ok" is ticked.
    • In the Settle statuses box displayed, ensure "not in" is selected in drop-down box and "3 - Cancelled" is ticked.

    Once saved, the condition will look like this in the Rule manager:

    AdobeNotificationSettingsCondition.png

    Add new action
    (B) Click “Add new action” and specify the endpoint for the URL notification.

    webhook-2010-03-en.png
    • Ensure the settings displayed are configured as follows:
      • Action name: <Specify a recognisable name>
      • Use site security details: NO
      • Security algorithm: sha256
      • Notification password: Provide a password to prevent your notifications from being modified by unauthorised users. This password must match the value saved in the Required settings section of Trust Payments payment method configuration page in the Adobe Commerce Store Admin, as documented in this article.
      • Pipe notification to browser: NO
      • Process notification: offline
      • Website address (URL): In this field, you must enter the following URL (replace <your_domain> with the domain where your extension is hosted):
        https://<your_domain>/securetrading/apisecuretrading/notificationresponse
      • Method: POST
    • We recommend that you include the following Fields as a minimum, but you can add more if you need to:
      • enrolled
      • errorcode
      • orderreference
      • paymenttypedescription
      • requestreference
      • settlestatus
      • sitereference
      • status
      • transactionreference

    Once saved, the action will look like this in the Rule manager:

    AdobeNotificationSettingsAction.png

    Add new rule
    (C) Using the drop-down boxes, assign the condition to the action and click “Create rule“.

    webhook-2010-03-en.png
  6. Ensure the rule is active (this is shown with a tick under the Active column). Once enabled, the rule will be applied to all payment sessions for the given sitereference, and the URL notification will be triggered whenever the condition specified is met. Once enabled, no further steps are needed.

      All new rules should be created on your test sitereference and tested to ensure they work as expected before being added to your live sitereference.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request