Clear evidence. Lasting trust.
A daily check on every financial movement
GlowNearMe’s reconciliation compares gateway settlement gross, processing costs and net with the original financial journal. It keeps observed differences as an audit history, rather than treating an unpaid hold, a return page or a requested refund as money received.
Two directions. One currency.
The check reads gateway settlement pages, then looks for journal movements missing from that daily slice. Amounts must match exactly in the same currency. Unsupported conversions are flagged, never equated.
Resume, don’t restart.
A day is checked in bounded steps. Interrupted steps retain their progress and repeat safely. Fresh checks keep new results alongside earlier observations; they never erase an older mismatch.
Corrections preserve the original.
Journals have equal debit and credit amounts. A correction must exactly reverse its original journal and retain a reason. Owner checks cannot approve refunds, rewrite balances or dismiss discrepancies.
A matched check is not a payout guarantee
The daily comparison uses Stripe’s platform balance-transaction settlement feed. It does not certify the bank statement, transfer funds or make earnings withdrawable. Payouts still require completed care, the configured hold, dispute protection and a verified weekly settlement workflow.
What a discrepancy can mean
- A captured charge has not reached the journal yet.
- A gateway cost arrived after the first payment update.
- A refund is pending, failed or differs from the expected sum.
- A journal movement settled on a different calendar day.
- The platform settlement uses an unsupported currency conversion.
- A transfer, bank payout or subscription still needs its dedicated settlement workflow.
No journal is created automatically from an unmatched settlement. Payment recovery and reconciliation are separate tasks. Refresh verified payment evidence first, then start a fresh check to retain the resulting comparison.
Confirmed refunds, not requested amounts
Late or unusable captures use one saved compensation identity. Pending, failed and cancelled refunds do not count toward a successful refund total. Returned processing costs remain the platform’s responsibility and never become an extra provider deduction.
Previously confirmed appointments require the separate policy-aware cancellation workflow. They cannot accidentally enter late-payment compensation merely because their current booking status changed.
Daily scheduling & administrator safeguards
A protected scheduled task is written for the previous completed Malaysia/Singapore day. Deployment still needs a trusted scheduler and a private financial-task credential. Repeated calls resume the same check until both scan directions finish.
Owners see only their own business evidence. Platform-wide discrepancy records remain reserved for mandatory-two-factor administrator access, which is unavailable in the current account service. Customer charging remains closed while quota, refund-policy, payout and local-method safeguards are unfinished.
Stripe credentials are present. Real settlement checks still require verified financial protections.
Deterministic comparison checks
10 charge, refund, missing-cost, currency, reversal and net comparisons passed, together with UTC+8 daily boundaries. These checks do not contact Stripe or create financial entries.
Connected Stripe, owner permissions, resumable jobs and database protection still need separate browser and gateway QA. No charge, refund or payout was sent by this guide.