Exchanger rules

01Approval and agreement

• Staff reviews your application first, then runs /approve_applicant in your private application ticket. Read these rules and the Terms of Service before pressing I agree. Agreement starts setup only when the bot has recorded staff approval.
• Deposit instructions appear in that ticket with a DM copy. A DM check tests delivery; it is not approval, identity verification or confirmation of a deposit. The approval card links the full rules; no separate rules command is needed.
• Pressing I disagree stops that application step. Ask staff about unclear requirements before agreeing or funding.

02Deposit, activation and available funds

• The standard setup requires $50 total in supported LTC, native SOL or USDC on Solana within seven days. Follow your personal bot instructions for the actual requirement, deadline, asset and address; an authorized exemption may apply.
• This is working wallet funding, not an application fee or insurance premium. Activation waits for the required confirmed value. Pending transfers are not a reason to send again; use the deposit-progress control.
• Available funds are affected by prices, active reservations, pending transactions and owed server charges. Your nominal deposit is not a guaranteed claim ceiling. A released reservation is not a refund of funds already paid out.
• Withdraw only available funds using the supported controls. Never evade a reservation or use another account to bypass a restriction. Ask staff to review an unavailable balance rather than making a duplicate transfer.

03Get ready before claiming

Claim manually through NinjaSwap controls. Autoclaimers, self-bots, scripts and tools that race other exchangers for tickets are prohibited. Ordinary bot notifications are allowed.

• Read /guide, choose the payment roles you actually support, check your balance and secure your account. Roles control matching; they do not replace eligibility or capacity checks.
• Use /queue to find orders and your active tickets. Read the full route, amount, expected profit and fees before claiming. Take only work you have the funds, payment access and time to complete.
• After claiming, use a saved payment account or explicitly share details in the ticket. Share the complete terms before asking the client to accept. Never leave a client to guess the destination.

04Communication and response

• Keep trade instructions, agreements and evidence in the ticket. Do not DM a client first, divert them to another server or settle a NinjaSwap trade off-ticket.
• Respond promptly. If you cannot respond within ten minutes and no money has moved, unclaim through the bot when permitted. Once payment has been sent or a dispute exists, involve staff instead of abandoning or resetting the trade.
• Be clear and respectful. Do not threaten, pressure clients to pay twice, conceal delays or ask for a positive vouch to release funds.
• Do not introduce an outside middleman without staff approval recorded in the ticket. Never redirect funds to an unapproved intermediary.
• Do not instruct clients to bypass bot checks or pay against closed or reassigned ticket instructions.

05Quotes and payment requirements

Do not outsource a claimed trade to another exchange server or give an outside exchanger the client’s payment details. Complete it using your own supported accounts and NinjaSwap’s approved payout flow.

• State the correct send and receive amounts, assets, networks, supported funding source and every fee before acceptance. Do not hide a markup, change the deal after payment or deduct an undisclosed penalty.
• Check both sides of the route and the destination. Accepted details are locked by the trade flow; ask staff to resolve a necessary correction instead of editing chat to contradict an accepted agreement.
• Use payment methods permitted for the transaction by the provider. Do not ask clients to mislabel a purchase, lie about its purpose, evade restrictions or give up legitimate dispute rights.
• If your quote or instructions are wrong, stop and tell the client and staff. Do not silently reduce payout or make the client fund your error.

06Verify payment and complete honestly

For gift cards, preserve a continuous recording of the balance check and redemption through the result. Keep codes and unrelated account information private; share relevant evidence only with authorized staff when needed.

• Confirm receipt in your own payment account or the correct blockchain record. Verify amount, currency, sender/reference and settled status. A screenshot, email, app notification or client confirmation is not enough by itself.
• Keep pending payments pending. Use the normal payment confirmation and payout controls only after the required checks. Never mark a trade complete to inflate volume, avoid a dispute or unlock funds.
• Verify the payout destination and network before approval. Record the transaction reference. Do not retry an uncertain payout until its existing transaction has been checked.
• Do not trade with yourself, collude to create activity or manufacture vouches, referrals or rewards.

07Server fees and wallet security

• The configured server share is charged against eligible exchanger profit; it is separate from the customer quote. Check the profit breakdown and current settings. A fee reservation or accrued amount is not proof of collection.
• Owed charges can reduce available funds while collection is pending. Do not clear debt manually or move funds to evade collection. Report an apparent duplicate or incorrect charge with the trade reference.
• Network costs and sponsorship depend on the supported route and current settings. Never promise that every transfer is free. Follow the wallet instructions rather than sending to an address supplied by another person.
• Keep withdrawal protection enabled, review approved addresses and never share seeds, private keys, passwords or 2FA codes. Staff must not request these secrets. Report compromise immediately.

08Disputes, evidence and client privacy

• Report reversals, wrong destinations, missing funds and suspicious activity promptly through staff support. Preserve receipts and hashes without exposing unrelated customer data. Do not retaliate or accuse a person before evidence is reviewed.
• A chargeback report is not an automatic reimbursement. Staff must establish the transaction, loss and any funds available before describing a remedy. Distinguish fraud from a legitimate dispute or provider-initiated reversal.
• Request only relevant evidence. Never ask for passwords, login sessions, full card details or recovery phrases. Redact unrelated information and keep evidence inside authorized support channels.
• Do not publish client identities or payment details as punishment or make unsupported claims about deposits, security or guaranteed compensation.
• If completion is impossible, involve staff to arrange any refund. Preserve the payment evidence and record the refund transaction before closing.

09Suspension, leaving and unresolved balances

• Rule violations can lead to restricted claiming, suspension or removal. Staff should explain the issue and review relevant evidence. You can request review through official support.
• Removing a role does not prove that a debt was collected or authorize automatic confiscation of all funds. Outstanding trades, charges and disputes must be accounted for before any balance adjustment or release.
• To leave, stop taking new work, resolve current tickets and contact staff. Use normal withdrawal controls for available funds; ask for an explanation of any remaining restriction. Do not abandon a paid ticket.
• Do not create another account to evade a suspension. Keep records needed to resolve existing transactions.

10Rules, guides and help commands

• These rules describe your obligations. /guide explains the steps and controls. The accepted terms inside each trade specify that client’s particular payment agreement.
• /explain deposit is an optional explanation of working funds, reservations and activation. It does not approve an applicant, create a wallet, request another deposit or replace the personal funding card.
• Other /explain topics are reusable support replies. Use them when someone needs clarification, not as mandatory extra steps or repeated messages. Read the full rules before accepting in Discord.