Payments are confirmed server-side
Cashfree hosts checkout, but MANGLO does not trust the browser alone. Wallet credit is created only after the server verifies the payment status and amount.
TRUST & SAFETY
Trust should live in the system, not just the copy.
MANGLO is built so important decisions—payment confirmation, pricing, wallet debits, destination checks, supplier outcomes and eligible refunds—are validated by the backend rather than left to appearances on the screen.
Protected order path backend-validated
Payment verifiedWallet top-ups require server-confirmed payment state.
Quote recheckedService price, quantity and availability are validated again.
Destination checkedSupported target types are verified before supplier submission.
Outcome monitoredSupplier status feeds refunds and service-health scoring.
BUILT-IN CONTROLS
Protection should happen before something goes wrong.
These are operational controls already present in MANGLO’s live product flow—not generic security claims added after the fact.
Every wallet movement leaves a record
Deposits, order debits and eligible refunds create separate wallet-ledger entries with the resulting balance so money movement stays traceable inside the account.
Wrong destination types are blocked early
MANGLO validates supported platform links before supplier submission—for example, follower services require profile or channel targets instead of content links.
Supplier quality is learned from real outcomes
Completed, partial and failed orders feed a rolling service-health score. Repeatedly failing services can be automatically quarantined instead of remaining equally recommended.
Eligible failures restore wallet value
Definitive supplier rejection and provider-reported failed or cancelled outcomes trigger protected, idempotent wallet restoration. Partial delivery can produce a proportional refund.
Sensitive credentials stay behind the server boundary
Supplier API credentials and payment secrets are not intended for client-side use. Customer actions call MANGLO endpoints, while secret-bearing provider operations stay on the backend.
BEFORE MONEY MOVES
One order passes through multiple checks.
MANGLO does not treat a button click as proof that an order is valid. The transaction path validates the current service state, live price, quantity, destination and wallet conditions before the supplier receives the order.
The order engine requires an active, operator-enabled service backed by recently synchronized supplier data.
MANGLO recalculates the live wallet charge and validates the quantity again before any debit is accepted.
Supported platform URLs are checked against the service intent so obvious target mismatches are rejected before submission.
The wallet debit and order record are created together, with an idempotent transaction entry tied to the order.
After submission, MANGLO reconciles provider status and converts it into customer-facing outcomes, refunds and service-health feedback.
SUPPLIER RELIABILITY
Trust is earned by recent outcomes.
MANGLO’s service-health system looks at recent completed, partial and failed provider outcomes so recommendation quality can change with evidence instead of leaving every supplier service on the same permanent score.
ROLLING QUALITY SIGNAL
Every outcome should make the next recommendation smarter.
New services begin from a neutral baseline. Real delivery history then pushes the health score up or down. Repeatedly failing services can cross the quarantine threshold and be paused automatically.
Completions improve confidence
Successful recent outcomes push a supplier service toward stronger recommendation quality.
Partial outcomes count differently
Partial delivery is treated as a weaker outcome than a full completion and may trigger a proportional wallet refund for the undelivered portion.
Repeated failures reduce trust
Provider cancellation, failure or rejection lowers the rolling health score rather than being ignored as a one-off customer problem.
Quarantine removes bad options
Once the failure evidence crosses MANGLO’s conservative threshold, the service can be automatically paused and audited so customers stop seeing it as available.
MONEY & OUTCOMES
Refund logic follows the actual provider outcome.
The dashboard status is not decorative. MANGLO reconciles supplier status and applies the eligible wallet outcome according to what the provider actually reports.
What different outcomes mean
Completed
The supplier reports full completion. No automatic refund is created for that completed order.
Partial
If the supplier reports an undelivered remainder, MANGLO can calculate and return the corresponding proportional amount to the wallet.
Cancelled / Failed
Eligible provider-reported cancellation or failure results in protected wallet restoration and a recorded refund entry.
Submission uncertain
If supplier confirmation is interrupted, MANGLO avoids blind retry and blind refund until the actual provider state is verified.
Important boundaries
No browser-side payment authority
A success screen by itself is not enough to create wallet credit; MANGLO verifies the payment from the backend.
No silent duplicate refunding
Order refunds use idempotency keys so the same terminal provider result does not repeatedly credit the wallet.
No blind retry on ambiguous submission
If supplier confirmation is interrupted and the submission state is uncertain, MANGLO holds the order for verification instead of risking a duplicate submission.
Support is tied to real account context
Signed-in customers can open order-linked support requests so the relevant MANGLO order can be checked rather than relying on screenshots alone.
MANGLO AI
AI can assist. The transaction engine still decides.
MANGLO AI can help compare the catalog and explain options, but AI is not allowed to bypass service availability, live pricing, destination validation, wallet balance or supplier checks. Manual browsing and ordering remain available without AI.
AI can help compare
Backend revalidates
Transaction rules win
REALISTIC PROMISES
Clear expectations are part of safety.
Social platforms and upstream providers remain outside MANGLO’s control, so trust also means being honest about what the product cannot guarantee.
MANGLO does not promise that a service will make content viral, produce organic sales, or create a specific algorithmic outcome.
MANGLO does not claim that any social-growth service can override a platform’s moderation, eligibility or account rules.
Retention, refill availability and delivery characteristics depend on the exact listing and upstream provider conditions.
Something still doesn’t look right? Bring the exact order.
Use order-linked support after signing in, or contact MANGLO at support@manglo.shop. Support can review the MANGLO order context, provider status and relevant wallet history instead of guessing from a generic message.