The imin Platform
2.0.0
2.0.0
  • Introduction to the imin Platform
  • Using the Platform
    • imin's Platform Products
    • Authentication
    • Our Platform Data
      • Understanding Responses
      • Namespaces and Extensions
      • Defensive Data Consumption
      • Mocking the Interface
  • platform products
    • Search
      • imin Events API
        • Events API Reference
        • Virtual & Physical Sessions
        • Concepts
          • EventSeries
          • ScheduledSessions and eventSchedules
          • Activities and Collections
            • Activities
            • Activity Concept Collections
          • Accessibility Support
          • Prices
        • Filters
          • Modes
          • Age Ranges
          • Dates and Times
          • Activities and Concept Collections
          • High Frequency Sessions
      • imin Facilities API
        • Query Parameter Search
          • Mandatory Query Parameters
            • mode=discovery-geo
            • mode=upcoming-slots
          • Optional Query Parameters
        • ByID Search
          • FacilityUse By-ID
          • Slot By-ID
        • FacilityUses and IndividualFacilityUses
        • Slots
        • Facilities Slot Booking
      • imin Places API [BETA]
        • Example Request & Response
    • Firehose
      • Introduction to the Firehose
      • Accessing the Firehose
      • Firehose Usage Policy & Restrictions
      • Firehose and Search
      • Bookable Firehose Feeds
      • Bookable Sellers Feed
      • Attribution Catalog Endpoint
    • Live Timetables
      • Pre-Requisites: Open Data Feeds
      • The Onboarding Process
        • 1. Ensuring your Data Offers the Best User Experience
        • 2. Setting up and Embedding your First Timetable
        • 3. Setting up the Rest of your Timetables
        • 4. Activating Booking via Guest Checkout
      • Features Available Upon Request
      • Styling the Live Timetables
      • FAQs
    • Data Dashboard
  • incorporating book and pay
    • imin Branded Checkout
      • Introduction
      • Setup
        • Information We Require From You
        • Actions You Need to Complete
      • Authenticated Checkout
        • Testing [BETA]
        • 👪Group Booking [BETA]
      • Standalone Checkout
      • Firehose and Checkout [BETA]
        • Loading the Checkout via Firehose
    • imin Booking Platform
      • Customer Account Management
        • Create Customer Account
        • Update Customer Account
        • Get Customer Account
        • Delete Customer Account
        • Example Scenario
        • Payment Card Management
        • Linked Accounts
        • Entitlement
          • Evidence Requests
          • Entitlement Pricing in Search
          • Entitlement Pricing in Checkout
        • Access Pass
        • Webhooks
      • Orders
        • Order History
        • Order (by ID)
        • Cancellations & Refunds
      • Upcoming OrderItems
      • Receipt (by ID)
  • imin and booking systems
    • Seller Onboarding
      • API
  • HINTS & TIPS
    • Get the Best Out of Search
      • Displaying Schedule Information
      • URLs and Offering a Call to Action
      • Searching by Activity
      • Your Search Results and HighFrequencySessions
      • Customer Specific Images
  • Info for Data Publishers
    • Your RPDE Feed & the imin Platform [BETA]
      • Providing Places Data [BETA]
      • Providing Schedule Information [BETA]
Powered by GitBook
On this page
  • Specific Branding
  • URLs and Email Addresses
  1. incorporating book and pay
  2. imin Branded Checkout
  3. Setup

Information We Require From You

PreviousSetupNextActions You Need to Complete

Last updated 1 year ago

This page contains a few important characteristics:

Specific Branding

The example shown above is for Badminton England, where Checkout has been branded/themed to fit Badminton England’s colours, including the logo in the top left.

What information we require from you:

  • Full brand guidelines if available, or preferred brand colours at a minimum;

  • Screenshots or a demo of the activity finder/search results page from which the Checkout will load (so we can understand use of colour palettes);

  • Logo (in transparent PNG, preferably); and

  • Any specific background images you would like to use (note: you must have licence to use this image). If not, we can select from our library of stock images. Please provide the highest resolution you can, with 1600x880 being the optimum.

URLs and Email Addresses

URL for Search Platform

What information we require from you:

  • The URL for the search platform from which users will search and book.

  • If you require additional checkouts for testing purposes, then we will need these URLs as well, e.g.

URL for Homepage

This is your organisation's homepage, which will be included at the bottom of the Checkout flow and in the confirmation email.

What information we require from you:

  • The URL for your organisational homepage.

URL for Terms & Conditions

This link takes the users to the terms & conditions governing your provision and the end user's use of the booking service (or, if you do not have terms & conditions, the URL for your privacy policy).

We will include this URL on your Branded Checkout pages so that the end user can easily see the terms that govern the use of their personal data by you and your sub-processors, of which imin is one.

What information we require from you:

  • The URL of your terms & conditions (or privacy policy if you do not have terms & conditions) so we can integrate them into your Branded Checkout.

If you do not have user-facing terms & conditions and you are using imin to facilitate bookings, you may wish to consider whether this is something you might introduce in order to protect the interests of both you and your users.

"Contact Us" Email Address

This is an email address that the user can use to ask any questions to you (as the brand providing them the booking).

What information we require from you:

  • The most appropriate email address for users to contact your helpdesk or organisation.

Confirmation Email Address

Users will receive a confirmation email from the service, which includes details of their booking, barcode for venue entry, etc. This email will have a “From” email address that you can select that represents your organisation.

What information we require from you:

  • The selected email address that will appear in the “From” field for the confirmation emails that get sent to users.

  • It can be something like bookings@example.com or noreply@example.com.

For convenience, you can provide all of the following information by simply completing .

This is the URL where the search platform, e.g. the activity finder, will be hosted. This is needed so we can construct your checkoutBaseUrl(see ).

We will also provide you with some standard text to add into your Terms & Conditions that govern imin’s involvement in the booking and payment flow (see “" at the end of this document).

this Google Form
here
https://checkout-dev.example.com
https://checkout-staging.example.com
Update your terms and conditions