Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.
Read the safe reason first
Open Settings → Payments and confirm whether the failed attempt is the first destination or a replacement. A rejected replacement does not silently remove the current verified account.
Submit once and wait
Choose Correct and resubmit only after a real correction. Repeated identical submissions do not speed up review and can make investigation harder.
Contact support without identity data
If the safe reason remains unclear, include the business, time and non-secret attempt reference. Do not attach unmasked bank documents or identity numbers.
If Correct a Rejected Payout Verification is not working
If a replacement fails, confirm the current verified destination remains active and do not submit identical data repeatedly.
Confirm the result
- Every amount is read in its labelled currency.
- The provider, order, wallet or withdrawal status supports the action taken.
- No pending action was duplicated or silently converted.
- Sensitive payout and identity data stayed inside protected fields.
When to ask Selstack for help
Distinguish customer payment from seller payout
A customer payment and a payout to the seller are separate stages. A successful order can be recorded before the associated funds are available to withdraw. Selstack’s wallet and payment records help explain that relationship, including pending funds, available balance and recorded withdrawal activity. Start with the labelled state of the relevant amount. Do not assume that a bank credit, an online payment confirmation and a wallet balance all describe the same event or become available at the same time.
Use the requirements for the verified business context
Payout setup depends on the business’s supported country, payment arrangements and verification requirements. Follow the fields and instructions shown for that account rather than copying another seller’s setup. The name, business details and payout destination should be accurate and legitimately associated with the person or organisation operating the account. Selstack’s global audience does not mean every seller uses the same local banking process. A useful guide explains the general workflow while the actual form supplies the requirements for the specific business.
Prepare information before submitting
Review the account or business details requested by the current setup process and check them for consistency. Correct ordinary spelling or ownership mistakes before submission. Use the designated secure fields for required verification information; do not place identity documents or complete bank details into a public profile, product description or customer lead form. If you are uncertain about a requirement, ask support about the named field and account context without sending sensitive documents through an unrelated channel.
Read verification states as different outcomes
A submitted request is not the same as an approved payout arrangement. While a request is pending, read the visible status and any instructions before submitting another version. If a request is rejected or needs changes, use the stated reason to identify what must be corrected. Repeatedly entering the same information is unlikely to resolve a mismatch. Do not describe verification as guaranteed or instant. The account should be treated according to the current recorded state, not the seller’s expectation that a previous form submission must already have completed.
Understand pending and available wallet amounts
Pending or ledger funds are not automatically available to spend or withdraw. Review the related payment, currency and release information shown in the wallet or order records. Available funds represent a different stage from a successful customer payment still subject to the platform’s release process. If an amount appears unexpected, trace it to its source rather than moving between pages looking for the largest number. A useful reconciliation explains which payments, fees, refunds or adjustments contribute to the balance currently shown.
Request a withdrawal deliberately
Before requesting a withdrawal, check the available balance, selected destination and current verification status. Review the amount and currency carefully, then submit through the supported wallet workflow. Keep the resulting reference and read the withdrawal’s own status. A request being recorded does not prove that the money has reached the destination account. Avoid creating several requests to compensate for a delayed status update. If the displayed state or outcome needs investigation, use the existing reference so the case can be traced accurately.
Handle payout-detail changes carefully
A new payout destination affects how future funds may be received and can involve a separate verification process. Review the current account state and the available replacement route before changing details. Confirm that you are working in the intended business and that the destination is authorised. Do not treat changing the public profile’s country or address as proof that payout arrangements have moved. Business relocation and residence changes have their own supported workflow, and historical orders should remain attached to the records under which they were originally processed.
Escalate a specific discrepancy
When asking for help, identify whether the problem concerns a customer payment, a pending wallet release, verification or a withdrawal. Include the safe reference, amount, currency and approximate time where relevant. Explain what the account shows and what you expected to happen instead. Do not send passwords, one-time codes or full payment credentials. A concise description of the stage that is blocked is more useful than several screenshots with unrelated balances or an assertion that every part of the payment process has failed.
Keep financial records usable over time
Reconcile wallet activity with the business’s order records and its own bookkeeping process. Preserve the original transaction currency and the recorded payout or remittance context where they differ. Keep access limited to authorised people and review account changes as part of the business’s normal operating routine. Selstack provides records and supported payout workflows; it does not remove the need to verify account ownership, understand the state of funds or maintain an accurate record of money the business has actually received.
Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.
