looks good.
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
good shit
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.
Appreciate u fr 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.
sntchbck777
Newbie
- Joined
- 21.09.25
- Messages
- 12
- Reaction score
- 6
- Points
- 3
Thnx
Awesome_Star777
Newbie
- Joined
- 28.05.26
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Will check and tell
eholloway13
Newbie
- Joined
- 28.05.26
- Messages
- 1
- Reaction score
- 0
- Points
- 1
yes
sweet
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.
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.
Let’s see i
f this works
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.
Widitdajoint
Newbie
- Joined
- 10.06.26
- Messages
- 2
- Reaction score
- 0
- Points
- 1
Dope!
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.
deeppangie
Newbie
- Joined
- 10.06.26
- Messages
- 1
- Reaction score
- 0
- Points
- 1
good
thankx 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.
O Processo
Veja bem, a verdade é que você nem precisa de um cartão fÃsico para verificar se ele é compatÃvel com o 3DS. O que isso significa para nós? Significa simplesmente que não precisamos procurar e comprar um monte de cartões só para testar se são compatÃveis com o 3DS. Basta gerar um conjunto de cartões a partir do BIN, executar uma verificação de compatibilidade com o 3DS em cada um e pronto! Temos uma máquina bem azeitada que verifica a compatibilidade com o 3DS para nós sem gastar um centavo comprando cartões.
View attachment 6327
Funciona assim:
- Geração de BIN : Comece com os primeiros 6 a 8 dÃgitos do BIN que lhe interessa. Em seguida, gere uma infinidade de números de cartão possÃveis usando esse BIN. Certifique-se de que eles passem na verificação do algoritmo de Luhn — não somos completos selvagens aqui.
- Processamento em lote : Pegue sua lista de números gerados e execute uma verificação 3DS. Lembra como abordamos esse processo anteriormente? Pois bem, a mesma coisa se aplica aqui.
- Análise : Observe os resultados. Se a maioria dos números gerados a partir de um BIN retornar como não-VBV, você provavelmente encontrou um tesouro. Se todos estiverem indo para 3DS, bem, azar o seu.
- Repita o processo : Faça isso para vários BINs e você começará a construir um banco de dados de BINs VBV versus não-VBV maior do que você pode imaginar.
O roteiro
Como eu gosto muito de vocês, criei e hospedei um script especialmente para vocês . Basta colar os arquivos BIN na caixa, clicar em gerar e ele irá gerar os cards que vocês poderão verificar no seu verificador (se seguiram nossa primeira parte) ou no Lux e em qualquer outro verificador de 3DS que vocês tenham escolhido.
View attachment 6328
Aqui está o link para o gerador:
* Texto oculto: não pode ser citado. *
Não pense que sou seu programador particular. Isso é uma oferta única, então use com sabedoria. O script gera cartões com base nos BINs que você inserir, incluindo datas de validade e CVVs. Não é nenhum bicho de sete cabeças, mas vai te poupar o trabalho de escrever seu próprio código.
Agora, o que você fizer com esses cartões gerados é problema seu. Use-os no seu verificador de 3DS, envie-os para o Lux, use-os como papel de parede, tanto faz. Só lembre-se: gerar cartões não é a mesma coisa que ter cartões reais e funcionais. Não seja o idiota que tenta usá-los para compras de verdade. Estamos usando-os apenas para validar se os BINs são de 3DS/VBV.
Concluindo
Então, aà está: um método para mapear o mapa do 3DS sem gastar um centavo em cartões de verdade. Muito inteligente, não é? Mas não se iluda. Isso não é uma varinha mágica que vai te transformar no Lobo de Wall Street. É uma ferramenta e, como qualquer ferramenta, pode construir um império ou cortar seus dedos se você não tomar cuidado.
Use esse conhecimento com sabedoria, ou não use. Só não venha chorar quando fizer besteira. Você foi avisado.
Agora vá lá e comece a construir esse banco de dados BIN. Com bastante trabalho, você terá um roteiro que o tornará o rei do paraÃso não-VBV.
Aula encerrada. Me orgulhem, seus lindos bastardos. d0ctrine fora.
Muito bem, seus filhos da puta, se vocês estão se perguntando por que esta é a Parte 2 e onde diabos foi parar a Parte 1, eu estava bêbado e acidentalmente a apaguei da existência. Mas não se preocupem — vou ressuscitar aquela desgraçada e postá-la depois deste guia. Por enquanto, vamos direto ao que interessa .
Enquanto a primeira parte tratava da verificação do status VBV/3DS dos seus cards, este guia vai além. Estamos falando de um método para verificar qualquer BIN sem nem mesmo ter os cards. Isso mesmo, você pode analisar faixas inteiras de cards antes mesmo de pensar em comprá-los. Chega de gastar dinheiro com cards ruins — você encontrará o BIN perfeito sem gastar um centavo.
View attachment 6324
Então, largue essa cerveja quente, limpe a poeira de Cheetos dos dedos e preste atenção. Isso não é só teoria sem fundamento — é conhecimento prático que vai te poupar tempo, dinheiro e muita dor de cabeça. Pronto para arrasar no BIN? Vamos nessa!
O Processo 3DS
View attachment 6325
Agora que você entende o motivo de estarmos aqui, para compreender totalmente nosso método, vamos mergulhar em como os processadores de pagamento descobrem se um cartão é compatÃvel com 3DS apenas olhando para o seu BIN. O processo não é nenhum mistério — tudo se resume a bancos de dados , consultas em tempo real e uma enorme quantidade de processamento em segundo plano. Eu já teria abordado isso na primeira parte, mas como estou escrevendo este texto agora, vou tratar disso aqui.
- Bancos de dados : Você precisa entender que esses processadores não estão trabalhando à s cegas. Eles têm acesso a bancos de dados detalhados diretamente dos bancos, repletos de informações sobre cada BIN existente. Estamos falando de suporte 3DS, nÃveis de risco de fraude, polÃticas do emissor — o pacote completo. E eles mantêm tudo isso atualizado regularmente.
- Processamento em tempo real : Quando uma transação é iniciada, o processador extrai o BIN e o compara com seu banco de dados em milissegundos. Mas, às vezes, eles não confiam em seus próprios dados. Para transações de alto risco ou quando estão se sentindo extremamente cautelosos, eles contatam em tempo real as redes de cartões ou até mesmo o banco emissor.
- Servidor de Diretório : É aqui que entra o Servidor de Diretório (DS). O processador consulta este DS, que então se comunica com o emissor para obter a palavra final sobre se o 3DS é necessário e qual versão está sendo usada.
- Conclusão da transação : Se o BIN não suportar 3DS ou se o emissor decidir que não é necessário, a transação é concluÃda sem as medidas de segurança adicionais.
Lixeiras
Vamos dar um passo atrás e falar um pouco sobre os catadores de lixo. Já falamos sobre esses idiotas em outro fórum, mas para quem perdeu, aqui vai um resumo.
Os jogadores que compram cartas aleatoriamente são a escória do mundo dos cards. Esses idiotas acham que são espertos porque pegam uma carta comprada, colocam uns números aleatórios e rezam para o RNGesus para que uma das combinações deles funcione. É como jogar na loteria, só que os prêmios são uma porcaria e as chances são ainda piores.
View attachment 6326
Eis o processo "genial" deles: começam com um BIN válido, geram uma infinidade de combinações possÃveis para os dÃgitos restantes, depois passam essas combinações por algum verificador tosco e torcem para que alguma funcione. É quase tão eficaz quanto usar um garfo para comer sopa, mas de vez em quando, eles têm sorte.
Mas veja bem: esses idiotas do Binner descobriram algo útil por acidente. Eles encontraram um jeito de testar BINs sem ter os cartões fÃsicos. E é aà que entramos. Vamos pegar essa ideia meia-boca deles e transformá-la em algo realmente valioso.
Veja bem, enquanto os especialistas em classificação estão tentando de tudo na esperança de que algo funcione, nós vamos ser inteligentes. Vamos combinar a técnica deles de geração de BINs com nosso conhecimento de verificação de 3DS. O resultado é um método para analisar intervalos inteiros de BINs em busca do status VBV sem gastar um centavo com cartões.
O Processo
Veja bem, a verdade é que você nem precisa de um cartão fÃsico para verificar se ele é compatÃvel com o 3DS. O que isso significa para nós? Significa simplesmente que não precisamos procurar e comprar um monte de cartões só para testar se são compatÃveis com o 3DS. Basta gerar um conjunto de cartões a partir do BIN, executar uma verificação de compatibilidade com o 3DS em cada um e pronto! Temos uma máquina bem azeitada que verifica a compatibilidade com o 3DS para nós sem gastar um centavo comprando cartões.
View attachment 6327
Funciona assim:
- Geração de BIN : Comece com os primeiros 6 a 8 dÃgitos do BIN que lhe interessa. Em seguida, gere uma infinidade de números de cartão possÃveis usando esse BIN. Certifique-se de que eles passem na verificação do algoritmo de Luhn — não somos completos selvagens aqui.
- Processamento em lote : Pegue sua lista de números gerados e execute uma verificação 3DS. Lembra como abordamos esse processo anteriormente? Pois bem, a mesma coisa se aplica aqui.
- Análise : Observe os resultados. Se a maioria dos números gerados a partir de um BIN retornar como não-VBV, você provavelmente encontrou um tesouro. Se todos estiverem indo para 3DS, bem, azar o seu.
- Repita o processo : Faça isso para vários BINs e você começará a construir um banco de dados de BINs VBV versus não-VBV maior do que você pode imaginar.
O roteiro
Como eu gosto muito de vocês, criei e hospedei um script especialmente para vocês . Basta colar os arquivos BIN na caixa, clicar em gerar e ele irá gerar os cards que vocês poderão verificar no seu verificador (se seguiram nossa primeira parte) ou no Lux e em qualquer outro verificador de 3DS que vocês tenham escolhido.
View attachment 6328
Aqui está o link para o gerador:
* Texto oculto: não pode ser citado. *
Não pense que sou seu programador particular. Isso é uma oferta única, então use com sabedoria. O script gera cartões com base nos BINs que você inserir, incluindo datas de validade e CVVs. Não é nenhum bicho de sete cabeças, mas vai te poupar o trabalho de escrever seu próprio código.
Agora, o que você fizer com esses cartões gerados é problema seu. Use-os no seu verificador de 3DS, envie-os para o Lux, use-os como papel de parede, tanto faz. Só lembre-se: gerar cartões não é a mesma coisa que ter cartões reais e funcionais. Não seja o idiota que tenta usá-los para compras de verdade. Estamos usando-os apenas para validar se os BINs são de 3DS/VBV.
Concluindo
Então, aà está: um método para mapear o mapa do 3DS sem gastar um centavo em cartões de verdade. Muito inteligente, não é? Mas não se iluda. Isso não é uma varinha mágica que vai te transformar no Lobo de Wall Street. É uma ferramenta e, como qualquer ferramenta, pode construir um império ou cortar seus dedos se você não tomar cuidado.
Use esse conhecimento com sabedoria, ou não use. Só não venha chorar quando fizer besteira. Você foi avisado.
Agora vá lá e comece a construir esse banco de dados BIN. Com bastante trabalho, você terá um roteiro que o tornará o rei do paraÃso não-VBV.
Aula encerrada. Me orgulhem, seus lindos bastardos. d0ctrine fora.