Events

Event contracts for the Float Service: what it publishes to EventBridge and what it consumes. Flow behavior lives on the domain pages linked from each row.

Published

user_float_created

Published to EventBridge by the API Lambda immediately after a float record is successfully written to RDS.

Field Value

Event source

float-service.api

Event type

user_float_created

Payload

Full float object: id, user_id, type, amount, fee, debit_status, debit_date, credit_id, evaluation_id, created_date, is_custom_payback_date, default_payback_date

Trigger

POST /{user_id}/floats — after the RDS write succeeds, before the response is returned

Downstream services subscribe via their own EventBridge rules; the Float Service does not manage those subscriptions.

Consumed

Each inbound event is tapped from EventBridge into a dedicated SQS queue (with DLQ) consumed by the handling Lambda; the ACH callbacks arrive on Kinesis.

Event Source Transport Handled by

new_account (balance update)

txn-service.feeder

EventBridge → SQS site-floats-balance-event-tap

webhook-worker — Webhook Collections

plaid_item_connection_lost

txn-service.miner

EventBridge → SQS site-floats-plaid-disconnect-event-tap

webhook-worker — Plaid Disconnected

plaid_item_connection_revoked

txn-service.miner

EventBridge → SQS site-floats-plaid-disconnect-event-tap

webhook-worker — Plaid Disconnected

ACH payment callbacks

Payments Service

Kinesis prod-payments

ach-handler — ACH Callbacks

Schedule-driven triggers (EventBridge rules and Scheduler entries) are documented in Infrastructure.