Re: Package Proposal: Magnetic Stripe Card

Sounds great, just do the standard procedure thang on package proposals and I'm sure it will fit. I think a good name would be Services_MagneticStripe or something along those lines. This one is a tricky one to name. Greg Mitchell Perilstein wrote:

When there is a card-present transaction with a financial transaction card, the card swipe device returns a string containing the data on the card's one, two, or three magnetic tracks. A client browser can capture the swipe string and post it to an application server, where it can be processed. I'm starting work on a PEAR class that takes such a string, parses it, verifies the various checksums, then makes the data components available. Roughly like this: class MagStripeCard extends PEAR { object MagStripeCard($string) {} // Does parse and checksums;

				    // ...returns self or PEAR_Error.
  string getPAN() {}		    // primary account number
  string getName() {}		    // account holder name
  string getExpireMonth() {}	    // two characters	
  string getExpireYear() {}	    // two characters
  string getServiceCode() {}	    // service code
  string getPVKI() {}		    // PIN Verification Key Indicator
  string getCVV() {}		    // Card Validation Value
  string getPVV() {}		    // PIN Verification Value

// etc... } * References * * Magnetic Stripe Card Standards - Card Reading * http://www.magtek.com/documentation/public/99800004-1.pdf * * Application Note - Character Conversion * http://www.magtek.com/documentation/public/99875065-4.pdf