Patent Publication Number: US-9406011-B2

Title: Virtual wallet

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This Application is a continuation-in-part application of U.S. patent application Ser. No. 13/904,939, filed on 29 May 2013, which claims the benefit of U.S. Provisional Application No. 61/689,083 filed on 29 May 2012, U.S. Provisional Application No. 61/796,594, filed on 15 Nov. 2012, U.S. Provisional Application No. 61/848,581 filed on 7 Jan. 2013, U.S. Provisional Application No. 61/849,213 filed on 22 Jan. 2013, U.S. Provisional Application No. 61/850,866, filed on 25 Feb. 2013, and U.S. Provisional Application No. 61/818,831, filed on 2 May 2013, all of which are incorporated herein in their entireties by this reference. 
     This Application also claims the benefit of U.S. Provisional Application No. 61/903,302, filed on 12 Nov. 2013, which is incorporated in its entirety by this reference. 
    
    
     TECHNICAL FIELD 
     This invention relates generally to the field of bank cards and, more specifically, to a new and useful payment card and associated methods in the field of bank cards. 
    
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         FIG. 1  is a schematic representation of a payment card; 
         FIGS. 2A and 2B  are schematic representations of the payment card; 
         FIG. 3  is a schematic representation of a variation of the payment card; 
         FIG. 4  is a schematic representation of a variation of the payment card; 
         FIG. 5  is a schematic representation of a variation of the payment card and a magnetic stripe reader; 
         FIG. 6  is a flowchart representation of a first method; 
         FIG. 7  is a flowchart representation of a variation of the first method; 
         FIG. 8  is a flowchart representation of a variation of the first method; 
         FIG. 9  is a flowchart representation of a second method; 
         FIG. 10  is a flowchart representation of a variation of the second method; 
         FIG. 11  is a flowchart representation of a variation of the second method; 
         FIG. 12  is a flowchart representation of a third method; 
         FIG. 13  is a flowchart representation of a variation of the third method; 
         FIG. 14  is a flowchart representation of a fourth method; 
         FIG. 15  is a flowchart representation of a variation of the fourth method; 
         FIG. 16  is a flowchart representation of a fifth method; and 
         FIG. 17  is a flowchart representation of one variation of the fifth method. 
     
    
    
     DESCRIPTION OF THE EMBODIMENTS 
     The following description of the embodiments of the invention is not intended to limit the invention to these embodiments, but rather to enable any person skilled in the art to make and use this invention. 
     1. Payment Card 
     As shown in  FIGS. 1 and 2A , a payment card includes: a sheet  110  comprising a first icon  111  and a second icon  112 ; a transducer  150  arranged within the sheet  110  and configured to output a voltage in response to an impulse on a surface of the sheet  110 ; a wireless communication module  120 ; a first input region  131  adjacent the first icon  111 ; a second input region  132  adjacent the second icon  112 ; a magnetic stripe emulator  140 ; and a processor  160  arranged within the sheet  110  and configured to transition from a passive state to an active state in response to receiving a voltage output from the transducer  150 , to receive a first magnetic sequence command associated with a first payment method and a second magnetic sequence command associated with a second payment method through the wireless communication module  120 , to assign the first payment method to the first input region  131  and the second payment method to the second input region  132 , to receive a selection for the second payment method from the second input region  132  in response to an input adjacent the second icon  112 , and to control the magnetic stripe emulator  140  according to the second magnetic sequence command in response to receiving the selection for the second payment method. 
     Generally, the payment card  100  functions to consolidate multiple plastic payment cards into a single physical card that can imitate payment functionalities of the multiple plastic payment cards through manipulation of a magnetic stripe emulator. For example, the payment card  100  can imitate a user&#39;s debit card issued through a bank, a user&#39;s primary credit card issued by a preferred credit card company, and a user&#39;s secondary credit card issued by another credit card company by selectively driving the magnetic stripe emulator  140  according to a unique magnetic sequence command associated with each individual card. The payment card  100  can additionally or alternatively imitate a gift card, an identification (i.e., ID) card (e.g., a driver&#39;s license), a loyalty card, a door or gate access card, or any other individual card containing data in a magnetic stripe. The payment card  100  can define a form factor substantially similar to that of a standard plastic payment card, that is, 3.370″ (850.60 mm) wide by 2.125″ (53.98 mm) tall by 0.06″ thick. 
     The payment card  100  can also interface with a mobile computing device, via the wireless communication module  120 , to authenticate an upcoming payment attempt, to download magnetic sequence commands of a subset of available payment methods, and/or to upload a current payment selection for display on the mobile computing device. For example, the mobile computing device can be a smartphone or tablet, and a native application executing on the smartphone or tablet can manage entry of new plastic bank cards, selection of magnetic sequence commands to upload to the payment card  100 , and authentication of upcoming payments. The payment card  100  can also include the set of input regions to enable a user to select a particular payment method to imitate, to enter a passcode to authenticate an upcoming payment attempt, and/or to select a particular operating mode of the payment card  100 , such as a timed payment mode (described below). Therefore, the payment card  100  can—separately or in conjunction with a native application executing on a mobile computing device—consolidate multiple plastic bank cards into a single dynamic payment card of a similar form factor, thereby substantially eliminating a need for a user to carry multiple (i.e., more than one) bank cards, gift cards, and/or identification cards, etc. at any given time. 
     The sheet  110  of the payment card  100  includes a first icon and a second icon. Generally, the sheet  110  functions as a housing for the various components of the payment card  100 , including the transducer  150 , the wireless communication module  120 , the input regions, the processor  160 , etc. The sheet  110  can therefore define the external dimensions of the payment card  100 , and the sheet  110  can therefore be of a form factor substantially similar to that of a standard plastic bank card. In one implementation, the sheet  110  includes a front layer  116  and a back layer  117  that sandwiches various components of the payment card  100 . For example, the transducer  150 , the wireless communication module  120 , the input regions, the processor  160 , and a battery can be mounted or constructed on a flexible circuit board  180  (shown in  FIG. 2A ) that is sandwiched between the front layer  116  and the back layer  117  to define an external geometry that is 3.370″ (850.60 mm) wide by 2.125″ (53.98 mm) tall by 0.06″ thick. Alternatively, the flexible circuit board  180  can be reaction injection molded between (or inside) the front layer  116  and the back layer  117 , and a glass card layer can be laminated over the front layer. However, the sheet  10  can be assembled in any other suitable way. The sheet no can also define a fluid-tight or dustproof housing that can seal any of the foregoing components against contamination by fluid or particulate ingress. 
     The sheet  110  also defines the first icon  111  and the second icon  112  that are visually and/or tactilely distinguishable by a user. In one example, as in the foregoing implementation, the first icon  111  and the second icon  112  can be printed on the front layer  116 . In this example, the front layer  116  can be transparent or translucent, and the first and second icons can be printed on an interior surface of the front layer  116  to protect the first and second icons from wear. In another example, the first icon  111  and the second icon  112  can be embossed or debossed on the front layer  116 , such as through stamping, molding, etching, or bulk micromachining. 
     The first icon  111  and the second icon  112  can include alphanumeric text. For example, the first icon  111  can include a printed, embossed, and/or debossed “A”, and the second icon  112  can include a printed, embossed, and/or debossed “B”. In a similar example, the first icon  111  can include a printed, embossed, and/or debossed “1”, and the second icon  112  can include a printed, embossed, and/or debossed “2”. The sheet  110  can also define additional icons, such as a third icon including a printed, embossed, and/or debossed “C” or 3″, a fourth icon including a printed, embossed, and/or debossed “D” or 4″, etc. aligned with a third input region and/or a fourth input, etc. Alternatively, the first icon  111  and the second icon  112  can include descriptions or other symbols. For example, The sheet no can define the first icon  111  that reads “Credit,” the second icon  112  that reads “Debit,” a third icon that reads “Gift,” and a fourth icon that reads “Driver&#39;s License.” However, the sheet no can define the first icon in, the second icon  112 , etc. that are of any other form and printed or formed on the sheet no in any other suitable way. 
     As described above, the sheet no can includes two (or more) layers that house or “sandwich” various components of the payment card  100 . Each of the two layers can be of the same or similar material, such as polyvinyl chloride (PVC), polyethylene terephthalate (PETG), or another polymer or silicone-based elastomer. Alternatively, the layers can be of disparate materials. For example, the sheet no can include a front layer  116  of chemically-strengthened alkali-aluminosilicate glass and a back layer  117  of polyurethane. The assembly of layers (i.e., the sheet  110 ) can also be flexible to approximate the “feel” of a standard PETG or PVC plastic bank card. The layers can be assembled with an adhesive, through hot or cold lamination, through surface activation, or by any other suitable process or technique. However, the sheet  110  can include any other materials, can define the first icon  111  and the second icon  112  in any other way, can be of any other form or geometry, and can feature any other mechanical property. 
     The transducer  150  of the payment card  100  is arranged within the sheet no and is configured to generate a voltage output in response to an impulse on a surface of the sheet  110 . Generally, the transducer  150  functions to convert a mechanical impulse (e.g., a tap) on a surface of the payment card  100  into an electrical signal of magnitude sufficient to ‘wake’ the processor  160  from a passive mode to an active mode. For example, the transducer  150  can be piezoelectric transducer electrically coupled to an ‘wake’ interrupt-enabled input pin of the processor  160 , wherein the transducer  150  outputs a voltage greater than 2.5V, which triggers the processor  160  to switch from a passive, low-current draw mode to an active, higher-current draw mode. 
     In the implementation in which the sheet  110  includes two layers, the transducer  150  can be arranged between the two layers, such as on the flexible circuit board  180  housed between the two layers. The transducer  150  can therefore be fabricated or installed across an inner broad face of one layer of the sheet  110 , such as across a portion of the inner broad face of the back layer  117  of the sheet  110 . The transducer  150  can also be aligned with a region of the sheet  110  that is substantially tactilely accessible to a user when the payment card  100  is held. For example, the form factor of the payment card  100  can be such that a user instinctively grasps the top and bottom long edges of the card between the thumb and the index and middle fingers of one hand and taps the card near the center of its broad face with the index finger of the other hand to wake the card from the passive setting. In this example, the transducer  150  can be arranged near the center of the broad face of the card. 
     Furthermore, the transducer  150  can be arranged proximal a portion of the payment card  100  likely to exhibit substantial deflection in response to a typical impulse. The transducer  150  may output a voltage potential proportional to its deflection, and the transducer  150  may therefore be arranged proximal a region of the sheet  110  that exhibits maximum deflection under impact. In one example implementation in which the payment card  100  is of a form factor similar to that of a standard plastic bank card, when a user grasps the top and bottom long edges of the card between the thumb and the index and middle fingers of one hand and taps the card near the center of its broad face with the index finger of the other hand, the sheet  110  may exhibit maximum deformation along a line substantially parallel to and equidistant from the long edges of the sheet no. In a similar example implementation, when the user grasps the left and right short edges of the card between the thumb and the index and middle fingers of one hand and taps the card near the center of its broad face with the index finger of the other hand, the sheet  110  may exhibit maximum deformation along a line substantially parallel to and equidistant from the short edges of the sheet  110 . Therefore, the transducer  150  can be substantially aligned with the center of the broad face of the sheet  110  to substantially ensure that an impact (e.g., tap) on the payment card  100  will yield a voltage spike, from the transducer  150 , of a magnitude sufficient to wake the processor  160  from the passive setting to the active setting substantially regardless of how the card is held by the user. However, the transducer  150  can be any other type of transducer arranged in any other way within the payment card  100 . 
     The wireless communication module  120  of the payment card  100  functions to establish a wireless connection with a mobile computing device (e.g., a smartphone, a tablet, or any other external device) to enable wireless data transfer to the payment card  100 . Generally, the wireless communication module  120  can enable communications between the payment card  100  and the mobile computing device to download payment method data (e.g., magnetic sequence commands for various payment methods) and to authenticate use of the payment card  100  to complete a transaction, as described below. The wireless communication module  120  can include both a wireless receiver and a wireless transmitter that enable two-way communication between the payment card  100  and the mobile computing device. For example, the wireless communication module  120  includes a short-range wireless transceiver, such as a Bluetooth communication module. However, the wireless communication module  120  can implement any other suitable type of wireless communication protocol, such as Wi-Fi, cellular, or ZigBee. 
     The wireless communication module  120  can be fabricated or installed on the flexible circuit board  180  and can include a radio antenna  122  tailored to a particular wireless communication frequency. For example, the wireless communication module  120  can include a Bluetooth transceiver configured to exchange data wirelessly in the industrial, scientific and medical (ISM) radio bands between 2400 and 2480 MHz, and the radio antenna  122  can be sized for the frequency band between 2400 and 2480 MHz. The radio antenna  122  can be integrated into the flexible circuit board  180  as a trace and can include a linear segment. Because the payment card  100  may flex, such as under an impact to wake to processor or to mimic a standard plastic bank card as described above, the linear segment of the radio antenna  122  may deform, thereby affecting an effective length of the antenna. Therefore, the linear segment can be arranged proximal a region of the sheet no subject to minimal relative deflection, such as adjacent and parallel to a short edge of the sheet  110  (i.e., perpendicular to a long edge of the sheet  110 ). The wireless communication module  120  can also include a crystal oscillator installed or fabricated on the flexible circuit board  180 . Flexure of the sheet  110  can induce strain across the crystal oscillator, thereby modifying a clock speed of the crystal oscillator  121 . For example, strain across the crystal oscillator  121  can reduce the clock speed of the crystal oscillator  121  from 2400 MHZ to 2390, which falls outside of the ISM range suitable for Bluetooth communication. Therefore, the crystal oscillator  121  can be arranged proximal a region of the sheet  110  subject to minimal relative deflection, such as adjacent (and parallel) to a short edge of the sheet  110 . However, the wireless communication module  120  can include any other type of antenna or oscillator arranged in any other way. 
     In one alternative implementation, the wireless communication module  120  can include an optical sensor, such as a photoresistor or photodiode, to enable optical transmission of data from the mobile computing device to the payment card  100 . For example, to upload a magnetic sequence command for a payment method to the payment card  100 , a user can place the payment card  100  over a screen of a smartphone with a long edge aligned with a long edge of the screen and a short edge aligned with a short edge of the screen, and a native application executing on the smartphone can switch a set of pixels adjacent the optical sensor in the payment card  100  between black (e.g., representing a ‘0’ bit) and white (e.g., representing a ‘1’ bit) states to transmit data to the payment card  100 . Furthermore, the wireless communication module  120  can include an optical transmitter, such as an infrared light-emitting diode (LED), to enable optical transmission of data from the payment card  100  to the mobile computing device. However, the wireless communication module  120  can receive and/or transmit data from and/or to the mobile computing device over optical communication in any other suitable way. 
     In one alternative implementation shown in  FIG. 4  the wireless communication module  120  can include an acoustic transducer, such as a microphone, configured to receive audio signals and to convert audio signals into electrical impulses. For example, to upload a magnetic sequence command for a payment method to the payment card  100 , a user can place the payment card  100  adjacent a speaker of a smartphone, and a native application executing on the smartphone can control a speaker driver to transmit card data acoustically to the payment card  100 . The wireless communication module  120  can further include a speaker and speaker driver to enable similar acoustic communication of data from the payment card  100  to the mobile computing device. In this implementation, the processor  160  can pass digital data stored in memory through an audio CODEC where it is converted to an analog signal. The analog signal can then amplified through a speaker and transmitted wirelessly as sound waves. The analog signal can be transmitted according to frequency shift keying (FSK), on-off keying (OOK), or phase shift keying (PSK) techniques, such as with around a frequency of 20 kHz. However, the wireless communication module  120  can function in any other way and include any other suitable component to enable wireless communication of data between the payment card  100  and the mobile computing device. 
     The first input region  131  and the second input region  132  of the payment card  100  are arranged within the sheet  110  adjacent the first icon  111  and adjacent the second icon  112 , respectively. Generally, the first icon  111  and the second icon  112  function to capture inputs on the sheet  110  to enable user selection from available payment methods and to enable authentication of the payment card  100  for a payment, as described below. As described above, the payment card  100  can include additional input regions, such as a third input region aligned with a third icon and a fourth input region aligned with a fourth icon. 
     In one implementation, the first input region  131  includes a first touch sensor, and the second input region  132  includes a second touch sensor, and the first and second touch sensors can be discrete. Alternatively, the first and second touch sensors can be physically coextensive, wherein a single touch sensor can be arranged behind the first icon  111  and the second icon  112  to capture inputs over both the first icon  111  and the second icon  112 . The first input region  131  and/or the second input region  132  can therefore include a capacitive touch sensor, an optical touch sensor, a resistive touch sensor, or any other suitable type of touch sensor. Furthermore, as in the implementation described above in which the sheet  110  includes a front layer  116  and a back layer  117  that sandwich a flexible circuit board  180 , the first touch sensor and the second touch sensor can be installed or fabricated on the flexible circuit board  180  and configured to detect a touch on the surface of the sheet no through the front layer  116 . However, the first and second touch sensors can be arranged in any other way and can function in any other way to detect a touch on a surface of the sheet no. 
     In another implementation, the first input region  131  includes a first mechanical switch, and the second input region  132  includes a second mechanical switch. The first and second mechanical switches can each be a dome switch or any other suitable type of mechanical momentary switch. The dome switch can be installed on the flexible circuit board  180 , the flexible circuit board  180  can be installed or ‘potted’ over an interior broad face of a back layer  117  of the sheet  110 , and the front layer  116  of the sheet  110  can be flexible (e.g., a silicone-based elastomer) and overlaid on top of the flexible circuit board  180  and mechanical switches such that a user may depress the first icon  111 , the forward-facing layer of the sheet no may deform locally, and the first mechanical switch may close to trigger an input. In this configuration, the user may similarly depress the second icon  112 , the forward-facing layer of the sheet  110  may deform locally, and the second mechanical switch may close to trigger a second input. However, the first input region  131  and the second input region  132  can include any other type of contact or contactless sensor to detect an input on a surface of the sheet  110  proximal the first icon  111  and the second icon  112 . 
     The magnetic stripe emulator  140  of the payment card  100  functions to imitate one or more tracks of a static magnetic stripe of a standard plastic bank card. As shown in  FIG. 2A , the magnetic stripe emulator  140  can include a set of (i.e., one or more) electromagnetic coils  141  controlled by the processor  160  through a coil drive circuit  142  to output data in the form of changing magnetic field polarities. For example, as shown in  FIG. 2A , the magnetic stripe emulator  140  can include a set (i.e., one or more) coil  141  and a coil drive circuit  142  that includes a transistor  144 , a resistor  145 , and a diode  146 . A voltage on the gate of transistor can enable current to flow from a battery  170  to a coil, and the resistor can enable a drive current through the coil. The diode can be coupled in parallel with the coil to protect against voltage pulses inherent in coil inductance. The coils drive circuit can additionally or alternatively include an H-bridge to drive the coil in both positive and negative directions to reverse a magnetic field output. 
     Generally, the processor  160  can control the coil drive circuit according to a magnetic sequence command to switch a polarity of one or more coils in the magnetic stripe emulator  140 . For example, the coil drive circuit can pass current through a coil of the magnetic stripe emulator  140  in a first direction to represent a ‘0’ bit, and the coil drive circuit can switch the direction of current passing through the coil to represent a ‘1’ bit. Each magnetic stripe sequence command can include a series of bits (i.e., ‘0’s and ‘1’s) representing a set of bits in a static magnetic stripe in a corresponding plastic bank card, and the processor  160  can control the coil drive circuit according to the bits in the magnetic stripe sequence command to enable the magnetic stripe emulator  140  to imitate the corresponding static plastic bank card. 
     In one example implementation, a magnetic sequence command includes data commonly included in a Track 2 standard (i.e., a banking industry magnetic tripe standard) including: a start sentinel (e.g., ‘;); a primary account number (PAN) (e.g., a credit card number); a separator (e.g., ‘=’); an expiration date (e.g., alphanumeric characters in the form of ‘YYMM’); a service code (e.g., a first digit specifying interchange rules, a second digit specifying authorization processing, a the third digit specifying a range of services); discretionary data (e.g., a card verification code (CVV); an end sentinel (e.g., ‘?’); and/or a longitudinal redundancy check (LRC) (e.g., a validity character calculated from other data on the track). The processor  160  can control the magnetic strip emulator, through the coil drive circuit, to sequentially output bits corresponding to the any of the foregoing data. The processor  160  can also control a first coil of the magnetic stripe emulator  140  according Track 2-type data and a second coil of the magnetic stripe emulator  140  according to another data structure, such as Track s-type or Track 3-type data. 
     The processor  160  and the magnetic stripe emulator  140  can also cooperate to detect a read head of a magnetic stripe reader (shown in  FIG. 5 ) as the payment card  100  is swept along the read head, and the processor  160  can drive the set of electromagnetic coils, via the coil drive circuit, according to the position and/or velocity (i.e., speed and direction) of the magnetic stripe emulator  140  relative to the read head as the payment card  100  is passed through the magnetic stripe reader. In one example, the magnetic stripe emulator  140  can include a first coil configured to sense a read head and a second coil to output bits according to a magnetic sequence command. In another example, the processor  160  can cooperate with a coil of the magnetic stripe emulator  140  to detect a read head, and, once a read head is detected, the processor  160  can control the coil via the coil drive circuit to output bits according to a magnetic sequence command. By detecting a read head through the magnetic stripe emulator  140 , the processor  160  can time or ‘clock’ sequential bits output by the magnetic stripe emulator  140  such that the payment card  100  appears to a standard magnetic stripe reader as a typical static plastic bank card and such that a standard magnetic stripe reader can detect and decipher magnetic pulses from the magnetic stripe emulator  140  (substantially) without modification. The processor  160  can thus “couple” the magnetic tripe emulator to a read head of a magnetic stripe reader as the payment card  100  is swiped through the magnetic stripe reader, as shown in  FIG. 5 . However, the magnetic stripe emulator  140  can include any other number of coils configured to detect or output any other data to a magnetic read head in any other suitable way. 
     The magnetic stripe emulator  140  can also be arranged parallel to and offset from a long edge of the polymer layer. For example, the magnetic stripe emulator  140  can be arranged in a location similar to a standard static magnetic stripe position on a standard plastic bank card. Furthermore, the set of electromagnetic coils of the magnetic stripe emulator  140  can be of a length and width similar to that of a standard static magnetic stripe on a standard plastic bank card. For example, the coils of the magnetic stripe emulator  140  can be arranged approximately 0.223″ (5.66 mm) from each short edge of the payment card  100  and can be approximately 0.375″ (9.52 mm) in width. Such arrangement of the magnetic stripe emulator  140  in the payment card  100  may thus enable the payment card  100  to be read by standard magnetic stripe readers already in use to read standard (i.e., static) plastic bank cards. However, the magnetic stripe emulator  140  can be arranged in any other way, can be of any other form or geometry, and can function in any other way to imitate a static magnetic stripe of a plastic bank card. 
     The processor  160  of the bank card is arranged within the sheet  110  and is configured to transition from a passive setting to an active setting in response to receiving a voltage output from the transducer  150 , to receive the first magnetic sequence command associated with a first payment method and the second magnetic sequence command associated with a second payment method through the wireless communication module  120 , to assign the first payment method to the first input region  131  and the second payment method to the second input region  132 , to receive the selection for the second payment method from the second input region  132  in response to an input adjacent the second icon  112 , and to control the magnetic stripe emulator  140  according to the second magnetic sequence command in response to the selection for the second payment method. Generally, the processor  160  function to control the magnetic stripe emulator  140  according to a tap on the payment card  100 , available payment methods stored on the payment card  100 , availability of a wireless connection with a mobile computing device, inputs on the input regions, and/or selection of a payment method through the input region, etc. 
     As described above the processor  160  can be electrically coupled to the transducer  150  via a trace on the flexible circuit board  180 . In particular an output of the transducer  150  can be electrically coupled to an interrupt input of the processor  160  such that a voltage spike generated by the transducer  150  in response to a tap on a surface of the payment triggers the processor  160  to switch from a passive (i.e., low-power) state to an active setting in which the processor  160  monitors various inputs from the wireless communication module  120 , the input regions, the magnetic stripe emulator  140  (e.g., to detect a read head of a magnetic stripe reader), etc. and generates various outputs to control the magnetic stripe emulator  140  and/or other components of the payment card  100 . For example, when the processor  160  receives a voltage spike from the transducer  150  and transitions from the passive setting to the active setting, the processor  160  can toggle one or more LEDs within the payment card  100  to provide visual feedback to a user that the payment card  100  is activated or ‘ON.’ 
     Alternatively, the processor  160  can be coupled to another input mechanism on the payment card, such as a mechanical switch, a strain gauge, a light or infrared detector, etc., and the processor can transition out of a passive setting in response to an input or output state change of the input mechanism. However, the processor  160  can interface or receive an output from any other suitable component within the payment card  100  to initiate an active mode or a payment mode on the payment card  100 . 
     Once in the active setting, the processor  160  can interface with the wireless communication module  120  to attempt wireless communication with the mobile computing device. In one implementation, the processor  160  cooperates with the wireless communication module  120  to identify and connect to a paired mobile computing device (e.g., wireless-enabled a smartphone or tablet). For example, the wireless communication module  120  can include a Bluetooth module, the processor  160  can store a unique Bluetooth serial identification number of the paired mobile computing device, and the processor  160  can cooperate with the wireless communication module  120  to identify the mobile computing device, within range of the payment card  100 , via the unique Bluetooth serial identification number. In this example, the wireless communication module  120  can assume a ‘master’ function to identity one or more other Bluetooth modules within range, identify a particular Bluetooth module of the paired mobile computing device based on a stored identifier of that Bluetooth module, and establish a connection with the particular Bluetooth module in a ‘slave’ function. Because the mobile computing device may have a more precise clock than that coupled to the wireless communication module  120 , once a connection is established between the payment card  100  and the mobile computing device, the mobile computing device can assume the master function and the payment card  100  can assume the slave function. Once a connection is established between the payment card  100  and the mobile computing device, the processor  160  can control one or more LEDs within the payment card  100  to provide visual feedback to a user that the connection was successful. For example, the processor  160  can flash a green LED three times once the connection is established. Similarly, the processor  160  can flash a red LED three times if a wireless connection with the particular mobile computing device fails. However, the processor  160  and the wireless communication module  120  can cooperate in any other way to identify, pair, and communicate with a particular mobile computing device within range. 
     Once the mobile computing device is identified and a wireless connection is established between the wireless communication module  120  and the mobile computing device, the processor  160  can cooperate with the wireless communication module  120  to download a magnetic sequence command associated with a particular payment method from the mobile computing device. For example, a native application executing on the mobile computing device can capture, store, and handle information for various cards. In this example, for a single bank card, the native application can store an issuing entity (e.g., a bank), an assignee (i.e., a name on the bank card), a card number, an expiration date, a verification number (e.g., a CVV number), a rewards account or username associated with the bank card, a magnetic sequence stored on a static magnetic stripe, etc. Furthermore, in this example, the processor  160  can communicate with the mobile computing device, via the wireless communication module  120 , to retrieve relevant information for a particular bank card, such as the magnetic sequence of the particular bank card in the form of a magnetic sequence command. 
     In one example implementation, once a wireless connection is established between the payment card  100  and the mobile computing device, the processor  160  cooperates with the wireless communication module  120  to synchronize or ‘sync’ with the native application executing on the mobile computing device, wherein the processor  160  downloads pertinent information (i.e., a magnetic sequence command) for each of a number of plastic bank cards corresponding to the number of input regions on the payment card  100 . In one example in which the payment card  100  includes the first input region  131  adjacent the first icon  111  and the second input region  132  adjacent the second icon  112 , the processor  160  can sync with the native application to download a first magnetic sequence command for a first payment method and a second magnetic sequence command for a second payment method. In another example in which the payment card  100  includes the first input region  131  adjacent the first icon  111 , the second input region  132  adjacent the second icon  112 , and a third input region adjacent a third icon, the processor  160  can sync with the native application to download a first magnetic sequence command for a first payment method, a second magnetic sequence command for a second payment method, and a third magnetic sequence command for a third payment method. The magnetic sequence commands downloaded to the payment card  100  from the mobile computing device can include magnetic sequence commands for a default selection of available payment methods, a ranked selection of available payment methods, a manual selection of available payment methods (e.g., a selection entered by a user through an interface within the native application), or any other suitable selection of available payment methods. 
     The processor  160  can automatically sync with the native application once a wireless connection is established between the wireless communication module  120  and the mobile computing device. Alternatively, the native application can push payment method information to the payment card  100  in response to a manual input entered through the native application, or the processor  160  can request a payment method update in response to a manual input on one or more input regions of the payment card  100 . For example, the processor  160  can receive sequence of inputs through the input regions (i.e., the first input region  131 , the second input region  132  and/or any additional input region), correlate the series of inputs with a request to sync with the native application, and transmit a request to the mobile computing device, via the wireless communication module  120 , to sync an updated selection of payment methods. However, the processor  160  can function in any other way to download magnetic sequence commands corresponding to one or more payment methods from the mobile computing device via the wireless communication module  120 . 
     In one alternative described in U.S. Provisional Application No. 61/848,581, which is incorporated in its entirety by reference, the processor  160  can also implement a “quick-sync” feature to download payment method data from the mobile computing device. For example, a user can select a specific payment method for one-time use (i.e., a single active session or one swipe) through the native application, and the wireless communication module  120  can sync with the native application (through the quick-sync feature) once a wireless connection is established to download the specific payment method for one-time use. In this example, the quick sync feature can thus enable the user to communicate instructions to the payment card  100  to emulate a specific payment method for one-time use without changing payment method assignments for the input regions. 
     The processor  160  subsequently functions to assign each payment method—corresponding to a received magnetic sequence command—to one input region on the payment card  100 . In one implementation, the processor  160  receives a first magnetic sequence command corresponding to a first payment method and a second magnetic sequence command corresponding to a second payment method, and the processor  160  subsequently associates the first magnetic sequence command with the first input region  131  (and therefore the first icon  111 ) and associates the second magnetic sequence command with the second input region  132  (and therefore the second icon  112 ). In one example of this implementation, the processor  160  can receive an input on the first input region  131 , correlate the input with a selection for the first payment method, and thus power the magnetic stripe emulator  140  according to the first magnetic sequence command to enable payment with the first payment method, as described below. Subsequently, the processor  160  can receive an input on the second input region  132 , correlate the input with a selection for the second payment method, and thus power the magnetic stripe emulator  140  according to the second magnetic sequence command to enable payment with the second payment method. 
     As described above, the processor  160  can receive a ranked set of payment methods, and the processor  160  can assign the corresponding magnetic sequence commands according to their rankings. For example, the native application can rank three payment methods, including a credit card as a first payment method, a debit card as a second payment method, and a gift card as a third payment method, the processor  160  can receive the ranked set of three payment methods, and the processor  160  can assign the set of payment methods to the first input region  131 , the second input region  132 , and a third input region accordingly. As described below, the native application executing on the mobile computing device can display a virtual representation of the input regions of the payment card  100  and an overlay on top of each virtual input region indicating the particular payment method assigned to each particular input region. The mobile computing device can thus function as a remote display for the payment card  100  to provide visual information pertaining to payment methods assigned to various input regions without necessitating a refreshable display within the payment card  100 . However, the processor  160  can assign payment methods to respective input region in any other way or according to any other rank, schema, or process. 
     Thus, when a user taps on the payment card  100  and the processor  160  wakes from a passive setting, the processor  160  can attempt wireless communication with the mobile computing device through the wireless communication module  120  to authenticate use of the payment card  100 . Generally, the payment card  100  can be linked (i.e., paired) to the mobile computing device, and the processor  160  can require identification of and communication with the mobile computing device before enabling a payment function of the magnetic stripe emulator  140 . For example, the payment card  100  can function under the assumptions that a valid user (i.e., a valid owner) of the payment card  100  will carry both the payment card  100  and the mobile computing device on his person when attempting a transaction and that an invalid user (i.e., a thief) of the payment card  100  may only have the payment card  100  and not the mobile computing device paired with the payment card  100 . Thus, the processor  160  can implement a level of security to prevent fraudulent use of the payment card  100  by necessitating a connection between two components of the payment system (i.e., the payment card  100  and the mobile computing device) substantially likely to be carried together by a valid user but substantially unlikely to be carried together by an invalid user. Furthermore, when the payment card  100  and the paired mobile computing device establish a wireless connection, the payment card  100  can sync with the mobile computing device to download new or updated payment method information (e.g., magnetic stripe sequence commands) from the mobile computing device, such as in response to an automatic sync&#39;ing feature or a manual sync request. 
     Alternatively, if the processor  160  and the wireless communication module  120  fail to establish a wireless connection with the mobile computing device, the processor  160  can suppress a payment function of the magnetic stripe emulator  140  (e.g., by suppressing power to the magnetic stripe emulator  140 ) to prevent use of the payment card  100  in a transaction. However, instances may occur in which a valid user has lost or forgotten the paired mobile computing device, the mobile computing device has ‘died’ or run out of battery charge, or a short-range wireless communication (e.g., Bluetooth) function on the mobile computing device is turned OFF, and the processor  160  can account for these situations by authorizing use of the payment card  100  with a passcode (e.g., a personal identification number or PIN) entered directly into the payment card  100 . For example, the processor  160  can receive a series of inputs entered into the input regions, compare the series of inputs to a passcode stored on the payment card  100  (i.e., in memory), and authenticate use of the payment card  100  if the series of inputs matches the passcode. In this example, when a user first creates an account with the native application executing on the mobile computing device, the native application can display a virtual representation of the input regions on the display of the mobile computing device, prompt the user to enter a sequence of inputs on the input regions (e.g., a sequence of four inputs), store the sequence of inputs as a personal passcode for the user, and transmit the passcode to the payment card  100  upon a subsequent sync event. 
     Alternatively, the processor  160  can implement similar methods to interface with the transducer  150  to authenticate a series of taps on a surface of the sheet  110  as a passcode. For example, the processor  160  can authenticate a specific number, sequence, and/or interval (e.g., timing) of impulses on the sheet  110  as a passcode and thus unlock the payment card  100  for use. However, the processor can implement any other method or technique to authenticate use of the payment card  100  through an input, tap, or impulse on a surface of the sheet  110 . 
     Therefore, the processor  160  can lock a payment function of the magnetic stripe emulator  140  until the wireless communication module  120  establishes a connection the mobile computing device or until a user enters a valid passcode directly into the payment card  100  via the input regions. The processor  160  can thus enable security features of the payment card  100  to prevent use of the payment card  100  by an invalid or unauthorized user but also to enable access to the payment function of the card for a valid user who is either carrying the paired mobile computing device or who knows the passcode. Furthermore, once a valid passcode is received, the processor  160  can control one or more visual elements within the payment card  100  to provide visual feedback to a user that the passcode was authenticated, such as by flashing a green LED three times. Similarly, the processor  160  can flash a red LED three times if the passcode attempt was invalid. However, the processor  160 , the input regions, and/or the wireless communicate module can cooperate in any other way to authenticate use of the payment card  100  for an upcoming payment. 
     Once the processor  160  authenticates use of the payment card  100  through a connection with the mobile computing device or through a valid passcode manually entered on the payment card  100 , the processor  160  can cooperate with the input regions to receive a selection for a particular payment method from a set of payment methods assigned to the input regions. In one example, the processor  160  sets a first payment method assigned to the first input region  131  as a default payment method such that, when swiped through a magnetic stripe reader, the processor  160  controls the magnetic stripe emulator  140  according to the first magnetic sequence command associated with the first payment method. However, in this example, if the user selects the second input region  132  assigned to the second payment method, the processor  160  can switch from a first payment mode corresponding to the first payment method to a second payment mode corresponding to the second payment method. Subsequently, when the payment card  100  is swiped through a magnetic stripe reader, the processor  160  can control the magnetic stripe emulator  140  according to the second magnetic sequence command to enable payment through the second payment method. 
     The processor  160  can correlate a single input on a single input region as a selection for a payment method assigned to the single input region, such as described above. In this implementation, the payment card  100  can store magnetic sequence commands for a number of payment methods corresponding to the number of input regions on the payment card  100 . The processor  160  can further identity substantially simultaneous inputs on two or more input regions as selection of an additional payment method. For example, the processor  160  can identify substantially simultaneous inputs on the first input region  131  and the second input region  132  as selection of a third payment method. 
     In another implementation, the processor  160  can respond to one or more inputs on the inputs regions by scrolling through a set of payment methods stored in memory on the payment card  100 . The processor  160  can thus access and enable more payment methods than input regions on the payment card  100 . In one example, the processor  160  defaults to a standard mode, wherein each input region is associated with a single payment method in a set of preferred, default, or most-used payment methods, but switches to a scroll mode when the user depressed two or more input regions for a threshold period of time. In the scroll mode the processor  160  can respond to an input on the first input region  132  by scrolling upward through a list of stored payment methods, the processor  160  can respond to an input on the second input region  132  by scrolling downward through the list of stored payment methods, and the processor can respond to an input on a third input region by selecting a particular payment method for subsequent emulation. Alternatively, the processor  160  can respond to a taps on the sheet  110  by scrolling through the list of stored payment methods. The processor  160  can also interface with the mobile computing device, via the wireless communication module  120  to display a currently-selected payment method and adjacent payment methods in the list of stored payment methods. 
     However, the processor  160  can assign payment methods to one or a combination of input regions in any other suitable way and can determine user selection of a payment method through one or more input region according to any other schema. 
     In applications in which the processor  160  has established a wireless connection with the mobile computing device through the wireless communication module  120 , the processor  160  can further transmit a user selection for a payment method to the mobile computing device through the wireless communication module  120 . In one implementation, the native application executing on the mobile computing device manipulates the receive payment method selection to provide visual feedback of a user&#39;s payment method section. For example, the native application can display a virtual representation of the payment card  100 , including the first icon  111  and the second icon  112 , and highlight an icon corresponding to the selected payment method, such as with a green border or bold typeface. However, the processor  160  can transmit a payment method selection to the mobile computing device in any other way, and the native application executing on the mobile computing device can provide any other suitable type of feedback to a user in any other way. 
     Alternatively, the native application can receive a user selection for a payment method through the mobile computing device, such as through a touchscreen displaying a list of available payment methods or a virtual representation of the payment card  100 , including virtual representations of the first and second icons assigned to a first payment method and a second payment method, respectively. The mobile computing device can then push the user payment method selection to the payment card  100 . However, the processor  160  can function in any other way to receive a user payment method selection directly through an input region or indirectly through the mobile computing device. 
     Once a payment method is selected manually by a user or by default, the processor  160  can control the magnetic stripe emulator  140  according to a magnetic sequence command corresponding to the selected payment method. Generally, as described above, the magnetic stripe emulator  140  can include a set of coils and a coil drive circuit, and the processor  160  can control the coil drive circuit to drive the set of coils according to a magnetic sequence command. In one implementation and as described above, the processor  160  and the magnetic stripe emulator  140  cooperate to detect a read-head of a magnetic stripe reader, and the processor  160  can couple the magnetic stripe emulator  140  to the read-head of a magnetic stripe reader by stepping through the selected magnetic sequence command according to a position and/or velocity of the payment card  100  relative to the read head. 
     As described above, the processor  160  can cooperate with the magnetic stripe emulator  140  to detect a local read head of a magnetic stripe reader. The processor  160  can also cooperate with the magnetic stripe emulator  140  to detect a speed or velocity of the magnetic stripe emulator  140  along the read head. In one implementation, once a local read head is detected, the processor  160  steps through bits specified in a magnetic sequence command according to a speed of the magnetic stripe emulator  140  moving along the read head. In this implementation, the processor  160  can determine a speed of the payment card  100  along the read head, calculate a magnetic stripe emulator bit rate by multiplying the speed of the card by a standard magnetic stripe bit density, and step through the magnetic sequence command (i.e., control the magnetic stripe emulator  140 ) according to the magnetic stripe emulator  140  bit rate. For example, the magnetic sequence command can include Track 2-type data with a bit density of seventy-five bits per inch, the processor  160  can estimate a speed of the payment card  100  along the read head of two inches per second, calculate a magnetic stripe emulator bit rate of 150 bits per second, and control the magnetic stripe emulator  140  to step through 150 bits per second. The processor  160  can also select a magnetic stripe emulator bit rate that is faster than a product of the estimated payment card speed and the magnetic stripe bit density to ensure the magnetic sequence is fully output before the payment card  100  exits the magnetic stripe reader. As in the foregoing example, the processor  160  can set a magnetic stripe emulator bit rate that of 165 bits per second, which is ten percent greater than the product of the estimated payment card speed and bit density. 
     As shown in  FIG. 2A , the payment card  100  can additionally or alternatively include one or more discrete read head sensors  148  arranged within the sheet no and configured to detect a read head of a magnetic stripe reader, and the processor  160  can cooperate with the one or more read head sensors  148  to couple the magnetic stripe emulator  140  to the magnetic stripe reader. The processor  160  can also interface with an accelerometer, gyroscope, Hall effect sensor, or other sensor within the payment card  100  to detect a read head and/or to determine a speed of the payment card  100  along a read head. However, the processor  160  can control the magnetic stripe emulator  140  in any other suitable way and according to any other schema. 
     Once payment through the payment card  100  is authenticated and/or once a user selects a payment method, the processor  160  can set a payment timer, such as a two-minute or a five-minute timer. Upon expiration of the payment timer, the processor  160  can cut power to the magnetic stripe emulator  140 , return to the passive setting, or otherwise terminate a payment function of the payment card  100 . Alternatively, once the payment card  100  is swept through a magnetic stripe reader during a transaction, the processor  160  can terminate the payment function of the payment card  100 . Similarly, once the payment card  100  is swept through a magnetic stripe reader during a transaction, the processor  160  can initiate a payment timer, such as a ten-second or one-minute timer, wherein the processor  160  withdraws the payment function of the payment card  100  and returns to the passive setting if an additional swipe is not attempted prior to expiration of the timer. However, the processor  160  can discontinue the payment function of the payment card  100  and/or return to the passive state in any other way and according to any other trigger or timer. 
     As shown in  FIG. 2A , one variation of the payment card  100  includes a flexible circuit board  180  board arranged within the sheet no. As described above and shown in  FIG. 2B , the flexible circuit board  180  can be sandwiched between two layers of the sheet  110  and can include traces, contacts, and/or via to communicate analog and/or digital signals between various electronic components of the payment card  100 . The flexible circuit board  180  can include a fiberglass, silicone, or polymer substrate or a substrate of any other suitable material. The flexible circuit board  180  can also be substantially thin and can include cavities or recesses to receive analog circuit components (e.g., resistors, capacitors) and/or integrated circuits (e.g., a microprocessor, a voltage regulator) such that the maximum height of the flexible circuit board  180  with components installed does not exceed a thickness of a standard plastic bank card. Furthermore, electrical components installed on the flexible circuit board  180  can exclude potting material in order to minimize component size (i.e., height). For example, the processor  160  can be a microprocessor including multiple (e.g., thousands or millions of) transistors fabricated on a silicone wafer, trimmed, shaved, and installed on the flexible circuit board  180  without encasement in a potting material. However, the flexible circuit board  180  can be of any other material, can be of any other geometry, include any other feature, and/or function in any other way to electrically couple various components of the payment card  100 . 
     As shown in  FIG. 2A , one variation of the payment card  100  further includes a battery  170  arranged within the sheet  110  and electrically coupled to the processor  160  via the flexible circuit board  180  board. Generally, the battery  170  functions to power the processor  160 , the wireless communication module  120 , the magnetic stripe emulator  140 , and other components of the payment card  100 . The battery  170  can be substantially thin. The battery  170  can include multiple cells that are flexible by nature of their thin cross-sections, or the battery  170  can include multiple cells with gaps therebetween such that the battery  170  can flex across the gaps. The battery  170  can be sandwiched between two layers of the sheet  110  adjacent the flexible circuit board  180 , mounted on the flexible circuit board  180 , or arranged in any other way within the payment card  100 . The battery  170  can be a lithium-ion, lithium-polymer, NiCd, or any other suitable type of battery and can be rechargeable or non-rechargeable. The processor  160  can also sense a remaining charge on the battery  170  and output battery level feedback to a user, such as by flashing an LED within the sheet no accordingly to current battery level. Alternatively, the wireless communication module  120  can transmit battery status to the native application executing on the mobile computing device to display battery information for the user. 
     As shown in  FIGS. 3 and 4 , one variation of the payment card  100  further includes a display  190  visible through a layer of the sheet  110 . For example, the display can include an e-paper or e-ink display. The display can output alphanumeric characters corresponding to a card number of a selected payment method, a CCV of a selected payment method, a cardholder&#39;s (i.e., the user&#39;s) name, payment method assignments to input regions, or any other relevant data pertaining to a user, a payment method, or a function of the payment card  100 . 
     However, the payment card  100  can also include any other component and can function in any other way to consolidate multiple payment sources into one payment card with a magnetic stripe emulator configured to output a magnet form of bits to mimic static magnetic stripes of various standard plastic bank cards. 
     In addition or as an alternative to the magnetic stripe emulator  140 , the payment card  100  can include a near-field communication (NFC) tag emulator, a radio-frequency identification (RFID) tag emulator, and/or any other payment authorization protocol emulator. For example, the payment card  100  can include rewriteable NFC tag, the processor  160  can store NFC commerce transaction identifiers for a set of NFC-based payment methods, and the processor  160  can rewrite the NFC tag with a NFC commerce transaction identifier for a selected payment method. In another example, the payment card  100  can include an RFID reader detector and an RFID tag emulator, the processor  160  can store RFID commerce transaction identifiers for a set of RFID-based payment methods, the processor  160  can cooperate with the RFID reader detector to detect a local RFID reader, and the RFID tag emulator can output a RFID commerce transaction identifier for a selected RFID payment method. For example, as shown in  FIG. 2A , the payment card can further include an integrated circuit  152  configured to transmit a digital transaction credential—stored in memory on the payment and corresponding to a payment method—over wired or wireless communication protocol. In this example, the integrated circuit  152  can retrieve a unique digital transaction credential of a particular payment method selected for an upcoming transaction, encrypt the unique digital transaction credential according to cryptographic protocols corresponding to the particular payment method, and wirelessly transmit the corresponding tokenized payment credential when the payment card is moved into proximity of a contactless card reader and/or when a read request is received wirelessly from the contactless card reader. However, the payment card  100  can include and implement any other payment authorization emulator and corresponding protocol, and any of the foregoing and subsequent methods can be implemented to enable consolidation of one or more plastic bank card, NFC, RFID, and/or gift card payment methods on a single payment card. 
     2. First Method 
     As shown in  FIGS. 6 and 8 , first method S 100  for controlling a payment card including a magnetic stripe emulator, a first input region, and a second input region, includes: establishing a wireless connection with the payment card  100  in Block S 110 ; transmitting a first magnetic sequence command to the payment card  100  over the wireless connection in Block S 120 , the first magnetic sequence command associated with a first payment method assigned to the first input region  131 ; transmitting a second magnetic sequence command to the payment card  100  over the wireless connection in Block S 130 , the second magnetic sequence command associated with a second payment method assigned to the second input region  132 ; and on a digital display, displaying virtual representations of the first input region  131  and the second input region  132  on the payment card  100  in Block S 140 , a visual identifier of the first payment method displayed proximal the virtual representation of the first input region  131 , and a visual identifier of the second payment method displayed proximal the virtual representation of the second input region  132 . 
     Generally, first method S 100  functions to enable a remote visual interface for the payment card  100  described above. In one implementation, first method S 100  can be implemented through a native application executing on a mobile computing device (e.g., a smartphone, a tablet), as described above. The payment card  100  described above can store a set of payment methods and enable payment with a payment method selected from the set of payment methods through a magnetic stripe emulator, and the payment card  100  can download different sets of payment methods over time and assign various payment methods to each input region over time. However, because the payment card  100  may omit a refreshable display, a mobile computing device paired with the payment card  100  can implement first method S 100  to provide visual feedback of payment methods assigned to each input region (or combination of input regions) on the payment card  100 . 
     In one example, a user attempting to make a payment with a payment method stored on the payment card  100  can wake the payment card  100  by tapping the payment card  100  as described above, the payment card  100  and the mobile computing device paired with the payment card  100  can establish a wireless connection, the mobile computing device can transmit a first payment method and a second payment to the payment card  100 , and the mobile computing device can display a virtual representation of the payment card  100  including the first input region  131  and the second input region  132  (and/or the first icon  111  and the second icon  112 ) with a visual representation of the first payment method overlaid over the first icon  111  and a visual representation of the second payment method overlaid over the second icon  112  according to payment methods assigned to each input region of the payment card  100 . In this example, the user can thus reference the virtual representation of the payment card  100  displayed on the mobile computing device to identify what payment methods are available in the payment card  100  and which payment method is assigned to each input region on the payment card  100 . 
     Block S 110  of first method S 100  recites establishing a wireless connection with the payment card  100 . As described above, once the processor  160  in the payment card  100  wakes from a passive setting to an active setting, the processor  160  can control the wireless communication module  120  to search for, identify, and connect with a paired mobile computing device. In Block S 110 , a wireless module within the mobile computing device can cooperate with the wireless communication module  120  within the payment card  100  to establish the wireless connection. For example, the payment card  100  and the mobile computing device can communicate over Bluetooth communication protocol or any other radio-frequency-type wireless communication protocol. Alternatively, as described above, the mobile computing device can implement Block S 110  by communicating with the payment card  100  over an optical- or sound-based communication channel. As described above, Block S 110  can toggle a set of pixels on a display of the mobile computing device between black and white settings to optically transmit bits (i.e., data) to the payment card  100 . Alternatively, as described above, Block S 110  can control an audio driver (e.g., a speaker) to transmit audio signals including payment method data. However, Block S 110  can establish communication with the payment card  100  through any other suitable communication protocol over any other communication channel or pathway. 
     Block S 120  of first method S 100  recites transmitting a first magnetic sequence command to the payment card  100  over the wireless connection, the first magnetic sequence command associated with a first payment method assigned to the first input region  131 . Similarly, Block S 130  of first method S 100  recites transmitting a second magnetic sequence command to the payment card  100  over the wireless connection, the second magnetic sequence command associated with a second payment method assigned to the second input region  132 . As described above, the mobile computing device can implement Block S 120  by transmitting a set of payment methods to the payment card  100  over Bluetooth, over another radio-frequency-type communication protocol, through an optical connection, through an audio-based connection, or over any other suitable wireless communication protocol or communication channel. 
     As described, Blocks S 120  and S 130  can transmit requisite payment information for each payment method, such as a magnetic sequence command specifying a series of bits implementable magnetically through the magnetic stripe emulator  140  of the payment card  100  to imitate a static magnetic stripe of a corresponding plastic bank card. 
     Blocks S 120  and S 130  can also transmit a payment method rank to the payment card  100 , wherein the payment rank defines a particular payment method as a default payment method. For example, Blocks S 120  and S 130  can specify the first payment method as the default payment method such that if a user does not select an alternative payment method through one or more input regions on the payment card  100 , the payment card  100  will default to payment with the default (i.e., first) payment method. 
     Blocks S 120  and S 130  can additionally or alternatively transmit payment method assignments for each input region to the payment card  100 . For example, Blocks S 120  and S 130  can receive a manual selection of payment methods from a user or automatically select a set of payment methods stored in the native application executing on the mobile computing device, assign one payment method in the set of payment methods to each input region on the payment card  100 , and transmit the assignments to the card in conjunction with the magnetic sequence commands for each payment method in the set of payment methods. Thus, Blocks S 120  and S 130  can maintain a current list of payment method assignments for each input region on the card, and Block S 130  can implement the list of payment method assignments to update the virtual representation of the payment card  100  including visual identifiers of the assigned payment methods. However, Blocks S 120  and S 130  can transmit any other suitable command, data, or specification to the payment card  100  in addition to a magnetic stripe sequence of one or more selected payment methods. 
     Block S 120  and Block S 130  can further encrypt and/or decrypt communications with the payment card  100 , such as by implementing one or more authentication and/or encryption schema. For example, Blocks S 120  and S 130  can implement cryptographic protocols such as Diffie-Hellman key exchange or Wireless Transport Layer Security (WTLS). Blocks S 120  and S 130  can additionally or alternatively encrypt data according to an encryption standard such as Data Encryption Standard (DES), Triple Data Encryption Standard (3-DES), or Advanced Encryption Standard (AES). The payment card  100  can similarly encrypt and/or decrypt communications with the mobile computing device. However, Blocks S 120  and S 130  (and the payment card  100 ) can implement any other security or encryption methods to protect private or sensitive user or banking information. 
     Block S 140  of first method S 100  recites, on a digital display, displaying a virtual representation of the first input region  131  and the second input region  132  on the payment card  100 , a visual identifier of the first payment method proximal the virtual representation of the first input region  131 , and a visual identifier of the second payment method proximal the virtual representation of the second input region  132 . Generally, Block S 140  functions to provide visual feedback of payment method assignments for the input regions on the payment card  100  through a refreshable display incorporated into the mobile computing device. 
     As shown in  FIG. 8 , in one implementation, Block S 140  displays a virtual image of the payment card  100  with both a descriptor of the first payment method arranged over a portion of the virtual image corresponding to the first input region  131  and a descriptor of the second payment method arranged over a portion of the virtual image corresponding to the second input region  132 . The descriptor for each payment method can include a stock image, such as a brand image of a credit card issuer, a banking institution, or a credit card rewards program. For example, when a user uploads a plastic bank card into the native application executing on the mobile computing device, the native application can identify a rewards program associated with the plastic bank card, and Block S 140  can automatically download a corresponding stock image for the rewards program from a remote server (i.e., over the Internet) and display the stock image over a virtual representation of corresponding input region of the payment card  100 . Alternatively, when a user uploads a plastic bank card into the native application executing on the mobile computing device, the native application can prompt the user to supply a description of the plastic bank card (e.g., through a virtual keyboard displayed on a touch display of the mobile computing device), and Block S 140  can display the description proximal a virtual representation of corresponding input region of the payment card  100 . Similarly, when a user uploads a plastic bank card into the native application executing on the mobile computing device, the native application can prompt the user to select a stock textual or visual identifier of the plastic bank card, and Block S 140  can display the identifier adjacent a virtual representation of corresponding input region of the payment card  100 . However, Block S 140  can function in any other way to display a virtual representation of the payment card  100  and identifiers of payment methods assigned to each input region of the payment card  100 . 
     As shown in  FIG. 7 , one variation of first method S 100  includes Block S 150 , which recites receiving a selection on the first input region  131  of the payment card  100  over the wireless connection and highlighting the visual identifier of the first payment method within the virtual representation of the payment card  100 . Generally, Block S 150  functions to update the virtual representation of the input regions and corresponding payment methods to indicate which payment method is currently enabled on the payment card  100 . For example, Block S 150  can highlight, expand, embolden, alter a color or, or other visually modify the identifier displayed proximal a virtual representation of an input region corresponding to the payment method currently selected for an upcoming transaction. 
     In one implementation, once a transaction with the payment card  100  is authenticated, such as described above, the mobile computing device implements Block S 150  by displaying a first colored (e.g., green) border around a virtual representation of an input region corresponding to a default payment method. If and when a user selects an alternative payment method by touching an input region corresponding to an other payment method, the payment card  100  can transmit the selection for the other payment method to the mobile computing device, and the mobile computing device can remove the first colored border and instead display a second colored (e.g., green) border around a virtual representation of an input region corresponding to the other payment method. However, Block S 150  can function in any other way to provide visual feedback for a selection of a payment method through the payment card  100 . 
     3. Second Method 
     As shown in  FIGS. 9 and 11 , second method S 200  for controlling a payment card including a magnetic stripe emulator and a set of input regions includes: receiving a tap input on a surface of the payment card  100  in Block S 210 ; in response to receiving the tap input, attempting wireless communication with a mobile computing device in Block S 220 ; suppressing a payment function of the magnetic stripe emulator  140  in response to failed wireless communication with the mobile computing device in Block S 230 ; receiving a series of inputs through the set of input regions in Block S 240 ; authenticating the series of inputs as a passcode in Block S 250 ; and in response to authenticating the series of inputs as the passcode, enabling the payment function of the magnetic stripe emulator  140  in Block S 260 . 
     Generally, second method S 200  can be implemented through the payment card  100  described above as a security measure to prevent fraudulent use of the payment card  100 . As described above, the payment card  100  can be paired with a mobile computing device, and because a verified user may carry both the payment card  100  and the mobile computing device but a fraudulent user may only have access to the payment card  100 , once activated, the payment can attempt to communicate with the paired mobile computing device to authenticate use of the payment card  100 . However, if the payment card  100  fails to establish a connection with the mobile computing device, the payment card  100  can implement second method S 200  to receive a passcode and authenticate use of the payment card  100 . 
     Block S 210  of second method S 200  recites receiving a tap input on a surface of the payment card  100 . As described above, the processor  160  of the payment card  100  can implement Block S 210  by receiving a voltage spike from a transducer (e.g., a piezoelectric transducer) in response to an impulse on the payment card  100  that deforms the sheet  110  of the payment card  100  and thus the transducer  150 . The ‘tap’ or impulse can thus transition the payment card  100  to an active setting. However, Block S 210  can handle a tap or impulse on the payment card  100  in any other suitable way. 
     Block S 220  of second method S 200  recites, in response to receiving the tap input, attempting wireless communication with a mobile computing device. As described above, the processor  160  and the wireless communication module  120  of the payment card  100  can cooperate to detect a paired mobile computing device. Once the mobile computing device is detected, the processor  160  can attempt to establish a wireless connection with the mobile computing device by transmitting an inquiry for the mobile computing device paired through the wireless communication module  120 . Block S 220  can make a predefined number of attempts to connect to the mobile computing device, such as two or five attempts, prior to switching to an idle setting and transitioning to Block S 230 . However, Block S 220  can attempt communication with the paired mobile computing device in any other suitable way. 
     Block S 230  of second method S 200  recites suppressing a payment function of the magnetic stripe emulator  140  in response to failed wireless communication with the mobile computing device. Generally, Block S 230  functions to block the magnetic stripe emulator  140  of the payment card  100  from implementing a magnetic stripe sequence of a payment method, as described above. For example, Block S 230  can maintain a coil of the magnetic stripe emulator  140  in an unpowered setting. In one implementation, Block S 230  suppresses the payment function of the magnetic stripe emulator  140  in response to a predefined number of failed attempts to pair with the mobile computing device that includes a unique wireless communication address, as described above. 
     Alternatively, Block S 230  can suppress the payment function of the magnetic stripe emulator by communicating a ‘void payment’ command to a payment processing company that handles payment transactions through plastic banking cards. For example, Block S 230  can establish a wireless Internet connection (e.g., via a Bluetooth connection with an external Internet-enabled electronic device) and transmit the ‘void payment’ command to a server hosted by the payment processing company such that the payment processing company can void a transaction attempted with the banking card  100 . However, Block S 230  can function in any other way to withdraw or suppress a payment function of the payment card  100 . 
     Block S 240  of second method S 200  recites receiving a series of inputs through the set of input regions, and Block S 250  of second method S 200  recites authenticating the series of inputs as a passcode. Generally, Block S 240  captures a set of inputs, such as four discrete inputs, across the input regions of the payment card  100 , and Block S 250  compares the set of inputs to a stored passcode to authenticate use of the payment card  100  if authentication through a connection with the paired mobile computing device fails. As described above, a user can set a passcode to unlock the payment card  100  into an interface with the native application executing on the mobile computing device, the mobile computing device can transmit the passcode to the payment card  100 , and the payment card  100  can store the passcode in memory. Once Block S 240  captures the set of inputs entered by the user, Block S 250  can match a sequence of the set of inputs with a stored sequence of inputs defining the passcode to authenticate use of the payment card  100 . However, Block S 240  and Block S 250  can function in any other way to capture and authenticate a series of inputs as a valid passcode. 
     Block S 260  of second method S 200  recites, in response to authenticating the series of inputs as the passcode, enabling the payment function of the magnetic stripe emulator  140 . In one implementation, the processor  160  implements Block S 250  to verify a passcode entered by a user, and the processor  160  subsequently implements Block S 260  to power the magnetic stripe emulator  140  according to a default or selected payment method when the payment card  100  is passed through a magnetic stripe reader (shown in  FIG. 5 ). 
     As shown in  FIG. 10 , one variation of second method S 200  includes Block S 270 , which recites receiving a selection of a particular input region, in the set of input regions, assigned to a particular payment method. Generally, Block S 270  functions to capture user selection of a particular payment method, from a set of payment methods stored on the payment card  100 , through one or more input regions on the payment card  100 . However, Block S 270  can function in any other way to receive a payment method selection from a user. 
     In response to receiving a payment method selection from a user, Block S 260  can enable the payment function of the magnetic stripe emulator  140  by powering a coil of the magnetic stripe emulator  140  according to a magnetic sequence command associated with the particular payment method, as described above. For example, the processor  160  can implement Block S 260  by outputting a control signal to the coil driver circuit  142 , which can generate magnetic polarity changes corresponding to the magnetic stripe sequence of the selected payment method, as shown in  FIG. 11 . However, Block S 260  and Block S 270  can function in any other way to receive and to implement a payment method selection entered by a user. 
     As shown in  FIG. 10 , one variation of second method S 200  further includes Block S 280 , which recites transitioning the coil of the magnetic stripe emulator  140  to an unpowered setting after a threshold period of time. Generally, Block S 280  functions to transition the payment card  100  to an inactive state in which the payment card  100  can not be used to provide payment information. In one implementation and as described above, the processor  160  can set a payment timer once payment through the payment card  100  is authenticated, once a payment method is selected by a user, or once the payment card  100  is swept through a magnetic stripe reader during a transaction, etc. In this variation, the processor  160  can maintain payment functionality of the payment card  100  until expiration of the timer, at which point the processor  160  implements Block S 280  to withdraw the payment function of the payment card  100  and transition the payment card  100  to the passive setting. However, Block S 280  can function in any other way to shutdown the payment card  100  after a threshold period of time or in response to any other time, timer, or trigger. 
     4. Third Method 
     As shown in  FIGS. 12 and 13 , third method S 300  for controlling a payment card including a magnetic stripe emulator, a first input region, and a second input region includes: receiving a tap input on a surface of the payment card  100  in Block S 310 ; in response to receiving the tap input, establishing a wireless connection with a mobile computing device in Block S 320 ; receiving a first magnetic sequence command and a second magnetic sequence command from the mobile computing device in Block S 330 , the first magnetic sequence command associated with a first payment method, the second magnetic sequence command associated with a second payment method; assigning the first payment method to the first input region  131  in Block S 340 ; assigning the second payment method to the second input region  132  in Block S 350 ; receiving a selection for the second payment method through the second input region  132  in Block S 360 ; and, in response to receiving the selection for the second payment method, driving the magnetic stripe emulator  140  according to the second magnetic sequence command in Block S 370 . 
     Generally, third method S 300  can be implemented through the payment card  100  described above as a security measure to prevent fraudulent use of the payment card  100 . As described above, the payment card  100  can be paired with a mobile computing device, and because a verified user may carry both the payment card  100  and the mobile computing device but a fraudulent user may only have access to the payment card  100 , once activated, the payment can implement third method S 300  to establish a wireless connection with the paired mobile computing device, thereby authorizing use of the payment card  100  for a subsequent payment. 
     Block S 310  of third method S 300  recites receiving a tap input on a surface of the payment card  100 . Generally, Block S 310  can function as Block S 210  described above to transition from an inactive (i.e., passive) setting to an active setting in which the magnetic stripe emulator  140  of the payment card  100  outputs a series of bits magnetically to mimic a static magnetic stripe of a plastic bank card. For example, the processor  160  can implement Block S 310  to transition from a passive mode to an active mode in response to a voltage output from the transducer  150  arranged within the payment card  100 . 
     Block S 320  of third method S 300  recites, in response to receiving the tap input, establishing a wireless connection with a mobile computing device. Generally, Block S 320  functions similar to Block S 220  described above to detect and identify a paired mobile computing device. However, if Block S 320  detects the paired mobile computing device, Block S 320  can further establish the wireless connection with the mobile computing device. For example, Block S 320  can transmit an inquiry for the mobile computing device and can pair the payment card  100  to the mobile computing device over the wireless connection, as shown in  FIG. 13 . However, Block S 320  can function in any other way to communicate wirelessly with the paired mobile computing device. 
     Block S 330  of third method S 300  recites receiving a first magnetic sequence command and a second magnetic sequence command from the mobile computing device, the first magnetic sequence command associated with a first payment method, the second magnetic sequence command associated with a second payment method. In one implementation described above in which the payment card  100  and the mobile computing device establish a radio-frequency-based wireless connection, Block S 330  can receive magnetic sequence commands for the set of payment methods though radio communications. In another implementation described above, the mobile computing device can output a series of optical signals (e.g., black and white or high and low light pulses) in the direction of the payment card  100 , and the payment card  100  can implement Block S 330  to receive and decode the optical signals into magnetic sequence commands for the set of payment methods. For example, Block S 330  can receive the optical signals through a photodiode or through a photoresistor. Similarly, in the implementation described above in which the mobile computing device outputs a series of audio signals (e.g., from a speaker or audio driver), the payment card  100  can impellent Block S 330  to receive and decode the audio signals into magnetic sequence commands for the set of payment methods. For example, Block S 330  can record a series of audio pulses through a transducer arranged within the payment card  100  and can correlate the first magnetic sequence command from the series of audio pulses. 
     As described above, Block S 330  can also receive a ranking for the payment methods, payment method assignments for the input regions, or any other suitable or relevant information pertaining to the payment methods. Block S 330  can also receive encrypted payment method data, and Block S 330  can further function to decrypt the received data. However, Block S 330  can function in any other way to receive and/or process information for one or more payment methods. 
     Block S 340  of third method S 300  recites assigning the first payment method to a first input region in the set of input regions. Similarly, Block S 350  of third method S 300  recites assigning the second payment method to a second input region in the set of input regions. Generally, Block S 340  and Block S 350  function to assign one input region to one payment method such that selection of a particular input region triggers the payment card  100  to emulate the corresponding payment method (i.e., a magnetic stripe of a corresponding plastic bank card). Block S 340  and Block S 350  can also assign a set of input regions to one payment method to enable selection of more payment methods than number of input regions on the card. 
     In one implementation, Block S 340  stores the first magnetic sequence command of the first payment method in a stack in computer memory and assigns an address of the first magnetic sequence command to the first input region  131 . Similarly in this implementation, Block S 350  stores the second magnetic sequence command of the second payment method in a stack in computer memory and assigns an address of the second magnetic sequence command to the second input region  132 . However, Block S 340  and Block S 350  can store and assign magnetic sequence commands for various payment methods in any other suitable way. 
     Block S 340  and Block S 350  can assigned each magnetic sequence command to an input region in order that each is received. Alternatively, Block S 340  and Block S 350  can assign the payment methods according to a payment method rank received from the mobile computing device, as described above. Furthermore, Block S 340  can set the first payment method as a default payment method, as described above, such that the payment card  100  defaults to emulating the first payment method when a payment is attempted through the card if a user fails to select an input region corresponding to another payment method. However, Block S 340  and Block S 350  can selectively assign each payment method to one or more input regions in any other way or according to any other schema. 
     Block S 360  of third method S 300  recites receiving a selection for the second payment method through the second input region  132 . Generally, Block S 360  functions to receive an input through a particular input region on the payment card  100  and to ‘arm’ the payment card  100  to implement the magnetic sequence command of the particular payment method. In one example, Block S 360  receives an input on the surface of the payment card  100  proximal the second input region  132  that includes a capacitive touch sensor and switches from a default payment mode specifying the first payment method to a manual payment selection mode that specifies the second payment method. 
     In one implementation in which Block S 240  and Block S 250  store the first and second magnetic sequence commands in a stack in computer memory and assign addresses of the magnetic sequence command to respective input regions, Block S 360  can set a pointer within the stack to a particular address in response to a selection on a corresponding input region. However, Block S 360  can function in any other way to receive and implement selection of a payment method through a corresponding input region on the payment card  100 . 
     Block S 370  of third method S 300  recites, in response to receiving the selection for the second payment method, driving the magnetic stripe emulator  140  according to the second magnetic sequence command. Generally, Block S 370  functions to implement a magnetic sequence command of a selected or default payment method through the magnetic stripe emulator  140  of the payment card  100  to mimic a plastic bank card when use of the payment card  100  is attempted. 
     As described above, Block S 370  can detect a magnetic stripe reader and power one or more coils of the magnetic stripe emulator  140  according to the default or selected magnetic sequence command according to a speed and/or position of the magnetic stripe emulator  140  relative to a read head of the magnetic stripe reader. Block S 370  can therefore function to magnetically couple the magnetic stripe emulator  140  to the magnetic stripe reader and control a magnetic polarity of the magnetic stripe emulator  140  accordingly. However, Block S 370  can function in any other way to control the magnetic stripe emulator  140  of the payment card  100 , thereby enabling payment with a selected payment method through the payment card  100 . 
     5. Fourth Method 
     As shown in  FIGS. 14 and 15 , fourth method S 400  for controlling a payment card including a magnetic stripe emulator, a first input region assigned a first payment method, and a second input region assigned a second payment method includes: authorizing use of the payment card  100  in Block S 410 ; initiating a timed payment mode comprising a payment timer in Block S 420 ; receiving a selection for the first payment method through the first input region  131  in Block S 430 , the first payment method associated with a first magnetic sequence command stored in memory; in response to receiving the selection for the first payment method, enabling a payment function of the magnetic stripe emulator  140  with the first magnetic stripe command in Block S 440 ; locking the payment function of the magnetic stripe emulator  140  against an input on the second input region  132  to select the second payment method in Block S 450 ; and disabling a payment function the magnetic stripe emulator  140  in response to expiration of the payment timer in Block S 460 . 
     Generally, fourth method S 400  can be implemented through the payment card  100  described above to “lock” a selected payment method to the card for a specified period of time. Fourth method S 400  can therefore be useful during periods in which an owner of the payment card  100  ‘hands off’ the payment card  100  to another individual to make a payment. For example, fourth method S 400  can be implemented through the payment card  100  when a user (i.e., the owner of the payment card  100 ) hands the payment card  100  to a waiter following a meal at a restaurant. In this example, fourth method S 400  can lock a particular payment method selected by the user to avoid incidental selection of an alternative payment method when the waiter handles the payment card  100 . 
     Block S 410  of fourth method S 400  recites authorizing use of the payment card  100 . In one implementation, Block S 410  can implement Blocks of second method S 200  described above by establishing a wireless connection with a paired mobile computing device and authorizing use of the payment card  100  based on the wireless connection. For example, Block S 410  can receive a tap input on a surface of the payment card  100 , transmit an inquiry for a mobile computing device paired to the payment card  100 , and establish a wireless connection with a mobile computing device to authenticate use of the payment card  100 . Additionally or alternatively, Block S 410  can implement Blocks of third method S 300  described above by receiving a series of inputs on the input regions of the card and matching the series of inputs to a passcode to authenticate use of the payment card  100 . For example, Block S 410  can receive a tap input on a surface of the payment card  100 , receive a series of inputs through the first input region  131  and the second input region  132 , and authenticate the series of inputs as a valid passcode to enable use of the payment card  100 . As described above, Block S 410  can control a visual indicator within the payment card  100  (e.g., an LED) or displayed on the mobile computing device through the native application to indicate to a user than that payment card has been authenticated. However, Block S 410  can function in any other way to authenticate use of the payment card  100  in a subsequent transaction. 
     Block S 420  of fourth method S 400  recites initiating a timed payment mode, as shown in  FIG. 15 . Generally, Block S 420  functions to transition the payment card  100  into the timed payment mode in which a selected payment method is “locked in” (i.e., cannot be changed) for a period of time. In one implementation, the native application executing on the mobile computing device receives an input from a user specifying the timed payment mode, and Block S 420  receives a corresponding timed payment mode request from the mobile computing device. Thus, in this implementation, the mobile computing device and/or the native application can function as an external control unit for the payment card  100 . 
     In another implementation, Block S 420  receives a series of inputs through the first input region  131  and the second input region  132  and identifies the series of inputs as a timed payment mode request. In this implementation, Block S 410  can first receive passcode enter by a user through the input regions to authenticate use of the payment card  100  or authenticate use of the payment card  100  by establishing a wireless connection with the mobile computing device, and Block S 420  can subsequently receive a second series of inputs corresponding to a timed payment request. Alternatively, Block S 410  and Block S 420  can cooperate to receive a single passcode that both authenticates use of the payment card  100  and selects the timed payment mode as a current operating mode of the payment card  100 . For example, the payment card  100  can be configured to receive a first passcode (e.g.,  1212 ) to authenticate use of the payment card  100  through a standard operating mode in which payment methods can be selected at whim and the payment card  100  becomes inactive after a period of inactivity (e.g., one minute without a swipe through a magnetic stripe reader), and the payment card  100  can also be configured to receive a second passcode (e.g.,  1122 ) to authenticate use of the payment card  100  through the timed payment mode in which a selected payment method is locked to the card and the payment card  100  becomes inactive after a predetermined period of time. 
     Block S 420  can initiate the timed payment mode once a request to enter the timed payment mode is entered by a user by triggering a payment timer of a set period of time. In this implementation, Block S 430  can subsequently receive a selection for a payment method, Block S 440  can enable a payment function of the payment card  100  with the selected payment method, and Block S 460  can withdraw the payment function of the payment card  100  once the payment timer expires (i.e., after the set period of time transpires). 
     Alternatively, Block S 420  can initiate the timed payment mode once Block S 430  receives a selection of a payment more from a user. In this implementation, Block S 430  can receive a payment method selection, Block S 420  can initiate the payment timer, Block S 440  can enable the payment function of the payment card  100  with the selected payment method, and Block S 460  can subsequently withdraw the payment function of the payment card  100  once the payment timer expires. In this implementation, Block S 420  can initiate the timed payment mode by setting the payment timer, and Block S 430  can trigger the payment timer once a selection for a payment method is entered. 
     Block S 420  can specify a default timer length for the payment timer, such as five minutes. Block S 420  can also sync with the mobile computing device and retrieve a suggested timer length from the mobile computing device. For example, the mobile computing device can estimate an optimum timer length based on a time of day, a location of the user (e.g., determined by a global positioning system sensor in the mobile computing device), a preference of the user, etc., and Block S 420  can retrieve the estimated optimum timer length from the mobile computing device. Alternatively, Block S 420  can receive a user input to control the length of the payment timer. For example, Block S 420  can receive a user input requesting the timed payment mode, control a visual indicator within the payment card  100  (e.g., an LED) or displayed on the mobile computing device through the native application to provide visual feedback that the payment card  100  is in the timed payment mode, receive a subsequent input through the payment card  100  or through the mobile computing device specifying a length of the time, and then set the length of the timer according to the user input. However, Block S 420  can function in any other way to initiate the timed payment mode. 
     Block S 430  of fourth method S 400  recites receiving a selection for the first payment method through the first input region  131 , the first payment method associated with a first magnetic sequence command stored in memory. Generally, Block S 430  functions like Block S 360  described above to receive an input on an input region and to correlate the input with a selection for a payment method assigned to the input region. As described above, Block S 430  can receive a selection for a particular payment method through a physical input region arranged on the payment card  100  and/or through a virtual input region displayed on a touchscreen or other display of a paired mobile computing device. However, Block S 430  can function in any other way to capture a user selection for a payment method. As described above, Block S 430  can also function to trigger the payment timer once a user selection for a payment method is captured. Block S 430  can also provide visual feedback of the payment selection through the payment card  100  (e.g., by controlling an LED within the payment card  100 ) or through the native interface executing on the mobile computing device. 
     Block S 440  of fourth method S 400  recites, in response to the selection for the first payment method, enabling a payment function of the magnetic stripe emulator  140  through implementation of the first magnetic stripe command. Generally, Block S 440  functions like Block S 260  and Block S 310  to drive the magnetic stripe emulator  140  according to a magnetic sequence command corresponding to the selected and “locked” payment method. For example and as described above, Block S 440  can detect a magnetic stripe reader and power the magnetic stripe emulator  140  according to the first magnetic sequence command and a position and/or speed of the magnetic stripe emulator  140  relative to a read head of a magnetic stripe reader. Block S 440  can also provide visual feedback through the payment card  100  or through the mobile computing device that the payment function of the payment card  100  is active. However, Block S 440  can function in any other way to enable a payment function of the payment card  100  through a magnetic sequence command corresponding to a selected payment method. 
     Block S 450  of fourth method S 400  recites disregarding an input on the second input region  132  as a selection for the second payment method. Generally, Block S 450  functions to implement a “lock” feature of fourth method S 400  by ignoring additional inputs on the physical input regions of the payment card  100  or the virtual input regions displayed on a display of a mobile computing device to select (purposefully or accidentally) an alternative payment method. For example, Block S 450  can lock the magnetic stripe emulator  140  in a first payment method payment mode in response to the selection of the first payment method and prior to expiration of the payment timer such that the magnetic stripe emulator  140  cannot be switched from the first payment method payment mode to another payment method payment mode until the payment timer expires. 
     In one implementation, the processor  160  of the payment card  100  can implement Block S 450  by cutting power to a touch sensor, mechanical switch, or other sensor adjacent the set of input regions to withdraw input sensing capabilities of the payment card  100  once Block S 430  receives a selection for payment method. In another implementation, the processor  160  can implement Block S 450  by actively ignoring (i.e., not responding) to input signals received from the set of input regions once Block S 430  receives a selection for payment method. However, Block S 450  can be implemented in any other way to actively or passively disregard an input on an input region of the payment card  100  once a payment method is selected in Block S 430 . 
     Block S 460  of fourth method S 400  recites disabling a payment function of the magnetic stripe emulator  140  after a specified period of time. Generally, Block S 460  disables the payment function of the payment card  100  once the payment timer expires and/or once the payment card  100  has implemented the selected payment method in a transaction. For example, Block S 420  can set the payment timer at five minutes from selection of a payment method, Block S 430  can initiate the timer when the user selects a payment method, and Block S 460  can cancel or stop the payment function of the payment card  100  when the timer expires. 
     Block S 460  can also provide visual feedback that the timer is approaching expiration. For example, Block S 460  can blink an LED within the payment card  100  during the last thirty seconds on the payment timer. Block S 460  can similarly blink the LED at a rate proportional to the amount of time left on the payment timer such that the LED blinks faster as the payment timer approaches expiration. 
     Once the timer expires, Block S 460  can transition the magnetic stripe emulator  140  to a standby or default setting in which the magnetic stripe emulator  140  is unpowered in the default setting, as shown in  FIG. 15 . Alternatively, Block S 460  can transition the payment card  100  to a passive, inactive, ‘sleep,’ or OFF setting. In this alternative, the payment card  100  can subsequently repeat Block S 410  to enable a subsequent payment. However, Block S 460  can function in any other way to disable the payment function of the payment card  100 . 
     6. Fifth Method 
     A fifth method S 500  for controlling a reprogrammable payment card includes: at the payment card, establishing a wireless connection with a mobile computing device in Block S 512 ; receiving, over the wireless connection, a first magnetic sequence command corresponding to a first payment method, a first digital transaction credential corresponding to the first payment method, and a second magnetic sequence command corresponding to a second payment method in Block S 520 ; initiating a first mode in Block S 530 ; in the first mode, arming a controller within the payment card to drive a magnetic stripe emulator within the payment card according to the first magnetic sequence command in Block S 540 ; in the first mode, activating an integrated circuit within the payment card to broadcast the first digital transaction credential in Block S 542 ; and, in the first mode, disabling operation of the magnetic stripe emulator and the integrated circuit in response to failure of a wireless connection with the mobile computing device in Block S 570 . 
     One variation of the fifth method S 500  includes: activating a payment card in response to receipt of an initial input at the payment card in Block S 510 ; at the payment card, entering a first mode in Block S 530 ; in the first mode, driving a magnetic stripe emulator within the payment card according to a first magnetic sequence command corresponding to the first payment method in response to detecting a magnetic stripe card reader proximal the payment card in Block S 540 ; in the first mode, outputting a digital transaction credential of the first payment method in response to receiving a digital read request from a digital card reader proximal the payment card in Block S 542 ; entering a second mode in response to selection of a second payment method for the upcoming transaction in Block S 550 ; in the second mode, driving the magnetic stripe emulator according to a second magnetic sequence command corresponding to the second payment method in response to detecting a magnetic stripe card reader proximal the payment card in Block S 560 ; and in the second mode, disabling output of the digital transaction credential of the first payment method from the payment card in Block S 562 . 
     A similar variation of the fifth method S 500  includes: activating a payment card in response to receipt of an initial input at the payment card in Block S 510 ; at the payment card, entering a first mode in Block S 530 ; in the first mode, outputting a first fluctuating magnetic field simulating a static magnetic stripe of a first payment method in response to detecting a magnetic stripe card reader proximal the payment card in Block S 540 ; in the first mode, transmitting a digital transaction credential of the first payment method over radio-frequency wireless communication protocol in response to receiving a digital read request from a card reader in Block S 542 ; entering a second mode in response to selection of a second payment method for the upcoming transaction in Block S 550 ; in the second mode, outputting a second fluctuating magnetic field simulating a static magnetic stripe of a second payment method in response to detecting a magnetic stripe card reader proximal the payment card in Block S 560 ; and in the second mode, disabling transmission of the digital transaction credential of the first payment method over radio-frequency wireless communication protocol in Block S 562 . 
     In yet another variation, the fifth method S 500  includes: at the payment card, establishing a wireless connection with a mobile computing device in Block S 510 ; receiving, over the wireless connection, a first magnetic sequence command corresponding to a first payment method in Block S 520 ; upon selection of the first payment method for emulation in a transaction, driving a magnetic stripe emulator arranged within the payment card according to the first magnetic sequence command in response to an output of a magnetic read head sensor within the payment card indicating proximity of the payment card to a magnetic stripe card reader in Block S 560 ; upon suspension of the first payment method for emulation in a transaction, driving the magnetic stripe emulator according to a second magnetic sequence command corresponding to a second payment method in response to an output of the magnetic read head sensor indicating proximity of the payment card to a magnetic stripe card reader in Block S 540 ; and transmitting a digital transaction credential corresponding to the second payment method in response to receipt of a digital read request from a digital card reader proximal the payment card in Block S 542 . 
     6.1 Applications 
     Generally, the fifth method S 500  can be executed by the reprogrammable payment card described above (or other device similarly configured) to selectively emulate payment methods of different types. For example, the fifth method S 500  can be executed by a payment card both to selectively emulate a magnetic stripe card (e.g., a credit card, a debit card, a gift card) by outputting a fluctuating magnetic field simulating a static magnetic sequence coded onto a static magnetic stripe of the magnetic stripe card and to selectively emulate a “smart card” (e.g., an integrated circuit card) by wirelessly broadcasting or communicating over a wired connection a tokenized payment credential mimicking a tokenized payment credential output by the smart card at the same payment card. In this example, the payment card (or other device) can execute the fifth method S 500  to activate a magnetic stripe emulator within the payment card to emulate a magnetic stripe of a first payment card and to activate a wired or wireless transmitter within the payment card to output a tokenized payment credential corresponding to the first payment card in the first mode; the payment card can thus output a fluctuating magnetic field corresponding to the first payment card when the payment card is swept through a magnetic stripe card reader and can thus output a digital (wired or wireless) signal corresponding to the first payment card when the payment card is held near or inserted into a smart card reader. In this example, the payment card can also execute the fifth method S 500  to activate the magnetic stripe emulator within the payment card to emulate a magnetic stripe of a second payment card and to deactivate the wired or wireless transmitter within the payment card for the second payment method not associated with or containing a tokenized payment credential in a second mode. Alternatively, in this example, the payment card can execute the fifth method S 500  to activate the magnetic stripe emulator within the payment card to emulate a magnetic stripe of a second payment card and to activate the wired or wireless transmitter to output a tokenized payment credential corresponding to the second payment card in the second mode. The payment card can therefore execute the fifth method S 500  to selectively enable and disable emulation of various transaction types (or “payment pathway types”) supported by the same payment card, such as based on availability of emulation data (e.g., a magnetic stripe sequence command, a tokenized payment credential, etc.) for payment methods, access methods, and/or identification methods selected for emulation by the payment card in a subsequent (e.g., upcoming) transaction. 
     The fifth method S 500  is therefore executable by a reprogrammable payment card or any other suitable device (e.g., wearable device, hard case for mobile computing device, etc.) containing a component and/or circuitry configured to emulate an external payment method (e.g., credit card), identification method (e.g., employee badge), and/or access method (e.g., door access card). The fifth method S 500  is described below as a method executable by a payment card configured to emulate a magnetic stripe card—such as a magnetic stripe credit card, a magnetic stripe debit card, magnetic stripe gift card, and/or a magnetic stripe door access card—and a contactless smart card (e.g., an NFC-based credit card). However, the fifth method S 500  can similarly be executed by a payment card or other device configured to additionally or alternatively emulate one or more other types of transactional systems, such as integrated circuit cards (or “chip” cards, “smart” cards), bar code cards, Wiegand wire embedded cards, RFID proximity cards, and/or tokenized (e.g., dynamic) payment credentials, etc. for payment methods, access methods, and/or identification methods. However, the fifth method S 500  can be implemented in conjunction with any other suitable type of payment card or other device configured to emulate any other suitable type of payment method, access method, or identification method. 
     In one example application, a first payment method—corresponding to multiple payment pathway types (e.g., a magnetic stripe, a tokenized payment credential etc.)—can be substantially intransiently set as a primary or default payment method for transactions with the payment card. In this example application, the payment card is branded for a particular financial institution and the first (default) payment method is issued by the particular financial institution. In particular, the particular financial institution assigns a first magnetic stripe sequence command and a first digital transaction credential (with cryptographic protocols) for the first payment method and issues the payment card encoded with the first magnetic stripe sequence command and the first digital transaction credential (and the cryptographic protocols) to the user. When the user supplies the payment card for various transactions, the first payment method is emulated by the payment card by default, including execution of the first magnetic stripe sequence command when the payment card is swept through a magnetic stripe card reader, including transmission of the first digital transaction credential over wireless communication protocol when a read request is received from a contactless smart card reader, and including transmission of the first digital transaction credential over wired communication protocol when a read request is received from a contact-based smart card reader. In this example application, the user can further interface with a native payment card application executing on his mobile computing device to upload additional payment methods (e.g., debit cards), access methods (e.g., hotel keys), and/or identification methods (e.g., employee identification) to the payment card. The payment card can assign such additional payment, access, and/or identification methods to secondary payment slots, tertiary payment slots, etc. on the payment card, and the user can elect an alternative payment, access, and/or identification method—in place of the first (default) payment method—for emulation in an upcoming transaction, such as by selecting a second input region or a third input region on the payment card or by selecting the alternative payment, access, and/or identification method from within the native payment card application. In this implementation, the payment card can also be physically branded according to the particular financial institution issuing the payment card or according to an alternative brand affiliated with the particular financial institution. For example, a logo of the particular financial institution or of the affiliated brand can be printed or embossed on an external surface of the payment card. In this example, the first payment method—issued by the particular financial institution and/or associated with the affiliated brand—can thus persist as a default payment method for emulation by the payment card during subsequent transactions despite addition, retraction, and occasional emulation (responsive to manual selection by the user) of other payment methods, access methods, and/or identification methods at the same payment card, as described above. 
     6.2 Activation 
     As shown in  FIG. 16 , Block S 510  of the fifth method S 500  recites activating a payment card in response to receipt of an initial input at the payment card. Generally, Block S 510  is executable by the payment card to prepare the card for use in a transaction in response to an input entered directly onto a surface of the payment card or in response to receiving a command from a computing device (e.g., a smartphone, a tablet) affiliated with the payment card. 
     In one implementation, a processor within the payment card executes Block S 510  to activate the payment card in response to detecting one or more inputs on a surface of the payment card. For example, as described above, the payment card can include a piezoelectric transducer electrically coupled to a ‘wake’ interrupt-enabled input pin of the processor such that, when a user taps on or bends the payment card with sufficient impact, the piezoelectric transducer outputs an electrical signal to the interrupt pin of the processor, which wakes the processor out of an off or “hibernate” mode. The payment card can then attempt wireless communication with the associated computing device in Block S 512  to authenticate use of the payment card in a subsequent transaction, as described above. The payment card can also automatically enter the payment card into first mode in Block S 530  in response to successful wireless communication with the computing device, such as in response to establishment of a wireless connection with the affiliated computing device or in response to receipt of a wireless communication from the computing device following transmission of an inquiry for the computing device from the payment card, as described above. The payment card can thus execute Block S 510  to trigger wireless communication with a mobile computing device associated with the payment card in Block S 512  in response to receiving a manual input on a surface of the payment card. However, in this implementation, if wireless communication with the affiliated computing device is unsuccessful following an input (e.g., an “activation input”) on a surface of the payment card, the payment card can transition into a locked state. In the locked state, the payment card can prompt a user to enter a passcode to unlock the payment card; the payment card can also authenticate a series of inputs into the payment card as a passcode and unlock the payment card accordingly, as described above, to enable use of the payment card in a transaction even when wireless communication with the affiliated computing device is not available. The payment card can thus maintain disablement of emulation of a payment method by the magnetic stripe emulator (e.g., execution of a magnetic stripe sequence command) and by an integrated circuit within the payment card (e.g., transmission of a tokenized payment credential or other digital transaction credential) in response to failure to establish a wireless connection with the mobile computing device, and the payment card can re-enable emulation of the payment method by the magnetic stripe emulator and the integrated circuit in response to authenticating a series of inputs into the payment card as a valid passcode. 
     In a similar implementation, the payment card is operable in a sleep mode when not in use and occasionally transitions into a test mode to check-in with the associated mobile computing device to establish and maintain authorization of use of the payment card based on a result of attempted wireless communication with the mobile computing device. For example, the payment card can transition from the sleep mode into the test mode once per five-second interval (or at any other frequency or interval); once in the test mode, the wireless communication module within the payment card can broadcast an inquiry for a unique wireless address of the computing device affiliated with the payment card. In this example, if a token or other wireless communication is received from the mobile computing device in response to transmission of the inquiry (e.g., within 500 milliseconds of transmitting the inquiry), the payment card can establish and/or preserve authorization of use of the payment card and transition back into the sleep mode. However, in this example, if a communication is not received from the mobile computing device within a threshold period of time (e.g., 500 milliseconds) of transmitting the inquiry, the payment card can transition into a locked state (or reattempt wireless communication with the mobile computing device by transmitting a second inquiry before transitioning into the locked state) in which emulation of a payment method by the payment card in a subsequent transaction is disabled until a passcode is entered into and authenticated at the payment card or until a wireless connection is again established with the mobile computing device, as described above. Therefore, in this implementation, the payment card can preserve (i.e., maintain) authentication of the payment card until a scheduled check-in with the affiliated mobile computing device fails to yield a viable wireless connection. Alternatively, the payment card can execute Block S 112  to establish a (constant) wireless connection with the mobile computing device, to authenticate use of the payment card in a subsequent transaction while the wireless connection persists, and to de-authenticate use of the payment card (e.g., disable emulation of a payment method) when the wireless connection fails or is lost. 
     In another implementation, the payment card activates in Block S 110  in response to receipt of an activation command from a mobile computing device wirelessly connected to the payment card following establishment of a wireless connection with the payment card in Block S 112 . For example, the user can enter an activation command into a native payment card application executing on the mobile computing device, and the mobile computing device can transmit an activation command to the payment card over wireless communication protocol; the payment card can then handle the activation command by transitioning into a ready state in preparation to receive a selection—at the mobile computing device or at the payment card—for a first payment method or a second payment method for emulation by the payment card in a subsequent transaction. Alternatively, the payment card can handle the activation command by automatically transitioning into the first mode in preparation for emulation of a first (e.g., default) payment method stored on the payment card. 
     As shown in  FIG. 16 , Block S 512  of the fifth method S 500  recites, at the payment card, establishing a wireless connection with a mobile computing device. Generally, the payment card (e.g., the processor in conjunction with the wireless communication module) can execute Block S 512  to authorize use of the payment card in a transaction in Block S 510  and/or to download payment methods (e.g., magnetic stripe sequence commands; digital payment credentials and cryptographic protocols for tokenized payment credentials) from the affiliated computing device, as described above. Block S 512  can therefore execute methods and techniques similar to those of Block S 110  of the first method, etc. described above. 
     As shown in  FIG. 16 , Block S 520  of the fifth method S 500  recites receiving, over the wireless connection, a first magnetic sequence command corresponding to a first payment method, a first digital transaction credential corresponding to the first payment method, and a second magnetic sequence command corresponding to a second payment method. Generally, the payment card can execute Block S 520  to download emulation data from an external resource, as described above. For example, the payment card can download a magnetic stripe sequence command and/or a digital transaction credential and cryptographic protocol for one or more payment methods in Block S 520 . The payment card can also assign particular payment methods—correspond to emulation data received from the computing device—to particular payment slots on the payment card, as described above. For example, the payment card can receive a first magnetic sequence command for a first payment method from the affiliated mobile computing device (e.g., smartphone) wirelessly paired to the payment card and can then assign the first payment method to a first input region on the payment card in Block S 520 . 
     6.3 First Mode 
     As shown in  FIGS. 16 and 17 , Block S 530  of the fifth method S 500  recites, initiating a first mode; Block S 530  can similarly recite, at the payment card, entering a first mode. Generally, the payment card can execute Block S 530  to enter into a first mode in which a various payment pathways of a first payment method are emulated by the payment card based on proximity of the payment card to readers configured to read one or more particular payment pathway types (e.g., a magnetic stripe, a tokenized payment credential over a wired connection, a tokenized payment credential over a wireless connection, etc.). 
     In one implementation, the payment card (or the computing device, the native payment card application executing on the computing device) sets the first payment method as a default payment method, and the payment card automatically enters into the first mode in response to authorization of use of the payment card, such as in response to establishing a wireless connection with the mobile computing device as described above. In this implementation, the payment card can automatically arm a controller within the payment card to drive the magnetic stripe emulator within the payment card according to the first magnetic sequence command corresponding to the first payment method in response to activation of the payment card (or in response to authorizing use of the payment card in an upcoming transaction) in Block S 530 . In this implementation, in Block S 530 , the payment card can also automatically activate, power, or otherwise enable an integrated circuit within the payment card to transmit—over a wired or wireless connection—a digital transaction credential (e.g., a tokenized payment credential) corresponding to the first payment method in response to activation of the payment card and/or in response to authorizing use of the payment card in an upcoming transaction. !!!! 
     In another implementation, the payment card enters into the first mode in Block S 530  in response to selection of a first input region—on a surface of the payment card—corresponding to the first payment method assigned to the first input region, as described above. Similarly, the payment card can enter into the first mode in response to receipt of a command from the computing device—over wireless communication protocol—to enter into the first mode and/or to arm various subsystems within the payment card to emulate the first payment method. 
     The payment card can also transition from the second mode in which the second payment method is emulated back into the first mode in which the first (e.g., default) payment method is emulated by the payment card when a payment timer on the payment card expires, when the payment card is deactivated (e.g., shut down, entered into a sleep or hibernate mode, etc.) and then reactivated, when the first input region (or first payment slot) is selected manually at the payment card, and/or when a command to emulate the first payment method is received from the computing device, etc. For example, the payment card can transition from the second mode into the first mode when selection of the second payment method is suspended, disabled, de-authorized, or otherwise discontinued at the payment card, such as in response to expiration of a timer, in response to receipt of a manual input into the payment card, or in response to receipt of a corresponding command from the computing device. 
     However, the payment card can arm or otherwise prepare one or more subsystems within the payment card to emulate a first payment method (or first identification first, first access method, etc.) in any other way and automatically or in response to a manual input entered by the user directly into the payment card or into the computing device wireless connected to the payment card. 
     As shown in  FIG. 17 , Block S 540  of the fifth method S 500  recites, in the first mode, arming a controller within the payment card to drive a magnetic stripe emulator within the payment card according to the first magnetic sequence command. Block S 540  can similarly recites, in the first mode, driving a magnetic stripe emulator within the payment card according to a first magnetic sequence command corresponding to the first payment method in response to detecting a magnetic stripe card reader proximal the payment card. Generally, the payment card can execute Block S 540  to emulate a static magnetic stripe of the first payment method when in the first mode, such as when the payment card is swept through a magnetic stripe card reader, as described above. For example, the payment card can output, through the magnetic stripe emulator, a fluctuating magnetic field simulating a static magnetic stripe of the first payment method (e.g., a first credit card) in response to an output of a magnetic read head sensor within the payment card indicating proximity of the payment card to a magnetic stripe card reader in the first mode. 
     As shown in  FIG. 17 , Block S 542  of the fifth method S 500  recites, in the first mode, activating an integrated circuit within the payment card to broadcast the first digital transaction credential. Block S 542  can similarly recite, in the first mode, outputting a digital transaction credential of the first payment method in response to receiving a digital read request from a digital card reader proximal the payment card. Generally, the payment card can execute Block S 542  to transmit a digital transaction credential—such as over wired or radio-frequency wireless communication protocol—mimicking a digital output of the first payment method. For example, the payment card can transmit the first digital transaction credential of the first payment method over radio-frequency wireless communication protocol (e.g., RFID, NFC) in the first mode in response to receiving a digital read request from a card reader transmitted to the payment card over the same radio-frequency wireless communication protocol. In particular, in this example, the payment card can wirelessly broadcast a tokenized payment credential (or other digital transaction credential) specific to the first payment method in response to receipt of a digital read request from a radio-frequency wireless-enabled digital card reader within wireless communication range of the payment card. In this example, the payment card can retrieve a digital transaction credential for the first payment method from static memory within the payment card, encrypt the digital transaction credential, and transmitting the digital transaction credential in encrypted form (e.g., as a tokenized payment credential) to the digital card reader in Block S 542 . In particular, in this example, the integrated circuit can generate a transaction credential for the first payment method in Block S 242  by retrieving (from local memory) static data including a first portion containing routing information and including a second portion containing transaction identification and authentication information for creating a transaction credential for the first payment method; the integrated circuit can then apply dynamic cryptographic principals to the second portion of the static data, combine the first portion of the static data with the (dynamically-) encrypted second portion to generate the tokenized payment credential, and transmit (over wired or wireless communication protocol) the tokenized payment credential substantially in real-time upon receipt of a read request from a smart card reader in contact with or proximal the payment card. The smart card reader can then route the encrypted second portion in the tokenized payment credential to a receiving party (e.g., a network, a token-issuer, or a bank issuing the payment card) based on the first portion of the tokenized payment credential received from the payment card. 
     In the first mode, the payment card can thus sample one or more sensors within the payment card to detect a magnetic, wired, radio-frequency, or other card reader proximal the payment card can to trigger emulation of a corresponding payment pathway type (e.g., a magnetic stripe, a tokenized payment credential over a wired connection, a tokenized payment credential over a wireless connection, etc.). For example, the payment card can arm (or otherwise activate) both a controller for the magnetic stripe emulator and an integrated circuit to output a magnetic sequence and a digital transaction credential, respectively. In this example, a processor within the payment card can sample one or more magnetic read head sensors within the payment card can trigger the controller to drive the magnetic stripe emulator according to a first magnetic stripe sequence command in response to an output of the magnetic read head sensor indicating proximity of a magnetic stripe card reader. While polling the magnetic stripe read head sensor(s) within the payment card, the processor can also poll a wireless communication module (e.g., a receiver, an antenna) within the payment card for receipt of a request for a digital transaction credential (or other tokenized and/or digital identifier or credential); the processor can thus trigger the integrated circuit to retrieve the digital transaction credential from memory, to encrypt the digital transaction credential, and to broadcast the encrypted digital identified in response to receipt of such a request. In particular, in this example in which the first payment method (e.g., a credit card) supports (e.g., is affiliated with) both a first magnetic stripe sequence and a first digital transaction credential, the payment card can thus execute Blocks S 540  and S 542  to selectively emulate the first magnetic stripe sequence and the first digital transaction credential of the first payment method, such as to trigger the magnetic stripe emulator within the card to emulate the first magnetic stripe sequence when the payment card is in the first mode and swept through a magnetic stripe card reader and to trigger the integrated circuit to broadcast (a form of) the first digital transaction credential when the payment card is held over a contact or contactless digital credential reader. 
     For other payment pathway types supported by the payment first payment method and available at the payment card, the payment card can poll or sample sensors to identify a particular card reader proximal the payment card at any given time and to selectively emulate a particular payment pathway type most relevant, substantially relevant, or preferred for a particular card reader detected in the first mode. For example, when both a contact-based card reader and a contactless card reader are detected by sensors within the payment card in the first mode and the first payment method supports both contact-based and contactless transactions, the payment card can default to communicating a tokenized payment credential to the contact-based card reader (which may be more secure than a contactless transaction). For example, the payment card can apply location-based rules, payment method- (or access method-, identification method-, or other) based rules, user preferences, user transaction history, or any other data to ranking payment pathway types of the first payment method emulated by the payment card in the first mode. 
     6.4 Second Mode 
     As shown in  FIG. 17 , Block S 550  of the fifth method S 500  recites entering a second mode in response to selection of a second payment method for the upcoming transaction. Generally, the payment card can execute Block S 550  to prepare for emulation of a second (e.g., alternative) payment method during an upcoming transaction. 
     In one implementation, the payment card initiate the second mode in Block S 550  in response to receiving an input on a region of the payment card corresponding to the second payment method, such as described above. Alternatively, the payment card can enter the second mode in Block S 550  in response to receiving a command to emulate the second payment method from the affiliated computing device and over a wireless connection. 
     Once the second payment method is elected for emulation by the payment card in an upcoming transaction, the payment card can thus enter the second mode in Block S 550 , arm the controller to drive the magnetic stripe emulator according to a second magnetic sequence command corresponding to the second payment method in Block S 560 , and deactivate the integrated circuit for the second payment method not affiliated with a digital transaction credential (or other tokenized and/or digital identifier) in Block S 562 . Alternatively, once the second payment method is elected for emulation by the payment card in the upcoming transaction, the payment card can enter the second mode in Block S 550 , arm the controller to drive the magnetic stripe emulator according to the second magnetic sequence command corresponding to the second payment method in Block S 560 , and reprogram the integrated circuit to transmit a digital transaction credential (or other tokenized and/or digital identifier) affiliated with the second payment method in Block S 562 . Yet alternatively, once the second payment method is elected for emulation by the payment card in the upcoming transaction, the payment card can enter the second mode in Block S 550 , arm the controller to drive the magnetic stripe emulator according to the second magnetic sequence command corresponding to the second payment method in Block S 560 , deactivate a first integrated circuit programmed to transmit a form of a first digital transaction credential of the first payment method, and activate a second integrated circuit programmed to transmit a form of a second digital transaction credential (or other tokenized and/or digital identifier) affiliated with the second payment method in Block S 562 . 
     Block S 560  of the fifth method S 500  recites, in the second mode, driving the magnetic stripe emulator according to a second magnetic sequence command corresponding to the second payment method in response to detecting a magnetic stripe card reader proximal the payment card. Generally, the payment card can implement methods and techniques described above to control the magnetic stripe emulator within the payment card in Block S 560  to simulate a magnetic stripe of the second payment method when the payment card is swept through a read head of a magnetic card reader. For example, the payment card can output, through the magnetic stripe emulator, a fluctuating magnetic field simulating a static magnetic stripe of a second credit card (e.g., the second payment method) in response to an output of the magnetic read head sensor indicating proximity of the payment card to a magnetic stripe card reader. In particular, in this example, a controller, driver, or other processor within the payment card can drive the magnetic stripe emulator according to a second magnetic stripe sequence command corresponding to the second payment method in the second mode in response to an output of the magnetic read head sensor indicating proximity of the payment card to a magnetic stripe card reader. However, the payment card can execute Block S 560  in any other way to intermittently emulate a magnetic stripe of the second payment method in the second mode. 
     As shown in  FIGS. 16 and 17 , Block S 562  of the fifth method S 500  recites, in the second mode, disabling output of the digital transaction credential of the first payment method from the payment card. Generally, the payment card can implement methods and techniques described above to control one or more integrated circuits within the payment card to selectively enable and disable transmission of digital transaction credentials of various payment methods stored on the payment card. 
     In one implementation described above and shown in  FIG. 16 , in the second method, the payment card disables the integrated circuit arranged within the payment card (and configured to transmit (over wired and/or wireless communication protocol a form of the digital transaction credential of the first payment method) such that data pertaining to the first payment method is not (mistakenly) communicated from the payment card into a card reader when the payment card is brought within proximity of a card reader (supporting multiple payment pathway types) during a transaction when the user has instead elected the second payment method for emulation during the transaction. In this implementation, for the second payment method associated with a second (unique) digital transaction credential (and corresponding cryptographic protocols), the payment card can also activate a second integrated circuit within the payment card to transmit the second digital transaction credential (in encrypted form) in Block S 562 . Alternatively, in Block S 562 , the payment card can reprogram or redirect the integrated circuit to transmit the second digital transaction credential—rather than the first digital transaction credential of the first payment method—when the payment card is brought within proximity or in contact with a contactless or contact-based card reader, respectively. 
     In one variation, in Blocks S 550  and S 560 , the payment card can further receive—from the computing device wirelessly paired to the payment card—a third magnetic stripe sequence command corresponding to a third payment method, can replace the second magnetic stripe sequence command with the third magnetic stripe sequence command, and can drive the magnetic stripe emulator according to the third magnetic stripe sequence command in the second mode in response to an output of the magnetic read head sensor indicating proximity of the payment card to a magnetic stripe card reader, such as described above. The payment card can therefore execute Block S 550  and Block S 560  prepare to emulate an alternative (e.g., third) payment method, access method, or identification method in a subsequent transaction based on a selection for the alternative payment method, access method, or identification method entered by the user, such as directly into the payment card or into the computing device wirelessly connected to the payment card, as described above. 
     6.5 Disablement 
     As shown in  FIG. 16 , Block S 570  of the fifth method S 500  recites, in the first mode, disabling operation of the magnetic stripe emulator and the integrated circuit in response to failure of a wireless connection with the mobile computing device. Block S 570  can similarly recite, in the second mode, disabling operation of the magnetic stripe emulator in response to failure of a wireless connection with the mobile computing device. Generally, the payment card can implement methods and techniques described above in Block S 570  to disable payment method emulation functions of the payment card when a wireless connection with the affiliated computing device (e.g., smartphone) is lost. However, the payment card can execute Block S 570  in response to receipt of a disablement command from the computing device, in response to expiration of a payment timer, or in response to any other event detected at the payment card. 
     Alternatively, the integrated circuit can be substantially intransiently enabled and persist in function despite loss of communication with the computing device. In particular, the payment card can disable function of the magnetic stripe emulator in Block S 570  when wireless communication with the computing device is lost or otherwise unavailable to prevent emulation of magnetic stripes corresponding to various payment (and/or access or identification) methods while transmission of a digital transaction credential for the first payment method—which may be a more secure form of transaction than magnetic stripe data—remains enabled at the payment card. Yet alternatively, the payment card can disable emulation of all but a primary or default (e.g., the first) payment method in Block S 570  when wireless communication with the computing device is lost or otherwise unavailable such that transactions with the primary or default (e.g., first) payment method can persist at the payment card through both emulation of a primary magnetic stripe sequence and transmission of a primary digital transaction credential despite lack of proximity or communication of the computing device to the payment card. 
     As described above, the foregoing methods can be implemented in cooperation with or through a payment card including a NFC tag emulator, a RFID tag emulator, and/or any other payment authorization protocol emulator in addition or as an alternative to a magnetic stripe emulator. The foregoing methods can therefore enable substantially secure consolidation of one or more plastic bank card, NFC, RFID, gift card, and/or other payment method on a single payment card. 
     The systems and methods of the embodiments can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions can be executed by computer-executable components integrated with the application, applet, host, server, network, website, communication service, communication interface, hardware/firmware/software elements of a user computer or mobile computing device, or any suitable combination thereof. Other systems and methods of the embodiments can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions can be executed by computer-executable components integrated by computer-executable components integrated with apparatuses and networks of the type described above. The computer-readable medium can be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component can be a processor, though any suitable dedicated hardware device can (alternatively or additionally) execute the instructions. 
     As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the embodiments of the invention without departing from the scope of this invention as defined in the following claims.