Advanced Checkout Integration
There are a number of advanced configuration options that we are able to offer to selected partners. For specialist use cases we may able to offer additional integration options. Please contact your account manager for more details.
Using a Custom Domain (CNAME)
By default each instance of the TTG White Label and Checkout run as a subdomain of tixculture.com (eg. https://retailername.tixculture.com). We are able to create a custom CNAME so that the White Label and Checkout are available on a URL such as https://buy.retailername.com. This is a managed process, our team will work with you to configure the DNS records and enable this feature.
Sending email booking confirmations and barcodes
Out of the box the TTG Checkout is configured to automatically send booking confirmations and barcodes directly to users. If you would prefer to handle this directly we are able to suppress confirmation emails. Note that this is on a per account basis - we can enable and disable confirmation emails across all products. This is a managed process, our team can configure this feature on our behalf.
Redirecting to a custom confirmation page
The TTG Checkout includes an out of the box confirmation page that can be styled in line with the rest of the White Label and Checkout experience. It is possible to enable a custom redirect that allows you to redirect users back to your website on completion of a purchase.
In addition to redirecting the user we are able to append the booking reference and checksum value which can be used to retrieve the booking details (see below).
| Parameter | Description |
|---|---|
| supplierId | A static value in all redirects to identify a TTG booking (useful for integrators who use multiple suppliers) |
| reference | The TTG booking reference for this transaction |
| checksum | An associated checksum 'password' which can be used to retrieve the booking |
As an example a typical redirect URL could be:
https://www.retailername.com/confirmation/?supplierId=TTG&reference={reference}&password={checksum}
The experience can be customised by passing additional parameters.
Fetching realtime booking details via an API call
To retrieve the full details of a customers booking you can use the checkout/getBooking API. See the API reference for details.
Gift card orders also return the card code and expiry in giftCards; see Fetching bookings via the API.
Adding Google Tag Manager (GTM)
We can add a Google Tag Manager (GTM) container to your White Label and Checkout pages. To do this we need a GTM container ID (starting GTM-). Adding a GTM key is a managed process. It is possible to add conversion tracking to your GTM container, see the integration guide here.
Additional parameters (optional)
| Parameter | Description |
|---|---|
| partnersource_url | A URL to redirect the booking back to in the event of a failure |
| language | A two character language code (see below for supported languages) |
| logo | Filename of an alternative logo to be displayed on the basket page (logo must be supplied in advance) |
| orderdetails | A base64 encoded string of customer details that will be used to pre-fill the payment form (see below). |
| customstyles | Boolean value (defaults to false) to display additional in basket styling (agreed / supplied in advance) |
| send_events | For integrators embedding the checkout in an iFrame. If enabled, checkout status events are sent to the parent page using a postMessage as {source: "checkout", message: "<event>"}, eg. checkout_success, payment_success, basket_expired. Events carry no booking reference: keep the basket reference and checksum you opened the checkout with and use them to fetch the booking. Boolean value (defaults to false). |
| disable_phone | If the users phone number is validated before being passed to the WL checkout you can disable the display and validation of the phone number by passing a Boolean value (defaults to false). |
Supported languages
The following languages are available. To select a language other than English pass the two digit country code in the querystring.
| 2 Digit Code | Language |
|---|---|
| en | English (default) |
| da | Danish |
| de | German |
| es | Spanish |
| fr | French |
| it | Italian |
| nl | Dutch |
| no | Norwegian |
| sv | Swedish |
Passing customer details
Customer details can pre-fill the payment form. Pass them either as individual querystring parameters, or base64-encoded in a single orderdetails parameter for some obfuscation. If orderdetails is present, the individual parameters are ignored.
shopperemailshoppername(full name)shopperphonecountrycode: the dial code without+, eg.44for the UK. Not+44(a+in a querystring is read as a space) and notGB.shopperphonebillingpostalcode
If your checkout is set up with the contact details form hidden,
shoppername,shopperemail,shopperphoneandshopperphonecountrycodeare required. Without them the hidden form fails validation and the Pay button does nothing.
- As individual parameters:
&shopperemail=barry%40example.com&shoppername=Barry%20Tester&shopperphonecountrycode=44&shopperphone=07855123456 - As
orderdetails, start from the string:[email protected]&shoppername=Barry Tester&shopperphonecountrycode=44&shopperphone=07855123456&billingpostalcode=SE3 8LY - Encoded:
c2hvcHBlcmVtYWlsPWJhcnJ5QGV4YW1wbGUuY29tJnNob3BwZXJuYW1lPUJhcnJ5IFRlc3RlciZzaG9wcGVycGhvbmVjb3VudHJ5Y29kZT00NCZzaG9wcGVycGhvbmU9MDc4NTUxMjM0NTYmYmlsbGluZ3Bvc3RhbGNvZGU9U0UzIDhMWQ== - URL-encode the value when adding it (base64 can contain + and /):
orderdetails=c2hvcHBlcmVtYWlsPWJhcnJ5QGV4YW1wbGUuY29tJnNob3BwZXJuYW1lPUJhcnJ5IFRlc3RlciZzaG9wcGVycGhvbmVjb3VudHJ5Y29kZT00NCZzaG9wcGVycGhvbmU9MDc4NTUxMjM0NTYmYmlsbGluZ3Bvc3RhbGNvZGU9U0UzIDhMWQ%3D%3D
Updated 10 days ago