Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter isodeveloper

    (@isodeveloper)

    how do you get woo commerce to reject a credit card. If example Chase starts their credit cards off with 412345, the checkout field has to do an if then else, saying if Credit Card Field 1 = (whatever value you enter into the if then else) in this case 412345, display “Invalid credit card”.

    if credit field1 = “12345” then display “invalid credit card”
    if credit field1 = “12346” then display “invalid credit card”

    The credit card entering by the person would be broken down into the first six positions which is the bin and then the rest is whatever. But the problem is that there’s plugins avail. that will do a calculation and say the card is invalid based on all the numbers. Then your back to square 1. Unless there’s a way of pulling the first six data positions such as 4111 1111 1111 1111. The modules will see if the credit card number is valid based on a calculation on all 16 numbers. But how do you get it to pull the first 6 digits. If you setup two fields for the credit card number then you have to manually process them because the data passed onto the gateway will go ?????. So you have to get the it do pull the first 6 digits from someone entering 4111111111111111 and pull the first 6 digits out of it.

    We’ve searched the entire forum and found nothing. Payment providers some have them and say you can put them in, and then they do a 180 and say you could get your account closed for it. They pull that typical bs because they want to suck more money from you.

    Thread Starter isodeveloper

    (@isodeveloper)

    Wish it was that easy, we checked the entire forum. Right now we downloaded every PDF about woocommerce and found nothing.

    Thread Starter isodeveloper

    (@isodeveloper)

    Hey James. Right now we are using plugins to control the buyers into not buying everything in stock and then traying to scam us etc. We just started out, right now we are processing credit cards manually because our provider is back in the 80s and just got a 3rd party developer to get a plug in for them. We dont even want it even hit the gateway because the first section of the credit card input, would be the “bin list” of credit card numbers that we would immediately reject. We check every credit cards bin lookup and if it matches the bank we dont want to take, we want to add the number to some sort of list that the next time it will reject. But the plugins we are using are more towards controlling the buyer.

    Thread Starter isodeveloper

    (@isodeveloper)

    As far as the bin management, there should be a plug in based on the field of the credit card number before it passes it onto the gateway. Giving some sort of “invalid card number”, if you do not want to accept a specific brand type based on the bin number. Thats a simple if than else command line and the credit card number field is a variable.

    If “credit card” = this bin # then reject, else send it off to the gateway for processing.

    There would be a bunch of those if then else statements for each bin number or like a IP Ban on a website CPANEL have a box that the merchant can enter with the bin numbers he does not want to accept, or have a simple way the merchant can open the php file and manually add the if then else statements as they become aware of it.

    If processors are already doing it, or starting to do it, then is should be or a good idea to have that as a plug in. Im sure were not the first ones to bring this up.

    Again thanks guys.

    Thread Starter isodeveloper

    (@isodeveloper)

    Didnt state anything about the ship and tax. What we think what we were referring to is the ability to add a “service fee” to selected states. The service fee would be for items being shipped to states that have alot of fraud or purchases over a fixed amount.

    Say, you get alot of problems from the state of texas, any order from texas would have a service fee applied vs other states that dont. Additionally the same type of service fee would be applied to any large ticket orders that the merchants wants to obtain a signature confirmation or restricted delivery. Small ticket items would be unattractive to the buyer if they had to incur the same type of charge.

    Thread Starter isodeveloper

    (@isodeveloper)

    Thinking it this way, is there any procedure that can be done before the credit card hits the gateway, where the credit card field has a series of if, then, statements, before hitting the gateway. Prior to the customer hitting the payment gateway, there could be statements added to the checkout (credit card number field) that says if “credit card number field” equals “first six digits of a credit card that they dont accept” display –Invalid Credit Card–. When the merchant uncovers more numbers of the credit card brand, the merchant can just add the if then statement to the file that checks the credit card field.

    Is there a developer that can get this done. Thanks guys.

    Thread Starter isodeveloper

    (@isodeveloper)

    That’s a pretty good idea. Just do the opposite of what is says. I think breaking the first field into the first 6 positions of the credit card number (thats how you search for a bin lookup) xxxxxx-xxxx-xxxx-xx and check the first field against a list of numbers that equal the a preset number. Some sort of file that can be updated as the merchant goes along without hitting the gateway. The list can be updated manually as they find more and more card numbers they dont reject and you dont hit the gateway and get charged the transaction fee. As you know anytime you hit the gateway you get hit with the transaction.

    Make the credit card field the format above or have the script search the first six positions of the credit card number and reject if it matches the first six positions. before hitting the gateway.

    Wish people can just do what it says, but there are too many buyers out there that know what it says and do it on purpose to see if they can get away with it and when you call them out, they run and hide like cowards because they know what it says and they just go ahead and do it. As if a merchant is going to violate their own policies.

    Thanks dude appriciate your input.

Viewing 7 replies - 1 through 7 (of 7 total)