Blockchain transfers are designed to be final. This policy explains when the operator can reverse a ledger credit, decline a request, or leave an on-chain payment where it landed.
Unconfirmed or invalid deposits
If a hash is missing, duplicated, sent to the wrong address, or sent on the wrong network, there may be nothing the ledger can credit and nothing the operator can claw back on-chain. Submit Payment verification with the hash so the desk can say whether a credit is possible.
Confirmed deposits
Once a deposit is confirmed and the ledger is credited, the ordinary path is allocation or withdrawal — not a “refund button.” Administrators can post an auditable reversal when policy allows (duplicate credit, proven operational error). That reversal is a ledger entry, not a promise that the original chain payment will bounce.
Open allocations
Active investments follow the snapshotted package. Early cancellation, if the operator offers it at all, is an explicit administrative action with a reason. Daily profit already posted is part of the book unless a documented correction is written.
Withdrawals
A reserved withdrawal that is declined returns the reserve to available balance. A completed withdrawal that has a settlement hash is an outbound chain payment. Recovering a payment sent to an address you typed incorrectly is usually impossible.
Fees
Network fees paid to validators are not returned by this platform. Operator withdrawal fees, when configured, are shown before you confirm and follow the published package and settings.