An application needs reusable database logic for approving expenses across several pages and integrations. What design is strongest?

1. Copy different versions of the logic into each button's JavaScript
2. Centralize the transaction rule in a suitably secured database package
3. Store the rule only in page help text
4. Rely only on a report column format mask