Address
مصر
Help center
From your first article to tracking earnings: choose a topic or search for your question.
Step by step
How point-funded extra units, memberships, reservations, usage, capacity, and refunds work.
These are extra units purchased from your existing points wallet to extend a feature already defined by your membership, such as email messages, article creation, direct messages, or private-blog capacity. They do not create a new membership or change its price.
No. The system uses the existing points wallet, membership features, and usage rules. Extra purchases have a separate unit ledger for settlement while remaining tied to the account and existing feature.
Currently supported features include writer email messages, public article creation, private-blog articles, direct publishing, private-blog direct publishing, direct banner campaigns, direct messages, and private-blog capacity. Not every numeric or percentage setting becomes a consumable unit automatically.
N or 0 disables the base allowance. A number defines the base units in the selected period. Y means the base allowance is unlimited. Buying extra units does not automatically unlock a disabled feature unless the administrator allows standalone purchase for that feature.
The system uses the membership periods already supported, including daily, monthly, yearly, and a 7-day week when configured by the administrator. It does not invent plan numbers or prices.
Pack cost is the number of points charged, and pack units are the number of uses added to the feature. An administrator defines the offer; the code does not assume commercial numbers.
It is the maximum number of packs allowed in one purchase confirmation. It is not the account’s total balance and does not prevent later purchases when the offer and points remain available.
Yes. The system consumes the membership base allowance first and then uses extra units. The feature page shows each source so you can see what was used and what remains.
The feature continues using extra units when the membership still allows the feature or the offer is standalone. Extra units are not reset at the end of the base allowance cycle.
It depends on the feature’s allow standalone purchase setting. When disabled, purchase is blocked and dependent units remain preserved and suspended. When enabled, the units can be used for that feature only and grant no other membership permissions.
Units are not deleted or automatically expired. Units that depend on an eligible membership are suspended while the feature is unavailable and return when eligibility returns. Standalone units can work according to their policy while other account restrictions still apply.
No. Renewal applies to the membership base allowance. Purchased extra units remain until consumed or administratively revoked under the rules, with their usage and reservations recorded.
Private-blog capacity is a limit on existing slots, not a recurring article count. Existing blogs occupy slots and deleting a blog frees one. Membership expiry does not delete blogs or automatically remove units.
No. Creating a new article consumes a creation unit. Editing an existing article does not consume another creation unit, while normal publishing, review, and permission rules still apply.
Points are deducted only when a valid purchase is confirmed after the offer and balance are rechecked inside a locked transaction. Opening the offer or viewing the confirmation does not debit points.
The entire purchase is rejected, with a message beside the purchase action and a visible in-page alert. No points are debited and no units are added. Refresh the balance or reduce the pack count before trying again.
It prevents unexpected debits. The review shows the feature, units, points charged, expected balance, and whether units depend on membership. The quote expires quickly and is revalidated at purchase time.
The system rejects the old confirmation with a changed-or-expired-quote message. It does not use the old price or debit points; refresh the page and create a new quote.
No. Each purchase has a unique confirmation key and an idempotency constraint inside a transaction. Repeating a successful request returns the same purchase instead of charging twice; changing its details with the same key is rejected as a conflict.
A purchase can be refunded only while its units are unused and unreserved, subject to the refund action’s permission. If units were used or reserved, or the purchase supports occupied capacity, a full refund is rejected to protect the ledger and capacity state.
A used unit is recorded in the usage field. A reserved unit cannot be consumed by another operation until it is accepted or rejected and released. Administrative deductions do not touch reserved or used units.
Yes, with separate permission and a required reason. Adding points uses the existing wallet and point log; adding units creates an audited grant tied to the feature. An adjustment does not start a purchase or campaign automatically.
Points or units can be removed only with the matching direction permission. The system rejects removing more points than available or units already used, reserved, or required by existing blogs. Every adjustment has a reason, operation key, and immutable audit record.
Yes. A unit purchase debits the points wallet and records the wallet transaction, point log, and unit ledger in one transaction. If one part fails, the other part is not committed.
The service locks the owner, wallet, lots, or reservations as needed and rechecks the current balance. This prevents overspending and double consumption, while the second operation receives a clear result or safe rejection.
Open Increase Feature Limits with Points and choose a feature. The page shows base allowance, extra available, used, reserved, suspended balance, points, renewal time, and purchase history.
No. Extra units are tied to the selected feature only. Buying message units does not unlock direct publishing, and buying blog capacity does not grant publishing or membership permissions.
New purchases and usage are blocked. Previous purchases and usage history are not deleted, and settlement remains reviewable according to the account state and security restrictions.
The log shows balance type, account, administrator, direction, amount, before and after balances, reason, operation key, and time. It is read-only for review and cannot be edited or deleted from the interface.
Contact support if points were debited without a purchase record, a reservation remains after an operation ended, a limit looks wrong after a membership change, or a refund was rejected and needs review. Send only the operation number; never send a password or wallet secret.
Still need a hand?
Include the page link and a short description of what happened so we can follow up.