A Zora deposit reference is more useful than a refreshed balance
When a deposit does not appear as expected, the useful starting point is a pair of records: the payment provider’s transaction and Zora’s cashier entry. Record the amount, currency, approximate time and reference for each. A screenshot of the total account balance cannot identify which operation is missing.
Distinguish an authorisation from a completed charge. A banking application may show funds reserved before the final outcome is known. Likewise, a cashier status can describe processing without confirming receipt. Use the wording shown by each system rather than translating every pending entry into “money lost”.
Do not repeat the same payment simply because the first screen did not refresh. First check whether a transaction reference was generated and whether the provider lists a completed, pending or reversed operation. A second successful payment can create a different problem: two deposits rather than a corrected display.
If you contact Zora, provide the reference and the two visible statuses, with sensitive payment details concealed. Ask which stage requires investigation. Once the matter is resolved, match the final cashier entry to the original operation; a later deposit of the same amount is not evidence that the earlier one settled.
Use the reference to choose the right next action
First determine whether an operation was created. If the cashier produced no identifiable record, the question concerns the stage at which submission stopped. If a record exists, the next question is its state. If the provider also has a record, compare the two without assuming their status words mean identical milestones.
This is a navigation decision: return to the original operation rather than start another payment. A browser tab that still shows an amount is not necessarily the active record. The identifying reference, date and currency let you recognise the actual attempt after a refresh or device change. Similar amounts on the same day should remain separate until their relationship is confirmed.
Use the operator’s published escalation point carefully
Zora’s deposit Help says deposits are usually credited within ten minutes and advises contacting support when Pending continues beyond ten minutes. That is the Help article’s guidance, not a completion guarantee tested by this review. It gives a useful point for seeking clarification without inventing a universal instant-payment promise.
The same Help lists connection, details, insufficient funds and payment-provider rejection among possible failure causes. These categories direct the question but do not diagnose your attempt. If a failed transaction was debited, the article describes reversal within one business day and then support with the receipt if it has not returned. Keep the published instruction separate from an actual confirmed reversal in your statement.
Make the support request about the missing connection
A concise request can identify the operator reference, the provider reference and the state that cannot be reconciled. Ask whether the payment has been received, whether a further step is needed or how the two records relate. There is no need to include a password, a one-time code or unrelated account history in that narrative.
After an answer, return to the original reference and verify the explained outcome. A new deposit with the same amount does not resolve the old one merely because the total balance increased. Closing the route means the specific operation has a known result. A separate missing-bonus question should then be checked through activation and campaign rules, rather than used as the only evidence that the deposit itself failed.