According to recent communication with the iDenfy team, they confirmed my concern that the document expiry notification will not be overridden by the callback URL. This parameter only affects ID verification responses and events, including auto and manual reviews, expiration, and cancellation. Consequently, since we have multiple isolated instances running with the same iDenfy backend, we cannot rely on the notification to manage document expirations as it can be received by one instance per backend.
On the other hand, we can’t solely rely on the expiration data received via the webhook and stored in our database, as it has been missing in some instances. This expiration information is consistently available on the iDenfy dashboard, which may indicate a bug on their end. We need to follow up with iDenfy support regarding this issue.
According to recent communication with the iDenfy team, they confirmed my concern that the document expiry notification will not be overridden by the callback URL. This parameter only affects ID verification responses and events, including auto and manual reviews, expiration, and cancellation. Consequently, since we have multiple isolated instances running with the same iDenfy backend, we cannot rely on the notification to manage document expirations as it can be received by one instance per backend.
On the other hand, we can’t solely rely on the expiration data received via the webhook and stored in our database, as it has been missing in some instances. This expiration information is consistently available on the iDenfy dashboard, which may indicate a bug on their end. We need to follow up with iDenfy support regarding this issue.