Quote

Its not real.
Please feel free to post.

Quote

"Order not found" scam network active again: elcapo.io. KYC.rip is going public with the case as we speak. 0.57 BTC loss: https://kyc.rip/swap?id=16B53402BD0BA087C06855ED9CD3293E
Please put a warning on their listing

BTC deposit address bc1qw0zr6z996td5pg39wa20a5vryhavhq4fcgr79n 0.57 BTC

Quote

Sharing our respond to kyc.rip team:

Hi,

We've investigated thoroughly. This order was never created by us, and the deposit address is not ours.

We searched our records on four independent identifiers. None of them exist on our side:

1. Order ID 16B53402BD0BA087C06855ED9CD3293E not found
2. Deposit address bc1qw0zr6z996td5pg39wa20a5vryhavhq4fcgr79n not found on any order we have ever issued
Recipient 3. 87BQyWXKvC7LL3uCkLUxL5XnFsit… not found
3. Amount 0.57395628 BTC no order with this amount exists

We also found no POST /api/partner/orders request in our access logs.

We can state this definitively: every deposit address we issue is tied to an order in our records, and bc1qw0zr6z9… appears on none of them.

The Bitcoin transactions are real. The address received 0.57395329 BTC and the funds have since been spent. So a customer did pay, and someone did sweep it. It simply wasn't us on either end.

Your service is multi-provider, so the most likely explanation is an attribution issue — a response from one provider recorded against another. Specifically:

Which upstream actually served that request? If your router selected a different provider and the result was logged under our name, that explains everything.
What hostname did the request reach? Please confirm the exact URL, scheme and host your integration called. A stale config or DNS entry pointing elsewhere would produce exactly this.
Which API key was used? We can trace any key we issued and tell you what it did and when.
Does that response actually match ours? Compare it field by field against a known-good order from us — the differences should be immediately visible.
The raw request and response with a UTC timestamp, headers included.
Where we stand

We're not brushing this off. If a customer is out 0.57 BTC, that matters, and we'll help trace it however we can — give us an API key or a timestamp and we'll check it against our logs.

But we can only account for what reached us, and this did not. Please confirm which provider actually handled the request, because whoever controls that address is the one who can answer for the funds.