Change Log
2025 - 06 - 03
Jurisdiction: AUS
VEVO_PERSON_NOT_FOUND now assigned "status": "failure" rather than "status": "completed". Technically vSure's API was able to complete the visa check, but found no such combination of Document Type, Country, Identifier (number) and DOB in the Home Affairs database. Whilst technically a "completed" check, we felt returning as "failure" was more aligned to the developer expectation AND aligns to billing (failures are not charged, nor was VEVO_PERSON_NOT_FOUND. Now all completed checks are chargeable and failures are not).
2025 - 05 - 27
Jurisdiction: NZL
New result code: VISA_UNAVAILABLE
Check type: verification
Some clients were getting completed checks returning an empty visa array. We found retries fixed the issue. But to ensure this issue never recurs the vSure V2 API will now no longer return a completed check with an empty visa array. If it finds a successful check with no visa data, the check will now auto-retry up-to 3 times and if the NZL Immigration returns no visa data each time, the result will be a status: failure with the new result code: VISA_UNAVAILABLE. NOTE: we have found the rety function fixes the issue and have not seen any further examples of empty visa arrays, but this result code is there just in case.
2025 - 05 - 21
Jurisdiction: NZL
Check type: verification
Issue resolved: inconsistent returning of result code REALME_NO_ACCESS - "Customer Authority does not have access to perform a verification check" with the same Customer Authority credentials that worked before and after the error.
One client was receiving inconsistent outcomes with the same Customer Authority. That is they were getting result code REALME_NO_ACCESS - "Customer Authority does not have access to perform a verification check" with the same Customer Authority credentials that worked before and after the error. To resolve the issue we implemented up-to 4 retries in the event of REALME_NO_ACCESS. NOTE: we have found that the rety function fixes the issue and have not seen any further examples of false failures based on NZL immigration rejecting the Customer Authority.
2025 - 05 - 19
Jurisdiction: NZL
Check type: verification and employer
Issue resolved: ISO Country Code mapping error leading to UNKNOWN_ERROR result code
Whilst the vSure API Accepts the ISO Country code, the NZL Immigration system does not. In fact they have their own country list, that don't align to the ISO country names list at all. vSure maps the global standard ISO 3166-1 alpha-3 to the NZL Immigration country list. Errors were found in our map, which have now been corrected. Around 10% of countries were affected, with the most common being: GBR, NLD, VNM and KOR. The mapping has been updated and processes put in place to monitor NZL Immigration's official country list moving forward.