FishBSE Help Center

Questions? Start here.

A detailed guide to buying, selling, auctions, account security, MFA, notifications, shipping, delivery, Stripe checkout, refunds, warning rules, disputes, listings, safety, and what happens when a transaction goes wrong on FishBSE.

Popular help topics
  • Step-by-step buying and checkout
  • Selling, Stripe Connect, orders, and payouts
  • Auctions, bidding, winner payment, and anti-sniping
  • Refunds, cancellations, disputes, and DOA policies
  • Shipping, tracking, delivery, and transaction records
  • Buyer/seller warnings, responsibility, and account restrictions
  • MFA, recovery codes, secure sign-in, and protected account access
  • In-app notifications, browser alerts, unread activity, and account updates
No matching questions found.
Try a shorter search or choose a different topic.

FishBSE DOA coverage

For livestock vendors and buyers: application, coverage and claims.

Vendor DOA is funded by the vendor. Registered vendors selling fish, coral, invertebrates or live plants can choose no vendor guarantee or a standard live-arrival policy with a 2-, 6- or 24-hour reporting window after delivery or local handoff. Read the selected policy on the listing and at checkout; its terms stay with the paid order. An older order may have no standard policy recorded: check the original listing and messages for any separate promise. FishBSE coverage is a separate purchase.

FishBSE DOA coverage is a separate optional policy purchased at checkout for an eligible approved shipping listing. Dashboard and Orders identify a purchased policy with Provider: FishBSE, its policy number, fee, benefit limit and claim window. Not purchased means no purchased FishBSE policy is recorded for that order. Status unavailable means the records could not be verified; contact support instead of assuming there is no coverage.

Auctions and pickup purchases are not eligible for FishBSE DOA coverage. Ordinary order disputes remain a separate process.

FishBSE offers optional coverage for eligible shipped fish, coral and marine livestock. The seller must complete the listing review and enable the offer. The buyer must choose coverage and accept the displayed terms at checkout. A listing application, approved report or seller promise alone does not purchase coverage.

Check your order for the policy you actually purchased: its fee, maximum benefit, filing window and evidence requirements. If coverage is unavailable or new coverage sales are paused, ordinary marketplace terms still apply. Existing purchased policies keep their recorded terms.

  1. Create a fixed-price, single-unit livestock listing with Shipping and an eligible online payment setup.
  2. Open Dashboard, find the listing and select Apply for FishBSE DOA policy.
  3. Submit the livestock type, observation date, an accurate health report and 2–6 distinct photographs of the actual livestock.
  4. FishBSE reviews the health report and verifies the current listing’s livestock classification.
  5. After approval, return to the application, accept the current terms and enable coverage. Eligible buyers can then choose it at checkout.

Your ordinary listing can remain published during review. Approval does not guarantee a sale or a future claim payment.

Coverage is for eligible shipped fish, coral and marine livestock sold as a single unit at a fixed item price within the displayed limit. The item-price eligibility limit and aggregate benefit each cannot exceed $100; the current settings may be lower. The benefit limit includes eligible shipping and is not an extra $100 on top of the item price.

Pickup, auctions, bulk purchases, equipment, supplies, variable-price and call-for-price listings are excluded. Review the current limits on the application and checkout pages.

On Create Listing, Video Listing or Edit Listing, choose a livestock category and then a standard vendor DOA policy or No vendor DOA guarantee. Read the full terms before publishing. Equipment and dry goods cannot receive a livestock DOA policy. The 2-, 6- and 24-hour options start at recorded delivery or agreed local handoff. Photos should show arrival condition and, for shipping, the packaging and label. File the report on time even if more evidence will follow. Edits apply to future checkouts; existing paid orders retain their purchased terms. FishBSE approval and paid coverage are separate.

Yes. For a recorded FishBSE order, open Orders, select the order discussion or dispute, explain the issue and add evidence. No vendor or FishBSE DOA policy is required to raise an issue. Lack of coverage does not establish fault or guarantee a refund. For a local sale without a FishBSE order record, contact support with the listing, payment and handoff evidence; do not create a false online order.

If the order has no purchased FishBSE DOA policy, the vendor can decline a vendor claim during negotiation by selecting a reason and explaining the evidence in the order chat or dispute. Reasons include no vendor guarantee, a late report, insufficient photos, a loss after arrival, an item mismatch or disputed delivery facts. A denial records the vendor’s position and does not close the case. The buyer can respond and either party can escalate immediately. A vendor cannot deny a purchased FishBSE benefit; FishBSE reviews those claims under the purchased terms.

At any time from the order chat or dispute, choose Ask Disputes Center to review and explain why. You do not need the other party’s permission or have to wait 24 hours. Ordinary cases also escalate automatically after 24 hours without a completed agreement. The review preserves the purchased order terms, payment and refund records, delivery information, evidence references and the order-linked conversation and photos. Administrators record the next stage, judgment, remedy or closure reason. Cancellation keeps the history and does not cancel an outstanding payment obligation. Either party can request further review of an unresolved problem.

Open chat from the order so its order number appears, then choose Add photo. JPEG, PNG and WebP are supported up to 6 MB and 16 megapixels, one photo per message, with 20 photos per account per day and 100 per order. Photos are converted to JPEG, resized when necessary, stripped of embedded metadata and stored privately. Order photos are visible to both participants and authorized Disputes Center reviewers. Unrelated private messages are not included in an order case. Sensitive receipts can use the order evidence page and its support-only option. Sending a photo alone does not file a purchased FishBSE DOA claim or extend a deadline.

An approved health report documents the livestock before shipment and gives covered buyers a clearer record of what they purchased. Eligible buyers get the choice of coverage under written, order-specific terms.

The buyer pays the optional fee at checkout. FishBSE retains that fee and funds approved covered claims within the purchased limit; the covered benefit does not reduce the vendor’s sale proceeds. This does not remove the vendor’s fulfillment duties or protect them from ordinary refunds, disputes or other adjustments.

Describe the actual livestock, appearance, activity, feeding or polyp extension where relevant, visible damage, recent treatment and known concerns. Give the observation and photograph date in UTC. Include an overall view and clear close-ups.

Upload 2–6 distinct JPEG, PNG or WebP photos: up to 5 MB each, 20 MB total and 12 megapixels per photo. Video is not supported for the report. Reports are available to the vendor, authorized reviewers and buyers whose purchased policy references them. Keep personal information out of the images and report.

At first verified carrier acceptance, not delivery. The purchased number of elapsed hours runs from that event and may expire before a delayed delivery.

A prepared label, uploaded receipt or seller-reported handoff does not activate the policy. Check the exact deadline on your order. File the claim within the window even if supporting uploads are still being prepared. A timely claim remains under review after the window expires; filing does not guarantee approval.

Open the affected order in Orders and use its covered DOA claim option before the displayed deadline. Describe the loss, arrival and unboxing, affected livestock, and claimed incident time. Provide clear photographs and relevant receipts for review; video is unsupported. The current flow covers one purchased livestock item.

File promptly rather than waiting for uploads to finish. The order receipt is retained. FishBSE reviews eligibility, evidence, prior refunds and the remaining benefit. Any approved payment is limited to the eligible, unreimbursed loss and the purchased aggregate cap.

Approved covered DOA benefits are funded by FishBSE. The policy fee is retained on a DOA refund. Prior reimbursements count when determining the remaining eligible loss; there is no duplicate reimbursement for the same loss. Partial-loss shipping, tax and replacement remedies require manual review.

Ordinary order refunds and the marketplace dispute process are separate. Use the appropriate issue option on the order; opening an ordinary dispute does not file a covered DOA claim or extend its deadline. Refund submission is not the same as money arriving at the buyer’s bank. Review the recorded outcome and payment status in Orders.

Material listing changes can invalidate the matching health report or classification. A replacement report pauses new coverage offers until it is approved and you enable coverage again with renewed consent. Read the administrator’s feedback on the application page.

Earlier purchases keep their policy snapshot and referenced health report. Disabling a future offer does not cancel coverage already purchased.

Pickup, check-in & QR verification

From private pickup instructions to arrival and a confirmed handoff.

  1. Complete payment. The buyer or auction winner pays through Stripe. The confirmed payment time starts the pickup deadlines.
  2. The vendor schedules pickup within 72 hours. For both ordinary paid pickup and pickup auctions, the vendor opens the paid order and confirms the private location, instructions, calendar date, start time, end time and time zone. Auction details saved before payment are a draft; the vendor still confirms the paid order's schedule.
  3. Collect within seven days of payment. The scheduled pickup window must end within that period. The buyer receives a notification and can review the private schedule in Orders. Message the vendor if the offered time does not work, and check the current arrangement before travelling.
  4. Check in on arrival. The buyer taps I’m at the pickup location to notify the vendor and record the arrival time.
  5. Confirm the handoff. After receiving the item, the buyer confirms receipt and shows the single-use QR code. The vendor opens Dashboard → QR Verify, scans it, reviews the item and confirms handing it over.
  6. Keep the order record. The completed pickup page shows the item, order number, pickup location, and collection date and time.

Pickup auctions and Pay now, pick up later use online payment. Ordinary Local pickup listings can offer direct payment instead. Review the listing’s fulfillment and payment terms before committing.

After payment, sign in as the vendor and open the paid pickup order in Orders. Within 72 hours of confirmed payment, save the exact address or meeting point, pickup instructions, calendar date, start and end times, and the location's time zone. The entire pickup window must fall within seven days of payment. Saving the schedule notifies the buyer.

For pickup auctions, pre-payment private details can help prepare the arrangement, but the vendor must still confirm the schedule on the paid order. The meeting point must remain within the public pickup area advertised to bidders.

Changing the location, instructions or schedule invalidates an unused pickup code and requires a fresh check-in for the new arrangement. Changes do not restart the original deadlines. Tell the buyer about changes before they travel.

The vendor has 72 hours from confirmed payment to provide the private pickup location and a dated time window. This applies to Pay now, pick up later purchases and paid pickup auctions. The pickup window must end no later than seven days after that same payment; it is not seven additional days after scheduling.

Use the order's calendar, start and end times, and time zone. Both people should review that schedule before travelling. Reopening the order, retrying a payment notification or editing the schedule does not restart either deadline.

Older orders may have no recorded scheduling deadline or structured time window. The order identifies missing historical information rather than inventing a deadline; contact the other party or support to arrange those orders.

FishBSE notifies the buyer and vendor when a pickup deadline is missed. Open the pickup order to contact the other person or report an order issue and request a refund review. Include the agreed schedule, messages and any arrival or handoff evidence.

A missed deadline does not automatically refund the payment, complete pickup or decide who was at fault. The existing dispute process records a proposed refund or replacement, participant agreement or an administrator's decision, and the confirmed payment outcome. Opening a case does not automatically freeze seller payouts. Either party can request Disputes Center review; ordinary cases without a completed agreement escalate after 24 hours.

Pickup auction winners pay through Stripe. FishBSE attempts the authorized winner payment. If more action is needed, follow the payment instructions on the auction page within its displayed payment window. Pickup auctions do not add a shipping charge.

Check the auction and Orders for the payment result before trying again. If a payment is processing or the order is being finalized, follow the displayed guidance and contact support if it remains unresolved. Use the order’s recorded payment status when arranging collection; a payment screenshot alone is not the order record.

Ordinary Local pickup listings may offer payment arranged directly with the vendor. That separate listing option does not change an auction winner’s Stripe payment obligation.

The exact address and instructions are shared through the authenticated pickup order with its buyer and vendor after payment. Notifications link to that private page rather than displaying the address in the notification message. The public auction continues to show its advertised pickup area.

Keep the exact meeting address in the private pickup fields. Anything you include in a public description, photo, or comment may be visible to people browsing the listing.

Sign in as the buyer, open the paid pickup order from Orders, and tap I’m at the pickup location when you arrive. The vendor receives a FishBSE notification, and both participants can see the check-in time on the pickup page. The page checks for arrival updates automatically.

Check-in records the buyer’s arrival report; it does not use GPS or confirm receipt of the item. Repeated taps for the same pickup instructions do not send duplicate arrival notices. If the vendor changes the instructions, refresh the page, review the current location and check in again when you are there.

If an alert has not appeared, open the order or Notifications directly and message the other participant. Allow time for notification delivery and confirm the agreed meeting time before travelling.

The QR code becomes available at the handoff. Once you are with the vendor and have received the item, open the pickup order, select the receipt confirmation checkbox and choose Confirm receipt & get pickup QR code.

Show the QR code to the vendor. An 8-digit code is displayed as a backup. Both represent the same single-use confirmation and expire after 15 minutes.

Keep the page open. The code is shown once. Share it only with the vendor at the actual handoff, after inspecting and receiving the item. Payment and arrival check-in do not generate a receipt confirmation.

  1. Sign in as the order’s vendor and open Dashboard → QR Verify.
  2. Choose Scan buyer’s QR code, allow camera access, and point the camera at the code on the buyer’s pickup page.
  3. FishBSE opens the matching order. Review its item, order number and pickup details.
  4. Confirm that you are with the buyer and have handed over the item, then choose Confirm handoff & complete pickup.

Scanning opens the order for review. Your final confirmation completes collection. Only that order’s vendor can complete this step, and the buyer’s code must still be valid.

Check that your browser has permission to use the camera, improve the lighting, and keep the full QR code in view. The camera starts when you select the scan button. You can stop it using Stop camera.

QR Verify also offers Scan a QR image for a PNG, JPEG or WebP image smaller than 10 MB. Or expand Enter a pickup code manually and enter the buyer’s order number and 8-digit code. If you already have the matching pickup order open, enter the 8-digit code there.

A different-order warning means you should open the matching order and verify its item. A successful scan or manual entry still requires the vendor’s final handoff confirmation.

Each QR and its 8-digit backup can be used once and expire after 15 minutes. If you close the page or lose the code, reopen the pickup order and follow its instructions for a replacement. While a code is still active, the page can require you to wait five minutes from issuance before replacing it.

Five incorrect entries lock the current code. Stop guessing and ask the buyer to review their pickup page. An expired, replaced, already used or locked code cannot complete a new handoff. Updating pickup instructions also expires an unused code.

Only confirm receipt after receiving the item. If you already handed over the item but cannot finish confirmation, keep the order number and relevant messages and contact support.

The buyer confirms receiving the item to generate the code. The vendor verifies that code and confirms handing over the matching item. Those two actions connect both participants to the same handoff.

Arrival check-in records that the buyer says they are there. The final handoff confirmation records collection. An open order issue remains available after confirmation; seller bank payout timing follows the applicable Stripe payout process.

The order must have eligible payment status and a vendor-confirmed pickup location and calendar time window. If the schedule is missing, message the vendor and check the deadline shown on the order. Report an order issue if the vendor misses that deadline. If payment is incomplete, return to the auction or order and follow its payment instructions.

A newly paid order may briefly show that its verified payment time is still syncing. Scheduling becomes available when that time is confirmed. The 72-hour and seven-day deadlines use the original successful payment time; syncing does not restart them. Refresh the order, and contact support if the message persists.

A pending or completed refund, a payment review, an already collected order, or a role mismatch can prevent pickup actions. If instructions change while your page is open, refresh and review the new details before continuing.

Use the same account associated with the order. For an unresolved payment or pickup message, contact support with the order number and the message shown.

Open the matching pickup order from Orders. After both handoff confirmations, the receipt shows the collected item, order number, pickup location and instructions, and the collection date and time.

Times are stored in UTC. Where your browser supports local formatting, the page displays them in your device’s time zone. Check the time zone when comparing records. Arrival check-in is recorded separately from collection.

Review the calendar date, pickup window and time zone saved by the vendor before travelling. Payment starts the 72-hour scheduling and seven-day pickup deadlines; it does not itself confirm a meeting time. Follow the vendor’s instructions about parking, access and suitable transport supplies for the item.

If someone is late or the address is unclear, contact the other participant. Keep the messages showing your arrangements. Ask the vendor to update the private order schedule if the meeting details change, then refresh your pickup page. Any new window must still fit inside the original seven-day period. If that is no longer possible, use the order issue or support option.

Inspect the item at handoff and confirm receipt only after you have received it. For missing, incorrect or damaged items, open the order’s Report or review an order issue link or contact support. Include the order number, relevant messages and photos. A check-in or missed meetup does not automatically issue a refund.

Review any vendor guarantee recorded with your purchase. Pickup purchases and auctions are not eligible for FishBSE DOA coverage; read about vendor guarantees and FishBSE coverage.

Boosting your listings

Your daily boost, bonus boosts and account cooldown.

Open Dashboard, which starts on your Active listings. Choose an eligible listing and select Boost to front. A successful boost moves it to the front of the marketplace ordering used for boosted listings. Boosting does not guarantee views or a sale, change the listing price or approve DOA coverage.

The normal free boost is account-wide. After using it, your account has a 24-hour cooldown before the next normal free boost can be used on any eligible listing. The dashboard shows the remaining time.

Administrator-assigned bonus boosts are separate and can be used during that cooldown when available. The button shows which kind is available. Archived and inactive listings cannot be boosted.

Online payment eligibility

Understand pricing messages before changing your listing.

FishBSE checks the proposed transaction against its current sale-fee and processing-cost policy, including the item price, buyer-paid shipping, estimated processing costs and seller proceeds. Some combinations do not qualify for online checkout. Missing payment configuration, seller account readiness or fee acceptance can also require attention.

Contact support before changing your price solely to clear the message. A configuration or account issue may need review rather than a price change. Read the sale breakdown and accept the displayed terms when eligible. Where appropriate, ordinary Local pickup with a non-Stripe payment method is an alternative. Shipping and Pay now, pick up later require Stripe.

Ask FishBSE to review payment eligibility

Buying on FishBSE

From finding a listing to payment, pickup, shipping, tracking, and completion.

FishBSE supports different transaction types, so the exact process depends on what the seller offers.
1
Review the listing carefully. Check the photos/video, description, price, location, fulfillment method, shipping fee, seller notes, and any live-arrival or return terms stated by the seller.
2
Ask questions before committing. Use FishBSE messaging to confirm condition, livestock details, pickup timing, shipping timing, or anything that is unclear.
3
Choose the transaction path offered by the listing. Local-only transactions may be arranged directly with the seller. Supported online purchases use FishBSE's Stripe-powered checkout flow.
4
Keep track of the order. For supported marketplace orders, FishBSE records the transaction and can show order, shipping, tracking, and status information associated with the purchase.
5
Report a problem quickly. If the item, shipment, user, or transaction raises a concern, preserve your photos, messages, tracking information, and receipts and use the available reporting/contact tools.
Important: A FishBSE listing is still a transaction between marketplace participants. Review the seller's terms and the actual listing before paying.

Local/direct transaction: You and the seller arrange the meetup and payment directly. Depending on what both parties agree to, that may involve cash, Zelle, Venmo, PayPal, trade, or another agreed method.
Supported FishBSE online transaction: Checkout is completed through Stripe, and FishBSE can associate the payment with an order record and supported shipping/transaction workflow.
Know the difference: FishBSE cannot reverse cash, Zelle, Venmo, PayPal, cryptocurrency, or other payments made outside FishBSE's supported Stripe checkout. Refunds or disputes for those payments depend on the payment service used and the agreement between buyer and seller.

For supported FishBSE marketplace purchases, the platform is designed to maintain a transaction/order record instead of relying only on private chat. Depending on the order and fulfillment stage, that record may include the item, amount paid, shipping fee, transaction status, shipment/tracking information, and related marketplace updates.
Keep your FishBSE messages, order page, shipment tracking, and photos until the transaction is fully complete. Those records can be useful if you later need to explain a problem.

Act quickly and document the condition.
  1. Take clear photos and, when useful, video of the package, shipping label, packaging, item, livestock, or damage.
  2. Save tracking information and delivery scans.
  3. Contact the seller through FishBSE and explain exactly what happened.
  4. If the seller has a stated DOA, return, or refund policy, follow its evidence and time requirements.
  5. If the issue cannot be resolved, use FishBSE's reporting/contact tools and preserve all transaction evidence.
For card-payment disputes, the cardholder's bank/card network ultimately decides the dispute outcome. FishBSE and Stripe do not guarantee that a dispute will be decided in either party's favor.

Shipping and Pay now, pick up later use supported Stripe checkout when the seller is eligible. Shipping checkout currently accepts US shipping addresses. Ordinary Local pickup uses the non-Stripe payment methods offered in the listing; arrange payment and handoff with the seller. Pickup auctions always use Stripe winner payment, followed by private pickup instructions and the check-in and QR handoff flow.

For a Stripe purchase, review the item, fulfillment method, shipping amount, address and total before continuing. Do not send card details or authentication codes to the seller in chat. Outside payments do not use FishBSE’s Stripe refund workflow.

No. Open Orders and check the payment status first. Closing a browser tab, returning from Stripe, or seeing an error does not by itself prove that payment succeeded or failed. A payment can still be synchronizing.

If you previously reached Stripe, check your receipt and order before retrying. Contact support with the order or listing number and approximate payment time if they disagree. Sellers should fulfill only after confirmed payment, not from a buyer’s screenshot alone.

Selling on FishBSE

Listings, Stripe Connect, fulfillment, records, tracking, and seller responsibilities.

1
Create an accurate listing. Add clear photos, optional supported video, description, price, location, fulfillment options, shipping fee/timeframe when applicable, and any seller-specific return or DOA terms.
2
Complete payment onboarding when required. Sellers using supported online checkout or auction settlement may need an eligible Stripe Connect account so payments and payouts can be routed correctly.
3
Respond to buyer questions. Clear communication before payment reduces misunderstandings about size, condition, livestock health, equipment condition, pickup, and shipping.
4
Fulfill the order as promised. For shipped orders, package appropriately, ship within the timeframe represented to the buyer, and add/share tracking where supported.
5
Keep documentation. Photos before shipment, packing photos, tracking, receipts, messages, and delivery information can be important if a refund request or payment dispute occurs.

Stripe Connect provides the payment-account infrastructure used for supported seller payments and payouts. Stripe may require identity, business, tax, or bank information depending on the seller and account requirements. FishBSE uses the connected-account status to determine whether payment-enabled seller features can be used.
FishBSE does not need buyers to send card information directly to sellers. Stripe handles the payment-processing side of supported card transactions.

Payment, funds arriving in a connected Stripe balance, and a payout reaching a bank are different events. FishBSE routes the seller’s proceeds through Stripe when payment is captured; delivery confirmation is not an escrow release.

Your Stripe account’s payout schedule and funds availability determine when a bank payout can occur. Verification, bank processing, weekends and holidays can affect arrival. FishBSE does not promise a 24-hour bank payout. Check your connected Stripe account for the actual payout date.

Keep enough information to show what was shipped, when it was shipped, and where it was sent. Useful evidence may include packing photos, carrier receipt, label, tracking number, acceptance scan, delivery scan, and the FishBSE conversation with the buyer. Where FishBSE provides private shipping-document sharing, use it instead of posting sensitive address information publicly.

Sellers are responsible for accurate descriptions and truthful photos, complying with applicable rules, clear sale and shipping terms, appropriate packaging, timely fulfillment, tracking where applicable, and responding to transaction issues. For a paid auction shipping order, the current policy gives the seller 72 hours to mark the order shipped. Follow the deadline shown on the order. State any seller DOA or return policy clearly before the buyer pays.

The current standard listing policy is 5.99% of the item price and buyer-paid shipping combined up to $100, then 9.99% on only the portion above $100. There is no upfront publishing charge under this sale-fee policy. Optional paid features have their own terms.

For a $150 fee base, the calculation is 5.99% of $100 plus 9.99% of $50, rounded in cents. It is not 9.99% of the entire $150. Review the policy displayed on your listing or auction: an existing accepted policy may differ, and updated terms may require acceptance before checkout.

Example under the 5.99% policy, with $25 actual postage
Buyer pays once$35.00
FishBSE sale fee−$2.10
Seller receives before postage$32.90
Postage purchased by seller−$25.00
Estimated proceeds after postage$7.90

This is not profit: the item’s cost, packaging, taxes, refunds and other adjustments are not included. The example explains proceeds; it does not guarantee that this price passes the current online payment eligibility rules.

The estimate updates when you change the item price, shipping charge or your expected postage cost. For unit listings it describes one item purchase, not all available stock; for bulk listings it describes the whole lot.

The editable postage estimate is a planning tool. It does not change the buyer’s charge, buy a label, deduct postage automatically, or guarantee your final carrier price. Enter your expected label cost even when you offer free shipping.

Your proceeds and FishBSE’s payment costs are different calculations. A positive seller estimate does not by itself establish online payment eligibility. FishBSE currently checks payment-account readiness, accepted fee terms and its configured payment-cost rules at publishing and again at checkout.

A pricing-rule message is not proof that you owe an extra Stripe fee. Contact support to review the rule before changing your price. You may choose ordinary local pickup with an offered non-Stripe payment method instead. Moving the same amount between item price and shipping does not change the fee when both are included in the fee base.

No. Card processing relates to a buyer’s payment. A monthly active-account charge, when applicable, relates to a seller account for a month. A payout charge relates to money sent to a bank or debit card. One bank payout can include proceeds from several sales.

As of September 21, 2026, Stripe’s published US “you handle pricing” Connect plan lists $2 per monthly active account and 0.25% + $0.25 per payout. Different plans or negotiated pricing may differ. These are not three extra charges automatically deducted from every seller’s sale; the FishBSE agreement and order breakdown determine the seller-facing fee. See Stripe Connect pricing.

FishBSE Auctions

Auction commitments, bid acceptance, Stripe authorization, anti-sniping, seller responsibilities, winners, payment recovery, and settlement.

1
The seller publishes the auction terms. The seller provides the item details, media, timing, fulfillment method, shipping information when applicable, and seller-specific terms. Sellers should publish information they are prepared to honor if the auction produces a qualifying winner.
2
The bidder reviews the auction and prepares payment authorization. Bidders must be signed in and eligible to bid. Review the complete listing, seller terms, fulfillment details, and any visible clarification before bidding. FishBSE may require Stripe payment-method setup so a valid payment method is available if that bidder wins.
3
FishBSE decides whether the bid is accepted. The server re-checks auction status, bidder eligibility, timing, payment authorization, and the required bid amount. Sellers cannot bid on their own auction. A typed amount is not an accepted bid until FishBSE confirms it.
4
Accepted bids are purchase commitments. Once FishBSE accepts the bid, the bidder should be prepared to complete the purchase if that bid ultimately wins. Do not bid as a placeholder while deciding whether you want the item.
5
Late qualifying bids can extend the closing time. FishBSE uses anti-sniping protection. Bidders should follow the updated end time shown by FishBSE because a qualifying bid near the end can extend the auction.
6
FishBSE finalizes the accepted bidding state. After the official closing time and any valid extensions, FishBSE determines whether there is a qualifying winner, including any applicable reserve requirement. If no qualifying bid wins, an eligible unsold auction automatically restarts for its original duration, keeping its existing bids and terms. Read about automatic timer renewal.
7
Winner payment is attempted and a paid order is created after settlement. FishBSE can attempt payment using the winning bidder's Stripe-authorized payment method. If successful, the auction moves into the marketplace order/fulfillment flow. For pickup auctions, the vendor must confirm the private location and calendar time window on the paid order within 72 hours of confirmed payment, with collection scheduled within seven days of that payment. Saving the schedule notifies the winner, who can then review it and follow the check-in and QR handoff steps. If additional payment action is required, FishBSE can provide the supported recovery path before non-payment is treated as final.
The FishBSE server state is authoritative. A browser countdown, notification, or typed bid amount does not override the auction record. If you are waiting on an important result, refresh the auction or check My Auctions/Orders directly.

Go to Create an Auction while signed in. Complete the auction listing details and required media/fulfillment information. Payment-enabled auctions require the seller to be eligible for the supported Stripe Connect payment flow. For a pickup auction, advertise the public pickup area and save a draft meeting point, availability and instructions under Private pickup details. Within 72 hours of confirmed winner payment, open the paid order and confirm its private location, calendar date, start and end times, and time zone. The pickup window must end within seven days of that same payment. Saving this schedule notifies the winner; a pre-payment draft does not make the order ready for pickup. Keep the exact address out of the public description. Once published, the auction can be viewed from Auctions and managed from My Auctions. An eligible unsold auction automatically renews for the duration you selected when there are no qualifying bids at closing. See timer renewal and the pickup, check-in and QR guide.

Open the auction and review the item description, media, fulfillment method, shipping charge when applicable, seller terms, and any visible clarification. Enter a bid that meets the amount currently required by the auction page. FishBSE then re-checks the live auction on the server, so a bid can be rejected if another bidder changed the required amount first, the auction ended, your account/payment authorization is not eligible, or the request fails validation.
An accepted bid is a purchase commitment. Do not assume a bid was accepted merely because you typed an amount or clicked the button. Wait for FishBSE to confirm acceptance and update the auction state.

A bid is accepted only after FishBSE validates the live auction and records the bid. Typing an amount, opening Stripe, or seeing a browser-side confirmation before the server completes validation does not create a successful bid by itself. Once FishBSE accepts the bid, treat it as a commitment to purchase if it becomes the qualifying winning bid.
Before submitting, verify the item, amount, fulfillment method, shipping cost, seller terms, and any visible clarification. A change of mind should not be assumed to cancel an accepted bid.

Auctions work best when winning bids can actually be completed. FishBSE's supported bidder setup uses Stripe to establish an authorized payment method for the auction flow so FishBSE can attempt the winning payment if that bidder becomes the winner. Stripe handles the card-payment infrastructure; FishBSE does not ask bidders to send card numbers directly to sellers.
Payment setup is not the purchase itself. A losing bidder is not the winning payer merely because a payment method was authorized. Winner collection is tied to the finalized winning bid and the supported settlement process.

FishBSE uses a late-bid extension mechanism so an auction is not decided only by who can submit in the final second. A qualifying accepted bid placed inside the final 120 seconds can extend the auction by another 120 seconds, subject to the auction system's extension limit.
Follow the updated FishBSE end time. The server-side auction state determines whether a bid was timely. A stale browser countdown, delayed notification, or previously displayed end time does not override an extension recorded by FishBSE.

An eligible unsold auction automatically gets another full bidding period. This happens when a live auction reaches its end with no qualifying winner, such as no bids or a reserve that has not been met. FishBSE uses the original auction duration, beginning when the close is processed. For example, an auction originally set for three days gets another three days.

It remains the same auction. Its existing bids, bid history, current bid, starting bid, reserve, pickup or shipping arrangements, and seller terms stay in place. A renewal does not cancel accepted bids or reduce the next required bid. The anti-sniping extension count resets for the new bidding period. The vendor and previous participating bidders receive a FishBSE notification linking to the auction and its new end time.

A qualifying winner proceeds to payment. An auction waiting for winner payment, a failed winner payment, a paid or canceled auction, or a historical auction already closed without a sale is not automatically reopened. An unavailable listing or seller account is not reopened by timer renewal.

The countdown may briefly show Finalizing… while FishBSE processes the close. Follow the new end time recorded on the auction. The auction grid checks expired timers automatically while the page is visible and keeps any search text you are typing. If it asks you to refresh, open the auction or refresh the results for the latest status.

When the auction closes, FishBSE finalizes the accepted bidding state and determines whether there is a qualifying winner. The supported payment flow then attempts to collect the finalized winning amount plus any applicable displayed shipping charge using the Stripe-authorized payment method associated with the winning bidder. If payment succeeds, FishBSE creates the corresponding paid-order record and moves the transaction into fulfillment. If automatic collection cannot complete and additional buyer action is required, FishBSE provides a recovery window of up to 24 hours before unresolved non-payment can become final.
A winning bid is not an invitation to renegotiate. Bid only when you are prepared to pay the accepted winning amount and complete the applicable pickup or shipping transaction.

A winning payment can require additional action because of a declined card, expired payment method or bank authentication request. Check the auction and My Auctions for the required next step and payment deadline. A temporary payment error alone is not a conduct warning. If payment appears to have succeeded but the order has not updated, contact support before trying again.

Bidders should be able to understand what they are bidding on. When FishBSE displays a seller clarification, treat it as additional auction information and review it before placing another bid. Clarifications should explain or correct information; they should not be used to quietly replace the item or materially rewrite the deal after bidding has begun.
If a change would materially alter the item, fulfillment method, price structure, or another important auction term, the seller should not assume a clarification makes that change acceptable. Contact FishBSE support when a material correction is necessary.

No. FishBSE's auction bidding rules prevent the auction seller from bidding on their own auction. Attempts to manipulate auction pricing or bidding activity may also be reviewed under FishBSE marketplace rules.

While an auction is still scheduled/live, the current FishBSE policy allows a seller cancellation. If there are no accepted bids, the cancellation does not create a seller auction-conduct warning. If there is at least one accepted bid, FishBSE cancels the accepted bid records, notifies affected bidders, does not attempt a winner charge, and records one seller cancellation warning.
Seller cancellation is no longer the normal path once the auction has reached closing/finalization/payment state. A paid auction is handled through the order/refund workflow instead. Repeated seller auction-conduct warnings can restrict new listing and auction creation.

You should treat every submitted bid as a purchase commitment. Do not use bidding as a way to reserve an item while deciding whether you want it. If there is a genuine mistake or exceptional problem, contact FishBSE immediately, but a change of mind should not be assumed to cancel an accepted bid or a completed winner payment.

Auction Warning System & Responsibility

How FishBSE assigns buyer/seller responsibility, when warnings are issued, and what happens at the limit.

FishBSE keeps separate auction-conduct histories for buyers and sellers and uses a three-warning limit in each role.
Seller total: auction-cancellation warnings + paid-auction-order fulfillment warnings. At 3 combined seller warnings, new marketplace listings and new auctions are disabled.
Buyer total: unpaid winning-auction warnings + buyer-caused cancellation/refund warnings on paid auction orders. At 3 combined buyer warnings, auction bidding is disabled.
The restrictions are role-specific. A buyer bidding restriction does not shut down normal marketplace access. A seller listing restriction does not prevent that account from buying, bidding, managing existing transactions, or accessing orders.

If the auction is still scheduled/live and has no accepted bids, the seller can cancel without receiving a seller warning. If there is at least one accepted bid, FishBSE cancels the accepted bid records, archives the auction listing, notifies affected bidders, does not attempt a winner charge, and records one seller auction-cancellation warning.
Once the auction reaches its closing/finalization/payment stage, seller cancellation is no longer the normal cancellation path. A paid auction has become an order and must be handled through the order/refund process instead.

The current auction payment window is 24 hours. If additional payment action is requested, follow the instructions on the auction or My Auctions page before the deadline. Failure to complete payment can result in a non-payment warning. A temporary payment error alone does not establish that a warning is due. If your receipt and order disagree, contact support before paying again.

For a paid auction order with shipping, the current seller ship-by deadline is 72 hours after the paid order is created. Failure to fulfill an eligible order by its deadline can result in a fulfillment warning. Setting an order to Working does not extend that deadline. Use the shipping workflow to record actual shipment and tracking; contact support if you cannot fulfill the order.

On an eligible unshipped paid auction order, buyer-responsibility reasons include changing their mind, ordering by mistake, or no longer being able to complete the purchase. If the refund succeeds, FishBSE records one buyer cancellation/refund warning. The same buyer responsibility applies if the seller submits the refund using the reason that the buyer asked to cancel.
A warning is applied from the completed refund outcome, not merely from opening the refund page or selecting a reason.

If the seller refunds an eligible unshipped paid auction order because the item is unavailable, was damaged/lost before fulfillment, the auction/listing had a material error that prevents fulfillment, or the seller is otherwise unable to fulfill, the completed refund is classified as seller responsibility and can produce one seller fulfillment warning.

FishBSE treats several outcomes as neutral unless administration determines otherwise after review. Examples include mutually agreed seller/buyer cancellation, system or administrative refunds, duplicate-payment refunds, and support-reviewed situations that should not automatically assign fault. Regular non-auction marketplace refunds also do not feed the auction buyer/seller warning counters.

No. The automatic refund form is intentionally limited. If a buyer selects “seller has not shipped,” FishBSE checks the actual auction ship-by deadline; before that deadline the buyer cannot automatically assign seller fault. If a buyer says the seller “cannot fulfill,” the current flow requires the seller to submit the cancellation from the seller account or requires FishBSE support review before seller responsibility is assigned.

The same conduct event should not produce duplicate warnings. If a warning appears more than once for the same incident, contact support with the auction or order number. Separate incidents on an order may still receive separate review.

Yes. FishBSE administration has account-policy controls that can reset the active auction buyer or seller warning counters and restore the corresponding privilege after review. Historical warning/audit records are kept for moderation context rather than being silently erased.

Refunds, Cancellations & Disputes

What can be refunded, who initiates it, timing, auctions, local payments, and card disputes.

For an eligible unshipped paid order, use the available cancellation or refund option on the order. Explain the issue and preserve relevant messages, photos and tracking. The current self-service flow requests a full eligible refund; partial adjustments and other cases need support review. Check the recorded outcome. A submitted refund is not the same as money arriving at the buyer’s bank.

A full eligible purchase refund includes the refundable shipping amount collected in that payment. Post-shipment adjustments, partial resolutions and unusual cases need support review. A purchase refund is separate from a refund for a shipping label bought from a carrier.

Winning an auction should be treated as a purchase commitment. A change of mind does not automatically create a right to cancel an accepted winning bid or reverse a completed payment. Refunds may still be appropriate when the seller agrees, the item cannot be fulfilled, the transaction has a documented problem, or another valid resolution is reached.

No. FishBSE DOA coverage must be offered on an eligible, approved shipped-livestock listing and explicitly purchased by the buyer at checkout. Read the recorded policy on your order. Seller-specific promises remain separate. See how FishBSE coverage works and how vendors apply.
The purchased FishBSE claim window starts at first verified carrier acceptance, not delivery, and can expire before a delayed delivery. File within the displayed deadline and document the package and condition promptly.

FishBSE cannot directly reverse a payment that did not run through FishBSE's supported Stripe transaction flow. The buyer and seller must resolve the payment between themselves or use whatever protection/dispute process is offered by the outside payment service.

Refund: The transaction is voluntarily refunded through the payment flow, usually after the buyer and seller agree on a resolution or an authorized platform action is taken.
Card dispute/chargeback: The cardholder asks their bank/card issuer to challenge the charge. Stripe provides the dispute-management infrastructure and evidence flow, but the cardholder's bank/card network makes the decision.
Sellers should keep transaction evidence because a dispute can require documentation such as the listing, messages, tracking, proof of delivery, and refund history.

A submitted refund can be pending before it succeeds or fails. Check the order’s refund status rather than treating a button click as confirmation. Refunds go back to the original payment method; bank posting is separate from FishBSE’s status.

Stripe says card credits commonly appear about 5–10 business days after a refund is initiated, depending on the bank. Some refunds appear as a reversal of the original charge. If the expected credit is missing, contact support with the order number and ask about a refund reference. See Stripe’s refund guidance.

Pending means the outcome is not final; do not submit duplicate refund requests. Succeeded means the payment-side refund completed, though bank posting can take longer. Failed needs review; use the available order action or contact support rather than assuming the buyer received money.

While a refund is pending or succeeded, FishBSE blocks normal fulfillment advancement. A full eligible purchase refund includes the refundable shipping collected in that payment. It is separate from a refund for a label bought from a carrier.

A supported refund must account for the buyer’s refund and the seller’s previously transferred proceeds. FishBSE’s current configured refund flow requests the related transfer reversal and return of the application fee; the order and provider results determine what actually completed.

A buyer refund does not mean every payment-processing expense is returned to FishBSE. Refunds, bank disputes and postage can have separate costs or adjustments. Do not promise a partial amount or deduct a fee informally: review the actual refund summary or contact support. See Stripe’s refund guidance.

Open the order in Orders and use its dispute controls when available. Explain the issue and preserve messages, listing terms, photos, tracking and delivery evidence. The current workflow offers a refund or replacement proposal.

  1. Either party can propose terms during the negotiation window.
  2. The buyer accepts the current proposal.
  3. The seller gives final confirmation of those exact terms.

The window is 24 hours from opening the case. Changing a proposal clears earlier acceptance; it does not restart the clock. If agreement is not completed in time, the case requires administrator review. That deadline is not a promise of a bank refund within 24 hours.

The supported replacement workflow creates a linked fulfillment order without a new buyer charge. Follow the agreed replacement terms and the instructions on that order. Report a replacement problem through the dispute on the original order rather than starting an unrelated payment.

A confirmed proposal can still require fulfillment or refund processing. Pending resolution is not proof that a replacement shipped or that money reached the buyer. Contact support if it remains pending or the remedy cannot be completed.

No. A FishBSE case records communication and a possible marketplace resolution. A bank dispute challenges the card payment through the cardholder’s issuer; it follows a separate evidence and decision process. A FishBSE agreement does not automatically withdraw a bank dispute.

Tell FishBSE if a bank case is already open, keep notices and deadlines, and coordinate any proposed refund with support to avoid conflicting actions. The card issuer decides the bank dispute outcome. Read Stripe’s dispute overview.

Shipping & Stripe

Checkout, addresses, seller shipping fees, tracking, payment processing, disputes, and payouts.

If the listing supports FishBSE's online shipping checkout, the buyer reviews the item price and seller-set shipping charge, enters the required shipping information, and completes card payment through Stripe. After successful payment, the seller fulfills the order and shipment/tracking information can be associated with the FishBSE transaction.
Shipping is currently described by FishBSE as U.S.-address fulfillment. Always verify the listing's current fulfillment details before purchasing.

After the order shows confirmed payment, buy a suitable label from your preferred carrier or label provider. Open the order in Orders, upload the label, and enter the carrier and tracking number. The current manual-label workflow requires a label within 24 hours of payment; use the exact deadline shown on the order.

A label upload is not proof of dispatch. Select the carrier-handoff confirmation only after you actually hand the parcel to the carrier. The order then becomes Shipped. Keep packing photos and the carrier’s acceptance receipt.

Auction ship-by deadlines are separate from label-upload deadlines. Meet both where shown. For livestock, plan for weather, carrier rules, packing and suitable transit times.

Yes. For a supported shipping checkout, the seller's configured shipping charge is added to the item amount so the buyer can see the transaction total before completing payment.

Stripe provides the payment-processing infrastructure used by supported FishBSE card transactions and connected seller-account flows. Stripe also provides payment-security, fraud/risk, refund, and dispute-management capabilities associated with its services.
Stripe processing does not mean Stripe guarantees the condition, legality, health, delivery, or quality of a FishBSE listing. FishBSE is also not representing that Stripe endorses FishBSE. Stripe is the third-party payment services provider used for supported transactions.

Supported card checkout is handled through Stripe's payment flow rather than asking a buyer to provide raw card information directly to the seller. Sellers receive the marketplace/order information needed to fulfill the transaction, not a buyer's full card credentials.

Stripe Connect controls the connected-account payout process. Payout timing may vary based on seller verification, Stripe requirements, account history, risk review, payout schedule, bank processing, weekends, and holidays.

Live-animal shipping requires more judgment than ordinary merchandise. Sellers should use appropriate bags/containers, insulation, temperature control when needed, suitable carrier/service levels, and weather-aware scheduling. Buyers should be available for delivery and should inspect/document the shipment promptly. Any seller-provided DOA/live-arrival policy should be clearly stated before payment.

With included shipping, the seller includes the cost in the item price and sets the buyer’s shipping charge to zero. With separate shipping, checkout adds the displayed shipping charge to the item price. Either way the buyer makes one payment.

Under a fee policy that includes shipping, a $35 item with free shipping has the same fee base as a $10 item plus $25 shipping. The seller still buys postage. Buyer-paid shipping is not a promise that the actual label will cost that amount; the seller bears the difference.

Orders in the current manual shipping workflow have a label deadline of 24 hours after confirmed payment. Check the order for its exact due time. Sellers can request an extension with a reason; the buyer must approve it. Approved extensions may total no more than three additional days.

A pending or rejected request does not grant extra time. Uploading a label meets the label step, not the actual dispatch step. Auction ship-by deadlines, when present, are separate; follow the deadlines shown on the order or ask support if they conflict.

Buy a suitable shipping label through your preferred carrier or label provider. In FishBSE, open the paid order’s label/shipping controls, upload the label, and provide carrier and tracking details. Supported label files are PDF, JPG, PNG or WebP up to 8 MB.

The label is shared privately through the order with authorized participants. Do not publish addresses or labels in listing photos or public comments. FishBSE’s current manual-label page does not automatically buy postage or subtract the label’s actual cost from checkout proceeds.

No. Creating or uploading a label says the label is ready. Confirm carrier handoff only once the parcel has actually been given to the carrier. That action marks the order Shipped and closes the automatic pre-shipment refund option.

Keep the carrier acceptance receipt and follow tracking scans. A tracking number or a “label created” scan alone is not proof of carrier possession or delivery. If a number is wrong, correct it through the order workflow where permitted and notify the buyer.

FishBSE can show overdue status and send reminders. A missed label deadline does not itself prove a refund succeeded. Use the order’s eligible cancellation, extension or dispute controls, or contact support.

If you bought the label outside FishBSE, request a void or postage refund from that carrier or label provider under its rules. Refunding a FishBSE purchase does not automatically cancel an external label, and a carrier label refund does not refund the buyer’s purchase.

Confirm receipt only after you have the item. Buyer confirmation and seller reports are separate evidence; neither automatically closes an open issue or guarantees condition. Payment is not held for release by a delivery-confirmation button.

For supported paid pickup orders, check in on arrival. After receiving the item, the buyer confirms receipt to generate a single-use QR code and an 8-digit backup, valid for 15 minutes. The vendor uses Dashboard → QR Verify to scan the code, review the matching item and explicitly confirm the handoff. Report missing, damaged or incorrect items through the order rather than confirming receipt prematurely.

When a Transaction Goes Wrong

What to check and how to get help when an order or payment goes wrong.

Hours follow West Coast time, including daylight-saving changes. You can submit the contact form anytime. For a purchase or sale issue, select the related order so support has the right details.

Follow the claim, dispute and fulfillment deadlines shown on your order. Support hours and holiday closures do not pause those deadlines.

ScenarioFishBSE resultAutomatic auction warning?
Seller cancels before any accepted bidAuction canceled; no winner chargeNo
Seller cancels after accepted bidsBids canceled; bidders notifiedSeller
Auction ends with no bidsNo saleNo
Reserve is not metNo saleNo
Bidder is outbidNo winner charge to that bidderNo
Winner's card declines or needs authenticationFollow the requested payment actionNot yet
Winner remains unpaid after the full deadlinePayment remains incomplete after reviewBuyer
Buyer cancels paid auction order for change of mind/mistakeEligible pre-shipment full refundBuyer after successful refund
Seller cannot provide the paid auction itemEligible pre-shipment full refundSeller after successful refund
Seller misses paid-auction shipping deadlineBuyer notified; refund path becomes eligibleSeller
Buyer and seller mutually agree to cancelNeutral refund classificationNo automatic warning
System/admin/duplicate-payment refundNeutral/system resolutionNo automatic warning
Problem occurs after shipment/deliverySelf-service cancellation closes; support/dispute routeNo automatic pre-shipment warning

FishBSE finalizes the auction as No sale. There is no winning-order payment to collect and the no-sale outcome does not create a buyer or seller conduct warning merely because the auction did not sell.

Setting up the Stripe payment method is not the purchase itself. If another bidder becomes the winner, FishBSE does not treat the losing bidder as the winning payer. The payment authorization remains a Stripe/FishBSE auction payment-method record for the supported flow, but the winning-auction charge is tied to the finalized winning bid.

Do not pay again simply because the order has not updated. Refresh the order or auction after a short wait and check your receipt. If the payment and order still disagree, contact support with the order or auction number and the payment reference shown on your receipt. Do not send card numbers or authentication codes.

If you believe you were charged twice for the same auction, do not make another payment. Check the order and receipts, then contact support with the auction or order number and the apparent duplicate charges. An authorized payment correction does not itself count as an auction conduct warning. Check the recorded refund status rather than assuming a correction has completed.

Do not submit another refund while the first is pending. The payment provider may still be confirming the outcome. Check the order for its recorded refund status and contact support if it remains unclear. Pending does not mean that the buyer has received the money or that the request failed.

FishBSE records the refund as Failed with a failure reason when the outcome is definite. If the order remains otherwise eligible and there is no completed refund reference, the refund can be retried or reviewed. A conduct warning tied to a buyer/seller refund reason is intended to be applied only after the refund reaches a successful refunded state.

Check the ship-by deadline on the order and contact the seller for an update. If that deadline has passed and the item remains unshipped, use the issue or refund options available on the order. Contact support if an appropriate option is unavailable. Keep your messages and payment records.

Before the order is delivered, the seller can return to the shipping workflow and update the carrier/tracking information. FishBSE records the new shipping information and can notify the buyer that shipping was updated. The tracking field is format-validated, but buyers should still use the carrier's tracking record to verify actual movement and delivery.

A delivery status does not settle a disagreement about receipt. Check the carrier’s tracking record and delivery location, preserve scans and messages, and report the problem from the order’s dispute or support controls. Buyer receipt confirmation and seller delivery reports are recorded separately.

Do not confirm receipt of an item you have not received. A receipt confirmation does not automatically close an existing issue. Once an order is shipped or delivered, use the dispute/support route rather than the pre-shipment cancellation form.

Document the packaging, label and item immediately, keep the seller’s listing and DOA terms, and contact the seller. Open the order’s dispute workflow in Orders when available; contact support if it is unavailable. The automatic pre-shipment cancellation form is not the route for a shipped or delivered order.

A FishBSE dispute can document a refund or replacement proposal. An allegation alone does not prove fault or guarantee a refund. Do not dispose of evidence or return livestock or goods without agreed instructions.

For Pay now, pick up later purchases and paid pickup auctions, review the private calendar window and contact the other party. The vendor has 72 hours after confirmed payment to provide the plan, and the pickup window must end within seven days of the same payment. Keep messages, schedule changes and arrival evidence; use the order issue link to request review or a refund if the arrangement fails. Follow the order's guidance if an older purchase has no recorded deadline.

A missed pickup deadline or reported no-show does not automatically refund the payment or assign a warning. Responsibility is determined through the supported cancellation classification or dispute review. Ordinary Local pickup listings with direct payment remain arrangements between the participants.

The fulfillment controllers reject advancement when a refund is pending or succeeded. The shipping page also refuses shipping changes in those states. This is intentional: once a refund is being processed, the seller should not continue fulfillment as though the paid order were unchanged.

FishBSE can assist with its supported marketplace payment and order workflows. Payments made through an outside service follow that provider’s rules; FishBSE cannot directly reverse them. Preserve your messages and payment records, and use the provider’s dispute or support process when appropriate.

Buyer payment settlement and the seller's later bank payout are different events. A Stripe Connect payout delay does not mean the buyer failed to pay. Sellers should check their connected Stripe account for payout status, verification requirements, or bank processing issues. Auction buyer non-payment warnings are based on the winning auction failing to reach a paid order, not on how quickly the seller's bank receives a payout.

Getting Started

Accounts, costs, and the basics of using FishBSE.

FishBSE is a community-first aquarium marketplace for local listings, supported shipped orders, and auctions. Members can create listings, communicate with hobbyists, buy and sell locally, use Stripe-powered checkout for supported online transactions, and participate in FishBSE auctions.

Creating an account and using standard marketplace features may be free unless FishBSE states otherwise for a specific feature. Supported card transactions use Stripe, and payment-processing or FishBSE marketplace fees may apply according to the transaction and applicable terms. When FishBSE requires a seller to accept an auction fee policy before publishing, review that displayed fee information before creating the auction; the seller should not rely on an old screenshot, forum post, or previously quoted fee for a new auction.

Click Sign Up, fill in basic info, and you’re in. You can edit your profile and preferences from your dashboard anytime.

How FishBSE Features Work

A practical map of the marketplace tools buyers, sellers, and bidders may use.

  • Listings: Publish fish, coral, invertebrates, plants, and aquarium equipment with descriptive information, location, price, media, and fulfillment options.
  • Search/filtering: Helps members narrow marketplace inventory by relevant listing information such as region, species/category, or gear.
  • Favorites: Lets a signed-in member save listings they want to return to later.
  • Messaging: Gives buyers and sellers a place to ask questions, coordinate pickup/shipping, and keep transaction-related communication together.
  • Online status: Helps members understand whether another FishBSE user is currently active when the feature is available.
  • Photos/video: Listings can include multiple images and a supported short video presentation so buyers can better evaluate what is being offered.
  • Local fulfillment: Agree on a meeting time. Ordinary local pickup follows the listing's direct payment terms; paid pickup orders use check-in and QR handoff confirmation.
  • Supported online checkout: Uses Stripe for card-payment processing and connects the payment to FishBSE's marketplace order workflow.
  • Stripe Connect: Provides the connected seller-account infrastructure needed for supported marketplace payouts.
  • Order records: Keep supported online transactions tied to an identifiable marketplace order rather than relying only on chat.
  • Shipping/tracking: Lets supported fulfillment information be associated with the order so participants can follow shipment progress.
  • Private shipping documents: Allows transaction-related shipping proof or label/receipt information to be shared more privately than posting it publicly.
  • Auctions: Provide timed bidding, bidder eligibility/payment setup, server-validated bids, anti-sniping extensions, winner determination, and a Stripe-backed winner-payment flow.
  • Notifications: Surface important marketplace, order, and auction activity so members know when attention may be needed.
  • Block/report tools: Let members limit unwanted contact and alert FishBSE to suspicious, prohibited, or problematic activity.

FishBSE's value is not simply a payment button. The marketplace can combine the listing, member identity, communication, supported payment status, order record, shipping/tracking activity, auction state, notifications, and reporting tools around the same transaction. That gives participants more context and documentation than an isolated payment with no marketplace record.

Listings

Create, edit, archive, and manage what you post.

Go to Create Listing, choose a category, add photos (up to 5), an optional short video, details, location, and your preferred fulfillment method (local pickup, shipping, or pay-now-pickup-later). Submit to publish instantly.

  • Edit: From your dashboard, open the listing and choose Edit.
  • Archive: Hides the listing without losing data. You can unarchive later.
  • Delete: Permanently removes the listing, its images, any uploaded video/poster, and the generated listing page.

Live fish (freshwater/saltwater), corals, invertebrates, and aquarium equipment/dry goods. Follow all local/state/federal laws; prohibited or invasive species are not allowed.

Trading & Payments

Messaging, local trades, and payment options.

For ordinary local-pickup listings or trades, participants can coordinate directly and agree on an offered payment method. Pickup auctions and Pay now, pick up later use Stripe online payment; follow the payment terms shown for that transaction. For supported FishBSE online transactions, card checkout is processed through Stripe and tied to FishBSE's marketplace/order workflow. Payments made outside that supported checkout cannot be directly reversed by FishBSE.

Yes—real-time chat with online status indicators. Start a conversation from a listing to ask questions, negotiate, arrange pickup, or share shipping/tracking updates.

Photos & Video

Upload requirements, video support, and media handling.

You can upload up to 5 images (JPG/PNG). Individual files are limited to 4MB each.

Eligible VIP members can add or replace a supported listing video. Current eligibility is checked again when saving. Existing videos remain when a non-VIP owner saves other permitted changes. Use the uploader instructions for supported formats and limits.

Deleting a listing removes its public listing record when deletion is permitted. Media may be retained for order snapshots, other references and controlled cleanup; deletion does not promise immediate erasure of every physical file or previously downloaded copy.

Account Security & MFA

How multi-factor authentication protects your FishBSE account, recovery codes, and protected account access.

Multi-factor authentication (MFA) adds another verification step after your normal sign-in. When MFA is enabled, knowing the account password alone is not enough to complete access to protected FishBSE account areas.
MFA is especially useful for accounts that can manage listings, orders, payouts, seller activity, or administrative tools because it reduces the risk of someone using a stolen password by itself.

When FishBSE asks you to verify your sign-in, enter the current 6-digit code from the authenticator app connected to your account. If you cannot use the authenticator app, you can enter one of your unused FishBSE recovery codes instead.
1
Sign in normally. FishBSE first verifies your regular account credentials.
2
Complete the MFA challenge. Enter the current authenticator code or an unused recovery code.
3
Continue to the protected page. After successful MFA verification, FishBSE marks the current session verified and returns you to the page you were trying to access.

Recovery codes are backup credentials for situations where you cannot access your authenticator app. A FishBSE recovery code is single-use: after one is accepted, that same code cannot be used again.
Store recovery codes somewhere private and separate from your normal password. Do not post them in chat, listings, screenshots, or support messages. If you lose both your authenticator access and all unused recovery codes, contact FishBSE support for account-recovery assistance.

Repeated unsuccessful verification attempts can temporarily lock MFA verification. Follow the message on the sign-in page and wait before trying again. Check that you are using the correct authenticator and a current code, or use an unused recovery code. If you cannot regain access, use the MFA Reset support option.

Finish the requested MFA verification before using protected account features. If a feature remains unavailable after successful verification, refresh the page or contact support. Do not share your password, authenticator codes or recovery codes.

FishBSE Notifications

How the in-app notification inbox, unread activity, browser alerts, and protected notification access work.

FishBSE has an in-app notification inbox for signed-in members. The site periodically checks for recent account activity, shows an unread count, and presents recent notifications with a title, message, time, and a safe FishBSE destination when an action or related page is available.
Notifications are designed to help you notice important activity; they do not replace checking the actual auction, order, shipment, payout, or account page when a transaction requires action.

Depending on the feature involved, FishBSE notifications can be used for important marketplace activity such as trade activity, auction updates, winner/payment events, order or shipping changes, pickup readiness and arrival check-ins, completed handoffs, account-policy events, and moderation actions. When FishBSE administration removes one of your ordinary marketplace listings, the notification system can also tell you that the listing was removed and provide the administrative reason recorded for that action.

FishBSE bridges supported trade activity into the general notification inbox. That means trade-related events can appear alongside other marketplace notifications instead of requiring a completely separate place to check for every type of account activity.

Not exactly. The FishBSE in-app inbox is the account notification feed shown while you use the site. Browser/push alerts are an optional convenience that may display an alert through your browser when the feature is enabled and your browser has granted permission.
You can review supported browser-notification preferences from FishBSE's notification settings. Disabling browser alerts does not mean you should ignore the in-app notification inbox or the underlying order/auction status.

FishBSE tracks whether an in-app notification has been read. The unread count represents notification records that are still marked unread for your account. The compact feed shows your most recent notification activity, while the underlying notification record can remain associated with your account after you read it.

Notifications are private account information. Sign in and complete any required MFA verification to view them. If access remains unavailable, follow the account guidance or contact support.

The notification feed is a convenience layer over the underlying FishBSE records. A temporary browser, network, sign-in, MFA, or server issue can delay the feed. If you are waiting on something important, check the related order, auction, trade, dashboard, or shipping page directly instead of relying only on an alert.

Safety & Policies

Safer meet-ups, prohibited items, reports, and moderation.

Meet in public, well-lit places; bring a friend when possible; and confirm item condition before paying. Keep chat in-app until you trust the other party.

Yes. Listings must comply with all applicable laws (e.g., CITES, Lacey Act, and state regulations). Illegal or invasive species are not allowed.

Use the Report or Block options from a listing or conversation. Our team reviews reports and may take action according to our policies.

Forums, rewards and moderation

Open Forums, choose a category, then start a thread. Sign in, enter a clear title and your message, complete any displayed security check, and submit. Category quick-posting takes you to the full composer for review before publication.

Use the thread editing option while signed in as its owner. A locked thread cannot be edited through the normal editor. If the discussion changes or becomes locked while you are editing, refresh and review its current state before retrying.

The thread may be locked or removed, your account may be restricted, or a posting limit may apply. Read the displayed message. A saved page can be out of date, so refresh before composing another reply.

The forum limits rapid posting and repeated submissions. Follow the displayed message and wait before posting again. Check whether your previous post already appeared before submitting another copy.

Repeating the same reply in the same thread shortly after posting can be blocked. Check whether your first reply already appeared before submitting again. If you need to add information, write a distinct follow-up.

The thread composer can request a security challenge when recent activity requires one. Complete the current challenge and submit the displayed form. An expired challenge or an old browser tab may require refreshing the form.

Forum messages allow supported formatting while removing unsafe markup and links. Pasted scripts, event handlers and unsupported HTML are not preserved. Review the saved message and use the editor controls for ordinary formatting.

Administrators can remove threads using the moderation controls. The action checks their current permissions and removes the discussion and its replies. Report a thread that needs attention rather than trying to remove another person's content.

Yes. Administrators can remove an individual reply. The original opening post is protected from the individual-reply deletion action; removing the whole discussion uses thread deletion. Reply counts and the latest-reply information are updated after removal.

Removing a thread removes it and its attachment links from the normal forum experience. Some files may be retained for necessary recordkeeping and controlled cleanup. Copies already downloaded or cached by other people cannot be recalled.

Use the supported model file types and archive limits shown by the uploader. Archives that cannot be safely checked or contain unsupported content are rejected. Review the displayed error and prepare a supported archive; contact support if a valid upload continues to fail.

Use supported images and follow the size and usage limits shown by the uploader. Reduce oversized files, wait if a usage limit applies, and contact support if supported images keep failing.

An eligible thread earns its author one bonus listing boost when it reaches 1,000 qualifying views. The reward is added to the existing account boost balance, and an in-app notification explains that it is available. This is a once-per-thread reward.

Displayed views and qualifying reward views are different counts. Older views are not retroactively converted into reward progress, and not every visit qualifies. The reward progress shown for your thread is the relevant count for the milestone.

No. Your own visits and artificial or repeated activity do not qualify for the forum reward. Focus on useful discussions and genuine readers. The reward is based on qualifying views, which can differ from the displayed view total.

No. The implemented reward is one bonus boost per eligible thread at the 1,000 qualifying-view milestone. Additional views on that same thread do not repeatedly award the milestone reward.

Open your Dashboard, check your bonus boost balance, and choose an eligible listing to boost. When your daily free boost is available, it is used first. Bonus credits are used when the daily free boost is on cooldown; the reward is not automatically tied to one listing.

The reward counter excludes views of locked threads. If a thread is removed, it is no longer available to accumulate new qualifying visits. A displayed historical view total does not guarantee that new reward progress is being recorded.

Managing listings and favorites

Use the Dashboard filters to switch between active, completed, cancelled and archived listings. Search also accepts a listing ID. A listing missing from the Active view may still be available under another status.

Listings linked to orders, active checkout reservations, auctions or other protected history cannot always be permanently deleted. Read the reason shown on the listing card. Archiving may be appropriate when available, but it does not remove transaction history.

No. Archiving stops new listing checkout when permitted and preserves existing history. It does not cancel an order, refund a buyer, or release you from fulfillment duties. Manage an existing purchase from its order workflow.

An active checkout reservation protects the listing while payment is being resolved. Wait for its status to settle and refresh the Dashboard. Do not change or delete the listing to work around a pending payment.

No. The Dashboard bulk action targets the described set of your unarchived, non-auction listings, not just the filtered cards currently visible. Read the confirmation carefully. If a protected record prevents the operation, the transaction is rolled back.

Some listings with released checkout history require an explicit checkbox and typed confirmation. This is an additional confirmation for a permanent action, not permission to delete protected orders or active reservations. The server checks the listing again when you submit.

Photos may still be referenced by another listing or an order snapshot. The deletion workflow retains physical media for controlled cleanup rather than deleting files that could be needed by transaction records.

Adding or replacing listing video requires current VIP eligibility. The editor checks that eligibility again when saving. Existing videos can remain when a non-VIP owner saves other permitted text or photo changes.

Changes to online sale terms can require validation of the saved fee agreement and current payment eligibility rules. An older listing with missing fee acceptance may need support before those terms can change. Ordinary permitted text or photo edits do not automatically migrate payment terms.

Sign in and choose Favorites from Explore. You can filter saved items by fulfillment method and use their available actions to view, contact, purchase or bid as appropriate. Saving a listing does not reserve its stock or price.

Saved inactive, archived or deleted listings can remain in your Favorites until you remove them. Their presence is a saved reference, not confirmation that they can still be purchased.

Saved auctions use their auction status and displayed bid information. Open auctions lead to bidding, while ended auctions can remain available for review. A favorite does not place a bid or authorize a payment.

Guest listings and private access links

The guest listing flow supports a local sale listing after email verification. Start from List, provide the required contact details, complete the security challenge and accept the terms. You then use the private email link to verify and prepare the listing.

Open the verification link within 24 hours of requesting it. One private link controls one local listing for 30 days from the email request. Closing the listing revokes that link. Follow the page's instructions if access has expired.

Reopen the private email link on the device you want to use. It can restore access while the link remains valid, including after the device session expires. Keep the link private because it grants access to that listing.

No. Guest listings are restricted to local pickup and direct payment. The guest flow cannot enable shipping, online checkout, auctions or FishBSE DOA coverage. Use an eligible member seller account for supported online selling features.

Closing archives the guest listing and revokes its private management link. Do not close it merely to refresh the page or test the link. Keep any records you need before confirming closure.

No. The existing private link does not allow changing the email address. Contact support if you need help with access rather than sharing the management link with another person.

The guest flow validates and normalizes the phone number, but it does not prove ownership by SMS. Email verification proves access to the email address. Neither check is a guarantee of a seller's reliability or the item's condition.

No. Share the public listing address. Your private email link grants management access and should not be posted in the description, messages or forum.

The first email request does not create a published listing or upload photos. Verify using the emailed link first, then use the management form to add supported photos and publish. Images must pass the normal upload checks.

Your city is public, but the dedicated guest contact number is shown only to signed-in members while the listing is available. Your email is not displayed as public contact information. This does not hide contact details you type into a public description, comment or photo.

Support, contact forms and account access

Choose the topic that describes your issue, such as Transaction Dispute, Report Listing, Report User, Billing Issue, Account Issue or MFA Reset. Include the relevant order or listing number and a clear explanation, without passwords or card details.

The form limits repeated submissions to reduce abuse. Follow the displayed message and wait before trying again. Check whether your earlier request was already saved, and keep its ticket number instead of sending duplicate requests.

An outdated form or a submission made too quickly may need to be reviewed and sent again. Review the preserved message and follow the instructions on the refreshed page. Avoid repeatedly pressing Submit.

The support form is for FishBSE help. Unsolicited sales pitches, website-development offers and marketing solicitations are not accepted. Clear promotional messages can be rejected before a support ticket is saved.

Yes. Choose Report User or the most relevant reporting topic and explain that you received an unwanted message. Include the relevant user or listing details and describe the problem. Do not send repeated copies of the same report.

A successful submission displays a support ticket or report number. Keep that number for reference. If you see a validation error or a temporary-unavailable message, do not assume a ticket was created.

The transaction-report form accepts up to five valid HTTPS evidence links. Use links to relevant photos or documents and check that the intended reviewers can access them. Do not include account passwords, card numbers or secret authentication codes.

Use the contact form's MFA Reset topic and provide the requested account details, reason and access information. Support reviews account ownership before MFA can be removed. Submitting a request does not automatically disable MFA or bypass identity checks.

Messages, notifications and everyday use

Private-message notifications are acknowledged when the relevant conversation and incoming messages load. Opening one conversation should not mark unrelated conversations as read. If loading fails, the unread indicator may remain until the messages can be opened.

Yes. A private-message notification can open the existing conversation even when the other person is offline. They do not need to be currently online for you to review saved messages.

Opening chat from the order links the conversation to that transaction. Its messages and photos can then be relevant to authorized dispute review. Unrelated private conversations are not automatically included in that order's case.

Yes. Open Explore and choose Stripe to read FishBSE's payment information page. Viewing this page does not connect a seller account, authorize a payment or create an order.

Still need help?

Send us a message through the contact form if you couldn't find the answer you needed about a listing, order, auction, refund, shipment, or account.

Explore Auctions