search for: cvv

[This email is either empty or too large to be displayed at this time]

I'm trying to figure out if a file has changed since the last rsync call. I use the following command line: rsync -cvv /mnt/xxx/vol1/dbase/100/kunden.dbf /mnt/label | grep "^total: " | sed -e 's/.* data=//' This gives a 0 if the file is unchanged and the file size if the file has changed. Adding the "dry-run" option "n" to the command line always gives a 0. I wonder if this...

...d_session_data_to_account(account) #adds the impl-specific things to the account if(!@credit_card.blank?) card = CreditCard.new do |cc| cc.account_type = @credit_card[:type] cc.account_name = @credit_card[:name] cc.account_number = @credit_card[:number] cc.cvv = @credit_card[:cvv] cc.account_expiration = @credit_card[:expiration] cc.address = @credit_card[:address] cc.city = @credit_card[:city] cc.state = @credit_card[:state] cc.zip = @credit_card[:zip] cc.country = @credit_card[:country] cc.phone =...

...successfully accepted into the syste; decline, the transaction was declined; baddata, invalid parameters passed; and error, system error when processing transaction. For decline types, the transaction can be declined for a number of reason, from bad card number to insufficient funds, to bad AVS or CVV matching, and a few other reasons. Similarly, there are several bad-data and error types possible. # The question Is there a generally accepted "best practice" regarding what level of information should be divulged to the would-be customer if their card is declined? Surely, they shoul...

...vice? heres my validation method so far: def validate_on_create # validate that the credit card authorization is successful auth = CreditCard.authorize(self, :card => card_number, :expiration => card_exp, :cvv => card_cvv) if auth[:result] == ''A'' self.authcode = auth[:authCode] else errors.add :card_number, ''^The credit card was declined.'' end end -- Posted via http://www.ruby-forum.com/.

...y by reading credit card numbers off the web, and punching them into the POS machine on their desk. My plan is this: 1) protect against casual hijacking of the CC numbers by using 2-way encryption, storing the salt somewhere other than in the database 2) delete the encrypted card number and CVV2 after each order is marked as paid Does anyone have any thoughts? Better ways to do this? Warnings? Cheers, Steven Luscher (BDes Hons., Provisional RGD) { c = Steven Luscher Design; w = http://www.stevenluscherdesign.com/ e = design@stevenluscherdesign.com; p = 604.628.9813...

Hi all. I have never implemented online payment and it''s the only thing that keeps me from accepting a project for a UK based client. (I must reply quickly!) While I can afford spending an extra week - or 2 - to learn/try/tune the payment system, I must be sure to succeed before I accept the contract. If you''ve already been through that path, any hints, links and/or