Introduction

Worldpay provides secured, scalable, and reliable payment processing services through Worldpay's Express payment processing platform.

Worldpay provides the following capabilities and benefits:

1. Credit Cards Payment
2. Debit Cards Payment
3. ACH payment (Bank account transfer)

Package features include:

1. Payment Services
   1. You can use this package to execute a payment transaction in your application process.
2. Max attempt control
   1. Limit the number of calls an application can make to Worldpay's Express platform.
3. Analytics Milestones and Segmentation
   1. This package includes pre-built Milestones to help analyze the success rate.
   2. This package includes pre-built Segment to help analyze the payment type (cards vs ACH).
4. Server and Client value objects
   1. This will help to use the results in an external service, for example, a enrollment application.
5. Detailed data and system errors
   1. This can be particularly useful as the service will block unnecessary calls if anything is missing or wrong.
   2. It will also provide detailed messaging to help fix the problem, either for the applicant in case of missing information, or the form builder in case of misconfiguration.
6. TAF + Maven support
7. Exchange regression suite - automating over 50 scenarios
   1. This helps us improve turn around time in case of defects fixes.
   2. It also helps us makes release new enhancements faster.

This package doesn't support multiple applicants. If the application is of multiple applicant nature, the total payment should be calculated and payed by one of the applicants.

This package is built on the Exchange Framework (TIF). It is used to develop integrations in Journey Manager in a more efficient, standardized and scalable manner to reduce the ongoing costs for upgrades and maintenance.

Licensing

Clients must ensure they are appropriately licensed in order to use this package. Organisations who wish to use this package are required to establish a commercial relationship with the 3rd party vendor directly.

Compatibility

This package has the following compatibility requirements:

Release Notes

Version 1.1 April 1, 2020

• Configuration service support.
• Added support for disabling milestone events optionally.

Version 1.0 Nov 14, 2019

• Baseline release.

Installation

Exchange Installation

This package should be installed as a single archive via the Temenos Marketplace. Once installed you should walk through the following procedure to ensure you complete any required configuration:

1. Review the documentation below for each of the imported services and make any adjustments necessary to service parameters.
2. Review the documentation below for any Service Connections and add your credentials as required.
3. Review the Help Doc tab for each of the imported services and make any required adjustments to service parameters.
4. Review the Service Connection requirements under the same Help Doc tab for each of the imported services and make any required configurations to the Service Connection. Service Connections can be configured in Transact Manager under the Services >> Service Connections menu item.
5. Installation of any included Maestro libraries requires you to login to you Maestro server and import them either into your organization (for global availability) or to your specific project.

Note: The default value of service parameters from this package, such as maxAttemptNumber will always override the value for existing service. After you reinstall or upgrade the package, make sure the service parameters value are suitable to your requirement.

Maven dependency

Note: Each service within this package must have Unified App Data enabled when building a form. Navigate to Forms > Form > Form Version and tick the Unified App Data checkbox.

How to trigger fluent functions in Narrator

Below is the example on how to trigger the fluent functions and provide input parameters in Form Narrative

{
  "name": "Worldpay Narrative",
  "version": "1.0.0",
  "pages": [
    {
      "name": "PaymentOptions",
      "allowGoBack": false,
      "allowSubmit": false,
      "preActions": [],
      "postActions": [],
      "nextPages": ["OtherPaymentOptions", "EFTOptions"]
    },
    {
      "name": "OtherPaymentOptions",
      "condition": "${ txn.formDataMap.get('FundingOptions') == 'other'  }",
      "allowGoBack": true,
      "allowSubmit": true,
      "preActions": [],
      "postActions": [],
      "nextPages": []
    },
    {
      "name": "EFTOptions",
      "allowGoBack": true,
      "allowSubmit": false,
      "condition": "${ txn.formDataMap.get('FundingOptions') == 'eft' || txn.formDataMap.get('FundingOptions') == ''  }",
      "preActions": [],
      "postActions": [],
      "nextPages": ["WorldpayACH", "WorldpayCardPaymentInfo"]
    },
    {
      "name": "WorldpayACH",
      "allowGoBack": true,
      "allowSubmit": false,
      "condition": "${ txn.formDataMap.get('EFTType') == 'CheckSale' || txn.formDataMap.get('EFTType') == ''  }",
      "preActions": [],
      "postActions": [],
      "nextPages": ["BillingAddressAch"]
    },
    {
      "name": "WorldpayCardPaymentInfo",
      "allowGoBack": true,
      "allowSubmit": false,
      "condition": "${ txn.formDataMap.get('EFTType') == 'TransactionSetup' }",
      "preActions": [],
      "postActions": [],
      "nextPages": ["WorldpayCardPayment"]
    },
    {
      "name": "WorldpayCardPayment",
      "allowGoBack": true,
      "allowSubmit": false,
      "condition": "${ txn.formDataMap.get('EFTType') == 'TransactionSetup' }",
      "preActions": [],
      "postActions": [],
      "formActions": [
        {
          "name": "Worldpay - Cards Payment",
          "version": "1.1.0",
          "alwaysProcess": "false"
        },
        {
          "name": "Worldpay - Cards Payment Verification",
          "version": "1.1.0",
          "alwaysProcess": "false"
        }
      ],
      "nextPages": ["NotComplete", "Complete"]
    },
    {
      "name": "BillingAddressAch",
      "condition": "true",
      "allowGoBack": true,
      "allowSubmit": false,
      "preActions": [],
      "postActions": [],
      "nextPages": ["AmountAch"]
    },
    {
      "name": "AmountAch",
      "allowGoBack": true,
      "allowSubmit": false,
      "preActions": [],
      "postActions": [
        {
          "name": "Worldpay - ACH Payment",
          "version": "1.1.0",
          "alwaysProcess": true,
          "condition": "${( txn.formDataMap.get('PaymentMethod') != 'Worldpay ACH Payment Method' ||
            ( !txn.propertyMap.get('Worldpay.Payment.ACH.'+txn.formDataMap.get('RoutingNumber')+'-'+txn.formDataMap.get('AccountNumber')+'.currentAttemptsLeft') ||
            (txn.propertyMap.get('Worldpay.Payment.ACH.'+txn.formDataMap.get('RoutingNumber')+'-'+txn.formDataMap.get('AccountNumber')+'.currentAttemptsLeft')?:'0').toInteger() > 0 ))}",
          "params": {
            "BillingName": "${txn.formDataMap.get('BillingName')}",
            "BillingAddress1": "${txn.formDataMap.get('BillingAddress1')}",
            "BillingZipcode": "${txn.formDataMap.get('BillingZipcode')}",
            "Amount": "${txn.formDataMap.get('Amount')}",
            "RoutingNumber": "${txn.formDataMap.get('RoutingNumber')}",
            "AccountNumber": "${txn.formDataMap.get('AccountNumber')}",
            "AccountType": "${txn.formDataMap.get('AccountType')}",
            "VerifiedByExternalSource": "${ (txn.formDataMap.get('OnlineAccountVerification') != 'Worldpay')?'external':'' }",
            "CheckType": "0",
          }
        }
      ],
      "nextPages": ["NotComplete", "Complete"]
    },
    {
      "name": "NotComplete",
      "condition": "${ txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == 'Setup' || txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == 'Error' || txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == 'False' || txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == 'Unknown' || txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == '' || txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') == null}",
      "allowGoBack": false,
      "allowSubmit": false,
      "preActions": [],
      "postActions": [],
      "nextPages": ["PaymentOptions"]
    },
    {
      "name": "Complete",
      "allowGoBack": false,
      "condition": "${ txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') != 'Setup' && txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') != 'Error' && txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') != 'False' && txn.propertyMap.get('Worldpay.Payment.Result.paymentStatus') != 'Unknown'}",
      "allowSubmit": true,
      "preActions": [],
      "postActions": [],
      "nextPages": []
    }
  ]
}

Below is an example of a form design that works with the above Form Narrative

High Level Diagram

Cards Payment

ACH Payment

Cards Payment Configuration

Maestro Assets

Use the following procedure to configure Worldpay - Cards Payment component in your form:

• Make sure the exchange-worldpay-taf Maestro library has been added to your Maestro project.
• In Maestro, place the Worldpay - Cards Payment component onto your form in the location you wish to use cards payment service.
• Select Worldpay - Cards Payment component, then from the Properties tab, select the Input Fields section. Next, click on Field References and map the form's actual payment fields the to predefined keys.
• Once the form is published, make sure you enable the Unified App Data as follows:
  • Navigate to Forms>Form>Form Version and tick the Unified App Data checkbox.

Using maestro components ACH Payment and Cards Payment in the same form will cause an XML duplicate binding warning. Ignore the warning and click Build.

Note: By default, the Maestro form will show an alert box when validation errors happen. Since the component already has the built-in fields to display various data errors, you can add the following Javascript on Form Load in your form to suppress the alert box.

    Form.serverValidationErrorHandler = function() {};

Journey Manager services

Use the following procedure to configure the Worldpay - Cards Payment service in your Journey Manager:

• Search for the Worldpay - Cards Payment service using the All Services page under the Services menu.
• Click the Worldpay - Cards Payment service in the search results to navigate to the service page.
• Click the Parameters Edit tab.
• Click the Edit Parameter link next to the Transaction Setup Configuration parameter to edit the ReturnURL parameter.
• The value of the ReturnURL parameter should point to an empty html file deployed in your Space. The only requirement of this parameter is to contain a URL to an empty file that exists in the same domain as the form.

ACH Payment Configuration

Maestro Assets

Use the following procedure to configure the Worldpay - ACH component in your form:

• Make sure the exchange-worldpay-taf Maestro library has been added to your Maestro project.
• In Maestro, place the Worldpay - ACH component onto your form in the location you wish to use the ACH payment service.
• Select the Worldpay - ACH component, then from the Properties tab, select Options. Then, select the "Show Error Messages" box if you want to use the built-in error messages.
• Once the form is published, make sure you enable the Unified App Data as follows:
  • Navigate to Forms>Form>Form Version and tick the Unified App Data checkbox.

This component doesn't trigger the related Worldpay - ACH Payment fluent function. The function is called as part of the narrative when the user clicks the Continue button since the service is typically configured as a post action. Therefore, the purpose of this component is to display the error and validation messages (if enabled).
It is recommended to use the component even if the messages are disabled, in which case developers can use the different fields inside the component to construct custom messages.

Using maestro components ACH Payment and Cards Payment in the same form will cause an XML duplicate binding warning. Ignore the warning and click Build.

Note: By default, the Maestro form will show an alert box when validation errors happen. Since the component already has the built-in fields to display various data errors, you can add the following Javascript on Form Load in your form to suppress the alert box.

    Form.serverValidationErrorHandler = function() {};

Max Attempt

This feature is intended to limit the number of calls to Worldpay API.

Configuration

1. Set the maxAttemptNumber to a positive number in the service parameter. The default value is 3.
2. If you don't want to apply any restriction, set it to -1. However, it is recommended to limit the number of calls.
3. If you want to alert the applicant to the number of attempts that are left, the number of attempts remaining display in both the JSON result and Data Field:attemptsLeft in the Maestro component.

Max Attempt Behaviour

• The maxAttemptNumber service parameter under the Worldpay - Cards Payment service will limit the number of calls to the Worldpay API from a single transaction.
• The maxAttemptNumber service parameter under the Worldpay - ACH Payment service will limit the number of calls to Worldpay API for each applicant account. If the maximum limit is reached for a particular account, the applicant can try another account.

Journey Analytics

Milestone events

Milestone events are automatically generated to show milestones on the User Journey view in Journey Analytics, the Journey Manager analytics tool.

Segment events

Segment events are automatically generated to offer further analytics on the User Journey view in Journey Analytics.

Note: Please make sure you've added the following segment name and valid values to the Journey Analytics segment whitelist before using this component.For more information, please refer to Journey Analytics Preferences

Service Txn properties/ Server VO

The table below describes Worldpay server VO fields stored in the Form XML Data and also stored in transaction properties.

Scheduled Jobs

The Worldpay - Cards Payment and Worldpay - ACH Payment services execute the payment transaction and return different values for the paymentStatus variable in Service Txn properties to indicate a successful transaction.
Upon successful call, the Worldpay - Cards Payment service will return a paymentStatus value Approved. However, depending on the configuration with Worldpay, a reconciliation process will run - typically within 24 hours- that will change the value of the transaction to Settled. Therefore, depending on the use case a job might need to be created and run to query and update the value of paymentStatus variable.
Similarly, upon successful call, the Worldpay - ACH Payment service will return a paymentStatus value Pending. Due to the nature of ACH processing, the status of ACH transactions will be updated over a period of several days. Therefore, depending on the use case a job might need to be created to frequently update the value of paymentStatus variable.
The status of the payment transaction for both payment methods can be determined by submitting a TransactionQuery request through the Express reporting interface. The request should include the ReferenceNumber parameter. The value of the ReferenceNumber variable should be obtained from the Server VO variable Worldpay.Payment.Result.referenceNumber.

Configuration Service Support

Create a service parameter keyMapping as below in your configuration service (service-def.json) if you haven't done so

    {
      "name": "keyMapping",
      "type": "String",
      "filePath": "json/keyMapping.json",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },

Note: You only need to create keyMapping service parameter once when you setup your first Exchange package. The rest of the Exchange package will just be keep adding content into the existing service parameter.

Create or append the following content into json/keyMapping.json

"worldpay": [
    {
      "serviceKey": "cards",
      "serviceName": "Worldpay - Cards Payment",
      "serviceParamKeyMap": {
        "recResInXml": "recordResponseInTxnXML",
        "recResInProp": "recordResponseInTxnProperties",
        "terminalConfig":"terminalConfiguration",
        "txnConfig":"transactionConfiguration",
        "accCredConfig":"accountCredentialsConfiguration",
        "appConfig":"applicationConfiguration",
        "txnSetConfig":"transactionSetupConfiguration"
      }
    },
    {
      "serviceKey": "ach",
      "serviceName": "Worldpay - ACH Payment",
      "serviceParamKeyMap": {
        "recResInXml": "recordResponseInTxnXML",
        "recResInProp": "recordResponseInTxnProperties",
        "terminalConfig":"terminalConfiguration",
        "txnConfig":"transactionConfiguration",
        "accCredConfig":"accountCredentialsConfiguration",
        "appConfig":"applicationConfiguration"
      }
    },
    {
      "serviceKey": "verify",
      "serviceName": "Worldpay - Cards Payment Verification ",
      "serviceParamKeyMap": {
        "recResInXml": "recordResponseInTxnXML",
        "recResInProp": "recordResponseInTxnProperties",
        "accCredConfig":"accountCredentialsConfiguration",
        "appConfig":"applicationConfiguration"
      }
    }
  ]

Copy the following service parameters definition in your configuration service (service-def.json) and set the proper values for your project.

 {
      "name": "worldpay-cards|1.1.0-conn.endpoint",
      "description": "Service connection Endpoint for Worldpay - Cards Payment service",
      "value": "https://certtransaction.elementexpress.com/",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-conn.username",
      "description": "Service connection Username for Worldpay - Cards Payment service",
      "value": "1051704",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-conn.password",
      "description": "Service connection password for Worldpay - Cards Payment service",
      "value": "874767386",
      "type": "Password",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-terminalConfig",
      "description": "Terminal configurations",
      "value": "TerminalID\u003d0001\r\nTerminalType\u003d2\r\nCardPresentCode\u003d3\r\nCardholderPresentCode\u003d7\r\nCardInputCode\u003d4\r\nCVVPresenceCode\u003d2\r\nTerminalCapabilityCode\u003d5\r\nTerminalEnvironmentCode\u003d6\r\nMotoECICode\u003d7\r\nCVVResponseType\u003d1\r\nConsentCode\u003d3\r\nTerminalSerialNumber\u003d\r\nTerminalEncryptionFormat\u003d0\r\nLaneNumber\u003d\r\nStoreCardID\u003d\r\nStoreCardPassword\u003d\r\nOperatorID\u003d",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-txnConfig",
      "description": "Transaction configurations",
      "value": "TransactionAmount\u003d\r\nReferenceNumber\u003d\r\nTicketNumber\u003d\r\nMarketCode\u003d3\r\nPartialApprovedFlag\u003d0\r\n\r\nDuplicateCheckDisableFlag\u003d1\r\nDuplicateOverrideFlag\u003d1\r\nMerchantSuppliedTransactionID\u003d\r\nPaymentType\u003d\r\nSubmissionType\u003d\r\nNetworkTransactionID\u003d\r\n\r\n\r\n\r\n\r\n",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-accCredConfig",
      "description": "AccountToken configuration ",
      "value": "AccountToken\u003d8331A712ECB527DEB0A51EFC8D3EDEE37470C415D92FE9658ACEF1B45439268D81891D01",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-appConfig",
      "description": "Application configurations. Id, name, and version.",
      "value": "ApplicationID\u003d10096\r\nApplicationName\u003dAvoka Test Application\r\nApplicationVersion\u003dBeta",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-txnSetConfig",
      "description": "Transaction setup configurations",
      "value": "TransactionSetupMethod\u003d1\r\nEmbedded\u003d0\r\nDevice\u003d2\r\nCVVRequired\u003d0\r\nAutoReturn\u003d1\r\nDeviceInputCode\u003d0\r\nCompanyName\u003dVault\r\nLogoURL\u003d\r\nWelcomeMessage\u003d\r\nTagline\u003d\r\nReturnURL\u003dhttps://exchange.avoka-transact.com/web-plugin/index.htm\r\nReturnURLTitle\u003dReturn to Vault\r\nOrderDetails\u003d\r\nProcessTransactionTitle\u003d\r\nCustomCss\u003d\r\n\r\n\r\n",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-customCSS",
      "description": "CSS configurations",
      "value": "body {\r\nfont-family: Arial; font-size: 12px; color: #000099;\r\nbackground-color: #FFFFFF;\r\n}\r\n.selectOption {\r\nfont-family:Arial;\r\n}\r\n.inputText {\r\nfont-family:Arial;\r\n}\r\n.buttonEmbedded:link {\r\ncolor: blue;\r\n}",
      "type": "String",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-enableHttpAudit",
      "description": "With HTTP auditing enabled, details about each HTTP request (including request and response data) are stored in a transaction property as a JSON array against the relevant transaction.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-disableMilestones",
      "description": "Whether to disable Journey Analytics milestones for this service.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-recResInProp",
      "description": "Record response as txn property.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-recResInXml",
      "description": "Record response in FisIdvVO and persisted in Txn XML.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-cards|1.1.0-maxAttemptNumber",
      "description": "Max number allowed to initiate API calls in a single session. -1 means no limit.",
      "value": "3",
      "type": "Number",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-conn.endpoint",
      "description": "Service connection Endpoint for Worldpay - Payment ACH service",
      "value": "https://certtransaction.elementexpress.com/",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-conn.username",
      "description": "Service connection Username for Worldpay - Payment ACH service",
      "value": "1051704",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-conn.password",
      "description": "Service connection password for Worldpay - Payment ACH service",
      "value": "874767386",
      "type": "Password",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-terminalConfig",
      "description": "Terminal configurations",
      "value": "TerminalID\u003d0001\r\nTerminalType\u003d2\r\nCardPresentCode\u003d3\r\nCardholderPresentCode\u003d7\r\nCardInputCode\u003d4\r\nCVVPresenceCode\u003d2\r\nTerminalCapabilityCode\u003d5\r\nTerminalEnvironmentCode\u003d6\r\nMotoECICode\u003d7\r\nCVVResponseType\u003d1\r\nConsentCode\u003d3\r\nTerminalSerialNumber\u003d\r\nTerminalEncryptionFormat\u003d0\r\nLaneNumber\u003d\r\nStoreCardID\u003d\r\nStoreCardPassword\u003d\r\nOperatorID\u003d",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-txnConfig",
      "description": "Transaction configurations",
      "value": "TransactionAmount\u003d\r\nReferenceNumber\u003d\r\nTicketNumber\u003d\r\nMarketCode\u003d3\r\nPartialApprovedFlag\u003d0\r\n\r\nDuplicateCheckDisableFlag\u003d1\r\nDuplicateOverrideFlag\u003d1\r\nMerchantSuppliedTransactionID\u003d\r\nPaymentType\u003d\r\nSubmissionType\u003d\r\nNetworkTransactionID\u003d\r\n\r\n\r\n\r\n\r\n",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-accCredConfig",
      "description": "AccountToken configuration ",
      "value": "AccountToken\u003d8331A712ECB527DEB0A51EFC8D3EDEE37470C415D92FE9658ACEF1B45439268D81891D01",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-appConfig",
      "description": "Application configurations. Id, name, and version.",
      "value": "ApplicationID\u003d10096\r\nApplicationName\u003dAvoka Test Application\r\nApplicationVersion\u003dBeta",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-enableHttpAudit",
      "description": "With HTTP auditing enabled, details about each HTTP request (including request and response data) are stored in a transaction property as a JSON array against the relevant transaction.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-disableMilestones",
      "description": "Whether to disable Journey Analytics milestones for this service.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-recResInProp",
      "description": "Record response as txn property.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-recResInXml",
      "description": "Record response in FisIdvVO and persisted in Txn XML.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-ach|1.1.0-maxAttemptNumber",
      "description": "Max number allowed to initiate API calls in a single session. -1 means no limit.",
      "value": "3",
      "type": "Number",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-conn.endpoint",
      "description": "Service connection Endpoint for Worldpay - Payment Verification service",
      "value": "https://certreporting.elementexpress.com/",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-conn.username",
      "description": "Service connection Username for Worldpay - Payment Verification service",
      "value": "1051704",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-conn.password",
      "description": "Service connection password for Worldpay - Payment Verification service",
      "value": "874767386",
      "type": "Password",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-accCredConfig",
      "description": "AccountToken configuration ",
      "value": "AccountToken\u003d8331A712ECB527DEB0A51EFC8D3EDEE37470C415D92FE9658ACEF1B45439268D81891D01",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-appConfig",
      "description": "Application configurations. Id, name, and version.",
      "value": "ApplicationID\u003d10096\r\nApplicationName\u003dAvoka Test Application\r\nApplicationVersion\u003dBeta",
      "type": "String",
      "bind": false,
      "required": true,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-enableHttpAudit",
      "description": "With HTTP auditing enabled, details about each HTTP request (including request and response data) are stored in a transaction property as a JSON array against the relevant transaction.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-disableMilestones",
      "description": "Whether to disable Journey Analytics milestones for this service.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-recResInProp",
      "description": "Record response as txn property.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    },
    {
      "name": "worldpay-verify|1.1.0-recResInXml",
      "description": "Record response in FisIdvVO and persisted in Txn XML.",
      "value": "false",
      "type": "Boolean",
      "bind": false,
      "required": false,
      "clearOnExport": false,
      "readOnly": false
    }

Note: Once you setup your application to use configuration service, all the service connection and service parameters data directly comes from the your configuration service. So there is no need to setup the original service connection or service parameter of the Exchange fluent function.

Enable/Disable the configuration service

  ConfigServiceName=MyCompanyServiceConfiguration

Note: Configuration service is an organisation level option. Once enabled, all Exchange services within the organisation will start retrieving the service connection and service parameters info from configuration service you specified above.

Shared Styles

• LoaderIframeStyle Library: exchange-worldpay-taf