Integration data flows
Use this reference to identify what starts an external request, what information leaves Finsaku, and where to check the result. The exact fields depend on tenant configuration, templates, and the selected record. Inspect a representative preview or provider request before approving production use.
- For
- Integration administrators, privacy reviewers, security reviewers, and operations staff investigating an external action.
- Requires
- Permission to inspect integrations and the consuming product, template, event action, or record.
- Available when
- The tenant has the relevant provider and workflow configured.
- Before you begin
- Identify the provider account owner, environment, record type, trigger, and representative test case.
- Expected result
- The approved data flow, provider result, stored evidence, and failure procedure are understood before production use.
Provider flows
| Provider | Trigger | Information sent | Result and evidence |
|---|---|---|---|
| Mailgun | User or event action sends an email. | To, CC and BCC recipients, subject, rendered HTML body, and attachments. | Message information and event-action execution can be checked in Finsaku; delivery evidence and retention remain provider-side. |
| Amazon SES | User or event action sends an email. | Recipients, subject, rendered HTML body, and attachments. | Check the Finsaku message or execution history and the owning AWS account for provider evidence. |
| Text2Reach | User or event action sends an SMS. | Telephone number, sender configured for the account, and rendered message. | Check Finsaku execution state and the provider account for delivery evidence. |
| DocuGenerate | User or event action generates a document. | Template data assembled from the selected application or loan context. | PDF or DOCX output can be attached to the selected record; inspect the document and execution history. |
| KIB | Authorised user requests a credit report or a configured export runs. | Personal identifier and the application or selected lending information required by the configured operation. | Enrichment result, report, provider reference, or export outcome appears in the applicable workflow. |
| Loan Calculator | Application terms are calculated through an enabled external calculator. | Product and application terms required by that calculator. | Calculated terms return to the application. Verify inputs, result, rounding, and error state before processing. |
| Neopay | User creates a banklink payment request. | Transaction reference, amount, currency, payment purpose, country or locale, and return context. | A confirmed callback can create a regular loan payment. A cancelled callback does not create one. Reconcile provider and Finsaku references before retrying. |
| Slack | An event action posts a message. | Configured channel and rendered message. | Execution history records Finsaku's attempt; channel delivery and retention are controlled by the Slack workspace. |
viss.gov.lv |
Authorised user performs a PEP check. | Normalised person code. | The result is stored with the applicable enrichment information and can influence configured labels or review steps. |
| Power BI | The configured reporting connection reads available business-intelligence data. | Data selected and exposed through the reporting service. | Validate the dataset, tenant scope, refresh result, destination workspace, and export controls in the Microsoft environment. |
| Custom webhook | A configured tenant or product event occurs. | Standard event data or a custom Handlebars request, URL, headers, and selected method. | Administration → Execution History records status, attempts, response details, and errors available to Finsaku. The receiver must detect repeated events safely. |
Establish account ownership and legal role
Before enabling a provider, record whether the account and agreement belong to Finserio or the customer. This affects incident coordination, data-subject requests, audit access, termination, and whether the provider belongs on the Finsaku subprocessor schedule or the customer's own processor register.
Credit bureaus, payment providers, public-authority services, and customer-selected reporting destinations can have independent legal duties. Do not classify them from the integration type alone.
Test the boundary
- Use non-production or approved representative data.
- Preview the rendered template or webhook body, including optional and repeated information.
- Verify that recipients, endpoints, headers, and provider environment are correct.
- Perform one successful request and the main provider rejection or timeout case.
- Compare Finsaku state, audit or execution history, and provider-side evidence.
- Check what happens if the same request or callback is received more than once.
- Record retention, deletion, support, and incident contacts without copying credentials.
See Integrations, Event actions, and Service providers and subprocessors.