Gleanin
You can integrate Gleanin into your Visit Create event.
The Gleanin integration provides:
- A Gleanin widget on registration forms, enabling Gleanin’s social media buttons.
- Support for a large number of languages.
You need:
- The Gleanin module enabled in your Visit Create contract.
- A Gleanin account. This is where you configure your registration and sharing options.
- A Gleanin event token. You can request this from Gleanin yourself, or contact your Visit client manager.
When you Set up an event, select Enable Gleanin and provide the token.
Add Gleanin to your registration form
You can add the Gleanin social media login widget to any page of the form, and the social media sharing widget to the final page.
- Click in a text field. This brings up the inline text editor menu.
- Select Add Gleanin login or Add Gleanin sharing widget.
Payment service providers
To process payments, you must set up a link between your chosen Payment Service Provider (PSP) and Visit Create. This link must go both ways: you must set up Visit Create to communicate with your PSP (refer to Add payment service providers for more information), and set up your PSP account to communicate with Visit Create. This page contains information on setting up your PSP account.
Docdata setup
- Go to DocData Payments.
- Log in with your Docdata username and password.
- Select Settings.
- Select View/Edit Merchant Profile.
- Select URL.
- Enter the following URL in the Update URL box:
https://payment.gesevent.com/docdata-command/notify/?mtid=
- Select the Send mail when all update URL tries fail check box.
- Select Store.
- Set up payment profiles. In each profile, add the type of payment method(s) you want to offer. There are two types of payment methods:
Method | Response | Payment method | Timing |
---|---|---|---|
Direct Response | Response during transaction, whether or not the payment is successful. | Credit Cards, iDeal | Use at any time leading up to event. |
No Direct Response | No response during the transaction. | Direct debit, Manual transfer | Recommended to stop using this approximately 14 days prior to event start. |
- If you intend to use both Direct Response and No Direct Response payment methods, GES recommend setting up two payment profiles:
- Standard: include all payment methods you want to use during pre-registration.
- Standard direct: include the payment methods you want to use in the last two weeks of pre-registration, typically credit cards and iDeal.
- Select Settings.
- Select Edit Payment Profiles. Payments profiles that have already been created are displayed in the top box, one row per payment method for each profile.
- Select a method from Available payment methods.
- Enter a profile name in the In profile box.
- Select Add.
Visit Create setup
You need your Docdata merchant code and XML secret. These should be in the email your company received when it set up its Docdata account.
Enter the Docdata merchant code in the Username field, and the Docdata XML secret in the Password field.
Refer to Add payment service providers for more information.
Payment status
Docdata status | Visit Create status |
---|---|
new | Paying |
started | |
hold | |
paid | Registered |
closed_success | |
chargedback | Registering, then Stopped after 30 minutes if no action taken. |
closed_insufficentpaid | |
closed_cancelled | |
closed_expired | |
closed_refunded |
PayPal
To use PayPal with Visit Create, you need to:
- Have a PayPal business account.
- Create a REST API app for Visit Create in your PayPal business account.
Depending on your company location, the procedures for setting up accounts and apps in PayPal may be different. Refer to PayPal’s documentation for help with setting up your REST API app.
Visit Create setup
You need your PayPal client ID and secret. You receive these when you set up the REST API app.
Enter the client ID in the Username field and the secret in the Password field.
Refer to Add payment service providers for more information.