A schema checks structure and types; a business rule checks whether a result makes sense for the task. Neither replaces the other. A negative money amount can have the correct integer type, while an extra field can introduce an action the caller never approved.
Return accepted true only when case.payload matches the supported case.schema and amount_cents is nonnegative. A valid JSON object can still violate the business rule. Return only the accepted boolean field.
The notebook executes your Python against an original local mock. Use the supplied case rather than copying visible values. The hidden checks change identities, revisions and boundary inputs; no provider endpoint or external tool is contacted.
An example implementation of the function contract.