Quote:
Originally Posted by epicmarket
Biggest mistake i made when i got into carding was believing the bullshit that i needed to over complicate things. What normal buyer uses anti detect, proxys, vms, canvas spoofers, etc etc? None
You buy cards you get card info, ip and useragent. If you have a good supplier you get get cookies too. You cannot match perfectly info that you don't get when you buy a card. fingerprints exact ip etc isn't possible. Don't add more links in the chain as each one adds a vulnerability.
buy a mobile phone and place orders. Its not rocket science. Learn what bins and sites work
|
over email you can fingerprint user
with card you get email
all depend on your skills
using this method bypass a lot of security...
all is not perfect you right but a lot of info is added in your mask, just beginning from 1 card with an email attached
""As more and more transactions are app based and we see rapid development of new ways to make payments there was a need for an updated version of 3-D Secure that could deal with this, which is 3-D Secure version 2.
What will change
One of the core differences is that the issuer can use a lot of data-points from the transaction to determine the risk of the transaction (risk-based analysis). For low-risk transactions, issuers will not challenge the transaction (e.g. not sending an SMS to the cardholder) although authenticating the transaction (frictionless). Inversely, for high risk transaction, issuers will require the cardholder to authenticate with an SMS or biometric means (challenge). This can then result in a frictionless authentication, which doesn't involve the consumer to be redirected. In case the consumer is using an app this also applies. In case a challenge is required by the issuer this can be handled inside the app. This greatly improves the user experience and will increase conversion.
Separately the Strong Customer Authentication (SCA) required in Europe by September 14th, 2019 as specified in PSD2 will result in a substantial increase in the number of transactions requiring the use of 3-D Secure authentication. The use of 3-D Secure version 2 should limit the potential negative impact on conversion as much as possible.
In short 3-D Secure version 2 means:
You will need to implement 3-D Secure before September 14th, 2019 if your transactions fall within the EU PSD2 SCA guidelines (in case you don't already support 3-D Secure).
You are advised (and for some are required) to submit additional data points to support the risk assessment performed by the issuer in case of 3-D Secure version 2
You might need to update your privacy policy with regards to GDPR as you might be sharing additional data-points with 3rd parties
A much better user experience for your consumers
The flow with the redirection for 3-D Secure version 2 could potentially only involve a page that allows the issuer to collect data from the consumers device without any user interaction. This is called a MethodURL flow in the 3-D Secure version 2 documentation. We have chosen to handle this flow on our hosted payment pages to reduce the implementation impact on you. This means that redirection will not always result in a so called Challenge towards the consumer and could still be considered friction-less in the 3-D Secure version 2 terminology. The statuses for each of the flows are identical with REDIRECTED for the flow that involves redirection and all the other possible statuses, like REJECTED, PENDING_APPROVAL, CAPTURE_REQUESTED, etc.""
skills for making people fingerprint to sucess will become normal soon, i mean is already the case but is looking like some don't see
just 1 of the way they can detect you and is not new
https://arstechnica.com/information-...iple-browsers/
to understand and begin to hack something from zero knowledge
take a real card do some card order from different real card and intercept transaction from that type (over a page) of transaction
with simple open source tool you can know what fingerprint they ask for exactly
then you can make your URLmethod with a simple page hosted to collect data needed from your victim
without be a programmer you make a URLfingerprintCatcher just using same methods