# Rapira: Complete Service Overview > Rapira is a cryptocurrency exchange for spot and P2P trading, deposits and withdrawals, crypto wallet services, AML checks, and API integrations. This document provides an expanded, LLM-friendly overview of the public product information available on rapira.net. ## About This Document This file summarizes Rapira features and operating guidance in one place. It is intended for language models, search systems, and users who need a text-first description of the service without relying on the JavaScript application. The English website uses URLs without a locale prefix. Some account actions, including wallet operations, order management, verification, security settings, and API-key management, require authentication. Availability, supported assets, payment methods, fees, limits, and processing times may change. The live application and current legal documents remain the authoritative sources. Users should not provide passwords, two-factor authentication codes, API private keys, or seed phrases in a support request. They should verify that they are visiting `https://rapira.net` before entering credentials. ## Platform Overview Rapira combines the following services: - Spot trading for buying and selling supported cryptocurrencies through market and limit orders. - A P2P marketplace where users trade cryptocurrency directly using available payment methods. - A wallet for cryptocurrency and supported fiat deposits and withdrawals. - Address books for managing deposit and withdrawal addresses. - rCode transfers between Rapira users where the method is available. - AML checks for cryptocurrency addresses and transaction hashes. - API access for market data, trading, balances, withdrawals, AML, P2P, and crypto-processing integrations, subject to the permissions granted to an API key. - A support center with product FAQs, security guidance, and legal documents. The public home page provides a product overview. Trading, account, wallet, and API actions may require registration, identity verification, two-factor authentication, or approval from support, depending on the feature. ## Accounts, Verification, and Security An account can be created with an email address, password, and email confirmation code. Some payment methods, withdrawals, API features, and higher-risk operations require identity verification. Account verification is normally automated. A national passport or identity card may be requested. Some cases can require manual review. The exact requirements shown during the verification flow take precedence over this summary. Rapira supports Google Authenticator-based two-factor authentication. Two-factor authentication is used to protect security-sensitive actions such as API-key management and withdrawals. Users who lose access to their authenticator should contact official support and complete the requested account-recovery checks. Security guidance: - Confirm the `rapira.net` domain before entering credentials. - Do not share passwords, two-factor authentication codes, API private keys, or other secrets. - Treat unexpected messages, requests to transfer funds, and requests to move a P2P conversation outside Rapira as suspicious. - Contact official support when an email, SMS, or account action appears suspicious. - Use IP restrictions and the minimum required permissions for API keys. ## Spot Trading The Spot Trading interface provides public market information and authenticated order management. Available pairs include cryptocurrency-to-stablecoin and cryptocurrency-to-cryptocurrency markets. The current list of pairs in the trading interface is authoritative. Supported order types include: - Market orders, which execute against available orders in the order book. - Limit orders, which remain open until matched, canceled, or otherwise completed according to platform rules. The trading interface includes an order book, recent trades, charts, drawing and analysis tools, open orders, and order history. Users can also review exchange operations in their account history. Trading fees depend on the market, pair, order conditions, and the user's applicable fee level. Current values must be checked in the trading interface and the Fees and Limits page before placing an order. Public resources: - [Spot Trading](https://rapira.net/exchange): Public market and trading interface. - [Spot Trading FAQ](https://rapira.net/support/faq/exchange): Supported order types, history, fees, and support guidance. - [Fees and Limits](https://rapira.net/commissions-and-limits): Current trading, deposit, and withdrawal conditions. ## P2P Trading The P2P marketplace lets users buy and sell cryptocurrency directly through published offers. Offers specify the asset, fiat currency, payment method, limits, rate, and payment window. When a P2P order is opened, the cryptocurrency involved is frozen on the seller's Rapira balance until the order is completed, canceled, or resolved through arbitration. Sellers can therefore offer only cryptocurrency available in their accounts. Core safety rules: - Review the counterparty's completion rate, reviews, and previous trading activity before opening an order. - Keep all communication in the Rapira order chat. - Do not share unnecessary contact information or move the transaction to an external messenger. - Do not mark an order as paid until the payment has actually been sent. - Verify receipt of funds before releasing cryptocurrency. - Do not unilaterally change the rate, payment method, commission, or other order terms after an order is opened. - Use arbitration when the parties cannot resolve a payment or order dispute. Payment details are provided through the order flow and chat. If the payment deadline expires, users should not send funds for a canceled order. If payment has already been made and a problem occurs, the user should keep the payment confirmation, order number, recipient details, amount, and payment time for support or arbitration. Rapira may label some P2P participants or offers to communicate additional context, such as intermediary payment details, split payments, or exchanger activity. These labels call for additional diligence and do not replace the user's responsibility to verify payment. Public resources: - [P2P Marketplace](https://rapira.net/p2p/BUY): Public P2P offers. - [P2P FAQ](https://rapira.net/support/faq/p2p): Orders, payments, platform rules, fraud protection, and arbitration. ## Wallet, Deposits, and Withdrawals The authenticated wallet groups balances, deposits, withdrawals, address management, and operation history. Available currencies, networks, and payment methods are loaded dynamically for the user's account. ### Cryptocurrency Deposits A typical cryptocurrency deposit flow is: 1. Open the wallet deposit section. 2. Select the cryptocurrency and network. 3. Select or create a deposit address. 4. Copy the address and any required memo or tag. 5. Confirm that the token contract, network, address, and memo match the values shown by Rapira. 6. Send an amount that meets the displayed minimum. 7. Wait for the required blockchain confirmations and any applicable AML checks. Important deposit warnings: - Sending through an unsupported network can result in loss of funds or require a manual recovery review. - A missing or incorrect memo or tag can prevent correct crediting. - A deposit below the displayed minimum may not be credited or returned. - The token contract must match the contract displayed by Rapira. - A temporary deposit address can be replaced, so the address must be checked before every transfer. - Required confirmations are shown in the deposit interface and vary by network. ### Fiat and Other Deposits Depending on current availability and verification status, deposit methods can include cash offices, bank-related methods, cards, P2P, or rCode. Each method can have its own identity requirements, minimum and maximum amount, fee, operating hours, and processing time. The sender's details may need to match the verified Rapira account. Users must follow the payment instructions displayed for the selected method and check the live conditions before sending funds. ### Cryptocurrency Withdrawals A typical cryptocurrency withdrawal flow is: 1. Open the wallet withdrawal section. 2. Select the cryptocurrency and network. 3. Enter or select a saved withdrawal address and any required memo. 4. Enter an amount within the displayed minimum and remaining daily limit. 5. Review the network fee and total amount. 6. Confirm the withdrawal using the required security method, including two-factor authentication or address confirmation when requested. Withdrawals can be rejected when an address presents elevated AML risk or when a token or network is temporarily unavailable. Once a withdrawal has been sent to the blockchain, it cannot be canceled. A pending withdrawal may only be cancelable before network submission. ### Address Management and History The wallet includes separate records for deposit and withdrawal addresses. Users can create and name deposit addresses, choose a default address where supported, and save withdrawal addresses. Operation history contains deposits, withdrawals, exchange operations, P2P operations, and rCode operations. Public resources: - [Deposit and Withdrawal FAQ](https://rapira.net/support/faq/deposit-withdrawal): Wallet procedures, address management, confirmations, histories, and troubleshooting. - [Fees and Limits](https://rapira.net/commissions-and-limits): Current methods, fees, minimums, maximums, and availability. ## Fees and Limits Fees and limits are dynamic and can depend on the asset, network, market, payment method, account level, verification status, location, or current service availability. The Fees and Limits page is the source of truth for: - Spot trading fees by pair or fee level. - Cryptocurrency deposit minimums and required network conditions. - Cryptocurrency withdrawal minimums and network fees. - Cash office deposit and withdrawal conditions. - Card, bank, and other supported fiat methods. - Daily or method-specific limits. - Temporarily suspended payment methods, assets, or networks. Agents should not quote a fee or limit from cached information when a user is about to transact. They should direct the user to the live [Fees and Limits](https://rapira.net/commissions-and-limits) page and the confirmation screen for the specific operation. ## Rapira AML Rapira AML analyzes cryptocurrency addresses and transaction hashes to identify links with known blockchain sources and help users evaluate counterparty and transaction risk. An address check examines transactions and related activity associated with an address. A transaction-hash check evaluates risk information relevant to the sender and recipient of a specific transfer. The service groups identified sources into categories such as dangerous, suspicious, and trusted. Results can include source exposure percentages and an aggregate risk assessment. Users can save reports and repeat checks because an address's activity and risk profile can change over time. Supported checks described by the product include assets on Bitcoin, Ethereum/ERC-20, Tron/TRC-20, and BNB Smart Chain/BEP-20 networks. The live AML interface is authoritative for the exact list of supported assets and networks. An AML result is a risk-assessment aid, not a guarantee that a transaction is legal, safe, accepted by another service, or free from future compliance review. Users should apply their own risk model and follow applicable law and platform policies. Public resources: - [Rapira AML](https://rapira.net/aml): AML product overview and access point. - [AML FAQ](https://rapira.net/support/faq/aml): Check types, supported networks, risk sources, reports, and interpretation. - [AML/KYC Policy](https://rapira.net/support/docs/aml-kyc-policy): Compliance and verification policy. ## API and Integrations Rapira provides API documentation for market data, balances, order management, payouts, AML, P2P, rCode, and crypto-processing features. The public API base URL is `https://api.rapira.net`. API access can require an authenticated and verified Rapira account, support approval, two-factor authentication, and creation of an API key in account settings. The private key is displayed only once when created and is not stored by Rapira for later display, so it must be stored securely by the user. Authentication uses JWT. API-key settings can include: - A key name. - JWT time to live. - Access levels such as read-only data, trading, withdrawals, AML, or P2P. - An allowlist of trusted static IP addresses. Use only the permissions required by the integration. A zero IP mask means that IP filtering is not restricting access and is less secure than an explicit allowlist. Operational guidance: - Respect the rate limits and Web Application Firewall rules described in the API documentation. - An HTTP 403 can indicate a temporary WAF block after a rate-limit or request-policy violation. - Keep system time synchronized when creating signed requests. - WebSocket clients must answer server pings with correctly formatted pong messages; inactive connections can be closed. - Do not enter Rapira API or private keys into an untrusted third-party service. - Currency codes are available from the public token endpoint and API documentation. - API-generated addresses remain associated with the account that created them. Public resources: - [API Documentation](https://rapira.apidog.io/): Authentication, endpoints, schemas, and integration guidance. - [API FAQ](https://rapira.net/support/faq/api): API-key creation, permissions, security, IP restrictions, and troubleshooting. - [Public Token Metadata](https://api.rapira.net/open/token): Current token and API-format metadata. ## Support The Support Center organizes guidance for account security, deposits and withdrawals, spot trading, P2P, AML, referrals, API keys, the Telegram bot, financial levels, offices, and bank transfers. Users can contact support through the website's online chat, the official Rapira Support Bot on Telegram, or the support email shown by the application. For transaction or P2P cases, users should provide the relevant order or transaction identifier and non-sensitive evidence. Secrets such as passwords, two-factor authentication codes, and private API keys must not be included. Public resources: - [Support Center](https://rapira.net/support): Main support index. - [Account and Security FAQ](https://rapira.net/support/faq/account-security): Registration, verification, two-factor authentication, recovery, and phishing guidance. - [Deposit and Withdrawal FAQ](https://rapira.net/support/faq/deposit-withdrawal): Funding and withdrawal procedures. - [Spot Trading FAQ](https://rapira.net/support/faq/exchange): Trading guidance. - [P2P FAQ](https://rapira.net/support/faq/p2p): P2P guidance and arbitration. - [AML FAQ](https://rapira.net/support/faq/aml): AML check guidance. - [API FAQ](https://rapira.net/support/faq/api): API access and troubleshooting. ## Legal and Compliance Use of Rapira is governed by the current legal documents published on the website. These documents take precedence over summaries in this file. The User Agreement covers important warnings, prohibited jurisdictions, user risk acknowledgments, representations and warranties, acceptable use, prohibited activities, service restriction or termination, identification and verification, transaction cancellation and refunds, deposits and withdrawals, fees, compliance with law, liability, dispute resolution, and contact information. The Privacy Policy describes how personal data and user information are collected, stored, processed, protected, and shared, including processing for AML, counter-terrorist financing, KYC, and customer due-diligence purposes. The AML/KYC Policy describes verification, risk assessment, third-party involvement, company rights when applying compliance controls, policy changes, and user obligations. The Cookie Policy explains the website's use of first-party and third-party cookies and available controls. Public resources: - [User Agreement](https://rapira.net/support/docs/user-agreement): Contractual terms for Rapira services. - [Privacy Policy](https://rapira.net/support/docs/privacypolicy): Personal-data processing and protection. - [AML/KYC Policy](https://rapira.net/support/docs/aml-kyc-policy): Compliance, verification, and risk controls. - [Cookie Policy](https://rapira.net/support/docs/cookiepolicy): Website cookie practices. ## Quick Routing Guide - For a current market or pair, use [Spot Trading](https://rapira.net/exchange). - For a P2P offer, use the [P2P Marketplace](https://rapira.net/p2p/BUY). - For a current fee, limit, payment method, or network condition, use [Fees and Limits](https://rapira.net/commissions-and-limits). - For wallet procedures, use the [Deposit and Withdrawal FAQ](https://rapira.net/support/faq/deposit-withdrawal). - For address or transaction risk analysis, use [Rapira AML](https://rapira.net/aml). - For API implementation details, use the [API Documentation](https://rapira.apidog.io/). - For account, transaction, or dispute assistance, use the [Support Center](https://rapira.net/support). - For contractual or compliance questions, use the current legal documents linked above. ## Related LLM Resource - [Rapira llms.txt](https://rapira.net/llms.txt): Concise project overview and curated resource index.