Request is not decision
A submitted request should receive a receipt, but it is not an approval. The account must show pending, approved, denied, partially refunded, or refunded state honestly.
Provider event is authority
Your order changes only after the payment provider confirms the charge, refund amount, currency, and time.
Economics reverse together
A refund or lost dispute must reverse the matching entitlement, referral share, provider share, and other allocations according to the same item basis.
Show the rule before payment
Every paid offer must display one approved refund rule before checkout. The rule must state whether refunds are available, the request deadline, any use or completion limits, how partial periods or digital course access are treated, how taxes are handled, how to ask, and when a decision should be expected.
Each offer shows its refund window, eligibility, digital-access effect, and location-specific exceptions before payment. The offer at checkout controls.
A person should always know what happened
- The signed-in account selects the exact order or charge and submits a reason through an approved support or account route.
- The service returns a request receipt with an opaque request ID, order ID, requested amount or scope, server time, and current status.
- An authorized reviewer applies the approved offer rule and records the decision, reason category, actor class, and time.
- If approved, the payment adapter sends the exact idempotent refund request to the provider.
- The account remains pending until a verified provider event confirms the actual refunded amount and currency.
- The order, receipt, entitlement, allocation, and access projections update together from that confirmed event.
Do not collapse different outcomes into one label
| State | What it means | What it does not mean |
|---|---|---|
| Request received | The platform recorded an identity-bound request and returned a receipt. | The refund is approved or money has moved. |
| Approved, provider pending | An authorized decision was recorded and the provider request was sent or queued. | The bank or card statement already shows the credit. |
| Partially refunded | The provider confirmed a cumulative amount below the original paid amount. | The whole order, term, or every entitlement was refunded. |
| Refunded | The payment provider confirmed the cumulative refund amount and your order shows it. | All separate account data was deleted. |
| Denied | The approved rule did not allow the request, with an explainable reason and review path. | A person has no separate rights under applicable law. |
Reverse only the amount that was actually reversed
Each provider event must carry the cumulative refunded amount for the exact charge or invoice. The service records only the new delta after subtracting prior confirmed refund events. Replayed or out-of-order events cannot double count a refund.
Referral share, provider share, discounts, credits, and tax need a documented allocation basis. A partial refund should reverse the matching share of each eligible allocation, never an unrelated order or period. Live refunds must stay closed until tax-inclusive or tax-exclusive basis, rounding, and residual-cent handling are proven.
Money and access must reconcile
The exact offer must state whether a full or partial refund ends access, shortens access, changes a membership room, or leaves a separately purchased course available. The server must update entitlement from the same confirmed event and keep the order history and receipt visible.
A refund does not by itself close the main account, remove a community post, delete Signal.OS Focus Maps, erase payment records, or resolve a separate provider relationship. Those actions follow their own approved rules and data boundaries.
A payment dispute is not the same as a refund request
A payment-provider dispute can place an order under review and may limit related access while evidence is evaluated. A won dispute can restore the eligible order state. A lost dispute reverses the payment and matching allocations. The account must show the state without accusing the person of fraud unless an approved process establishes it.
Evidence collection, response timing, access during review, account restriction, fraud classification, and appeal remain operating decisions that require counsel and provider review.
The platform can confirm processing, not a bank's posting time
A completed refund receipt shows the confirmed amount, currency, processing time, and masked destination when available. Bank posting time can vary, so the receipt also shows the provider's current timing range.
A real refund needs more than a button
The refund system handles full and partial refunds, repeated and delayed events, over-refund refusal, taxes, access changes, referral and provider reversals, disputes, interrupted recovery, and an account receipt that matches the payment record.