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:
Bulk Maintenance - Append and Replace:
For safeguarding organisations that maintain their profiles via bulk maintenance, the append and replace upload process has been improved to significantly reduce the time required to process files. A file containing 15,000 records; 5000 passengers and 10,000 observers, previously took approximately 25 minutes to process. A file of this size will now take approximately 3 minutes to process.
The upload options are located under Profiles->Bulk Maintenance for Append and Replace:
An error will now be displayed, during file review, if the IsPassenger field is blank. This field is now mandatory, to ensure that the correct profile type is created, and requires either:
- TRUE - Passenger
- FALSE - Non-Passenger (observer or employee)
After a file has been submitted for processing, if the file loaded contains more than the maximum 5000 passengers allowed, an error will be displayed:
If the file loaded contains an invalid telephone number, the upload process will fail. An error message is now shown to confirm that the file has failed to upload:As email address must be unique, if two profiles with the same email address have been manually created for an organisation, as the upload is not able to identify which profile should be updated, an error will be displayed. This contains the email address that already exists for a profile in the organisation:
Stripe Account Status:
Where an organisation has linked their Stripe account to allow payment, the account status will now been shown in Payment settings. An organisation can login to their Stripe account and view their dashboard to view more information regarding the status.
Where an account is enabled (the account allows payments to be taken but a sales volume hasn't yet been reached to require additional information) or complete (all information required has been provided and verified), Stripe account status 'Approved' will be displayed:
As sales volumes increase, additional information is required; such as identity documents, to fully authorise the account. Stripe may restrict an account, disabling payments and payouts, if required documentation is not provided within the required timeframe. Usually 14 days notice is provided for documentation to be submitted. Where an account has a deadline to receive information, the status will be shown as 'Restricted Soon':
Where documentation has been submitted for Stripe review or Stripe are attempting to verify recently provided details about an account, payments and payouts are enabled and the account status will be 'Pending':
Where an organisation doesn't provide required information, Stripe may restrict the account so that payments are disabled. In these cases the account status will display 'Restricted'.
As Stripe disabling payments will prevent passengers and observers making payment for bookings via the Kura app or website, default route settings will automatically change when an account enters a restricted state so that 'Bookable by' is 'None'. This will prevent passengers and observers seeing errors whilst attempting to submit payment, as active routes will not be displayed to book. Once Stripe receive and approve required documentation and the account is approved, the prior 'Bookable by' default setting will be restored so that bookings resume.
In general, accounts are rejected by Stripe if they’re suspected of fraudulent activity. In the event that an account is rejected, a status of 'Rejected' will be displayed'.