Skip to content

PAYMENT_RULES.md

Latest commit

 

History

History
74 lines (46 loc) · 1.19 KB

PAYMENT_RULES.md

File metadata and controls

74 lines (46 loc) · 1.19 KB
Raw

💰 Payment Rules & Validation

EN: Current-state payment lifecycle, validation rules, and operator responsibilities.

PT: Ciclo de vida atual de pagamentos, regras de validação e responsabilidades do operador.

Payment States

  • pending → requires verification
  • completed → confirmed valid
  • rejected → invalid proof or mismatch

Payment Types

Cash

  • Immediately marked as completed

Multicaixa / Bank Transfer

  • Requires proof upload
  • Starts as pending

Proof Handling

  • Files stored securely
  • Access via signed URLs
  • Proof must be reviewed manually

Validation Rules

A payment is valid if:

  • Amount matches expected value
  • IBAN matches gym account (if applicable)
  • Transaction reference is consistent

Operator Responsibility

At current stage:

  • Operator must validate proofs
  • System does NOT guarantee automatic verification

Reconciliation

  • Payments must be reviewed against:
    • expected revenue
    • class bookings
    • memberships

🚨 Risks

  • Incorrect proof interpretation
  • Missing verification
  • Manual approval errors

Goal

Ensure:

Financial data is traceable, auditable, and explainable