EMV software ATM



Valvolk

Carding Novice
Joined
29.04.23
Messages
1
Reaction score
2
Points
3
Hello everyone, today I’m discussing my personal experience with the mystical “EMV CLONING”. This post is only to retain information and people’s opinions. I speak from experience. So I’ve been semi-successful In cloning a EMV chip, I’m not claiming it works just stating what I’ve learned. After countless weeks of research, a lot of the information that you can find on public forums provide some sense about EMV software and its work arounds. I was thankful to get some working software, and as per usual formatted the blank card , fused it and burned the information on the JCOP chip. A lot of research goes into using the right SDA bins, for a somewhat functional clone and a successful burn on the chip, There’s a lot that can go wrong and a lot of Mis leading information is posted online not only that but the scammers that claim this and that trying to take your hard earned money. Also, I initially thought the software was fake , until I realized there’s steps to be taken , like fusing and initializing the card to prepare for the process. So for one, this process is about basically copying the cards stored information and burning the applet to a blank. I know that the EMV software I used can’t fully read all the records on the card, but reads enough to make a clone, so half the issue could be missing information but we also don’t know if that information is really checked when processing a ATM transaction. As far as bins and their ATRs go , several clones I made with different ATR matching or not matching the bin still functions the same wether it’s related or not. My clone was fully readable by the ATM, got through the pin stage and proceeded to try to withdraw money, the ATM was successful is authorizing the EMV chip read , and indeed it did try to pull from the account. No here’s where the problem lies, as the transaction failed I got a notification from the bank app stating that I tried to withdraw from the ATM, only reason it didn’t go through was because the cvv or expiration date was wrong. Meaning there either was a user error or cloning error in the process. After countless try’s and trips to the ATM, the same issue continues to happen. So In theory we know the chip is readable , we also know the ATM can process it. By verifying the card and codes on the receipt. Know it’s just about making sure the applet properly burned on the chip. After testing the cards with a personal pos, i continue with the same issue. Either the software is not reading that specific protocol of the applet or by user error which in my case I think I’ve ruled out by inputing information several different ways, on multiple clones. Maybe there is a way to manually set the expiration date by ADPU commands and or script, still working on that, in the same way you would change the ATR of the card using EMV Foundry, EMV Explore or manually with pyADPUtool. Reading the card after clone, functions in a wallet app as it should, and records appear to be proper. So I’ve come to the conclusion either the software is missing a function or simply can’t properly burn that data and or the ATM reads that record in a different way the others. I’ll continue to research in learn on this endeavor while many say it’s pointless. Non the less this is just from my experience. Feel free to leave your opinion and experience as well, thanks everyone.
Contact me @bagboygee if you have vital information
 

lm2aomf

Carding Novice
Joined
29.05.23
Messages
1
Reaction score
0
Points
1
Hello everyone, today I’m discussing my personal experience with the mystical “EMV CLONING”. This post is only to retain information and people’s opinions. I speak from experience. So I’ve been semi-successful In cloning a EMV chip, I’m not claiming it works just stating what I’ve learned. After countless weeks of research, a lot of the information that you can find on public forums provide some sense about EMV software and its work arounds. I was thankful to get some working software, and as per usual formatted the blank card , fused it and burned the information on the JCOP chip. A lot of research goes into using the right SDA bins, for a somewhat functional clone and a successful burn on the chip, There’s a lot that can go wrong and a lot of Mis leading information is posted online not only that but the scammers that claim this and that trying to take your hard earned money. Also, I initially thought the software was fake , until I realized there’s steps to be taken , like fusing and initializing the card to prepare for the process. So for one, this process is about basically copying the cards stored information and burning the applet to a blank. I know that the EMV software I used can’t fully read all the records on the card, but reads enough to make a clone, so half the issue could be missing information but we also don’t know if that information is really checked when processing a ATM transaction. As far as bins and their ATRs go , several clones I made with different ATR matching or not matching the bin still functions the same wether it’s related or not. My clone was fully readable by the ATM, got through the pin stage and proceeded to try to withdraw money, the ATM was successful is authorizing the EMV chip read , and indeed it did try to pull from the account. No here’s where the problem lies, as the transaction failed I got a notification from the bank app stating that I tried to withdraw from the ATM, only reason it didn’t go through was because the cvv or expiration date was wrong. Meaning there either was a user error or cloning error in the process. After countless try’s and trips to the ATM, the same issue continues to happen. So In theory we know the chip is readable , we also know the ATM can process it. By verifying the card and codes on the receipt. Know it’s just about making sure the applet properly burned on the chip. After testing the cards with a personal pos, i continue with the same issue. Either the software is not reading that specific protocol of the applet or by user error which in my case I think I’ve ruled out by inputing information several different ways, on multiple clones. Maybe there is a way to manually set the expiration date by ADPU commands and or script, still working on that, in the same way you would change the ATR of the card using EMV Foundry, EMV Explore or manually with pyADPUtool. Reading the card after clone, functions in a wallet app as it should, and records appear to be proper. So I’ve come to the conclusion either the software is missing a function or simply can’t properly burn that data and or the ATM reads that record in a different way the others. I’ll continue to research in learn on this endeavor while many say it’s pointless. Non the less this is just from my experience. Feel free to leave your opinion and experience as well, thanks everyone.
Contact me @bagboygee if you have vital information
same thing happend to me, jus wondering is x2 burnt out and x2.5 is needed?
 

Unknownny

Carding Novice
Joined
01.06.23
Messages
11
Reaction score
2
Points
3
x2.5 is low key same thing ive burned a total of 6 cards and got 1 to actually work. suing emv foundry to go in and rewrite somethings that were overwritten by the ist burn in x2 in my belief is what makes the difference. its kinda like checking your work. also region locks make things harder try getting dumps in your area. it works just very tedious process cause if it were that easy everyone would do it
 

Lewiscarr223

Carding Novice
Joined
17.06.23
Messages
3
Reaction score
2
Points
3
Hello everyone, today I’m discussing my personal experience with the mystical “EMV CLONING”. This post is only to retain information and people’s opinions. I speak from experience. So I’ve been semi-successful In cloning a EMV chip, I’m not claiming it works just stating what I’ve learned. After countless weeks of research, a lot of the information that you can find on public forums provide some sense about EMV software and its work arounds. I was thankful to get some working software, and as per usual formatted the blank card , fused it and burned the information on the JCOP chip. A lot of research goes into using the right SDA bins, for a somewhat functional clone and a successful burn on the chip, There’s a lot that can go wrong and a lot of Mis leading information is posted online not only that but the scammers that claim this and that trying to take your hard earned money. Also, I initially thought the software was fake , until I realized there’s steps to be taken , like fusing and initializing the card to prepare for the process. So for one, this process is about basically copying the cards stored information and burning the applet to a blank. I know that the EMV software I used can’t fully read all the records on the card, but reads enough to make a clone, so half the issue could be missing information but we also don’t know if that information is really checked when processing a ATM transaction. As far as bins and their ATRs go , several clones I made with different ATR matching or not matching the bin still functions the same wether it’s related or not. My clone was fully readable by the ATM, got through the pin stage and proceeded to try to withdraw money, the ATM was successful is authorizing the EMV chip read , and indeed it did try to pull from the account. No here’s where the problem lies, as the transaction failed I got a notification from the bank app stating that I tried to withdraw from the ATM, only reason it didn’t go through was because the cvv or expiration date was wrong. Meaning there either was a user error or cloning error in the process. After countless try’s and trips to the ATM, the same issue continues to happen. So In theory we know the chip is readable , we also know the ATM can process it. By verifying the card and codes on the receipt. Know it’s just about making sure the applet properly burned on the chip. After testing the cards with a personal pos, i continue with the same issue. Either the software is not reading that specific protocol of the applet or by user error which in my case I think I’ve ruled out by inputing information several different ways, on multiple clones. Maybe there is a way to manually set the expiration date by ADPU commands and or script, still working on that, in the same way you would change the ATR of the card using EMV Foundry, EMV Explore or manually with pyADPUtool. Reading the card after clone, functions in a wallet app as it should, and records appear to be proper. So I’ve come to the conclusion either the software is missing a function or simply can’t properly burn that data and or the ATM reads that record in a different way the others. I’ll continue to research in learn on this endeavor while many say it’s pointless. Non the less this is just from my experience. Feel free to leave your opinion and experience as well, thanks everyone.
Contact me @bagboygee if you have vital information
Hello everyone, today I’m discussing my personal experience with the mystical “EMV CLONING”. This post is only to retain information and people’s opinions. I speak from experience. So I’ve been semi-successful In cloning a EMV chip, I’m not claiming it works just stating what I’ve learned. After countless weeks of research, a lot of the information that you can find on public forums provide some sense about EMV software and its work arounds. I was thankful to get some working software, and as per usual formatted the blank card , fused it and burned the information on the JCOP chip. A lot of research goes into using the right SDA bins, for a somewhat functional clone and a successful burn on the chip, There’s a lot that can go wrong and a lot of Mis leading information is posted online not only that but the scammers that claim this and that trying to take your hard earned money. Also, I initially thought the software was fake , until I realized there’s steps to be taken , like fusing and initializing the card to prepare for the process. So for one, this process is about basically copying the cards stored information and burning the applet to a blank. I know that the EMV software I used can’t fully read all the records on the card, but reads enough to make a clone, so half the issue could be missing information but we also don’t know if that information is really checked when processing a ATM transaction. As far as bins and their ATRs go , several clones I made with different ATR matching or not matching the bin still functions the same wether it’s related or not. My clone was fully readable by the ATM, got through the pin stage and proceeded to try to withdraw money, the ATM was successful is authorizing the EMV chip read , and indeed it did try to pull from the account. No here’s where the problem lies, as the transaction failed I got a notification from the bank app stating that I tried to withdraw from the ATM, only reason it didn’t go through was because the cvv or expiration date was wrong. Meaning there either was a user error or cloning error in the process. After countless try’s and trips to the ATM, the same issue continues to happen. So In theory we know the chip is readable , we also know the ATM can process it. By verifying the card and codes on the receipt. Know it’s just about making sure the applet properly burned on the chip. After testing the cards with a personal pos, i continue with the same issue. Either the software is not reading that specific protocol of the applet or by user error which in my case I think I’ve ruled out by inputing information several different ways, on multiple clones. Maybe there is a way to manually set the expiration date by ADPU commands and or script, still working on that, in the same way you would change the ATR of the card using EMV Foundry, EMV Explore or manually with pyADPUtool. Reading the card after clone, functions in a wallet app as it should, and records appear to be proper. So I’ve come to the conclusion either the software is missing a function or simply can’t properly burn that data and or the ATM reads that record in a different way the others. I’ll continue to research in learn on this endeavor while many say it’s pointless. Non the less this is just from my experience. Feel free to leave your opinion and experience as well, thanks everyone.
Contact me @bagboygee if you have vital information
We are in the same boat . Everything readable like the regular card go to cash out . No go but it’s doing all the functions. I was thinking it was my area or the work I was use never thought about the software. Will it make a difference if I hit the burn button multiple times?.
 

rocblocc

Carding Novice
Joined
05.08.23
Messages
1
Reaction score
0
Points
1
you have to use foundry to modify experationdate
 

soccorio

Basic
Joined
30.11.21
Messages
40
Reaction score
12
Points
8
Join my group if u dont know who i m do ur homework,

Dont believe all posting here about foundary and x2 x3
 
Top Bottom