App Updates:
Android: Native: 3.1.2, JS: 3.1.4
iOS: Native: 3.1.2, JS: 3.1.4
There have been no updates to the app in the past two weeks.
Website Updates:
Wonde – Year Group:
For safeguarding organisations that use or wish to integrate Wonde to maintain their profiles, year group is now included as an optional permission. If you currently use Wonde and would like to enable year group, please grant permission to current_nc_year and inform your Kura account manager, as a full re-sync of Wonde data will need to be arranged. Once permission is given and Wonde data is re-synced, current year group will display in a passenger’s profile:
A passenger's year group will also display in the Passenger Manifest report, in column 'Year':
A year can be entered into the Year search, to display results for the criteria entered:
The Passenger Manifest csv export will also contain Year:
The Passenger Manifest PDF export will also contain Year:
If search criteria has been added to any column, the csv and PDF exports will contain only the filtered results, as normal.
Wonde Information:
If an organisation has already invited observers and passengers to use Kura a conversion may be required before integrating Wonde, to ensure that existing profiles are matched and retained. Additionally Wonde integration may not be possible where multiple systems are used. Text has been added to Wonde integration to let organisations know that Kura support should be contacted before integrating Wonde in these situations.
This has been added to the Bulk Maintenance Wonde integration section:
This has also been added in Settings:
Pricing Navigation:
Pricing navigation has been moved and can now be found in a separate section under vehicles:
Pricing and Payment Setup:
Pricing and payment setup has been consolidated into one page to better guide users during setup, as there are dependencies such as zonal pricing requiring configuration before a Stripe account can be linked to Kura.
When Pricing is selected, zonal pricing, currency and tax are presented for setup:
Once zonal pricing, required tax and currency have been saved, a message will be displayed to confirm that setup is complete and to let a user know that payment and discount features are now accessible:
Once the Kura portal is reloaded, Stripe setup will be shown at the top of the pricing screen. This opens the Stripe portal where a user can enter their Stripe credentials to link their Stripe account to Kura:
The discount menu will also display in the navigation menu, below pricing:
Once a Stripe account is linked, a message will display to show that the integration was successful. When you wish to start allowing payments, select the 'Enable' button and payments will be requested at the time of booking in the Kura portal and app:
Once a Stripe account is linked, a Monthly Payments section is also displayed and a minimum total booking price can be entered for instalment payments to be offered to passengers and observers at the time of booking:
Entering a minimum price will also reveal the cancelled subscription action. If 'none' this will retain all bookings where a user cancels their instalment subscription. If 'remove bookings' is selected, all future bookings will be automatically removed where a user cancels their subscription:
If no minimum price is saved, passengers and observers will pay for their bookings in full.
If a booking cost is higher in value than the minimum booking price and the booking request includes trips that are more than 2 months in the future, an option to pay in instalments will be offered to passengers or observers when booking in the app or website.
An instalment offering is based on full months, from the date of booking to the last trip date included in the booking request, for example:
- If a passenger or an observer are booking on 8th April, for travel from September to 20th December, they will be offered 8 instalment payments.
- If a passenger or an observer are booking on 21st April, for travel from September to 20th December, they will be offered 7 instalment payments.
- If a passenger or an observer are booking in September for travel in September, paying in instalments will not be offered.
- If a booking value is less than the minimum price configured, paying in instalments will not be offered.
The minimum instalment interval offered is 2 months.
The first instalment will be taken at the time of booking and recur each month until the instalment term is complete. This prevents instalment payments continuing after the last month of booked trips, as this could lead to future instalment payments being cancelled after all booked trips have been taken.
If the minimum price was implemented but this is no longer required, the minimum price can be deleted. Once deleted, passengers and observers will no longer be shown the option to pay in instalments when booking.
For organisations using the current instalment configuration, a 'convert' button will display allowing you to use the new instalment method:
If there are any changes to a Stripe account status, this will now display at the top of the Pricing page: