OurDream Dreamcoins Not Refreshed? Check the Renewal Event
Compare the subscription renewal date, coin ledger and stated processing time before interpreting a missing OurDream allocation as a failed payment.
Match your actual renewal date and plan to the coin ledger. OurDream’s refresh page states 2 p.m. EST on the renewal date, while its Standard plan guide describes recurring monthly allocations. Do not assume local midnight is the promised processing time. If records disagree, ask support to confirm the applicable time zone and allocation event.
A monthly coin allocation and a payment are related records, but they are not the same entry. When OurDream dreamcoins appear not to refresh, start with the plan and renewal event rather than a generic calendar date.
The refresh help page names a renewal-date processing time. The Standard plan guide describes the plan’s allocation structure. Neither page verifies the state of your account.
Match three records
Keep the subscription’s displayed renewal date, the relevant receipt and the coin-history entry together. Record the account context privately so a receipt belonging to one login is not compared with another account’s balance.
| Record | What it tells you |
|---|---|
| Plan and renewal state | Which allocation cycle you expect |
| Payment receipt or billing history | What charge event is recorded |
| Coin ledger | What allocation and later use are recorded |
A current balance alone cannot prove that an allocation never arrived. If the ledger contains both an allocation and later deductions, those are different events from a missing credit. Preserve their sequence before reporting a discrepancy.
Do not replace the stated time with midnight
The refresh page uses the wording 2 p.m. EST. That is not the same as saying midnight in every customer’s location. It also does not explain every daylight-saving or plan-specific case.
Keep that source wording in your notes. If a conversion matters, ask the provider to confirm the actual time zone used for your cycle rather than silently treating EST as an unspecified Eastern local time. An outside guide cannot infer a private processing timestamp from that short FAQ alone.
Compare an expected event with an observed one
For an invented example, a person expects a credit on the first day of every calendar month because that is when they checked last month. Their account instead shows a renewal anniversary later in the month. The two dates describe different expectations; the account’s cycle needs to be identified before declaring an error.
Do not purchase an additional coin package to test whether a periodic allocation is missing. That would create a separate paid event without resolving the original question.
Ask support about the identified cycle
Provide the plan reference, displayed renewal date, relevant receipt status and observed coin history. State whether the allocation is absent, delayed or present with a different amount. If you cannot access the ledger, mark that limitation instead of treating the balance as a complete history.
Avoid sending full card details or login codes. A useful response confirms the allocation cycle and explains the relevant credit entry. It need not involve changing the subscription, accepting a promotion or relying on an unverified claim of free coins.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.