SFTP share for death notifications

Operations available to manage death notifications. Notifying the corporate partner that a death notification is available is performed using a webhook, or by retrieving XML files from an SFTP server. This page offers an instruction for corporate partners who've been appointed a fileshare. If you wish to request an SFTP fileshare, please contact your Closure account manager.

Authentication

Authentication details have been shared with your technical contact person. Closure solely supports SFTP (over SSH) using key-based authentication. This key should only be used by the production environment and can only be configured by Closure manually. The SFTP share set-up for production use is further protected by IP whitelisting. N.B.: your credentials can not be used for command line access on the Closure infrastructure.

Operations

By default, the SFTP share is set-up with an unwritable root directory, and will contain three folders. These folders are write, edit and delete enabled and are explained below.

new/

In this folder, Closure will place a single death notification per file, in the agreed file format (either XML or JSON). Closure offers a default XSD or JSON template, or can accept a standard offered by the corporate partner. The name of the file shall indicate a Closure ID and a timestamp.

processed/

If the internal business logic processing the death notification is done, the notification file is to be moved to processed/. Additionally, the partner is offered to be change the notification to report a status. The partner should not remove or overwrite any data from the notification.

Closure will by default look for a StatusCode key in the root object, in which HTTP response code standards are to be used: 200 indicates success, 422 unprocessable entity, and 404 will be expected if the deceased person is not found using offered data. If a standard is agreed upon, Closure will follow the standard only.

If the deceased person is not found (404), Closure will take appropriate action to inform the deceased person and optionally allow a change in their data to retry the notification. In this case, Closure will post a new death notification.

If the notification is marked as unprocessable, Closure will escalate the notification and first will manually check the notification, republish a new file in new/ if any human error was made, or contact customer support of the corporate partner's customer support to manually inform the partner.

archived/

When Closure has interpreted the processed notification, Closure will move the file to archived/ and keep the file there for 7 days. After this time, the file will be deleted.

Multiple products

If the corporate partner is to be informed of multiple products for a single (deceased) customer, Closure will publish a notification per product. If Closure should combine the notifications into a single file, please contact our Support.