Last updated 8 October 2026
In short. We don't want TeleCard used for money laundering, fraud or sanctions evasion. So deposit and withdrawal addresses are screened against a sanctions list, suspicious operations go to manual review, and merchants verify their identity. Regular wallet users don't need to provide documents to sign up.
1. Why this policy exists
1.1. This policy describes the measures the operator of TeleCard ("we", "us" or the "Operator") uses to reduce the risk that the Service is used for unlawful purposes: laundering proceeds of crime, financing terrorism, fraud and evading sanctions.
1.2. We describe how this works in practice. The policy is part of the Terms of Use; how we handle the data collected during checks is covered in the Privacy Policy.
1.3. The measures match the level of risk: most operations go through automatically, and attention goes where there are signs of risk.
2. Checking deposits
2.1. The source of a deposit is screened against the OFAC SDN sanctions list, which is published by the US Treasury. For Bitcoin, every input address of the transfer is checked.
2.2. If the source matches the list, the transfer has no sender address, or it has an unusually large number of inputs, the deposit isn't credited straight away and goes to manual review. If screening is temporarily unavailable, the transfer waits and then also goes to manual review.
2.3. Funds are credited only after the network has confirmed the transfer. A deposit that is under review is decided by a person on our team.
3. Checking withdrawals
3.1. The destination address is screened against the same list before anything is sent.
3.2. A withdrawal goes through automatically when the amount is within the auto-approval threshold (by default 500 USDT in equivalent), the address passes screening and the daily limit (by default 5,000 USDT) hasn't been reached. All other withdrawals are reviewed by a person.
3.3. If the destination address is on the sanctions list, the withdrawal isn't sent automatically and our team gets an urgent alert. If screening can't be completed, the withdrawal also goes to manual review.
3.4. We check our own addresses too: hot wallets and deposit addresses that hold a balance are compared against the USDT blocklist maintained by its issuer, Tether.
4. How sanctions screening works
4.1. The OFAC SDN list is downloaded to our servers and refreshed roughly every 12 hours. Screening runs on our own servers, so customer addresses aren't sent to third parties for this purpose.
4.2. If the list hasn't been loaded or hasn't been updated for too long, the rule "not on the list, so clear" doesn't apply: such operations go to manual review. A match with the list always counts.
4.3. This check covers sanctions only, and only addresses. It doesn't assess the whole chain of transfers, and it doesn't guarantee that funds were obtained lawfully. If we connect third-party address-analysis services, we'll update this policy.
5. Verifying merchants (KYC)
5.1. Merchants complete a five-step check:
- A questionnaire: full name, date of birth, citizenship, country of residence and phone number.
- A bank account: the details of the account the merchant uses to receive payments and to pay orders.
- Documents: an identity document, a selfie with the document and an account statement.
- Collateral for the chosen tier.
- A review of the application by our team.
5.2. Every application is reviewed by a person. We can approve it, send it back for corrections with the reasons, or reject it, in which case the collateral is returned.
5.3. Orders are paid only from a verified account that belongs to the merchant. The name on the account has to match the application.
5.4. The document number is stored encrypted. An irreversible hash of it lets the system spot repeat applications, so that one person can't apply several times.
5.5. Only staff with a special permission can see the documents and application data, and every access is logged. Retention periods are in the Privacy Policy.
6. Monitoring payments and merchants
6.1. Limits. Both a single payment and the monthly total have limits (by default from ₽10 to ₽100,000 per payment and ₽300,000 per month). You can have only one active order at a time.
6.2. Receipt checks. For each paid order the merchant attaches the bank's receipt. The system checks that the payment was made from the merchant's own account, that the amount and time match the order, and that the receipt hasn't been used before. Unclear cases are reviewed by a person.
6.3. Pauses. When the risk is high, a merchant is paused automatically, with no new orders, until our team decides, and earnings from the affected orders stay on hold. An open dispute likewise holds back earnings withdrawals and taking new orders.
6.4. Collateral sets the maximum order size and covers disputes the merchant loses.
7. Regular users
7.1. You don't need documents to create a wallet: you sign in with Telegram. Right now the Service doesn't ask regular users for documents at sign-up.
7.2. If an operation is sent for manual review, we may ask you to explain it and to confirm some details. You can reply in the support chat.
8. What can happen
8.1. After a check, an operation may be completed once it's cleared, delayed while the check runs, or declined. An account or individual features may be paused or limited.
8.2. We try to explain our reasons. In some cases, though, the law doesn't allow us to disclose the details of a check or to return funds, and we follow the law.
8.3. Any automated check can get it wrong. If you think an operation was held unnecessarily, write to support and include the operation number.
9. What we expect from you
9.1. Use the Service lawfully, with your own funds and in your own name.
9.2. Merchants give accurate information and receive payments only to their own accounts.
9.3. Don't split payments to get around limits and checks, and don't try to hide the source of funds.
9.4. If you notice suspicious activity, tell support.
10. Cooperation with authorities and record keeping
10.1. When a competent authority makes a lawful request, we disclose information as far as the law requires.
10.2. Screening results and operation records are kept together with the history of the operation for as long as the law and the security of the Service require.
11. Changes to this policy
11.1. We may update this policy. The new version is published on this page with a new date.
11.2. This version applies from 8 October 2026.
12. Contact
Questions about checks and operations under review: the support chat in the app (Profile, then Support) and the bot @itelecard_bot.