Refund a purchase.

Review a refund of my RIPSTACK paid share purchase on BNB Smart Chain (chain ID 56) using my Binance Agentic Wallet.

EXISTING WALLET SESSION
Use my Binance Agentic Wallet session already connected to this agent. Run baw wallet status --json once under the official skill preflight; reuse its result if already checked in this workflow. If CONNECTED, continue with that wallet: do not run auth signin, sign out, request another QR/pairing code, or ask me to connect on the RIPSTACK website. Only follow the official Binance sign-in flow when status explicitly reports no active session. A network error or unavailable status is not evidence of disconnection: stop and report it instead of starting another login. Confirm the BSC address and registered Agent ID without changing accounts. Keep Binance credentials on my device. Website connection is not required for this agent workflow. This session does not replace transaction previews or required Binance confirmations.

PREFLIGHT
Use the official binance-agentic-wallet skill and its current preflight and external-sign references. Confirm my BSC wallet on chain 56. Check baw wallet settings --json for active Developer Mode before preparing or previewing the refund. If disabled, ask me to enable it in the Binance App and wait. Use my own agent session; keep wallet credentials private.

DEPLOYMENT
Read https://ripstack.fun/refund and https://ripstack.fun/api/stack/status once. Require state=ready and verify snapshot.sale against the published StackPublicSale address, chain and verified ABI. If unavailable, stop; do not poll for deployment. This refund calls the sale directly and does not require a new share quote, website login or /auth signature. Purchases being paused does not itself block an eligible refund.

SELECT ONE PURCHASE
Ask for my purchase transaction hash or a positive position ID. If I provide a hash, read its successful receipt and use the Purchased event emitted by the verified sale for my address. If several purchases match, let me select one position. If I provide an ID, read that position directly. Never scan every sale position or refund all positions automatically.

CHECK ELIGIBILITY
Read positions(id), refundDeadline(id) and poolOpenedAt() on the sale at the same recent canonical block. Require positions(id).buyer to match my wallet, cancelled=false, poolOpenedAt()=0 and block.timestamp strictly less than refundDeadline(id). The deadline is 30 days from that individual purchase, not from my first purchase or launch. Verify paymentToken(), stackToken() and their decimals. If already cancelled, expired or the pool is open, explain the state and stop.

REVIEW
The full positions(id).paid amount is returned in USDT. The entire principal + bonus allocation is permanently burned, including the released tokens already in my wallet and tokens still held by the sale. Show those exact amounts, the sale and token addresses, the UTC deadline and gas. Network gas is not refunded. Origin redemption is outside this paid-purchase refund route.

EXECUTE
Use the official baw contract-call preview for refund(uint256 id) on that sale with zero native value and --json. No token approval, token transfer or separate burn is required. Show the successful simulation and ask for my explicit confirmation. Recheck eligibility before executing the approved requestId once. If the pool opens or the deadline passes, stop. A failed simulation must not be executed. If the preview expires, preview again and obtain a new confirmation rather than reusing it.

VERIFY
Confirm the canonical successful receipt and Refunded event from the verified sale. Its id and buyer must match; returned must equal the position's paid amount and tokensBurned must equal principal + bonus. Confirm positions(id).cancelled and the actual USDT transfer to my wallet. If confirmation times out, reconcile the original transaction hash before retrying. Finish after this one refund.

REQUEST DISCIPLINE
Run one workflow for this wallet, with at most one non-stream request in flight. Use a 15-second timeout for ordinary API reads; a live event stream and the official blocking Binance pairing flow are separate. Reuse valid authentication and configuration. Do not refresh quotes, balances, registry data or approvals in a loop. Respect Retry-After; on 429 without that header, wait at least 60 seconds. The specific round and receipt retry schedules override this general read schedule. For other transient read failures, wait 2, 4 and 8 seconds with small random jitter, then pause and report the problem after three retries. Never fan requests out across providers. On 400, 403, 404 or 410, stop and explain the response. On 409, reconcile state once and follow the specific state instead of repeating the rejected action. On 401, allow one reauthentication within an explicitly authorized session scope; otherwise get my confirmation first. If it fails again, stop. Never automatically repeat a signature or blockchain submission. An unexpected HTML response or missing deployment means unavailable, not permission to try alternative endpoints.

TRANSACTION TRACKING
Keep a private local record of the wallet, chain, contract, action, selected quantity or edition, and the original transaction hash or wallet order ID. Resume that record after interruption. Execute each approved preview only once. If execution returns an order ID or pending confirmation, use the official skill's documented status flow; do not execute again to obtain a hash. Check a pending transaction after 6, 12, 24, then 30 seconds, with only one check in flight. After five minutes without a final result, pause and report it as pending with its identifier. A timeout or missing receipt is not a failed transaction. Never replace or resubmit it without reconciling the original request and obtaining my confirmation. Verify the canonical receipt and contract events before reporting success. Stop after the requested operation is complete; do not start purchases, refunds, renewals or vested claims that I did not request.