Footsites

Stores Part of Footsite Network

Footsites are comprised of the following stores:

• Champs

• Foot Locker

• Kids Foot Locker

Top Supported Bots

• Fly

• ValorAIO

• Prism

• Hayha

Profiles

Name

• Random first, real last name

For Footsites you can use a random first name for all your profiles typically.

Some reuse the same first and last name across all profiles, which works perfectly fine too. I’ve had 20+ orders ship from the same Footsite all using the same exact first name, although I generally just use random first names for the most part. Both work.

Address

• Use real address registered to card.

• If there is no line 2 in your registered card address, then do not add a random line 2 to your address in your billing profile simply for the sake of jigging.

• Not recommended to jig as it increases chances of getting payment verification cancels. • Footsites do not block checkouts to one per address.

• Footsites will typically restrict you to 4-5 pairs during a scheduled drop on their launch calendar (not necessarily for random scheduled drops like dunk, mid restocks, etc.)

• Can be helpful to use your USPS verified address if struggling with PV. You can find this by carting any random item on Footlocker such as this item, heading to the checkout screen and inputting your address information as you normally would. After you fill it in, you may see a prompt telling you to use your USPS verified address instead.

Cards

• Some cards that are known to work include:

  • American Express Employee Cards

  • Amex Extend

  • Capital One (Visa only, MasterCard does not work)

  • Hard Cards

  • Revolut

  • Stripe Issuing

  • Tradeshift

• Card Checkout Limits

  • One checkout per card allowed during a drop per Footsite. Don't reuse cards across profiles or the checkout attempt will get blocked.

  • One card can typically checkout on each Footsite, meaning one checkout on Foot Locker, one checkout on Champs, etc.

• Sharing Virtual Cards/Merchant Locks

  • Capital One Eno cards and Privacy cards can be shared across each Footsite

• Best Cards for Reducing PV Cancels

  • Hard cards will typically work better than common VCC like Privacy, Capital One Eno, Tradeshift.

  • Privacy isn't as recommended as it tends to result in more PVs.

  • Amex employee cards work well for not getting PV.

  • Having stronger profiles/emails with more order history on them can help prevent PV cancels due to card.

Email

• Real emails or catchalls work

• Catchall domains and individual emails can be banned or produce higher risk of fraud, so be sure to swap domains after a while if they seem to be getting cancelled more frequently.

• Recommended to use reputable catchall domains such as one ending in .com, .org, etc.

• + and . trick don't work.

• If using catchall, recommended to include name at least partially in email used. Not required but may help sometimes.

• Footsites track customer numbers by their email, which plays a role in PV cancels. This customer number will be the same across all Footsites for an email.

• Individual emails can get flagged, so if you have a specific email that is always getting PV cancelled regardless of how many you hit, then swapping it can help.

• Running more drops can help to build trust for that customer number/email.

• One checkout per email per Footsite allowed during a drop.

Phone Number

• Random Phone Number with Real Area Code

• One checkout allowed per Footsite for a phone number.

Matching Shipping and Billing

• For Footsites, I would highly recommend making sure your shipping and billing information match.

• Mismatching shipping and billing address seems to have a higher chance of giving a higher fraud score which can cause PV cancellations.

Checkout Limits

• Footsites track duplicates by card, email and phone number combination.

• You are allowed to use the same profile on other Footsites for one checkout, but a profile cannot be reused on the same Footsite for multiple checkouts.

• Footsites allow typically 4-5 pairs on a scheduled drop to one address. Checkouts after this will get cancelled instantly for payment verification failure. Jigging does not help to bypass this.

Payment Verification Cancels

• Footsites use Adyen for their payment processor, which is conducting a fraud check on your payment attempt post authorization.

• When submitting a payment, your purchase attempt is granted a risk score. Orders past a certain threshold will be cancelled for potential fraud. For example, if the threshold is set to 70, and your score was 78, then your order will be declined for high risk of fraud.

• Your risk score is a complicated calculation that is comprised of a few things, such as your name, email, address, card, phone, IP, order velocity (amount of times you order), and more.

Risk Rules

• Footsites can configure several rules that help to determine your risk score. Adyen Site

• We do not know how they configured it or what weighs more compared to other rules.

Shopper Profile

• When Adyen is collecting transaction data and creating a customer profile for you, some of the information they can use includes:

  • Name

  • Email Address

  • Phone Number

  • Address

  • Zip Code

  • Card

  • IP Address

  • Shopper Reference (Customer Number)

Order Velocity

• Velocity checks refer to the number of transactions a shopper has attempted in a given time.

• Order velocity for Footsites essentially refers to purchasing a bunch of items at once in a given period of time. The more items you purchase from Footsties, the higher your risk score will get over time. Footsites have become extremely strict on this. This is why you’ll have your first 4-5 orders go through in some cases, but start to receive mass cancels afterwards.

Troubleshooting Cancels

• PV cancellations after 4-5 orders during a drop is normal and is for exceeding the allowed checkout limit to an address.

• PV cancellations before this are typically related to the profile/checkout returning a high risk of fraud.

Address

• Using an address that does not match what is registered to the card has always been a common trigger of payment verification cancelations since they do address verification.

• Try formatting your address differently, such as using your USPS verified address or the one registered to card if you aren't already. See which one gives you the highest ship rate, and try to stick to a similar address method in future profiles.

• Try some variations on street address, such as spelling variations on street suffixes - street to st, etc.

Email

• Sometimes just swapping out the email address can help you to avoid cancelations. This may be due to the customer number of that email being flagged.

• If you’ve been getting mass cancelations on profiles using a catchall domain, consider trying either a different catchall domain, or just use individual email addresses per order and set up auto forwarding on those email addresses.

• If you are using Gmails or catchall domain, try using ones that include names in them that you can use for the profile first and last name. Since email is your customer number, it's possible that the customer number itself has been flagged.

Cards

• Hard cards generally seem to be the best method to avoiding payment verification cancels. If you are able to, prioritize hard card checkouts, followed by virtual cards.

• If you’re getting tons of cancels on one type of virtual card provider, such as Privacy or Capital One, try switching to another card provider such as Amex Business, Stripe or Slash, and see if that improves your shipped order rate.

• They can flag different banks that are showing too much "abusive" behavior. They do this by looking at the BIN number of the card (first 6 digits identifying the bank). In this case, we have our standard Privacy, Cap 1 Eno and Citi virtual cards that thousands and thousands of resellers are using.

Proxy/IP Address

• Your profile is used for checkouts from too many different IP addresses in a short amount of time.

• Checkout IP is too far from the shipping address.

• Too many shoppers have used that IP address for orders with different info and could have been flagged as a result.

• Using IP addresses from other countries.

• The checkout IP is a suspected proxy and flagged for potential fraud.

Queue-It

• Footsites currently utilize the Queue-It queue system. This queue will go up generally around 30 minutes before a drop.

Captcha

• In order to enter queue, each task will need to solve a captcha. Footsites currently utilize invisible reCAPTCHA v2 with their Queue-It system.

• Unfortunately bots are no longer able to share captcha solves with all tasks. You will need to solve a captcha per task for every bot you are running.

• You can either use AYCD Autosolve AI, your own Gmails, or use a third party captcha solving service such as Capmonster, 2Cap, Anti-Captcha, etc.

• Not recommended to use your own Gmails as they will get flagged solving a high number of captchas like Footsites demand.

• Third party captcha solvers such as Capmonster will typically die and are not reliable for getting tasks into queue.

• AYCD AI with rotating residential proxies is currently the best option for getting tasks into queue.

Setting Up AYCD Autosolve AI

• You will need to purchase an Autosolve AI subscription if you don't have one already.

• For rotating residential proxies, you can purchase from either AYCD or Lemon if you don't have another provider.

• You don't need a lot of data to run this. A 2 GB plan is more than enough for a drop, and 4 GB lasted me for a whole month worth of drops personally on several thousand tasks.

1. From AYCD One Click, first ensure you have your rotating residential proxy list added under the Proxies tab on the top row.

2. Select Accounts tab on the top row.

3. Click File

4. Add Solver

5. Select the category you want to add the solvers to. Give them a name such as AI. For quantity, set the number of solvers you want to have running at once. I personally run 100 solvers so I can get as many tasks into queue as fast as possible, but if you aren't running many tasks or not sure if your pc can handle it, feel free to do around 50 and scale up/down as needed. Also select your rotating residential proxy list.

Proxies

• Residential and ISP proxies both work for Footsites.

• For best results, it is recommended to run a mix of both if possible.

ISP

• ISP proxies still work best on Footsites as long as you have working ones.

• A lot of ISP are flagged on Footsites. If they are flagged, then typically they will either get a 429 rate limit error trying to access any Footsite or be datadome banned and not able to add any item to cart even though they can access the site fine otherwise.

• When buying ISP, check with the provider if they are working on Footsites upon delivery. Some providers will not be upfront about it and will just say it may work on Footsites or not guaranteed.

Residential Proxies

• Residential proxies are viable on Footsites again.

• Data does not get drained as it once did since Footsites swapped to Queue-It for queue instead of Fastly. Fastly had a GIF playing in queue that drained proxy data.

• While ISP will typically perform better (as long as unflagged), residential proxies allow you to scale up your task count which helps greatly when trying to hit often limited stock on Footsite drops.

• Some residential providers that have worked well on Footsite drops include Live, Lemon, Wolves, Sakura, Oculus.

Task to Proxy Ratio

• When using ISP, task to IP ratio should be 1:1. Running more tasks makes for a higher chance for the range to get flagged. It also will increase the rate at which individual proxies get datadome banned during a drop for attempting to cart too many times.

• Residential proxies should be at least 3 or 5 proxies per task (excluding Live). Residential proxies are not as reliable or stable as ISP or Live proxies are, so you want to allow them to rotate as needed if they are dead or banned.

Sharing Proxies Across Each Footsite

• It seems okay to reuse a proxy on another Footsite if you are running multiple sites, such as Footlocker and Champs.

• If sharing, recommended to only run 2 Footsites at a time.

• Residential proxies shouldn't be shared and should have dedicated lists if possible, unless there are a lot of proxies in a proxy list for tasks to rotate between as needed.

Checkout Proxy List

• Although your proxies can access each footsite fine and cart, they can be blocked from completing checkout.

• If you find you often get a lot of carts, but low successful checkout ratio, consider either using different proxies, or if your bot supports it, a separate checkout proxy list.

Monitor Input

• Most bots will use the SKU for a product.

• The SKU can be found in the product link or in the product description.

  • Example - https://www.footlocker.com/product/nike-air-force-1-07-le-mens/W2288111.html, the sku is W2288111.

Start Times

• Tasks should be started as soon as Queue-It goes live for a drop. Bots will let tasks sleep until scheduled drop time after solving captcha for queue entry.

• Starting tasks as early as possible allows more time for captchas to be solved, meaning more tasks can get into queue before the drop starts. This is advantageous if you are using third party solvers.

• If Queue-It does not go up before a drop, then you can typically start most bots 5 minutes before the drop.

Cart Holds

• Footsites utilize 5 minute cart holds during drops.

• You need an active cart hold to checkout. If a task cannot checkout within the allotted time period, then the cart is permanently lost afterwards.

Delays

• A delay of 3000 - 4000 on Footsites works well for most bots. Generally, a delay of 3000 works well across a wide range of bots, but some may recommend 3500.

• Running too low of a delay can cause more datadome bans or 429 rate limit errors.

Captchas

Datadome Captchas

• Footsites no longer utilize captchas when flagged by Datadome.

• Your IP will simply get blocked now instead of being able to solve a captcha as you could in the past to continue attempting to cart.

Queue-It Captchas

• Queue-It captcha is the only captcha you will need to solve during a drop.

• Queue-it captcha is invisible recap v2.

Restocks

• It is not recommended to run Footsites for restocks 24/7.

• Utilizing bot automation modes for restocks is preferred. Bots such as Noble, Prism, Valor have automated task creation for Footsites.

• You can also utilize a third party QT tool such as Joker or Ocean Automation to utilize automated quick task creation for bots that do not have an automated feature for it.

• Most ISP are locked on Footsites outside of drops to prevent them from abuse and getting flagged. You can either buy proxies that are unlocked (such as unlocked subnets) or use residential proxies when running restocks.

Miscellaneous Notes

• Footsites are often luck based. Even with a highly scaled setup, you can walk away from a drop with no pairs or little hits depending on stock.

• Bypass bots still exist and sometimes can heavily dominate certain drops compared to bots that aren't utilizing a bypass of some kind.

• Running as many tasks as you can is helpful to increase your chances of hitting. Make sure you are getting as many tasks into queue as possible, as the best time to hit a drop is right at the beginning where very few people are through queue and you have less competition.