Payment is a commercial event, not a decision
A payment can be relevant to an application, membership, credential, proposal or service engagement, but it should not silently change the substantive status of that record.
What can be recorded
Where configured, a record can retain a payment purpose, amount, currency, provider reference and payment status so operators and customers can understand what the payment relates to.
What remains separate
Eligibility review, approval, agreement execution, credential issuance, membership activation and project acceptance remain explicit decisions controlled by the applicable workflow.
Why the separation matters
Separating payment from decision status prevents inaccurate claims such as paid therefore approved, paid therefore certified or paid therefore a partner.