Payment Recording
The payment domain defines Cash and Online, but the current commercial workflow exposes only full cash settlement: direct Platform Admin recording or a Platform Admin request for customer proof followed by verification. Online gateway processing is explicitly outside the current scope.
How Payments Work in Survanta
The payment workflow follows these steps:
- A draft invoice is created with the order. There is no invoice without an owning order.
- The order is approved. The invoice changes from Draft to Unpaid.
- Settlement is chosen. A Platform Admin can record cash directly, or request payment proof from the customer for an approved Unpaid or Overdue order.
- The full amount and currency are verified. Partial payment is rejected by the model and workflow.
- Invoice, order, and subscription update together. Payment becomes Verified, invoice Paid, order Applied, and entitlements are applied.
Accepted Payment Methods
The persisted payment-method enum is intentionally narrow:
- Cash: manual settlement, optionally represented by an uploaded proof.
- Online: modeled with gateway provider/reference fields, but no current payment-gateway workflow creates it.
For specific banking details, account numbers, or other payment instructions, contact your Platform Admin directly. This information is communicated outside the platform for security reasons.
Requesting Payment Details
To inspect the payable amount and submit proof after Platform Admin requests it:
- Open Orders and select the approved order to review its invoice total (sign-in and billing permission required).
- Use Upload payment proof on that order's details page.
Open Invoices and select the invoice for the owning order to review its details.
Confirming Your Payment
After you have made a payment:
- Upload an allowed proof file only after Platform Admin requests proof for an Approved order with an Unpaid or Overdue invoice. Orders approved before the proof-request rollout retain the legacy upload path when no payment record exists.
- The first upload creates the invoice's one
PaymentRecordwith status ProofSubmitted. - A Platform Admin can verify it or reject it with a reason. After rejection, a replacement proof updates the same payment record rather than adding a partial or second payment.
- No verification-time service-level promise is encoded in the workflow.
What to Do if Your Payment is Not Recorded
If your invoice remains Unpaid while its payment shows ProofSubmitted:
- Confirm the proof appears on the order details page.
- Wait for Platform Admin verification or rejection.
- If rejected, review the recorded reason and upload a replacement proof on the same order.
Payment statuses are Pending, ProofSubmitted, Verified, Rejected, Failed, Cancelled, and ProofRequested; the cash-proof workflow uses ProofRequested, ProofSubmitted, Verified, and Rejected.