Worldpay Business Gateway 350

The Worldpay Business Gateway 350 (BG350) offering supports one-time card payment.

Pre-requisites

• FinDock is installed and configured.
• A working connection to ProcessingHub and WebHub.
• You have a WorldPay Business Gateway 350 account.

Install and activate BG350 extension

Follow the standard procedure for installing the Worldpay for FinDock package, and then activate the FinDock-WorldPay-BG350 extension.

Check and assign the required permissions. If you are using custom permission set groups, ensure the package-specific permission sets are assigned.

Set up Business Gateway 350 account

Before configuring the FinDock Worldpay extension, you need to do some configuration in the Worldpay Business Manager portal. Your organization should have a Business Gateway 350 account with Worldpay. Use those account credentials here: Worldpay login.

To set up Worldpay integration with FinDock:

1. In the left-hand menu, enable Production Mode.
2. Click SETUP in the left-hand menu, and then select the Installations tab.
   
3. In the row for Invisible XML, click the cog wheel for the test or production setup (depending on whether you are setting up a sandbox or product org).
4. Under Other Actions > Channels click Edit Channels.
5. In another browser tab, launch the FinDock app and click Setup.
6. Click on the FinDock-Worldpay-BG350 tile under Extensions - PSP, and copy the Notification URL.
7. Go back to the Business Manager portal.
8. Under Merchant Channels, add the Notification URL from FinDock to the http address field. Then select xml and POST, and make sure the http channel is Active.
   
9. Click Save Settings when you are done.

Keep the Business Manager portal open while you configure FinDock. Some information from your Worldpay account is needed for the FinDock settings.

Configure Worldpay BG350 extension

After you have finished the Worldpay merchant account setup, you can configure the Worldpay extension in FinDock.

To configure the Worldpay extension:

1. Launch the FinDock app and click Setup.
2. Click on the FinDock-Worldpay-BG350 tile under Extensions - PSP.
3. Fill in the settings as described below.
   • Notification URL: this value is automatically filled by the Notification Gateway.
   • Endpoint: the Worldpay service endpoint for authorizations and transactions. Enter the endpoint depending on whether you are configuring a sandbox (test) or production org.
     • Test: https://secure-test.worldpay.com/jsp/merchant/xml/paymentService.jsp
     • Production: https://secure.worldpay.com/jsp/merchant/xml/paymentService.jsp
   • Merchant Code: enter here your code as shown in the left-hand menu of the Business Manager portal.
   • Installation Id: enter the Installation ID under Setup > Installations > Invisible XML > Integration Setup
   • Username: enter the username for the Invisible XML installation
   • Password: enter the password for the Invisible XML installation
4. When you have entered all the details, click Save.

Refund handling

Worldpay payments can be refunded from the Worldpay dashboard. However, refunds are not automatically processed in FinDock.

Payment API

To test your Worldpay configuration for one-time payments, you can use the following API message.

If your configuration is correct, you should be able to navigate to the RedirectURL provided in the response and pay the amount specified. When a redirect ends in an unexpected error, the error message is stored in the last status reason of the installment.

This request initiates a one-time credit card transaction with Worldpay.

{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Eric",
                "LastName": "Johnson",
                "Email": "eric@johnson.com"
            }
        }
    },
    "OneTime": {
        "Amount": "15"
    },
    "PaymentMethod": {
        "Name": "CreditCard",
        "Processor": "PaymentHub-WorldPay"
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}