Bybit P2P Escrow Fraud: 1,500,000 AMD Held (Ticket #27612502 / UID 213046727)

[Besmirb]

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

Initial P2P support mishandled the transaction where the buyer failed to complete the Idram transfer. However, after escalating to Bybit Security & Compliance (Agent Carmen) and filing official complaints with regulators (AFSA Ref: 2a6d8570-e55d-4aaa-8b48-f1a9ead523bb & VARA), the compliance team completed a thorough review and released the held escrow.

Thank you to the Bybit Compliance team for correctly reviewing the payment proofs and resolving this ticket.

Detailed Case Report:

On Bybit P2P, I opened an order for 1,500,000 AMD via Idram payment method.

The buyer marked the order as paid without making any actual payment. Initial P2P support failed to resolve the issue properly and frozen the escrow.

Actions taken:
1. Escalated directly to Bybit Compliance & Security (Ticket #27612502).
2. Filed official regulatory complaints with AFSA (Astana Financial Services Authority) - Ref: 2a6d8570-e55d-4aaa-8b48-f1a9ead523bb and VARA (Dubai).
3. Submitted payment proof from Idram and official account statements.

The case is currently under final priority review by Bybit Compliance. I will post a final update here as soon as the escrow funds are fully unfrozen.

[Oshosondy]

So far the issue has been resolved, why did you post it as a topic on this forum? If the issue has not been resolved, you can warn people not to use Bybit, that kind of post is good, but not a post that the issue has been resolved when we do not know if you had issue with Bybit before or not.

[Besmirb]

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

Initial P2P support mishandled the transaction where the buyer failed to complete the Idram transfer. However, after escalating to Bybit Security & Compliance (Agent Carmen) and filing official complaints with regulators (AFSA Ref: 2a6d8570-e55d-4aaa-8b48-f1a9ead523bb & VARA), the compliance team completed a thorough review and released the held escrow.

Thank you to the Bybit Compliance team for correctly reviewing the payment proofs and resolving this ticket.

I posted this to document the case and confirm that Bybit Compliance properly addressed the issue after escalation, providing full transparency for other traders facing similar P2P holds.

[OmegaStarScream]

I posted this to document the case and confirm that Bybit Compliance properly addressed the issue after escalation, providing full transparency for other traders facing similar P2P holds.

Did you make a post prior to this using another account? The information you posted does not really say much. Case and user IDs are for Bybit's internal use.

If this is your case (same UID and amount involved):

https://www.trustpilot.com/users/6aabdce2fd753e3a5ed704bb

You should edit your original post (here on the forum) and provide better detailed explanation of what happened like you did on trustpilot.

[Nathrixxx]

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

I hardly see users coming back to give us the concluding part of their challenges the face using a platform, all we often see is the issue encounter and once it is being result today mostly don't remember to come back again to complete the story.

But in your case, I don't think there is a need for you to create another thread just to announce that your issue has been resolved, it is something you could have pointed out on that same thread initially created if any.

[tabas]

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

If that is so, then you can also change the title about this thread and put up a word like "resolved" or "solved". And since this thread's purpose has been served and you've already done what you have to do to inform the community then make this topic locked as well. You can find the lock topic on the bottom of this thread on the left side.

[Besmirb]

Thanks for the feedback.

To clarify: The issue with Bybit was escalated to Compliance & Security (Ticket #27612502) and regulatory complaints were filed with AFSA and VARA.

I posted this update to ensure full public tracking and transparency of the resolution process. I will update the main post with full details once the final compliance response and funds release are fully processed.

[Woodie]

@Besmirb you need to add [RESOLVED] to your title not really just editing the contents of what the OP has.

How to do it: the same way you managed to edit the body of what happened, you should be able to also edit the title by adding the (resolved) tag at the end of title.

And good to see things went in your favour  

[Besmirb]

Thanks Woodie. The compliance review and unfreezing process is still under final processing by Bybit Support (Ticket #27612502). As soon as the escrow funds are fully released and account access is restored, I will immediately update the title to [RESOLVED] and lock the thread.

[tabas]

Thanks Woodie. The compliance review and unfreezing process is still under final processing by Bybit Support (Ticket #27612502). As soon as the escrow funds are fully released and account access is restored, I will immediately update the title to [RESOLVED] and lock the thread.

Then that means that it is not yet resolved until you get your funds back and they're unfrozen. But I see that it's on the process and you're very optimistic that it will end up in good fate, so let's wait and for the result and their process and hopefully it won't take long time for you to have it back.

[Coyster]

But in your case, I don't think there is a need for you to create another thread just to announce that your issue has been resolved, it is something you could have pointed out on that same thread initially created if any.

The OP has just 4 posts in this forum, as of the time of typing this. So it is easy to check and see that this thread is their very first post in bitcointalk. Though i get it is a bit weird that they want to document the resolution process here, when they didn't make the initial scam report here, but it is all good and could act as reference in similar future cases.

The compliance review and unfreezing process is still under final processing by Bybit Support (Ticket #27612502). As soon as the escrow funds are fully released and account access is restored, I will immediately update the title to [RESOLVED] and lock the thread.

Oh, maybe you should have waited until you have received your funds before writing this:

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

Apparently the case is still unresolved.

[The Cryptovator]

I am posting this update to confirm that the P2P dispute involving 1,500,000 AMD on Bybit (Ticket #27612502, UID 213046727) has been successfully RESOLVED and the funds have been returned/unfrozen.

Good to hear you get back your funds. Scammers often try to scam in various ways, especially in P2P trading. I have been using Bybit P2P for a long time, yet I haven't faced any such issue. Since the deal was through exchanges, it means unless you release funds, seller have to open resolution.

However, I hope you have taken the lesson. You have to check seller/buyer reviews and orders as well before placing an order. In case you release before receiving the full payment, then it will be hard to get refunds, and so many procedures have to follow then. Make sure you are dealing with the right person from the next time.

Mark the thread Solved as I marked reply title.