Finishline/JDSports
Included Stores
FinishLine
JD Sports US
Top Supported Bots
Hayha
Cybersole
SWFTiOS
ValorAIO
Sometimes, Finishline and JD only drop through mobile/app and requires accounts to purchase. Most bots will not work for these styles of drops except for swft iOS. The other bots support desktop drops which do not require accounts.
Profiles
Name
Name - Random First, Real Last Name
Address
Real Address with no jigs
You can simply use the real address that is registered to the card.
FNL and JD only allow one shoe per address per site during a drop, regardless of how you jig your address.
There are no working jigs for either of these sites since they filter heavily after an order is placed, just like Kith.
For best results, it is highly recommended to run unique addresses to have the most amount of pairs ship.
Orders placed after the first one will typically auto cancel immediately upon placing order.
You can get one item per SKU from each store, for a total of two pairs typically.
Card
Most cards work:
American Express Employee Cards
Amex Extend
Capital One Eno (Visa and MC)
Citi Virtual
Hard Cards
Revolut
Slash
Stripe Issuing
Tradeshift
It is best to keep it to one card per checkout to avoid cancels.
Hard cards are usually advised over virtual cards to avoid cancellations. Since it is one pair per sku per address, you really don't need to have 100 different cards/profiles for the same address.
One card can typically checkout on both FinishLine and JD Sports for your one pair per address allowed.
Capital One Eno cards can be shared across each site. Privacy cards cannot be shared across each site due to merchant lock restrictions.
Some banks in the past have frequently marked FinishLine and JD Sports charges as fraudulent, so keep this in mind when running.
Sometimes when placing an order and the item is out of stock, your card can still get authorized even if it doesn't go through. Keep this in mind if you are limited in the amount you can spend.
Email
Real emails work best.
Catchalls can work, but in the past some have reported a higher rate of cancellations on them. Recommended to use reputable catchall domains such as one ending in .com, .org, etc. if possible. However, since you are limited to one pair per address, there's really no need to use catchalls for your one pair.
Restricted to one checkout per email.
You can use emails with matching accounts to increase the amount of STATUS rewards earned to use for exclusive access later.
Phone Number
Random Phone Number with Real Area Code
Matching Shipping and Billing
It is recommended to have shipping and billing information match.
Mismatching shipping and billing address in the past has led to cancellations by their fraud protection in the past.
Using a card with a mismatched zip code can result in cancellations depending on fraud restrictions in place at the time the order is placed.
Cancels
Cancels on both of these sites are extremely common and should be expected when running these sites. Only run these two sites if you are okay with having a very high order cancellation rate.
Cancels can be due to several reasons, including their one per address rule, bot related for checkout flow, overselling or for fraud.
Profile Checkout Limits
Both of these stores are one checkout per address, regardless of anything you jig or change up in your profiles.
Orders placed after the first order will automatically be cancelled.
Bot Checkout Flow
The bot used to checkout does seem to play some role in cancellations.
This means that even if you only place one order to an address, it could still get cancelled anyways for having a flagged checkout flow.
Fraud
These stores use a system known as Riskified for their fraud protection system. According to various bot devs in the past, this fraud protection system gets turned off during drops/high traffic periods, which would result in less cancels due to suspected fraud in these periods.
Testing profiles outside of drops will generally not yield consistent results when testing. For example, using a proxy for a checkout while Riskified is enabled can sometimes cause a cancellation as the IP address is too far from the shipping address. Other characteristics of your transaction can also get caught up by their system as well.
For some drops or restocks, if the traffic on the site isn’t very high, then in the past it sometimes does not get turned off and cancelations can be high simply because all of your orders got caught up by their fraud detection system.
This is a separate system then the usual one pair per address rule. That will be in effect for any drop.
Overselling
Both of these websites do oversell often.
Cancels will usually come in after a few minutes for this, but can come up to a week later in some cases.
Legitimate Checkouts
You can still have orders with legitimate information get cancelled. This can often come down to the bot you're using, overselling or you checked out too many to one address.
It is advised to make your information as legitimate as possible to avoid cancellations due to fraud.
Using a card with a mismatched zip code can also result in cancellations due to fraud restrictions, so keep this in mind if you find yourself getting cancelled for doing this.
Declines
Declines and failed checkouts are very common when running.
Declines can be for various reasons. The most common reason is that it is simply out of stock by the time the bot attempted to submit the order.
Products do restock intermittently during a drop, so you may see some declines/failures and then successful checkouts afterwards.
Often, your card will get authorized when you submit an order, even if the order did not go through. Make sure to run a card that allows for more flexible spend limits if you are limited in spending power or are running other websites. It can take a few days for the authorizations to drop depending on your bank.
Queue
FNL and JD both use a queue on their sites when traffic on the site is high or before a scheduled drop.
Queue will usually go up 2-5 minutes before a scheduled drop. It will also go up around the usual times for exclusive access as a lot of people go on the site to check.
Captchas
When running the desktop version of the site, FNL and JD both require recaptcha v3 tokens, similar to Yeezy Supply.
Most bots will require you to open up your own harvesters for this. You can usually use 2-4 harvesters which should be good for a drop when running desktop. Using Gmails that are 0.9 will have best results like YS.
Running mobile on these sites does not require you to open up captcha harvesters. Bots will handle this on their end.
Stuck in Permanent Queue
You can get stuck in queue permanently depending on the type of browser/task mode you're running.
They will typically only let people on desktop pass at certain times, and likewise with mobile, only certain times they are able to get through queue.
Permanent queues can last for a while and is up to FNL/JD on when they will let people through.
Queue Bypass
There is no way to bypass queue.
Getting into queue as early as possible is advised to increase your chances of getting through faster.
Proxies
FinishLine and JD use Akamai for their bot protection. Depending on how strict they turn Akamai up to, it can cause difficulties for certain proxies when trying to get through queue and carting/checking out.
Residential proxies can often work better than ISP do depending on the ranges you have. Be sure to use static residential proxies and not rotating.
ISP proxies are not recommended to run anymore. Some can still work, but will come down to the ranges you are running, the bot being used and the current site security. Most devs advise to not bother with ISP anymore as it will struggle to pass queue. Recommended to not only rely on ISP if possible.
ISP sometimes can work on mobile opposed to desktop, but this will vary.
Data usage should not drain heavily when running.
Task to Proxy Ratio
Residential - minimum of 3-5 proxies per task. Residential proxies are not as reliable or stable as ISP are, so you want to allow them to rotate as needed if they are dead or banned. If you are using Live, you can run 3 tasks per proxy across both sites (across both sites, not each individual site).
ISP - one task per proxy is recommended typically. Running more tasks on an IP makes for a higher chance for the proxy range to get flagged by Akamai. Running a higher task to proxy ratio such as 1 proxy for 2 or 3 tasks is up to you, but not advised given the increase in Akamai blocks on these recently.
Miscellaneous Notes
Task Modes
FNL and JD will typically drop stock only through either the mobile or desktop API at a time. Usually they do not drop stock and allow checkouts through both at the same time.
Bots will usually suggest to setup tasks to do a 50/50 split between the two modes, and to mass edit tasks to the other mode when only one mode has been passing and checking out. Be sure to run both modes when starting tasks to ensure the best chance of hitting.
Mobile
If stock is only dropped on mobile, then only people on the app will pass queue and be able to checkout.
For this mode, you will usually not need to open up your own captcha harvesters for most bots, as devs will handle this on their end.
In some instances, the queue on mobile can be slower to pass than desktop.
Desktop
If stock is only released through desktop, then you will need to be running this mode in order to pass through queue and checkout during a drop.
Desktop mode requires you to open up your own harvesters with 0.9 gmails, and you won't be able to checkout without having these open.
Bot Supported APIs
The following bots support Desktop:
Hayha
Kodai
MekAIO
Prism
Valor
Wrath
The following bots support Mobile:
Hayha
Kodai
MekAIO
Prism
Swft iOS
Valor
Wrath
Note, only Swft iOS works when accounts are required to purchase on mobile only drops.
Monitor Inputs
Bots will require you to use the direct link or PID for a shoe.
The product PID is usually formatted as productid,styleid,colorid. Example: prod1380688,DH6927,111, where prod1380688 is the productid, DH6927 is the styleid, and 111 is the colorid.
These can be pulled usually from the product link itself or through either the release channel for that sneaker or from bot discords.
Monitor Input Suggested Inputs
Some bot inputs to use:
Hayha: direct product link
Kodai: PID
MekAIO: PID
Prism: PID
Swft: PID
Valor: direct product link
Wrath: PID
Start Times
Tasks can typically be started as soon as queue goes up for any bot.
Queue normally goes up 2-3 minutes before the drop. It can be see on the home page of these sites.
Bot Suggested Start Times
Some bot provided recommended start times include:
Hayha: when queue is up
Kodai: when queue is up
MekAIO: when queue is up
Prism: when queue is up
Swft: when queue is up on iOS app
Valor: when queue is up or 30 seconds before
Wrath: when queue is up/5 minutes before
Task Limits
Some bots may limit the amount of mobile mode tasks you can run.
Desktop bots do not have task limits in place.
Delays
Delays of 3000-500 are usually recommended.
Bot Suggested Delays
Hayha: 5000, 5000
Kodai: 3000-5000
MekAIO: 3000-5000
Prism: 3000
Swft: default, not able to change currently
Valor: default, not able to change currently
Wrath: 5000,5000
Accounts
In most cases, accounts have not been required to purchase items during drops.
For some mobile drops, products are account locked and did require an account in order to purchase, at least when running the mobile version. This does not seem to be enforced most of the time, however this varies from time to time.
Bot Guides
Below you can find the guide websites for various bots for their FNL/JD module:
Last updated