ai-diagrams · Diagram examples · Sample fintechEvent catalog
■ Conceptual card catalog
Platform domain event catalog
Ten events published by four producers: registration, accounts, billing and security. Each card shows when the event is emitted, its payload and its consumers.
E01
Customer registered
When
Onboarding approves the customer registration.
Payload
cliente_id, documento, situacao
Consumers
Accounts, notifications.
cliente.cadastrado.v1
E02
Customer updated
When
The customer's personal details or address change.
Payload
cliente_id, campos_alterados
Consumers
Accounts, billing.
cliente.atualizado.v1
E03
Account opened
When
The account status changes to open.
Payload
conta_id, cliente_id, numero
Consumers
Billing, statements, notifications.
conta.aberta.v1
E04
Account blocked
When
Security or customer support blocks the account.
Payload
conta_id, motivo, origem
Consumers
Billing, notifications.
conta.bloqueada.v1
E05
Transaction recorded
When
Each credit or debit recorded in the account.
Payload
movimento_id, conta_id, valor
Consumers
Statements, fraud prevention.
movimento.registrado.v1
E06
Invoice issued
When
The invoice is finalized and assigned a number.
Payload
fatura_id, valor_total, vencimento
Consumers
Notifications, statements.
fatura.emitida.v1
E07
Invoice overdue
When
The invoice becomes overdue with no identified payment.
Payload
fatura_id, dias_atraso
Consumers
Notifications, customer support.
fatura.vencida.v1
E08
Attempt declined
When
The automatic collection attempt is declined.
Payload
tentativa_id, fatura_id, resultado
Consumers
Notifications, customer support.
tentativa_cobranca.recusada.v1
E09
Payment received
When
The amount is credited and reconciled with the invoice.
Payload
pagamento_recebido_id, fatura_id, valor
Consumers
Accounts, statements.
pagamento.recebido.v1
E10
Access restored
When
The customer completes account access recovery.
Payload
cliente_id, canal, dispositivo_id
Consumers
Notifications, fraud prevention.
acesso.recuperado.v1
Each event goes through the producer's outbox; the consumer never reads a table from another schema.
The complete payload schema is in the schema registry; the v1 suffix is the contract version.