thx
Getting NONVBV/NON-3DS BINS (Part 2) (No Cards Method + Script)
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
Virtual Carding 💳 Getting NONVBV/NON-3DS BINS (Part 2) (No Cards Method + Script) 💳
- Thread starter d0ctrine
- Start date
-
- Tags
- 3ds bypass bank identification numbers bin checking card number algorithms card testing methods carder forums carding techniques credit card fraud credit card generation credit card validation cybercrime methods digital theft techniques financial security loopholes fraudulent transactions non-vbv cards online fraud tactics payment gateway exploits payment processing vulnerabilities transaction security flaws underground economy
thanks
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
El proceso
Mira, la verdad es que ni siquiera necesitas una tarjeta en vivo para comprobar si es compatible con la 3DS. ¿Qué significa eso para nosotros? Simplemente significa que no tenemos que buscar y comprar un montón de tarjetas solo para comprobar si son compatibles con la 3DS. Simplemente generamos un montón de tarjetas desde el BIN, realizamos una comprobación de la 3DS en cada una, ¡y listo! Tenemos una máquina bien engrasada que comprueba la 3DS por nosotros sin gastar un céntimo en tarjetas.
View attachment 6327
Así es como funciona esta mierda:
- Generación de BIN : Comienza con los primeros 6-8 dígitos del BIN que te interesa. Luego, genera un montón de posibles números de tarjeta usando ese BIN. Asegúrate de que pasen la verificación del algoritmo de Luhn; no somos unos completos salvajes.
- Procesamiento por lotes : Toma tu lista de números generados y compruébalos con una verificación 3DS. ¿Recuerdas cómo vimos ese proceso antes? Sí, aquí aplica lo mismo.
- Análisis : Mira los resultados. Si la mayoría de los números generados por un BIN no son VBV, probablemente hayas encontrado una fortuna. Si todos llegan a la 3DS, ¡mala suerte, Buttercup!
- Enjuagar y repetir : haga esto para múltiples BIN y comenzará a construir una base de datos de BIN VBV vs no VBV más grande de lo que pueda imaginar.
El guión
Como los quiero mucho, creé y alojé un script solo para ustedes . Simplemente peguen los BIN en el cuadro, hagan clic en "generar" y se generarán cartas que podrán revisar en su verificador (si siguieron nuestra primera parte) o en Lux o en cualquier otro tipo de verificador de 3DS que hayan elegido.
View attachment 6328
Aquí está el enlace al generador:
Texto oculto: no se puede citar.
No pienses que soy tu programador personal. Es un servicio único, así que úsalo con inteligencia. El script genera tarjetas basadas en los BIN que ingresas, con fechas de vencimiento y CVV. No es ciencia espacial, pero te ahorrará la molestia de escribir tu propio código.
Ahora bien, lo que hagas con estas tarjetas generadas es asunto tuyo. Pásalas por el verificador de 3DS, entrégaselas a Lux y úsalas como fondo de pantalla, por si acaso. Recuerda: generar tarjetas no es lo mismo que tener tarjetas reales y funcionales. No seas el imbécil que intenta usarlas para compras reales. Solo las usamos para validar si los BIN son de 3DS/VBV.
Concluyendo
Así que ahí lo tienen: un método para mapear el paisaje de la 3DS sin gastar un céntimo en cartas. ¡Genial, ¿verdad?! Pero no se les suba a la cabeza. No es una varita mágica que de repente te convertirá en el Lobo de Wall Street. Es una herramienta, y como cualquier herramienta, puede construir un imperio o cortarte los dedos si no tienes cuidado.
Usa este conocimiento sabiamente, o no. Simplemente no vengas llorando cuando la cagues. Estás advertido.
Ahora, sal y empieza a construir esa base de datos BIN. Con suficiente trabajo, tendrás una hoja de ruta que te convertirá en el rey del paraíso sin VBV.
Clase terminada. Haganme sentir orgulloso, hermosos bastardos. Doctrina fuera.
sloppyjoeturner
Newbie
- Joined
- 28.04.25
- Messages
- 14
- Reaction score
- 0
- Points
- 1
the goat
Brilliant, thx!
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
Reply
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
DontTreadOnMe3
Diamond
- Joined
- 04.02.24
- Messages
- 67
- Reaction score
- 12
- Points
- 8
thanks dude
justinfooh
Newbie
- Joined
- 04.05.25
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Gotta try this.
Thank a lot. Pro
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
charlesholt332
Newbie
- Joined
- 06.05.25
- Messages
- 3
- Reaction score
- 0
- Points
- 1
thanks bro
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
charlesholt332
Newbie
- Joined
- 06.05.25
- Messages
- 3
- Reaction score
- 0
- Points
- 1
thanks
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
good
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
Nice
KFCMCDONALDS
Newbie
- Joined
- 04.05.25
- Messages
- 18
- Reaction score
- 0
- Points
- 1
thab=nk
thanks so much!
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
thanks bro
Alright fuckers, if youre wondering why this is Part 2 and where the hell Part 1 went, I was piss drunk and accidentally nuked it from existence. But dont get your panties in a twist - Ill resurrect that bastard and post it after this guide. For now, were diving straight into the good shit.
While the first part was all about checking the VBV/3DS status of your cards, this guide takes it up a notch. Were talking about a method to check any BIN without even having any cards. Thats right, you can scope out entire ranges of cards before you even think about buying them. No more wasting money on duds - youll be finding the perfect BIN without spending a single dollar.
View attachment 6324
So put down that warm beer, wipe the Cheeto dust off your fingers and pay attention. This isnt just some theoretical bullshit - its practical knowledge thatll save you time, money and a whole lot of headaches. Ready to level up your BIN game? Lets fucking go.
The 3DS Process
View attachment 6325
Now that you understand why were here, in order to fully grasp our method, lets dive into how payment processors figure out if a card supports 3DS just by looking at its BIN. The process isnt black magic - its all about databases, real-time lookups, and a shitload of backend processing. I wouldve covered this on the first part already, but since Im making this now Ill just tackle this here.
- Databases: You need to realize that these processors arent flying blind. Theyve got detailed databases straight from the banks, packed with info on every BIN out there. Were talking 3DS support, fraud risk levels, issuer policies - the whole package. And they keep this shit updated regularly.
- Real-time processing: When a transaction is initiated, the processor extracts the BIN and runs it against their database in milliseconds. But sometimes they dont trust their own data. For high-risk transactions or when theyre feeling extra cautious, theyll reach out in real-time to card networks or even the issuing bank.
- Directory Server: This is where the Directory Server (DS) comes in. The processor queries this DS, which then communicates with the issuer to get the final word on whether 3DS is needed and what version theyre using.
- Transaction completion: If the BIN doesnt support 3DS or the issuer decides its not necessary, the transaction goes through without the extra security bullshit.
Binners
Lets take a step back and talk about binners for a second. We covered these dipshits on another forum, but for those who missed it, heres the lowdown.
Binners are the bottom-feeders of the carding world. These idiots think theyre clever because they can take a BIN, slap on some random numbers, and pray to RNGesus that one of their combinations works. Its like playing the lottery, except the prizes are shitty and the odds are even worse.
View attachment 6326
Heres their "genius" process: Start with a valid BIN, generate a fuckton of possible combinations for the remaining digits, then run these through some janky checker and hope something sticks. Its about as effective as using a fork to eat soup, but every now and then, they get lucky.
But heres the thing - these binner morons accidentally stumbled onto something useful. They found a way to test BINs without having actual cards. And thats where we come in. Were gonna take their half-assed idea and turn it into something actually fucking valuable.
See, while binners are busy throwing shit at the wall hoping something sticks, were gonna be smart about it. Well combine their BIN generation technique with our knowledge of 3DS checking. The result is a method to scope out entire BIN ranges for VBV status without spending a dime on cards.
The Process
See, the truth of the matter is you dont even need a live card to check if it supports 3DS. What does that mean for us? It simply means we dont need to source and purchase a bunch of cards just to test if they are 3DS. We simply generate a bunch of cards from the BIN run a 3DS check on each and bam! We got a well-oiled machine that checks the 3DS for us without spending a dime on buying cards.
View attachment 6327
Heres how this shit works:
- BIN Generation: Start with the first 6-8 digits of the BIN youre interested in. Then generate a fuckton of possible card numbers using that BIN. Make sure they pass the Luhn algorithm check - were not complete savages here.
- Batch Processing: Take your list of generated numbers and run them through a 3DS check. Remember how we covered that process earlier? Yeah same shit applies here.
- Analysis: Look at the results. If most of the generated numbers from a BIN come back as non-VBV youve probably struck gold. If theyre all hitting 3DS well tough luck buttercup.
- Rinse and Repeat: Do this for multiple BINs and youll start building a database of VBV vs non-VBV BINs larger than you can imagine.
The Script
Since I love you guys so much, I made and hosted a script just for you. Simply paste the BINs in the box, click generate and it will spit out generated cards that you can then check on your checker (if you followed our first part) or on Lux and whatever the fuck kind of 3DS checker you settled on.
View attachment 6328
Heres the link to the generator:
* Hidden text: cannot be quoted. *
Now dont go thinking Im your personal code monkey. This is a one-time deal, so use it wisely. The script generates cards based on the BINs you input, complete with expiration dates and CVVs. Its not rocket science, but itll save you the hassle of writing your own shit.
Now, what you do with these generated cards is your business. Run them through your 3DS checker, feed them to Lux, use them as wallpaper for all I care. Just remember - generating cards isnt the same as having real, working cards. Dont be the dipshit who tries to use these for actual purchases. Were only using these to validate if the BINs are 3DS/VBV.
Wrapping Up
So there you have it - a method to map the 3DS landscape without spending a dime on actual cards. Pretty fucking clever, right? But dont let it go to your head. This isnt some magic wand thatll suddenly make you the Wolf of Wall Street. Its a tool, and like any tool, it can build you an empire or slice off your fingers if youre not careful.
Use this knowledge wisely, or dont. Just dont come crying when you fuck it up. Youve been warned.
Now get out there and start building that BIN database. With enough work, youll have a roadmap thatll make you the king of non-VBV paradise.
Class dismissed. Make me proud, you beautiful bastards. d0ctrine out.
loosestickers
Banned
- Joined
- 04.10.23
- Messages
- 13
- Reaction score
- 1
- Points
- 3
ok thanks