Skip to content

[PLA-16771] Athora Belgium - Quote for Alert Export via API

Create a high level design and a quote for how we would provide the following data over API to a single customer - Athora Belgium.

h3. Requirements

The data export should include the same alert data that they would get by exporting the alerts from the UI "Export" button.

They do not need their own transaction details sent back to them, so long as we include their transaction ID(s) in the alert details.

They want a nightly snapshot of all alerts in the system so they don't have to worry about processing deltas.  (Their volumes are low, perhaps 600 tx per day and 1500 alerts per year.)

The alert transitions are not essential to them (at the moment) so long as they get the current alert details in the nightly snapshot - i.e. they do not mind if they miss alert transitions.

Their preferred format is csv but they are amenable to other formats if necessary.

We didn't discuss the technical details (e.g. retries if we don't get a response from the POST mechanism - did we build retry for Ebanx?) (e.g. retention period for old reports) but Tracy Clarke can put their tech people in touch if and when we need to talk to them.

h3. Acceptance Criteria

A design has been proposed to Athora that they are comfortable that they can integrate with their BI tools (namely Redshift and Power BI, plus some in-house tooling to move data around).

We have an estimate of the effort required to build, test and support the new report - an estimate that we can use to quote a price to Athora and discuss internal priority.

h3. Background

  • They have a number of different compliance systems generating risk scores and alerts, hence they pull the data into Redshift & Power BI to get a centralised view of risk per customer.
  • They have people who can (TBC) probably integrate with an API we give them, e.g. as per the Ebanx export.
  • Their regulatory team needs a yes/no and an estimate by close of play on Tuesday because they set their annual budget on Wednesday (or thereabouts) and need to factor this in.
  • They load transactions using the batch API on a daily basis, generally between 06:30 and 09:30 CET

Issue metadata

  • Issue type: Report
  • Priority: Minor
  • Due date: 2022-04-12