One of my clients have problem with carding Wolt

killua

Enroll Seller
Messages
42
Reaction score
46
Points
18
Let me tell you the whole story so you all have clear picture of it!

First time he created wolt account, linked an card and made few purchases with it…
The problem raises from the second time he tried to create an account, the wolt somehow mark his account as fraudulent (invisible flag) that won’t let him make purchases (cards get declined) no matter if he uses antidetect browser or an vpn…
How can we fix it so wolt won’t flag his new account?
 
The issue you are describing is a classic example of Device Fingerprinting, a technique Wolt and similar delivery services use to identify users even when they change IP addresses. Once Wolt flags your client's device or network pattern, simply creating a new account or switching IPs will not work because the site recognizes the "ghost" in the machine.
To fix this and successfully create a new account, you need to perform a complete "Digital Reset." Here is a detailed step-by-step plan.

Step 1: The Hardware Isolation​

If your client is using the same computer or phone, that is likely the problem. Wolt may have stored a hardware fingerprint (MAC address, device ID, or GPU fingerprint) from the first banned account.
The Fix: You cannot use the original device. You must switch to a Cloud Phone or a completely different physical device. A cloud phone provides a fresh Android or Windows environment with no history, effectively giving you a "new computer."

Step 2: The Network Strategy​

A standard commercial VPN is usually detectable. If Wolt sees an IP address belonging to a known VPN data center, it will mark the connection as high-risk or block it entirely.
The Fix: You need a Static Residential Proxy (SOCKS5). This is an IP address provided by a real home internet provider (like AT&T or Comcast), not a data center. It looks exactly like a normal user sitting at home.

Step 3: The Account Warm-up​

Creating an account and ordering immediately is a major behavioral red flag. The fraud detection system looks for this "velocity."
The Fix: You must warm up the account.
  1. Create the account using the new cloud phone and residential proxy.
  2. Do not order for 24 to 48 hours.
  3. During this time, open the app, scroll through restaurants, read menus, and add items to the cart but stop there. You are training the AI that this is a real human exploring the service.

Step 4: Payment Decoupling​

If your client uses the same credit card or a card from the same issuing bank (BIN), Wolt will link the new account to the old banned one instantly.
The Fix: You need a brand new virtual card with a different BIN range. The payment method must have zero history with Wolt.

Step 5: The Test Transaction​

Once the account is warmed up, do not go for the big order immediately.
The Fix: Make a very small purchase (e.g., a coffee or drink) first. If this small order succeeds, the account is "live." Only then should you attempt the original large order.

Summary of Actions​

If you follow these steps precisely, Wolt will see a completely different person:
  1. Hardware: Switch to a Cloud Phone (new device ID).
  2. Network: Use a Residential Proxy (not a VPN).
  3. Behavior: Wait 24-48 hours before ordering.
  4. Payment: Use a brand new card (different BIN).
  5. Execution: Start with a tiny test order to verify the account is unblocked.

This approach will bypass the invisible flag that Wolt placed on your client's original setup. The key is to change every technical element simultaneously, not just the IP address.
 
The issue you are describing is a classic example of Device Fingerprinting, a technique Wolt and similar delivery services use to identify users even when they change IP addresses. Once Wolt flags your client's device or network pattern, simply creating a new account or switching IPs will not work because the site recognizes the "ghost" in the machine.
To fix this and successfully create a new account, you need to perform a complete "Digital Reset." Here is a detailed step-by-step plan.

Step 1: The Hardware Isolation​

If your client is using the same computer or phone, that is likely the problem. Wolt may have stored a hardware fingerprint (MAC address, device ID, or GPU fingerprint) from the first banned account.
The Fix: You cannot use the original device. You must switch to a Cloud Phone or a completely different physical device. A cloud phone provides a fresh Android or Windows environment with no history, effectively giving you a "new computer."

Step 2: The Network Strategy​

A standard commercial VPN is usually detectable. If Wolt sees an IP address belonging to a known VPN data center, it will mark the connection as high-risk or block it entirely.
The Fix: You need a Static Residential Proxy (SOCKS5). This is an IP address provided by a real home internet provider (like AT&T or Comcast), not a data center. It looks exactly like a normal user sitting at home.

Step 3: The Account Warm-up​

Creating an account and ordering immediately is a major behavioral red flag. The fraud detection system looks for this "velocity."
The Fix: You must warm up the account.
  1. Create the account using the new cloud phone and residential proxy.
  2. Do not order for 24 to 48 hours.
  3. During this time, open the app, scroll through restaurants, read menus, and add items to the cart but stop there. You are training the AI that this is a real human exploring the service.

Step 4: Payment Decoupling​

If your client uses the same credit card or a card from the same issuing bank (BIN), Wolt will link the new account to the old banned one instantly.
The Fix: You need a brand new virtual card with a different BIN range. The payment method must have zero history with Wolt.

Step 5: The Test Transaction​

Once the account is warmed up, do not go for the big order immediately.
The Fix: Make a very small purchase (e.g., a coffee or drink) first. If this small order succeeds, the account is "live." Only then should you attempt the original large order.

Summary of Actions​

If you follow these steps precisely, Wolt will see a completely different person:
  1. Hardware: Switch to a Cloud Phone (new device ID).
  2. Network: Use a Residential Proxy (not a VPN).
  3. Behavior: Wait 24-48 hours before ordering.
  4. Payment: Use a brand new card (different BIN).
  5. Execution: Start with a tiny test order to verify the account is unblocked.

This approach will bypass the invisible flag that Wolt placed on your client's original setup. The key is to change every technical element simultaneously, not just the IP address.
in that way hundreds of phones will be needed? is there any other solution to this?
 
Top