datapasa.com
Case #282DataPasa, a VPS host, accepted the terms of the real test as they were written on its personal page — choose a coin, paste your address, receive $20, then pay a $15 SnapEX Pay invoice — and on 14 October entered its own address and received $20 in USDT on Ethereum. No AML questions came up then; when we reminded them of the $15 invoice, they called our payment flow unsafe, and when we asked them simply to return the $20, they set a condition “according our AML-policy”: only to the paying address. The terms they had accepted were simple — receive $20, pay $15 — and left no room for conditions added afterwards; even so, we agreed to theirs the same day. Yet since that offer, neither the address that received our $20 nor the wallet it was forwarded to (0x8199…C158) has sent any USDT, and the invoice is unpaid.
They accepted the terms and took the $20 — AML questions came up only when it was time to pay the $15.
Your payment processing flow is very unsafe (looks like totally vibecode). Can you rework your payment flow?
Public sources
- Payout
- $20 · USDT · Ethereum 0xaa5d…70c3 Transaction ↗
- Return invoice
- $15 · Not paid as of 2026-10-18
- We emailed DataPasa about SnapEX Pay
- Follow-up email with a personal real-test link
- Chose USDT · Ethereum and entered the payout address
- $15 return invoice issued, valid 24 hours
- We sent $20 in USDT · Ethereum Transaction ↗
- All 20.01433 USDT were forwarded to another wallet Transaction ↗ 0x8199…C158 ↗
- We reminded them about the $15 invoice
- Reply: our payment flow is “very unsafe”
- We asked them to return the 20 USDT instead
- They offered to return $20 to the paying address “according our AML-policy” — the first mention of AML in the whole correspondence
- We agreed and confirmed the address
- The return invoice expired unpaid
- A new real-test application came from oblako.sh — a domain on the same mail server (mail.depowe.red) and Cloudflare name servers as datapasa.com
- Unpaid for 2 d 19 h 46 min 04 s