Balance, top-up availability and transaction history
Check your wallet, purchase outcome and details needed for payment support.
Where to find it
- Dashboard → Balance
- Transaction history
Sign in to your account first
In this guide
Wallet funds and purchased services are separate records: the wallet holds a balance, while a plan or pack has its own duration and remaining credits. Top-up methods depend on currently available payment gateways; a visible form is not proof of a successful credit. This guide explains how to distinguish these states before contacting support.
Before investigating a payment
- Sign in to the account that confirmed the purchase. Have the product name and operation identifier ready if one appeared. For a listing purchase, its identifier is also useful.
- Check the current wallet data and gateway-availability message. An entered amount is not the available balance, and closing a form does not mean that payment succeeded.
Check payment availability first
If the page says the gateway is not connected, stop and use its support link. A displayed form or list of options does not establish that a payment method works. Do not send funds to an address, payment details or QR code supplied by another user claiming to represent FayVay. This page currently does not create a live external-provider invoice.
Check balance and history
Sign in to the correct account
Open Balance in your dashboard. Check the available amount and wallet currency. A balance from another account or an old screenshot is not confirmation of payment. If data fails to load, use Retry and wait for the server response.
Find Transaction history
Compare the date, identifier, operation type and reason, amount change and balance after the entry. A positive change increases the balance; a negative change decreases it. The screen shows recent available records; a missing older row does not prove that an operation never occurred. Give support the details you know to help find it.
Match the entry to its product
For Account Premium, check Subscription history in Premium. For plans and add-ons, open Promotion → My promotions and History. Wallet balance, remaining pack credits and product expiry measure different things. Owning a pack does not mean every credit has already been applied to a listing.
How to interpret the outcome
| Confirmed operation | The server has recorded the entry and associated purchase or adjustment. Check both the ledger and product state. A browser notification without refreshed data does not replace that check. |
|---|---|
| Awaiting publication | Promotion selected for a new listing can await moderation without an advance debit. This is a listing and activation state, not confirmation of a top-up. Check the result separately after publication. |
| Error or uncertain outcome | Insufficient funds, currency mismatch or changed terms block the relevant confirmation. A lost connection after submission can leave the browser unsure of the result. Refresh history before deciding whether to retry. |
Currency and confirming terms
Wallet currency is fixed for operations. The site’s display currency does not change the stored balance or perform an exchange. Before purchasing, check price, currency, target, duration and availability. If the server reports changed terms, refresh and review the offer again. Repeated clicks do not confirm an outdated price.
Disputed operations and refunds
How do I request a debit review?
Open support from Balance. Include the entry identifier and date, amount, currency, product name, your listing where relevant and a description of the issue. Attach the error text or a suitable screenshot. The decision depends on the specific operation and applicable terms; this guide does not promise approval, an amount or a refund deadline.
Is a returned Story credit a cash refund?
No. If a reserved Story is rejected or deleted before first display, its credit returns to the purchased pack. That restores an opportunity to use the pack. It does not mean the pack purchase in wallet history has automatically been reversed.
Where can a user see external payment statuses?
The current user page provides the wallet and ledger, while prepared forms do not start an external payment. There is no additional user tab documenting bank-transfer stages. For an uncertain result, use actual ledger entries and support instead of assuming a crediting deadline.
What should I keep out of a support request?
Do not share passwords, PINs, login codes, recovery codes, full card details or wallet secrets. An internal operation can be investigated using its identifier and context. Remove unrelated messages and personal information from screenshots before sending them.
Example: the connection drops after confirmation
Suppose you confirm a listing plan but receive a network error. First refresh the ledger and promotion card. If the debit and active plan are already present, avoid purchasing again. If the state remains unclear, give support the attempt details and request an investigation; the browser error establishes neither success nor absence of a debit.
