Step 1

Begin with a clear payment intent

A payment intent should connect to a real job, campaign, package, agreement, or project room. Before money moves, the parties should know what is being paid for and what counts as completion.

• Tie payment to a specific scope, not a vague conversation.
• Confirm deliverables, revisions, usage rights, and due dates before payment.
• Use Stage work records so payment review has context.

Step 2

Keep ledger records aligned

A ledger record is the operational truth for payment state. It should show what was created, what changed, what was approved, and whether the amount is ready for payout, refund, or hold.

• Avoid external settlement promises that are not reflected in the Stage record.
• Keep invoice, refund, dispute, and payout references attached to the work state.
• Use admin review when a payment state is unclear or sensitive.

Step 3

Approve work before payout release

Payout should follow the agreed workflow. If approvals, files, or usage rights are incomplete, the payout should wait until the record is complete or reviewed.

• Check final files, proof links, or delivery notes before approval.
• Confirm the correct recipient and payout readiness before release.
• Hold payout if a dispute or refund review is active.

Step 4

Use review paths for exceptions

Refunds, partial delivery, failed payment attempts, chargebacks, and disputes need a controlled review path. The safest outcome is based on the written record, not memory or external screenshots.

• Record reason, timeline, and responsible reviewer for every exception.
• Keep customer and creator communication consistent with the ledger state.
• Escalate money or legal uncertainty to the correct admin workflow.