←

System Explanation

Points Only • Not Money • Server Authority

What is Orion Pay X?

Orion Pay X is a store-based loyalty points system designed to increase repeat customers while keeping full control and strong fraud protection. Points are not money. They are a controlled reward balance inside the system.

Store-BasedEvery store has its own balance, rules, and history.
Source-LockedPoints can be redeemed only at the store that issued them.
Server DecisionThe server confirms or rejects every request.
Counts Only SuccessOnly confirmed successful operations are counted.

How it works (practical flow)

1
Store Login

The store logs in using its own credentials. Without a store session, no balance can ever change.

2
Scan Customer QR

The QR contains only a Customer_ID. It is an identifier, not a secret key and not permission.

3
Choose Action

The store selects Earn (grant points) or Redeem (use points), then enters the invoice/discount settings.

4
Server Validation

The server validates: store permissions, store balance, customer record, source-lock rule, limits, and anti-fraud checks.

5
Commit + Ledger

If and only if all rules pass, the server confirms success, updates balances, and writes a permanent ledger record.

Core rules (the system cannot break these)

1) Store Source Rule

Points are tied to the issuing store. The customer can redeem only at the same store. If someone attempts redemption in another store, the server rejects it automatically.

2) Store Balance Rule

The server prevents issuing points if the store does not have enough internal reward balance (budget). No “manual bypass” from the UI.

3) Server-Only Authority

Front-end screens never “edit balances”. They only send requests. The server decides and writes the final result after checks.

4) Operations Counting

An operation is counted only when it is confirmed successful by the server (Earn or Redeem). Failed attempts do not count and do not change anything.

Security & anti-fraud (deep)

Why a QR screenshot doesn’t work

A screenshot contains only a Customer_ID. It cannot modify balances. Balance changes require a logged-in store plus server approval of all conditions.

What the server checks before confirming

  • Store identity and permissions
  • Customer validity
  • Source-lock match (same issuing store)
  • Store balance and transaction limits
  • Ledger integrity (record is created only on success)

Store benefits

  • More repeat customers by making rewards easy.
  • Controlled reward costs (store budget rule).
  • Clear history and accountability (ledger).
  • No cross-store points risk (source-lock).
  • Less fraud exposure (server authority).
  • Fast operations with scan flow.
  • Only confirmed operations are counted.
  • System rejects invalid actions automatically.

Packages & pricing

Plan Operations Period Price
Trial50 free14 days€0.00
Basic800 / monthMonthly€19.99
Standard2500 / monthMonthly€49.99
Pro5000 / monthMonthly€89.99
Business10000 / monthMonthly€149.99
Pay-as-you-goUsage basedMonthly€0.025 per successful operation

FAQ

Why can’t points be redeemed in a different store?

Because points belong to the issuing store. This prevents cross-store abuse and protects each store’s reward budget. The server rejects any mismatch.

When is an operation counted?

Only when the server confirms success (Earn or Redeem). Failed attempts are ignored and do not affect balances.

If someone uses another customer’s QR screenshot, can they cheat?

No. The QR is only an identifier. Any balance change requires a logged-in store and server validation. The server is the final authority.

Contact
For support or business inquiries, email us.
support@orionpayx.org