DEPRECATION NOTE: The Docebo for Westpac PayWay integration is no longer supported since June 30, 2022, and reached its end of life on September 30, 2022.

Introduction

The Westpac PayWay payment gateway is an authorized payment gateway for the E-Commerce App in your learning platform. Please note that in order to use this system, you need a valid merchant account on Westpac and that this payment gateway currently accepts Australian Dollars only.

Refer to the official Westpac PayWay documentation for further information on how to create a Westpac PayWay account.

Configuring the Integration in Westpac PayWay

To configure Westpac PayWay into your platform, login to your Westpac PayWay account, select Setup Net from the left menu, then click on the Hosted Payment Page option. Flag Bill Payments/Shopping Cart - secure shopping cart handoff, and click on Next to proceed.

In the Biller Code page, copy and save the PayWay Biller Code and the Payment Page Base URL values, as you will need them later on while configuring the payment gateway in Docebo. Press Next.

Then, access the Notifications page. In the Merchant Notification Email section, set the Email Address to which payment alert email will be sent every time a user makes a payment. Also, define a Secret Text that will be included in the alert email as a confirmation that the email is not fraudulent.

Move to the Browser Return section, insert the URL to which users will be redirected when the payment is denied in the Browser Return URL Pre Payment field, then set the Browser Return Type to Redirect. Still in this section, set the URL to which users will be redirected when the payment is properly completed and set the Browser Return Payment Status to Approved.

Finally, move to the Server-To-Server Payment Notification section and configure the Notification URL and the Notification Email. Set the Notification Payment Status to All and the Notification Post Type to Extended.

Remember to set the URLs in this section using the Docebo SaaS domain, even if you have a custom domain.  If you are using the Extended Enterprise app, add the Extended Enterprise client after the SaaS domain name with this format:

[LMS SaaS Domain]/[extended enterprise client]/[redirect URL]

Press Next to proceed. In the Security Information page, copy and save the following values: Encryption Key, Username and Password. You will need them later on, when configuring Westpac PayWay in Docebo. In the IP Address section, add the IP address of the platform server managing payments. Failing to set a proper IP address in this field results in errors during the payment phase. Press Next to proceed.

Configure the parameters in the Customer Reference Number and in the Payment Amount Limits and Payment Methods sections according to your needs. Move now to the Account Settings page and copy your Merchant ID code for the Westpac PayWay configuration in Docebo. Set the surcharges for the credit card circuits you accept, then press Next. Westpac PayWay is now configured, you can move to Docebo to complete the payment gateway configuration in the platform.

Activating Westpac PayWay in Docebo

Activate the Payment Method - Westpac app as described in the Managing Apps & Features article of the Knowledge Base. The app is listed in the Third Party Integrations tab.

Configuring Westpac PayWay in Docebo

In order to configure Westpac PayWay in Docebo, log into your platform as the Superadmin, then access the Admin Menu from the gear icon in the top right corner and select the Manage option in the Payment Method - Westpac section. Activate the Enable Westpac Payway toggle to enable this payment gateway in your platform.

Then, use the corresponding text boxes to fill in the encryption key, biller code (PayWay biller code), username, password, merchant ID and Email needed for configuration. Please note that the username and the password required by the integration are those provided during the Docebo configuration on the Westpac PayWay portal, in the Security Information page, and not your Westpac PayWay credentials. Refer to the previous chapter of this article for further information.