Virtual Carding 💳 Getting NONVBV/NON-3DS BINS (Part 2) (No Cards Method + Script) 💳

[glassdagger]

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.

Thx m8

 

[glassdagger]

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

link to 3d secure checker?

 

[regardingax]

thanks daddy

 

[slaveoflife]

You are the best!

 

[akkthvgod]

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.

COOL

 

[bimbipjp2]

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.


Quá trình

Bạn thấy đấy, sự thật là bạn thậm chí không cần một thẻ trực tiếp để kiểm tra xem nó có hỗ trợ 3DS không. Điều đó có nghĩa gì với chúng ta? Nó chỉ đơn giản có nghĩa là chúng ta không cần phải tìm nguồn và mua một loạt thẻ chỉ để kiểm tra xem chúng có phải là 3DS không. Chúng ta chỉ cần tạo một loạt thẻ từ BIN, chạy kiểm tra 3DS trên mỗi thẻ và bam! Chúng ta có một cỗ máy hoạt động trơn tru có thể kiểm tra 3DS cho chúng ta mà không cần tốn một xu mua thẻ.

View attachment 6327

Đây là cách thức hoạt động của thứ này:

• Tạo BIN : Bắt đầu với 6-8 chữ số đầu tiên của BIN mà bạn quan tâm. Sau đó tạo ra một đống số thẻ có thể có bằng BIN đó. Đảm bảo chúng vượt qua kiểm tra thuật toán Luhn - chúng tôi không phải là những kẻ man rợ hoàn toàn ở đây.
• Xử lý hàng loạt : Lấy danh sách các số đã tạo và chạy chúng qua kiểm tra 3DS. Bạn còn nhớ chúng ta đã đề cập đến quy trình đó trước đó không? Vâng, điều tương tự cũng áp dụng ở đây.
• Phân tích : Hãy xem kết quả. Nếu hầu hết các số được tạo ra từ BIN đều không phải là VBV thì có lẽ bạn đã trúng vàng. Nếu tất cả đều trúng 3DS thì may quá buttercup.
• Lặp lại : Thực hiện thao tác này với nhiều BIN và bạn sẽ bắt đầu xây dựng cơ sở dữ liệu về BIN VBV so với BIN không phải VBV lớn hơn mức bạn có thể tưởng tượng.

Kịch bản

Vì tôi yêu các bạn rất nhiều, tôi đã tạo và lưu trữ một tập lệnh chỉ dành cho các bạn . Chỉ cần dán BIN vào hộp, nhấp vào tạo và nó sẽ đưa ra các thẻ đã tạo mà sau đó bạn có thể kiểm tra trên trình kiểm tra của mình (nếu bạn đã làm theo phần đầu tiên của chúng tôi) hoặc trên Lux và bất kỳ loại trình kiểm tra 3DS nào mà bạn đã chọn.

View attachment 6328

Đây là liên kết đến trình tạo:

* Văn bản ẩn: không thể trích dẫn. *


Bây giờ đừng nghĩ rằng tôi là con khỉ mã hóa cá nhân của bạn. Đây là một thỏa thuận một lần, vì vậy hãy sử dụng nó một cách khôn ngoan. Tập lệnh tạo ra các thẻ dựa trên BIN bạn nhập, hoàn chỉnh với ngày hết hạn và CVV. Nó không phải là khoa học tên lửa, nhưng nó sẽ giúp bạn tiết kiệm được rắc rối khi phải tự viết những thứ vớ vẩn của riêng mình.

Bây giờ, những gì bạn làm với những thẻ được tạo ra này là việc của bạn. Chạy chúng qua trình kiểm tra 3DS của bạn, đưa chúng vào Lux, sử dụng chúng làm hình nền cho tất cả những gì tôi quan tâm. Chỉ cần nhớ rằng - tạo thẻ không giống như có thẻ thực sự, đang hoạt động. Đừng là kẻ ngốc cố gắng sử dụng chúng cho các giao dịch mua thực tế. Chúng tôi chỉ sử dụng chúng để xác thực xem BIN có phải là 3DS/VBV không.


Kết thúc

Vậy là bạn đã có nó - một phương pháp để lập bản đồ cảnh quan 3DS mà không cần tốn một xu cho các thẻ thực tế. Khá thông minh, phải không? Nhưng đừng để nó làm bạn tự mãn. Đây không phải là một cây đũa thần đột nhiên biến bạn thành Sói già phố Wall. Nó là một công cụ, và giống như bất kỳ công cụ nào, nó có thể xây dựng cho bạn một đế chế hoặc cắt đứt ngón tay của bạn nếu bạn không cẩn thận.

Hãy sử dụng kiến thức này một cách khôn ngoan, hoặc không. Đừng khóc khi bạn làm hỏng nó. Bạn đã được cảnh báo rồi.

Bây giờ hãy ra ngoài và bắt đầu xây dựng cơ sở dữ liệu BIN. Với đủ công sức, bạn sẽ có lộ trình giúp bạn trở thành vua của thiên đường không phải HBV.

Giải tán lớp học. Làm tôi tự hào đi, mấy tên khốn đẹp trai. D0ctrine ra ngoài.

XIN CHO TÔI PHẦN 1

 

[Elpuntoexacto]

Thx m8

How come i cant see the link. Loved the info by the way

 

[Krist47]

Always a pleasure reading your stuff!

…

 

[rjhassang]

thanks

 

[Kaydan]

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.

thank you

 

[XavvyLogs]

ty

 

[MoneyWho]

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.

Lovely

 

[Bosslvl10]

Yes

 

[Bosslvl10]

Where can I find a 3ds checker?

 

[12al34]

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.

 

[mrgold]

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.

Wonderful. Respect.

 

[Tobytoby]

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.

Lets see

 

[lenkian]

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.

love you dude

 

[Skyfe]

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.

Thanks

 

[KVAZAR]

Thank you for your work!