Skip to content
GlowNearMe beauty and wellness discovery logo

Clear policies. Original promises.

Cancellation & attendance, explained

GlowNearMe applies the policy saved with a confirmed appointment. Review an itemized refund before cancelling, then follow its separate gateway result. An unpaid checkout hold is released without pretending a payment was made.

Flexible

Full refund when cancelled at least 24 hours before the appointment. No refund inside 24 hours.

Illustration: cancel 12 hours early

A Malaysia example: RM80 care + RM20 extras + RM10 travel + RM3.75 customer fee + RM6.83 tax. Not an actual booking or approved tax determination.

RM 0.00refund decision

Moderate

Full refund at least 24 hours before the appointment; 50% refund inside 24 hours.

Illustration: cancel 12 hours early

A Malaysia example: RM80 care + RM20 extras + RM10 travel + RM3.75 customer fee + RM6.83 tax. Not an actual booking or approved tax determination.

RM 60.30refund decision

Strict

Full refund at least 48 hours before the appointment. No refund inside 48 hours.

Illustration: cancel 12 hours early

A Malaysia example: RM80 care + RM20 extras + RM10 travel + RM3.75 customer fee + RM6.83 tax. Not an actual booking or approved tax determination.

RM 0.00refund decision

Decision first. Evidence second.

Each original receipt line uses the same policy percentage and half-up sen/cents rounding. The server rechecks the cutoff when you submit; a stale preview cannot silently change the refund. Customer cancellation is available before the scheduled start.

Cancellation, its actor/reason and the full window release are saved together. The original charge and allocations remain in history; successful refunds add separate balanced corrections. Reloading or retrying keeps the saved refund identity, even when a gateway response is delayed.

Pending, failed or unrelated refunds never count as a completed refund. Refund processing costs stay with the platform. A partial refund does not erase the original capture.

Provider cancellations always refund fully

An authorized professional cancelling a confirmed appointment saves a 100% customer refund and an internal reliability infraction. A suspended business can still manage existing appointments within assigned access. Staff, managers and owners never gain another workspace’s appointments through a link.

Quota impact is separate from refund percentage

Provider cancellation releases confirmed usage. Customer cancellation at least 48 hours early releases usage; inside 48 hours it still counts. This rule does not change whether Flexible, Moderate or Strict gives a refund.

One free reschedule

A customer can move a confirmed, paid appointment once at no charge until its saved policy cutoff: 24 hours for Flexible and Moderate, 48 hours for Strict. The new time must fit the same professional, branch, service, extras, notice period, buffer and any home-visit travel, and must also be before that cutoff. The original time remains reserved until the replacement is saved; if anyone else takes the new time first, nothing changes.

A move does not change the receipt, payment, commission or provider net. After a cancellation, refund or dispute begins, rescheduling is closed. Professionals see that the move happened, but no private customer detail is revealed by it.

No-shows and remaining safeguards

An authorized professional can record a no-show only after the scheduled start plus fifteen minutes, while the appointment is still confirmed. It saves permanent attendance history. The specification does not define the market’s no-show payout amounts, so those earnings stay blocked until that rule is configured.

Dispute resolution and policy payouts remain unfinished. Weekly transfers and recurring subscriptions are not available. Customer collection is still closed: connecting Stripe does not bypass provider approval, pricing review or unfinished settlement safeguards.

Calculation checks

Flexible, Moderate and Strict cutoffs, provider full refunds, half-up receipt lines, balanced allocation reductions and the exact 48-hour quota boundary passed deterministic checks.

These checks do not exercise signed-in actions, concurrent database decisions or a real gateway refund. Connected-service and browser QA are still required.