We noticed that JavaScript is disabled in your browser. We suggest enabling it for a better experience.
We noticed you're using an older version of Internet Explorer. We suggest you update to the latest version for a better experience.
Skip to main content
Print

Set up a payment gateway

Pro, Business and Enterprise plans

Only admins can set up payment gateways in OpenForms. If you're not an admin user, you can still add payments to forms using existing payment gateways.

If you want to take payments through your form, first you’ll need to set up a payment gateway. This is a service that connects your website and bank so online transactions can be completed in real time.

Once you’ve signed up for a payment gateway, you can set it up in OpenForms, then add payments to your form.

Sign up for a payment gateway

First, you’ll need to sign up for one of the payment gateways OpenForms accepts:

Once you’ve signed up for one of these, you’re ready to set up your payment gateway in OpenForms.

Set up your payment gateway in OpenForms

Signed up for a payment gateway? Now, set it up in OpenForms. You’ll need the following information, which should have been provided when you signed up for your payment gateway:

ANZ eGate
  • Merchant ID
  • Merchant access code
  • Currency code
 Authorize.net
  •  API Login ID
  • Transaction key
  • Currency code
  • Mode
Bridgepay
(US users only)

 
  • Username
  • Password
  • Merchant ID
  • Merchant Account Code
  • Mode

    The "Mode" setting for Bridgepay allows your developers to switch between live and test environments. For access to this option, contact Bridgepay.To move from a test to a live Bridgepay environment, you will need specific OpenForms transaction information that we can provide to you. Bridgepay will let you know the information you need when you request live credentials.
Commbank BPoint

  • Merchant Number

  • Username

  • Password

  • Biller code (optional)

  • Surcharge percentage applied to all payments 

  • Currency code

  • Mode

The "Mode" setting for Commbank BPoint allows your developers to switch between live and test ("UAT") environments. For access to this option, contact Commbank BPoint.

 
eWAY
(AU and NZ users only)

 

  • API key

  • API password

  • Client-side encryption key

  • Mode
    The "Mode" setting for eWAY allows your developers to switch between live and test ("sandbox") environments. For access to this option, contact eWAY.

NAB Transact
  • Merchant Id
  • Password
  • Currency code
  • Mode

The "Mode" setting for NAB Transact allows your developers to switch between live and test ("demo") environments. For access to this option, contact NAB Transact.
Pay Now
  • API Username
  • API Secret
  • PayNow URL
  • Payment Message

Windcave PxPay & PxPost

(formerly Payment Express)
  • Username
  • Password
  • Currency code
PayPal
  • Client ID
  • Client Secret
  • Currency code
  • Button style
  • Gateway Type
Point & Pay
(US users only)
  • Partner code
  • Product ID
  • Username
  • Password
  • Gateway type

POLi
(AU and NZ users only)

 

  • Merchant code

  • Authentication code

  • Currency code

  • Gateway type
SecurePay

  • Merchant ID

  • Transaction Password

  • Currency code

  • Gateway Type
Stripe
  • Secret API key
  • Currency code

Westpac PayWay API
(AU and NZ users only)

 

  • Username and password from API security settings in PayWay API Portal

  • Merchant ID

  • Currency code

  • Certificate file (please upload the .NET API Security Certificate from your PayWay API Portal)

  • Add the following IP addresses to the security list within PayWay API Portal:

    13.70.186.157
    13.70.187.103
    13.70.189.111
    13.70.191.71
    13.77.7.175
    52.189.195.235
    40.69.158.37

    13.77.50.96
    23.101.237.98
    40.115.70.133
    23.101.225.17
    40.127.64.147
    52.189.195.235 

  • If you're using a receipt number prefix in your forms, this must be unique for each form using the Westpac PayWay API.

  1. From the main menu, go to Integrations > Connectors > Payment gateways

  2. Find the gateway you'd like to add, and select Add from its detail page.

  4. Enter the details about your payment gateway and save your changes.

Send extra details to the gateway

When a form responder makes a payment, you can send extra details about the transaction to the payment gateway. Your staff can view this info in reports from the payment gateway. We’ll always send the receipt number as the payment reference.

The details that you choose here will be the default settings for all forms that use this payment gateway. To send different details per form or to send details based on field responses, open a form and change its payment field settings. 

Test your payment gateway

Once you have set up a payment gateway, you can test it by submitting a payment through a preview of a form while logged in as the form author. This will provide additional details - beyond what your form respondents normally see - if the payment fails. Use these details to troubleshoot issues.

Preview payments are still processed, so it's best to test forms with a very small payment.

See a list of forms that are using a payment gateway

  1. From the main menu, go to Integrations > Connectors > Payment gateways.

  2. Open an existing payment gateway.

  3. Open Forms using this payment gateway. You’ll see a list of the forms that are using it. You can search the list and select a form to edit it in its Build screen.

 

You’re now ready to add payments to your form.

Was this helpful?

Related topics