Certification process - The what and how?

The following is a quick reference to the certification process. In this section we will give you all necessary information to complete the Certification process, which will ensure that your integration is ready to go Live.

Please, consider that carefully reading this section and planning you implementation ahead knowing what is going to be specifically requested by us, can lead to a much better experience and a sooner reaching of the goal: Being Live and ready to sell. 

Of course, you can contact us with any doubts or questions by phone ((+34) 971 189 243 - Ext 5243 for Europe and Americas) or by email: integrations@activitiesbank.com.

 

Our certification process will look at 3 different areas:

 

Before we start with the certification process we will need some information from you. These information will be:

  • List of operations that you have implemented.
  • Website information

List of operations that you have implemented:

Sometimes clients decide not to implement all operations. We want to know the scope of your development. Here we will provide you with a template for you to fill in. The possible operations to be implemented are:

Operation

Implemented?

Comments

Search

YES / NO

Please detail here what type of searches and filters you have used. For example, if you have decided to implement filters for GPS and Destination. Detail all of the filters included

Detail

YES / NO

Indicate here whether you have implemented the "Simple" or "Full" 

Retrieve Pickups

YES / NO

Please indicate if you have implemented this operation

BookingConfirm

YES / NO

Please indicate if you have implemented the Confirmation as well as if you have implemented the Pre-Confirmation. Pre-Confirmation is typically used for clients that perform pre-payments to their clients and do not want to confirm before they have collected from the final consumer. This operation is Mandatory to complete a booking funnel.

Booking Detail

YES / NO

This operation is Mandatory to complete a booking funnel.

Booking List

YES / NO

Please indicate if you have implemented this operation

CancelRequest

YES / NO

Please indicate if you have implemented this operation. Is highly advised that you allow your customers to cancel their bookings and if so this operation shall be implemented. 

Modifications

YES / NO

Please indicate and share with us if you have implemented a process to modify bookings

Website information:

 We are going to need the URL of your site, so we are able to review the way you have implemented the API and what information (as well as ho it is shown) is being provide to your final customers. In order to do so, we will also need any possible credentials.

There are cases in which the business model is not aimed to provide a website for the final customer: it can be an intranet for a certain travel company, or a mobile app... In these cases, we will still need to review the technical implementation of the API and the info shown, and we will ask for alternative ways to do so:

  • Screenshots demonstarting each relevant step of a booking funnel, or
  • A video capture of a complete booking funnel, or
  • Maybe even a web meeting sharing screen and performing a full booking funnel.

 

Certification goals

The Certification process intention is to test and ensure that your team can get an additional external support in testing the functionality and implementation of the relevant and mandatory information. Why do we mandate for some information to be shown or provided to the customer? To avoid issues with the final consumer, or he/she being misled by any incorrect information. Our team is focused on ensuring that the final consumer is not going to have any problems. This is ultimately converting to customer satisfaction and no issues.

Having said this, the tests that we do consider two scenarios:

  • Standard operations: in case the implementation only considered the following operations Search, Detail, Booking Confirm, Booking Detail, BookingList, and CancelRequest
  • Enhance operations: in case the implementation also added features such as modifications and pickups the tests to be done will be increased.

TEST STEPS

The testing is planned to be done considering the following test variables:

Destinations to be used:

  • Barcelona (either using a GPS coordinates or a destination code).
  • Berlin (using GPS codes)
  • Orlando (using Destination the destination code and a keyword of your choice)
  • Algarve
  • Ljubljana

NOTE: If you are implementing availability using a Hotel Id please replace the test in Orlando using a Hotel ID (regardless of whether it is Hotelbeds, GIATA or TTI code).

Passengers’ distributions to be used:

  • 1 adult
  • 2 adults - 1 child (8 years old)
  • 3 adults - 2 children (3 years old and 9 years old)
  • 2 adults - 2 children (1 year old and 17 years old)

If the implementation considers the Standard operations, the following tests will be performed:

Test #

Description

Description and steps

Test 1

Booking funnel buying one product and cancelling it

 

  1. Search for a list product in Barcelona
  2. Select one product and perform the Detail operation for the selected product (you can select the product as per your convenience)
  3. Confirm the booking – Booking confirmation (here please use either the pre-confirm and/or re-confirm or confirm as per your implementation – In this case we will need to know the way you have decided for the implementation)
  4. Perform the detail of one product (you can select the product randomly)
  5. Generate the voucher
  6. Perform a booking detail to retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)
  7. Cancel the booking

 

Test2

Booking funnel confirming two services

 

  1. Search for product in Berlin (if the destination is being sold if not we will select a different one) using a GPS coordinates
  2. Perform the detail of one product (you can select a product randomly)
  3. Perform a detail of a second product (you can select a product randomly)
  4. Confirm the booking with both services – Booking confirmation (here please use either pre-confirm and re-confirm or confirm as per your implementation)
  5. Generate the voucher
  6. Perform a booking detail to retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)
  7. Cancel the booking

 

Test 3

Booking funnel confirming a bundle product (if you have implemented bundle product)

 

  1. Request for availability in Orlando (if the destination is being sold if not we will review another location)
  2. Perform a detail of one bundle product
  3. Confirm the booking
  4. Print the voucher/s for each product that is bundled
  5. Retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)
  6. Cancel the booking

 

Test 4

 

Booking funnel but adding a product that has questions in it

 

  1. Request availability for “Ljubljana”.
  2. Add one product that has questions, example:
  3. activityCode":"E-E10-ALPINELAKE"
  4. name":"Alpine Lakes Bled and Bohinj"
  5. Book the product including the questions: for example:
  6. question": {"code": "HOTEL", "text": "Please advise the name of your hotel" "answer": "Hotel TEST"
  7. Cancel the booking

 

 

NOTE: For each of these tests we will ask you to provide to us evidence of each operation including the Request and Response for all of them. 

In addition to this in the event that you are doing and opting for the Enhanced operations which include Pickup and Modifications, these:

 

Test #

Description

Description and steps

Test 5

Search and book and excursion

 

  1. Search an excursion product in Algarve (destination code “FAO”). Once the search is completed you can look for an excursion for example:               "value":"X-P01-INTERACAO". (Ensure you look for any product that is an excursion. "type":"EXCURSION").
  2. Obtain the full detail for the excursion
  3. Retrieve the pickup information
  4. Confirm the booking (in case you are doing a pre-confirmation please use the pre-confirmation and then the confirmation). If not please only provide us with the confirmation information.
  5. See an example of booking funnel for this here. You can use a combination of pax as per your own wish. Only one combination for this test will be sufficient.

 

Test 6

Modification of product already booked

 

  1. Obtain a product by searching for it in Orlando destination.
  2. Perform a full detail of the product to get the full description of it.
  3. Book and confirm the product (for example)
  4. Perform a second detail
  5. Confirm the modification of the product
  • See an example of booking modification for which the following was modified:
  • Client reference
  • Pax name
  1. Modality change (meaning that the service was kept the same but the modality first booked was replaced by a new modality for the same service).
  2. You can use a combination of pax as per your own wish. Only one combination for this test will be sufficient.

 

MANDATORY INFORMATION

As part of the integration process, there is some relevant information that have to be provided to the client at some point during the booking funnel.

We don't want to restrict or constraint the way you implement your booking funnel at all, however, we have to make sure that we do provide all relevant information to the end consumer. We will not tell you how many pictures, for example, you have to show, but we will require you to provide (if returned) the information on cancellation policies that apply to the product that is being booked. 

A list of all the relevant information that is mandatory to provide to the customer is provided below. 

Search  

The information to be provided to the client that is mandatory and as a minimum is the following:

Operation

Area that is mandatory

API Attribute

Search

Name of the ticket or activity

activities/@name

Search

Description: You will see that in the Search descriptions may be cut. As a result we strongly recommend that you concatenate a link to "More information" in order for the client to click there and go to the detail information of the product where the full description shall be used. We recommend to add the "More information" link in the red box shown in the example below

activities/content/@description

Search

At least one picture of the ticket

activities/content/@media

Search

Price from for Adults

activities/amountsFrom/@paxType

activities/amountsFrom/@amount

Detail

Regardless of whether the request is done for a full or simple detail, the following information is mandatory to be shown to the final consumer. These values in the response of the Detail must be provided to the end consumer at some point through the booking funnel.

Operation

Area that is mandatory

API Attribute

Detail (Simple or Full)

Name of the activity

/@name

Detail (Simple or Full)

Full description of the activity

/@description

Detail (Simple or Full)

At least 1 image

/media/images

Detail (Simple or Full)

Destination

activity/country/destinations/@name

Detail (Simple or Full)

Features

/featureGroups

Detail (Simple or Full)

Price per adult

activity/amountsFrom/@paxType

activity/amountsFrom/@ageFrom

activity/amountsFrom/@ageTo

activity/amountsFrom/@amount

Detail (Simple or Full)

Price per child

 

Detail (Simple or Full)

Currency

activity/@currency

Detail (Simple or Full)

OperationDates

activity/operationDays/@name

Detail (Simple or Full)

Cancellation policies

activity/modalities/rates/rateDetails/operationDates/@cancellationPolicies

activity/modalities/rates/rateDetails/operationDates/cancellationPolicies/@dateFrom

activity/modalities/rates/rateDetails/operationDates/cancellationPolicies/@amount

 

Detail (Simple or Full)

Modalities information

activity/modalities/@name

activity/modalities/duration

activity/modalities/duration/@metric

activity/modalities/duration/@value

Detail (Simple or Full)

Modality price

activity/modalities/amountsFrom/@paxType

activity/modalities/amountsFrom/@ageFrom

activity/modalities/amountsFrom/@ageTo

activity/modalities/amountsFrom/@amount

Detail (Simple or Full)

Questions to be answered

activity/modalities/questions

activity/modalities/questions/@text

Detail (Simple or Full)

Rate information

activity/modalities/rates/@name

activity/modalities/rates/@shortDescription

Detail (Simple or Full)

Session

activity/modalities/rates/rateDetails/sessions/@name

 

Detail (Simple or Full)

Language

activity/modalities/rates/rateDetails/languages/description

Detail (Simple or Full)

Rates

activity/modalities/rates/rateDetails/paxAmounts

Detail (Simple or Full)

Comments

activity/modalities/comments

activity/modalities/comments/@text

 

Confirmation

As per the previous analysis once a confirmation is done the following shall be shared as a minimum with the client:

  • Name of the activity
  • Date of service booked
  • Modality, Rate, Session selected by the client
  • Price paid
  • Currency
  • Pax distribution
  • Questions to be answered: (activity/modalities/questions). If the question is required (activity/modalities/question/@required) then this question is mandatory to be input in the Confirmation operation request.
  • Comments (as details in booking/activities/bundle/comments/@type and booking/activities/bundle/comments/@text)
  • Cancellation policies information, if available.

 Some of the controls that we will be implementing are:

  • See on your website calendars for selecting the dates whether the ticket is doable in the dates provided (this will be used by knowing the operation dates)

Retrieve pickups

The information to be provided here will depend on how much data you would like to give to the client but as mandatory the minimum information is:

Operation

Area that is mandatory

API Attribute

Retrieve Pickup

Description

pickups/@pickupName

Pickups/@shortDescription

Retrieve Pickup

Price

pickups/operationDate/totalAmount/@paxType

pickups/operationDate/totalAmount/@amount

 

VOUCHER INFORMATION:

  • Reference number. Booking number
  • Name of the excursion or ticket
  • Booking date or date in which the booking was confirmed
  • Pax name (lead name)
  • From and to for the excursion or ticket
  • Modality name
  • Session selected (in case available as not all activities have this being returned)
  • Language selected (in case available as not all activities have this being returned)
  • Pax distribution

·           Children ages

  • Destination
  • Remarks (essentially provides the redeem info for the client to know what to do to obtain the tickets)
  • Supplier information including (only if available)

        ·           Name
·           Address
·           Ref. Supplier (this is the external reference of the supplier)

  • Bookable and payable by information
  • Barcode or QR code information if applicable

TECHNICAL IMPLEMENTATION REVIEW

The technical implementation review is very simple: we will review how you have configured your requests and how well you are using GZIP compression. Also we will like to ensure that you are not sending multiple requests for one destination or, for example, to fulfill one destination product, that you are sending one request for each product in one destination.

The controls here are to ensure that you are performing and executing the requests in an expected manner.

In this step we will also review your website (if applicable) and understand if all the mandatory information is being provided and if not we will come back to you for further information or to ask you to perform the relevant changes.

CONFIRMATION OF YOUR CERTIFICATION

This is the last step and it will mean that you have been certified and approved to go live. At this time you will be expecting to have a different Key and Secret code that you will need to change on your side as well as the URL to connect.

Information will be given to you upon confirmation. The last step ones you are live is for us to review your LIVE process by executing one booking on your side and review the information that is given. The check will only be to ensure that the bookings is well created. We will do it on your behalf and in agreement with you.

You will then be ready and LIVE!

  

 

Remember that if you have any questions you can contact us on integrations@activitiesbank.com

 


Before we start with the certification process we will need some information from you. These information will be:

  • List of operations that you have implemented. Sometimes clients decide not to implement all operations. We want to know the scope of your development. Here we will provide you with a template for you to fill in. The possible operations to be implemented are:

Operation

Implemented?

Comments

Search

YES / NO

Please detail here what type of searches and filters you have used. For example, if you have decided to implement filters for GPS and Destination. Detail all of the filters included

Detail

YES / NO

Indicate here whether you have implemented the "Simple" or "Full" 

Retrieve Pickups

YES / NO

Please indicate if you have implemented this operation

BookingConfirm

YES / NO

Please indicate if you have implemented the Confirmation as well as if you have implemented the Pre-Confirmation. Pre-Confirmation is typically used for clients that perform pre-payments to their clients and do not want to confirm before they have collected from the final consumer. This operation is Mandatory to complete a booking funnel.

Booking Detail

YES / NO

This operation is Mandatory to complete a booking funnel.

Booking List

YES / NO

Please indicate if you have implemented this operation

CancelRequest

YES / NO

Please indicate if you have implemented this operation. Is highly advised that you allow your customers to cancel their bookings and if so this operation shall be implemented. 

Modifications

YES / NO

Please indicate and share with us if you have implemented a process to modify bookings

 

  • Website information: We will ask you for your website information (most probably your test environment). In particular we will need the following: 

1.     URL for TEST or LIVE website. If LIVE there needs to be a clear understanding on how to make bookings and how those are going to be cancelled afterwords. 

2.     If your business is not to provide a website to your clients we have to review technically your implementation but also ensure what is your certification process to your clients. Please have a process of what mandatory information you are asking your clients to fulfill. 

As part of the certification what is it going to be reviewed or tested?

As part of the certification process what we do is to test and ensure that your team can get an additional external support in testing the functionality and implementation of the relevant and mandatory information. Why do we mandate for some information to be shown or provided to the customer? The reason is simply to avoid issues with the final consumer or he or she being misled by wrong or incomplete information being provided. Our team is focused on ensuring that the final consumer is not going to have any problems. This is ultimately converting to customer satisfaction and no issues.

Having said this, the tests that we do consider two scenarios:

-          Standard operations: in case the implementation only considered the following operations Search, Detail, Booking Confirm, Booking Detail, BookingList, and CancelRequest

-          Enhance operations: in case the implementation also added features such as modifications and pickups the tests to be done will be increased.

The testing is planned to be done considering the following test variables:

Destination

  • Barcelona (either using a GPS coordinates or a destination code).
  • Berlin (using GPS codes)
  • Orlando (using Destination the destination code and a keyword of your choice)
  • Algarve
  • Ljubljana

NOTE: If you are implementing availability using a Hotel Id please replace the test in Orlando using a Hotel ID (regardless of whether it is Hotelbeds, GIATA or TTI code).

Passengers’ distributions to be used:

  • 1 adult
  • 2 adults - 1 child (8 years old)
  • 3 adults - 2 children (3 years old and 9 years old)
  • 2 adults - 2 children (1 year old and 17 years old)

If the implementation considers the Standard operations, the following tests will be performed:

Test #

Description

Description and steps

Test 1

Booking funnel buying one product and cancelling it

1.        Search for a list product in Barcelona

2.        Select one product and perform the Detail operation for the selected product (you can select the product as per your convenience)

3.        Confirm the booking – Booking confirmation (here please use either the pre-confirm and/or re-confirm or confirm as per your implementation – In this case we will need to know the way you have decided for the implementation)

4.         Perform the detail of one product (you can select the product randomly)

5.        Confirm the booking – Booking confirmation (here please use either pre-confirm and re-confirm or confirm as per your implementation)

6.        Generate the voucher

7.        Perform a booking detail to retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)

8.        Cancel the booking

Test2

Booking funnel confirming two services

1.        Search for product in Berlin (if the destination is being sold if not we will select a different one) using a GPS coordinates

2.        Perform the detail of one product (you can select a product randomly)

3.        Perform a detail of a second product (you can select a product randomly)

4.        Confirm the booking with both services – Booking confirmation (here please use either pre-confirm and re-confirm or confirm as per your implementation)

5.        Generate the voucher

6.        Perform a booking detail to retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)

7.        Cancel the booking

Test 3

Booking funnel confirming a bundle product (if you have implemented bundle product)

1.        Request for availability in Orlando (if the destination is being sold if not we will review another location)

2.        Perform a detail of one bundle product

3.        Confirm the booking

4.        Print the voucher/s for each product that is bundled

5.        Retrieve the information of the booking (this will only be done in case you are providing this service to the end customer)

6.        Cancel the booking

Test 4

Booking funnel but adding a product that has questions in it

1.        Request availability for “Ljubljana”.

2.        Add one product that has questions, example:

a.        "activityCode":"E-E10-ALPINELAKE"

b.        "name":"Alpine Lakes Bled and Bohinj"

3.        Book the product including the questions: for example:

a.        "question": {

                  "code": "HOTEL",

                   "text": "Please advise the name of your hotel"

                   "answer": "Hotel TEST"

4.        Cancel the booking

 

NOTE: For each of these tests we will ask you to provide to us evidence of each operation including the Request and Response for all of them. 

In addition to this in the event that you are doing and opting for the Enhanced operations which include Pickup and Modifications, these:

Test #

Description

Description and steps

Test 5

Search and book and excursion

1.        Search an excursion product in Algarve (destination code “FAO”). Once the search is completed you can look for an excursion for example:               "value":"X-P01-INTERACAO". (Ensure you look for any product that is an excursion. "type":"EXCURSION").

2.        Obtain the full detail for the excursion

3.        Retrieve the pickup information

4.        Confirm the booking (in case you are doing a pre-confirmation please use the pre-confirmation and then the confirmation). If not please only provide us with the confirmation information.

See an example of booking funnel for this here. You can use a combination of pax as per your own wish. Only one combination for this test will be sufficient.

Test 6

Modification of product already booked

1.        Obtain a product by searching for it in Orlando destination.

2.        Perform a full detail of the product to get the full description of it.

3.        Book and confirm the product (for example)

4.        Perform a second detail

5.        Confirm the modification of the product

See an example of booking modification for which the following was modified:

1.        Client reference

2.        Pax name

3.        Modality change (meaning that the service was kept the same but the modality first booked was replaced by a new modality for the same service).

You can use a combination of pax as per your own wish. Only one combination for this test will be sufficient.

 

Mandatory information

As part of the integration process relevant information is mandatory to be provided to the client at some point during the booking funnel.

We don't want to restrict or constraint the way you implement your booking funnel at all, however, we have to make sure that we do provide all relevant information is provided to the end consumer. We will not tell you how many pictures, for example, you have to show, but we will require you to provide (if returned) the information on cancellation policies that apply to the product that is being booked. 

A list of all the relevant information that is mandatory to provide to the customer is provided below. 

Search Response

The information to be provided to the client that is mandatory and as a minimum is the following:

Operation

Area that is mandatory

API Attribute

Search

Name of the ticket or activity

activities/@name

Search

Description: You will see that in the Search descriptions may be cut. As a result we strongly recommend that you concatenate a link to "More information" in order for the client to click there and go to the detail information of the product where the full description shall be used. We recommend to add the "More information" link in the red box shown in the example below

activities/content/@description

Search

At least one picture of the ticket

activities/content/@media

Search

Price from for Adults

activities/amountsFrom/@paxType

activities/amountsFrom/@amount

Detail

Regardless of whether the request is done for a full detail or a simple detail the following information is mandatory to be shown to the final consumer. These values in the response of the Detail shall be provided at some point to the end consumer through the booking funnel.

Operation

Area that is mandatory

API Attribute

Detail (Simple or Full)

Name of the activity

/@name

Detail (Simple or Full)

Full description of the activity

/@description

Detail (Simple or Full)

At least 1 image

/media/images

Detail (Simple or Full)

Destination

activity/country/destinations/@name

Detail (Simple or Full)

Features

/featureGroups

Detail (Simple or Full)

Price per adult

activity/amountsFrom/@paxType

activity/amountsFrom/@ageFrom

activity/amountsFrom/@ageTo

activity/amountsFrom/@amount

Detail (Simple or Full)

Price per child

 

Detail (Simple or Full)

Currency

activity/@currency

Detail (Simple or Full)

OperationDates

activity/operationDays/@name

Detail (Simple or Full)

Cancellation policies

activity/modalities/rates/rateDetails/operationDates/@cancellationPolicies

activity/modalities/rates/rateDetails/operationDates/cancellationPolicies/@dateFrom

activity/modalities/rates/rateDetails/operationDates/cancellationPolicies/@amount

 

Detail (Simple or Full)

Modalities information

activity/modalities/@name

activity/modalities/duration

activity/modalities/duration/@metric

activity/modalities/duration/@value

Detail (Simple or Full)

Modality price

activity/modalities/amountsFrom/@paxType

activity/modalities/amountsFrom/@ageFrom

activity/modalities/amountsFrom/@ageTo

activity/modalities/amountsFrom/@amount

Detail (Simple or Full)

Questions to be answered

activity/modalities/questions

activity/modalities/questions/@text

Detail (Simple or Full)

Rate information

activity/modalities/rates/@name

activity/modalities/rates/@shortDescription

Detail (Simple or Full)

Session

activity/modalities/rates/rateDetails/sessions/@name

 

Detail (Simple or Full)

Language

activity/modalities/rates/rateDetails/languages/description

Detail (Simple or Full)

Rates

activity/modalities/rates/rateDetails/paxAmounts

Detail (Simple or Full)

Comments

activity/modalities/comments

activity/modalities/comments/@text

Booking confirmation

As per the previous analysis once a confirmation is done the following shall be shared as a minimum with the client:

-          Name of the activity

-          Date of service booked

-          Modality, Rate, Session selected by the client

-          Price paid

-          Currency

-          Pax distribution

-          Questions to be answered: (activity/modalities/questions). If the question is required (activity/modalities/question/@required) then this question is mandatory to be input in the Confirmation operation request.

-          Comments (as details in booking/activities/bundle/comments/@type and booking/activities/bundle/comments/@text)

-          Cancellation policies information, if available.

 

Some of the controls that we will be implementing are:

-       See on your website calendars for selecting the dates whether the ticket is doable in the dates provided (this will be used by knowing the operation dates)

Retrieve pickups

The information to be provided here will depend on how much data you would like to give to the client but as mandatory the minimum information is:

Operation

Area that is mandatory

API Attribute

Retrieve Pickup

Description

pickups/@pickupName

Pickups/@shortDescription

Retrieve Pickup

Price

pickups/operationDate/totalAmount/@paxType

pickups/operationDate/totalAmount/@amount

 

Voucher information

1.        Reference number. Booking number

2.        Name of the excursion or ticket

3.        Booking date or date in which the booking was confirmed

4.        Pax name (lead name)

5.        From and to for the excursion or ticket

6.        Modality name

7.        Session selected (in case available as not all activities have this being returned)

8.        Language selected (in case available as not all activities have this being returned)

9.        Pax distribution

·           Children ages

10.     Destination

11.     Remarks (essentially provides the redeem info for the client to know what to do to obtain the tickets)

12.     Supplier information including (only if available)

·           Name

·           Address

·           Ref. Supplier (this is the external reference of the supplier)

13.     Bookable and payable by information

14.     Barcode or QR code information if applicable

Technical implementation review

From a technical review it is simple we will review how you have configure your requests and how well you are using GZIP compression. Also we will like to ensure that you are not sending multiple requests for one destination or for example to fulfill one destination product that you are sending one request for each product in one destination.

The controls here are to ensure that you are performing and executing the requests in an expected manner.

In this step we will also review your website (if applicable) and understand if all the mandatory information is being provided and if not we will come back to you for further information or to ask you to perform the relevant changes.

Technical implementation review

This is the last step and it will mean that you have been certified and approved to go live. At this time you will be expecting to have a different Key and Secret code that you will need to change on your side as well as the URL to connect.

Information will be given to you upon confirmation. The last step ones you are live is for us to review your LIVE process by executing one booking on your side and review the information that is given. The check will only be to ensure that the bookings is well created. We will do it on your behalf and in agreement with you.

You will then be ready and LIVE!

 

 

Remember that if you have any questions you can contact us on integrations@activitiesbank.com

 

Docs Navigation