What a customer's recurring platform fee is. Stored on
customer.data.recurringFee.
The feature owns no table of its own. When the fee fires is the
recurring-fee-sweep Temporal schedule's business, and what happened is the
fee_transfer row the charge produces, which already carries the customer,
the amount, the status and a unique idempotency key. A schedule table beside
those would be a third copy of state two systems already hold.
What a customer's recurring platform fee is. Stored on
customer.data.recurringFee.The feature owns no table of its own. When the fee fires is the
recurring-fee-sweepTemporal schedule's business, and what happened is thefee_transferrow the charge produces, which already carries the customer, the amount, the status and a unique idempotency key. A schedule table beside those would be a third copy of state two systems already hold.