Category: Knowledge base
Since June 16th 2018 Google Maps has made the use of their API paid over a certain limit of $200 free usage per month.
They require you to enable Billing on your Google console account so the API keys are operational. Here is a short video about setting up Billing in your Google console account: https://www.youtube.com/watch?v=3Tkp1UdwfjI
You will need to obtain 2 separate API keys as they are used in different cases across the booking platform: Browser and Server API keys.
The difference between these 2 keys is just the Referrer that you set as a security restriction so no one else can use your keys and exhaust your quota. 

To obtain the keys please go to the Google Cloud Console.
Create or select a project.
Click Continue to enable the API and any related services.
You will need to enable:

Google Maps Directions API
Google Maps GeoLocation API
Google Maps Geocoding API
Google Maps JavaScript API
Google Maps Places API for Web 

On the Credentials page, get an API key (and set the API key restrictions).
Note: If you have an existing unrestricted API key or a key with browser restrictions, you may use that key.
To prevent quota theft, secure your API key following these best practices.

You should restrict your API keys, you will see below options for restriction

1) None
2) HTTP referrers (websites) >> This will act as Browser API key
3) IP addresses (web servers, cron jobs, etc.) >> This will act as Server API key
4) Android apps
5) iOS apps

For Browser API key, you have to set different URLs that lead to your Booking form in all different languages. You can view and copy these URLs at your back office > Dashboard > Settings > Map settings.


For Server API key, you have to set server IP address as Referrer. The IP address of your server is also visible at the back office > Dashboard > Settings > Map settings.


Contact us if you have any questions or queries. Add a comment
Category: Knowledge base
At the moment for different prices during different times you have to create 2 separate cars with different availability and add the different price in the Fixed fare route - it will show both cars.
The customer at the front end will not notice any difference as the system will only show the car that is available for the selected time by the customer.

Note: When you use this method you have to take into account that after midnight a new day starts. If you need to create different price for 8 pm (20:00) to 6 am (06:00) time period you will actually have to create 2 separate cars with different availability to cover this time period: 1. 8 pm (20:00) to 11:55 pm (23:55) and 2. 12 am (00:00) to 6 am (06:00). Select the option for each car "Use for Fixed fare routes: Yes" and they all will be available in your Fixed fare route edit screen where you can set a different price for each car.
Add a comment
Category: Knowledge base
Hourly Hire

With The Booking Form you can have Hourly hire or set up each car with Price per hour.
To set that up go to the back office (My Company) > Dashboard > Settings > General Settings > Show Hourly hire: Yes
Then go to back office (My Company) > Dashboard > Cars > New (or Edit) Car.
User as Hourly hire: Yes
Minimum Hours to hire: XX - you can limit the minimum hire time here.
Maximum Hours to hire: XX - you can also limit the maximum hours that this car can be hired for.
Price per Hour: XX - this is your price per hour for the hire.
Hourly hire Fee: XX - this is a flat fee that you can add to your hourly hire, it will be added regardless of the number of hours selected in The Booking Form.

Notes:
  • Customers can select "Minutes" in quarters: 15, 30, 45 and the system will calculate minutes based on your "Price per Hour" option.
  • Customers have to select "Hourly hire" at the top of the booking form Booking type drop down. If only "Hourly hire" booking is available then the Booking type drop down will not be shown.
  • At the booking form number of hours that can be selected in the Hours drop down will be between "Minimum Hours to hire" and "Maximum Hours to hire".
  • You can create Custom fields and assign them to Hourly hire. There is a special Custom field type for hourly hire called "Address search", with it you can allow the Customer to type in Pick up location if you are picking up your customers for your Hourly hire service.
  • You can set up Search URLs directly to Hourly hire pre-selected settings and publish the links anywhere on the web, social media, emails, advertising campaigns, banners, buttons, links etc. 
Add a comment
Category: Knowledge base
For Test Payments:
 
1. Create a demo merchant account. Perform one of the following steps:
• If your company is based in Russia, use the following link:
• If your company is based in other countries, use the following link:
 
2. After the support team completes your registration, add an advanced account for your merchant account.
Perform the following substeps:
a) Open https://demo.moneta.ru and log in to your merchant account.
b) Go to My account > Account management.
c) Under Advanced accounts, click Add account.
d) Complete the form and click Save.
 
 
For LIVE Payments: 
 
1. Create a merchant account. Perform one of the following steps:
• If your company is based in Russia, use the following link:
• If your company is based in other countries, use the following link:
 
2. After the support team completes your registration, add an advanced account for your merchant account.
Perform the following substeps:
a) Open https://demo.moneta.ru and log in to your merchant account.
b) Go to My account > Account management.
c) Under Advanced accounts, click Add account.
d) Complete the form and click Save.
 
 
Merchant Account Settings
 
In account management section («Management» link in the «Accounts» block on the left part of the review page) the authorized personnel of the merchant can set the parameters of interaction between the merchant registration system and MONETA.RU system.
 
 
1) Test mode: Indicates whether your merchant account works in test mode. In test mode, Moneta.Assistant does not create transactions to transfer payments to your merchant account. Use this mode to test status requests and processed payment reports.
 
2) Check URL: (NOT REQUIRED) Specifies the address of the script in your online store that processes status requests from MONETA.Assistant. If you specify the Check URL field, MONETA.Assistant sends status requests to the specified address. 
Important: The web address must include the URI scheme. 
For example, http://www.YOURSTORE.com/check_url.php
 
3) Pay URL: (REQUIRED) Specifies the address of the script in your online store that processed payment reports from MONETA.Assistant. 
Important: The web address must include the URI scheme. 
Please use:
https://booking.drivenot.com/index.php?option=com_tbsaas&controller=pluginresponse&task=pluginnotification&tmpl=component
 
4) HTTP Method: Specifies the HTTP request method that MONETA.Assistant uses to pass parameters to the pages which addresses you specify in Check URL and Pay URL fields. 
Options are:
• GET
• POST
 
5) Code of data integrity verification: (REQUIRED) Specifies a character string that MONETA.Assistant and your online store must use to generate a unique signature for each request and response. You must keep this code secret.
 
6) Mandatory payment form signature: Indicates whether MONETA.Assistant requires the MNT_SIGNATURE parameter in payment requests from the payment form. 
Options are:
• Yes. MONETA.Assistant requires the MNT_SIGNATURE parameter in payment requests. If the payment form sends a request to MONETA.Assistant without the MNT_SIGNATURE parameter or this parameter has a wrong value, MONETA.Assistant returns an error.
• No. MONETA.Assistant does not require the MNT_SIGNATURE parameter in payment requests.
Note: This option is not secure.
 
7) URL settings can be reset: Indicates whether you can redefine the Success URL, InProgress URL,
Return URL, and Fail URL addresses by using the MNT_SUCCESS_URL, MNT_INPROGRESS_URL, MNT_RETURN_URL, and MNT_FAIL_URL parameters in a payment request. 
Options are:
• Yes. You can redefine the Success and Fail URLs in payment requests.
• No. MONETA.Assistant always uses the values that you specify in your merchant account settings.
 
 
8) Success URL: Specifies the address of a web page to which MONETA.Assistant redirects a customer after completing the checkout successfully. The customer is redirected to this web page even if the merchant does not receive a processed payment report.
Important: The web address must include the URI scheme. For example,
http://www.yourstore.com/success_url.php
 
9) Fail URL: Specifies the address of a web page to which MONETA.Assistant redirects a customer if the external payment system cannot process the payment. In this case, MONETA.Assistant does not send a processed payment report to the merchant.
Important: The web address must include the URI scheme. For example,
http://www.yourstore.com/fail_url.php
 
10) InProgress URL: Specifies the address of a web page to which MONETA.Assistant might redirect a customer after a successful funds authorization request, before the payment is confirmed and transferred to the merchant account. This parameter affects only some of the payment methods. MONETA.Assistant redirects a customer to this page even if the merchant does not receive the processed payment report. If you do not specify the InProgress URL, MONETA.Assistant uses the
default page to show the payment progress.
Important: The web address must include the URI scheme. For example,
http://www.yourstore.com/inprogress_url.php
 
11) Return URL: Specifies the address of a web page to which MONETA.Assistant might redirect customers after they decide to cancel a payment and return to the web store. In this case, MONETA.Assistant does not send a processed payment report to the merchant.
Important: The web address must include the URI scheme. For example,
http://www.yourstore.com/return_url.php
Add a comment