Rules for sending USD/EUR from a card
-
- BTC2PAY service accepts fiat payments in EUR and USD only from users with cards following countries:
For Visa: Albania, Andorra, Argentina, Armenia, Australia, Austria, Azerbaijan, Belgium, Bosnia and Herzegovina, Brazil, Bulgaria, Chile, Croatia, Cyprus, Czech Republic, Denmark, Egypt, Estonia, Finland, France, Georgia, Germany, Gibraltar, Greece, Greenland, Hungary, Iceland, Indonesia, Israel, Italy, Jordan, Kazakhstan, Kenya, Kenya, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malaysia, Maldives, Malta, Mexico, Moldova, Monaco, Montenegro, Namibia, Netherlands, New Zealand, Norway, Philippines, Poland, Portugal, Puerto Rico, Qatar, Ireland, Serbia, Romania, Samoa, San Marino, Singapore, Slovakia, Slovenia, South Africa, Spain, Sri Lanka, Sweden, Tajikistan, Tanzania, Thailand, Turkmenistan, Ukraine, United Arab Emirates, United Kingdom, Uruguay, Uzbekistan, Zambia..
For Mastercard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Liechtenstein, Norway, UK.
- It is mandatory for users to pass identity verification.
- If the systеm does not accept funds during payment of a repeated application – the program of fraud prevention has been triggered. In this case the user should go through the procedure card verification. The data obtained during such verification will be transmitted to the payment systеm.
Rules for sending KZT from a card
- BTC2PAY service accepts payments only from the cards of individuals. In case of payment from IE, LLC, JSC, funds will be irretrievably lost.
- It is mandatory for users to pass bank card verification.
- Payment details are active strictly 30 minutes from the moment the application is created.
- If the amount of KZT to be sent with tiyns, it is necessary to round it down to a whole number.
- Be prepared to provide a screenshot/receipt of the transfer if requested by the operator.
Rules for sending UAH from a card
- BTC2PAY service accepts payments only from individuals’ cards.
- Payment details are active strictly 15 minutes from the time of issuance. For payments made after this time (unless otherwise specified by the operator), in some situations, if it is not possible to restore access to the account, the funds may be irretrievably lost. If it is possible to restore access to the account, a fee of 10% of the amount credited will be charged for this service.
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, sender and recipient.
Rules for sending UAH from a bank account
- Before creating a request, write the name of the legal entity or individual from whose account the payment will be made in the chat. Agree on the possibility to specify the note you need.
- Payment details are active strictly 45 minutes from the time of their issuance.
- Crediting can take anywhere from 1 hour to several business days (depending on what day of the week and time of posting).
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, sender and recipient.
Rules for sending UZS from a card
- BTC2PAY service accepts payments only from individuals’ cards.
- Payment details are active strictly 20 minutes from the time they are issued. For payments made after this time (unless otherwise specified by the operator), in some situations, if it is not possible to restore access to the account, the funds may be irretrievably lost. If it is possible to restore the account, a 10% commission of the amount credited will be charged for this service.
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, sender and recipient.
- In rare cases, be prepared to undergo a procedure card verification at the request of the operator. The data obtained in the course of such verification will be transmitted to the payment systеm.
Rules for sending WISE USD/EUR/GBP
- BTC2PAY service accepts payments only from verified WISE accounts. If you pay from a bank account, the funds will be irretrievably lost.
- Payment details are active strictly 20 minutes from the date of their issuance. If you pay after this time (unless otherwise specified by the operator), the assets can only be unlocked after two months and will be charged a 10% fee of the amount credited. In some situations, if it is impossible to unlock the account, the funds may be irretrievably lost.
- The Operator can provide two types of details – either the e-mail address associated with the account in the WISE systеm or a link to the payment. This information is duplicated to the User’s e-mail address.
- Be prepared to provide a screenshot/receipt of the transfer if requested by the operator.
Rules for sending EUR from a bank account
- Before creating a request, check in the chat room whether the direction of exchange works, write in the chat room the name of the legal entity or individual from whose account the payment will be made. Agree on the possibility to specify the note you need.
- Payment details are active strictly 30 minutes from the time of their issuance.
- The payment details can be either Revolut or another bank that supports SEPA transfer.
- The Operator can provide two types of details – either @Revtag or IBAN and recipient’s full name. This information is duplicated to the User’s e-mail.
- Crediting can take anywhere from 1 hour to several business days (depending on what day of the week and time of posting).
- Fixing the rate after the payment is credited, not at the time of shipment.
- The payment may get to the verification of the payment systеm, in this case, it is necessary to wait for its completion.
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, sender and recipient.
Rules for sending Payoneer USD
- BTC2PAY service accepts payments from verified Payoneer accounts only.
- The operator provides details in the form of the email address associated with the Payoneer account and Description to be specified.
- Payment details are active strictly 20 minutes from the moment of their issuance. If payment is made after this time (unless otherwise specified by the operator), in some situations, if it is not possible to restore access to the account, the funds may be irretrievably lost. If account recovery is possible, a 10% commission of the amount credited will be charged for this service.
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, recipient and Transaction Number.
Rules for sending Skrill USD
- BTC2PAY service accepts payments from Skrill accounts only.
- The Operator will provide details in the form of the email address associated with the Skrill account and a Description to be specified.
- Payment details are active for 15 minutes from the moment of their issuance. If payment is made after this time (unless otherwise specified by the operator), in some situations, if it is not possible to restore access to the account, the funds may be irretrievably lost. If account recovery is possible, a 10% commission of the amount credited will be charged for this service.
- After successfully sending funds, you need to send a screenshot/receipt of the transfer to chat, where you can see the amount, recipient and Transaction Number.
Rules for sending cryptocurrency
- Correct network (blockchain). A cryptocurrency network is a virtual payment network where payments are extracted and received or sent. For example, BEP2, BEP20, ERC20, OMNI, TRC20, POLYGON, SOLANA et al. Before sending a crypto asset, you must be sure that you are sending it by the network that our exchange supports. Otherwise, your coins may be lost. If we accept assets from multiple networks, the actual network is indicated in brackets next to the Ticker of the coin.
- Presence/absence memo. This is an identifier that must be specified along with the address for transactions to take place. Not all cryptocurrencies use this technology, but in the case of those that do, without fulfilling this condition, the cryptocurrency will simply not reach the recipient.
Destination Tag is a unique identifier (ID) of an account on a digital asset exchange or service. It is used to indicate the specific user to whom the coins are being transferred. Entering the tag will be required when sending cryptocurrency in some blockchains (BEP-2, XLM, XRP, ATOM, Terra, EOS and others). Memo may be called differently in individual networks — Destination Tag, Message. - Quantity network confirmations, required to credit the cryptoasset. A confirmed transaction means that it is included in a block and therefore in the blockchain. For example, if you send one bitcoin to someone, that transaction will remain “unconfirmed” until the next block is created (in which case it will have one confirmation).
The number of “network confirmations” required varies from blockchain to blockchain. Also, each exchange independently sets the number of confirmations required for coins to be credited to the balance. - The amount is not less than minimum deposit. The exchange sets a minimum amount of cryptoasset that it can accept on its wallets. If you send an amount less than this, there is no technical possibility to credit your coins and they are will be lost. To avoid this, our Service has taken into account all minimum deposit amounts when creating an Order. Therefore, you do not need to send the exact amount of the Order.
- Non-traditional methods of sending. The exchange, to whose wallets we accept cryptoassets, does not support such non-traditional methods of sending: cross-chain transfer, smart contract, batch-all transactions, etc. If you send a transaction using these methods, your coins are will be lost.
| Cryptoactiv | Network translation |
Availability of a memo | Number of confirmations | Minimum deposit amount |
|---|---|---|---|---|
| Tether – USDT (TRC20) | TRC20 | 20 | 5 | |
| Tether – USDT (ERC20) | ERC20 | 32 | 30 | |
| Tether – USDT (BEP20) | BEP20 | 40 | 5 | |
| Tether EUR – EURT | ERC20 | 32 | 15 | |
| Tether Gold – XAUT | ERC20 | 32 | 0.0055 | |
| Tether – USDT | OPTIMISM | 150 | 0,00000001 | |
| Tether – USDT | AVALANCHE C-CHAIN | 30 | 0,00000001 | |
| Tether – USDT | ARBITRUM | 12 | 0,00000001 | |
| Bitcoin – BTC | BTC | 2 | 0.0005 | |
| Bitcoin Cash – BCH | BCH | 10 | 0.015 | |
| Ethereum – ETH | ERC20 | 32 | 0.01 | |
| Ethereum Classic – ETC | Ethereum Classic | 300 | 0.4 | |
| Litecoin – LTC | LTC | 10 | 0.01 | |
| Ripple – XRP | XRP | + | 1 | 1 |
| Monero – XMR | Monero | 10 | 0.01 | |
| Dogecoin – DOGE | Dogecoin | 15 | 65 | |
| Fantom – FTM | FANTOM | 1000 | 20 | |
| Polygon – MATIC (Polygon) | Polygon | 500 | 10 | |
| Polygon – MATIC (ERC20) | ERC20 | 32 | 20 | |
| Dash – DASH | Dash | 10 | 0.025 | |
| Zcash – ZEC | Zcash | 22 | 0.09 | |
| USD Coin – USDC | ERC20 | 32 | 30 | |
| TrueUSD – TUSD | ERC20 | 32 | 30 | |
| Pax Dollar – USDP | ERC20 | 32 | 30 | |
| Dai – DAI | ERC20 | 32 | 30 | |
| NEM – XEM | NEM | + | 10 | 130 |
| NEO – NEO | NEP5 | 10 | 1 | |
| Eos – EOS | EOS | + | 330 | 1 |
| Cardano – ADA | Cardano | 40 | 8 | |
| Stellar – XLM | Stellar Lumens | + | 1 | 10 |
| Tron – TRX | TRC20 | 20 | 50 | |
| Waves – WAVES | Waves | 90 | 1 | |
| OmiseGO – OMG | ERC20 | 32 | 7 | |
| 0x – ZRX | ERC20 | 32 | 45 | |
| Binance Coin – BNB (BEP2) | BEP2 | + | 40 | 0.01 |
| Binance Coin – BNB (BEP20) | BEP20 | 40 | 0.01 | |
| ICON – ICX | ICON | 870 | 20 | |
| Basic Attention Token – BAT | ERC20 | 32 | 25 | |
| ChainLink Token – LINK | ERC20 | 32 | 1.5 | |
| Tezos – XTZ | Tezos | 35 | 5 | |
| Polkadot – DOT | DOT | 50 | 1.03 | |
| Solana – SOL | Solana | 500 | 0.13 | |
| VeChain – VET | VeChain | 210 | 250 | |
| Sushi – SUSHI | ERC20 | 32 | 10 | |
| Sushi – SUSHI | BEP20 | 40 | 3.5 | |
| Shiba Inu – SHIB | ERC20 | 32 | 1000000 | |
| Maker – MKR | ERC20 | 32 | 0.014 | |
| Avalanche – AVAX (CCHAIN) | CCHAIN | 1 | 0.07 | |
| yearn.finance – YFI | ERC20 | 32 | 0.0017 | |
| Decentraland – MANA | ERC20 | 32 | 10 | |
| NEAR Protocol – NEAR | NEAR | 3 | 0.9 | |
| Pepe – PEPE | ERC20 | 32 | 3100000 | |
| Fetch.ai – FET | ERC20 | 32 | 20 | |
| Sui – SUI | SUI | 1 | 5 | |
| Arbitrum – ARB | ARBITRUM | 600 | 3.5 | |
| Aptos – APT | APT | 5000 | 0.5 | |
| Wojak — WOJAK | ERC20 | 32 | 34000 | |
| WhiteBIT Token — WBT | TRC20 | 20 | 1.5 | |
| WhiteBIT Token — WBT | ERC20 | 32 | 1.5 | |
| Optimism — OP | OPTIMISM | 1400 | 3.25 | |
| Tenet — TENET | ERC20 | 32 | ||
| Floki — FLOKI | ERC20 | 32 | 280000 | |
| PancakeSwap — CAKE | BEP20 | 40 | 2 | |
| Curve DAO Token — CRV | ERC20 | 32 | 12 | |
| 1inch — 1INCH | ERC20 | 32 | 15 |
