Payments
Zonal Bookings facilitates deposits and full pre-payment for table reservations or events. These payments need to be processed securely through reliable payment providers. The payment providers we can integrate in to are Braintree, WorldPay (specifically their Access Account type) or FreedomPay.
By integrating these payment providers directly, Zonal eliminates re-keying amounts, speeds up service. Asking for deposits or pre-payment before booking (particularly for large groups) helps discourage no-shows. The integration ensures the process is frictionless.
Payments Topics
Setting Up a Payment Provider
Follow the below steps, to set up a payment provider:
-
Select the Payment Provider name on the header tabs
If you have never configured a payment provider, it will most likely state Braintree
-
Enter payment provider details into the required fields
Each Payment Provider requires varying field data. This can be found in the Field Settings & Information below -
Enable the details
-
Click Validate
Correct details will display a message showing the Merchant ID, the status of the account and sometimes with the name of the business. Should the validation display an error, re-key the details supplied from your provider and try again. For any further issues, we suggest reaching out to your Account representative.
-
Click Save Changes
Zonal recommends you always make a test payment when any payment details are saved against an estate, company or site
Changing a Payment Provider
The Events platform is set to use Braintree by default.
The Events platform uses Braintree as its default payment provider. If you want to switch to another provider, contact your Account Representative, who will arrange for Zonal to make the necessary changes.
This update is carried out in the Estate Settings of Events, within the Payment Providers section, which can only be accessed by Zonal employees. Once the change is complete, your new provider’s name will appear in the Events Administration area under Payments. Any previously configured credentials will remain in the system but will be voided and can no longer be used.
Before making the switch, it’s important to plan ahead:
-
Manage existing payments: Decide how any current payments will be handled.
-
Update operational processes: Ensure staff understand the changes to avoid confusion.
Your Account Representative will log a request for Zonal to update your Payment Provider.
Test Payments
Zonal recommends that once your new payment provider is configured, a few test payments are made before going live. This ensures that:
-
Payments are processed successfully from start to finish
-
Transactions appear in the correct accounts
-
Payment records display accurately in your reports
Run test payments using realistic scenarios (e.g. typical booking amounts) and check both the customer-facing and reporting views. Confirm that the payment status, amounts, and references match in all relevant reports
Catching any discrepancies at this stage helps prevent payment issues and reporting errors once your system is in full use
Field Settings & Information
| Field | Description |
|---|---|
| Environment |
Sandbox payment provider details are used for testing transactions in a non-live environment, while production payment provider details are used for processing real customer payments in the live system |
|
Enabled |
Enabling will allow for payments to be made. If the field is set to be disabled, no payment links will be provided to bookers |
| Auto Refund |
This defines whether or not you allow for an Events user to carry out refunds within the Host app |
| Field | Description |
|---|---|
| Merchant ID |
A unique identifier for your Braintree account. It tells Braintree which account to process payments under. This is generated by Braintree when your account is created |
| Public Key |
A public credential used alongside your merchant ID to identify your account when communicating with Braintree’s systems |
| Private Key |
A secret credential used to securely authenticate your application with Braintree. It must be kept confidential and never exposed publicly, as it grants access to your payment account |
| Field | Description |
|---|---|
| Username |
The login name provided by WorldPay for API or integration access. This identifies your account when Events platform connects to WorldPay |
| Password |
The secure key paired with your username to authenticate your connection to WorldPay. This must match exactly what is set in your WorldPay account |
| Access Identity ID |
A unique identifier issued by WorldPay that specifies which merchant profile or account the integration should use for processing payments |
| Card Brands |
The types of payment cards your WorldPay account is configured to accept (e.g. Visa, Mastercard, American Express). Selecting the correct card brands ensures the system will accept the same cards you are enabled for in WorldPay |
| Field | Description |
|---|---|
| Store ID |
The unique identifier assigned to your location within FreedomPay. It links transactions from your system to the correct store in your FreedomPay account |
| Terminal ID |
The unique identifier for a specific payment device or terminal at your store. This ensures payments are tracked to the correct point of sale |
| ES Key |
The Encryption Services Key issued by FreedomPay. This secure credential is used to encrypt and authorise transactions between your system and FreedomPay’s payment gateway |
| Card Brands |
The types of payment cards your FreedomPay account is configured to accept (e.g. Visa, Mastercard, American Express). Selecting the correct card brands ensures your system accepts only the cards supported by your FreedomPay account |