Exchange methods

Know what to prepare before opening a ticket.

Different payment methods need different proof, checks and waiting times. ByteSwap keeps the final quote and instructions inside your official Discord ticket, but this page helps you prepare before you start.

Available method types

Each method has its own preparation and proof standard.

Availability can change depending on current staff coverage, risk level, amount and exchange direction. The official ticket always overrides general website guidance.

Usually fast

PayPal and digital wallets

Common for customers who want a simple payment flow. Exact instructions, recipient details and note rules must be followed from the ticket.

Prepare
  • Your payment amount and receive asset.
  • Correct PayPal or wallet account details.
  • Enough balance for the full quoted amount.
Proof required
  • Payment screenshot showing amount and recipient.
  • Transaction or receipt ID if available.
  • Confirmation that note rules were followed.
Review based

Bank transfer

Bank transfer may be available for some orders. It can be slower because confirmation depends on bank processing, region and payment visibility.

Prepare
  • Bank name, transfer type and exact amount.
  • Recipient details shown in the ticket.
  • Any reference text the ticket requires.
Proof required
  • Transfer confirmation or receipt.
  • Visible amount, time and recipient reference.
  • Status if the bank marks it pending.
Network based

Crypto payouts and crypto orders

Crypto orders can involve LTC, BTC or SOL depending on availability. Network, address and TXID accuracy matter because crypto transfers are irreversible.

Prepare
  • Your correct receiving wallet address.
  • The exact network requested in the ticket.
  • Enough time for blockchain confirmation.
Proof required
  • Transaction ID or explorer link.
  • Screenshot showing amount and destination if asked.
  • Confirmation that the address and network match.
Limited availability

Cards, gift cards and prepaid methods

Card-based or gift-card style orders should only be used when the ticket specifically offers them. These are usually reviewed more carefully.

Prepare
  • Only the card or payment type accepted in the ticket.
  • Original purchase or ownership proof if required.
  • No reused, unclear or partially hidden details.
Proof required
  • Receipt, balance or redemption proof when requested.
  • Clear images without cropped key information.
  • Manual review before payout if risk is elevated.

Proof checklist

Good proof prevents delays.

Support can only review what is visible in the ticket. Keep proof clean, readable and connected to the payment you are asking ByteSwap to process.

Amount visibleThe screenshot or receipt should show the exact amount sent.
Recipient visibleShow the recipient, wallet, transfer reference or ticket-required identifier.
Status visibleCompleted, pending or confirmed status should be clear when possible.
No editsDo not crop or edit proof in a way that removes important context.

Speed expectations

Some methods are faster because they are easier to verify.

Speed depends on method, proof quality, ticket volume, staff availability and whether the payment needs extra review.

Fastest when clear

PayPal / digital wallet

Usually fast after visible proof and correct ticket instructions, but risk checks can still apply.

Depends on network

Crypto

Blockchain confirmations and TXID verification can affect timing. Wrong network or address creates major delays.

Can be slower

Bank transfer

Bank status, region and settlement visibility can make this slower than instant payment methods.

Most review-heavy

Gift-card style methods

Only when offered. Usually needs stronger proof and manual review before the order can continue.

Method safety

If the payment instruction is not inside your official ticket, do not send.

ByteSwap staff will not ask for passwords, seed phrases, private keys or unrelated account access. If somebody sends payment instructions through random DMs, stop and ask support in the official server.