Skip to main content
Underflow connects the outside services that move a submission forward. Each integration writes back to the same submission, policy, or accounting record instead of creating a separate workflow.

Shared mailboxes

Receive and send submission correspondence through Mailgun.

Stripe payments

Collect invoice payments and record reversals.

Regulatory data

Screen parties and maintain state-specific surplus lines rules.

External risk scanning

Read consented public-internet findings into the underwriting record.

​
How integrations behave

An integration result is part of the record it affects. An inbound message stays with its thread and linked file. A Stripe receipt stays with its invoice. State filing results stay with the policy transaction. Sanctions outcomes are summarized on the file timeline when the screen runs and can hold the quote or bind that produced a possible match. Failure behavior depends on the service. A refused state filing stays failed for retry. An unverified table-priced state holds the quote letter for review. A sanctions error holds a quote or bind for a person. A cyber scan launches ONYPHE on-demand checks and resumes saved scan IDs. Incomplete or stale results fail without recording clean answers; unsupported findings and missing enrichment remain unknown.

​
Configuration

Underflow provisions shared mailboxes and provider credentials for each MGA. In the product, members manage personal email signatures and reading panes under Settings > Mail. Admins manage the workspace time zone, desk identity, surplus-lines licence, and Aurora charter under Settings > Workspace and Settings > Aurora. State rules are read-only in Accounting.