Changelog

Enhancements

Location-based liveness re-validation

The contract activation flow now enforces a 80 km radius check. When a user requests an OTP from a location more than 80 km from their last active device, the system requires liveness re-validation before proceeding. This prevents account takeover from geographically distant devices.

Use POST /api/BusinessRequest/CustomerSign/StepReValidateLiveness to handle this case — see the E-Contracting guide for the updated flow.

Improved AML screening

AML (Anti-Money Laundering) results are now returned in the services.AML object on all identity verification responses, including isVerificationProcessCompleted: true responses. Previously AML results were only available on the final liveness step.

Bug fixes

• Fixed idExpiry returning null for some national ID back scans
• Resolved an edge case where isDigitalIdentityVerified stayed false after a successful NTRA check when CSO was disabled on the tenant