In one or more embodiments, a method in an electronic device comprises receiving, by a user interface, user input defining an electronic payment transaction amount. In one or more embodiments, the method comprises determining, by one or more processors operable with the user interface, whether the electronic payment transaction amount meets a predefined criterion.

In one or more embodiments, when the electronic payment transaction amount meets the predefined criterion, the method comprises presenting, by the one or more processors on the user interface, a secondary confirmation challenge requiring other user input at the user interface re-entering the electronic payment transaction amount in a different format. Embodiments of the disclosure contemplate that while some prior art systems may present a prompt with a question such as “are you sure” in response to initiation of an electronic payment transaction, these are neither secondary confirmation challenges nor effective. They are not secondary confirmation challenge because they do not require confirmation of the electronic payment transaction amount. Moreover, they are not effective in that users more often than not proceed by just clicking “next” or “yes” without reading the prompt. Embodiments of the disclosure are distinct because the secondary confirmation challenges require some form of confirmation of the electronic payment transaction amount in a different format, which these prior art systems do not.

In one or more embodiments, the method comprises precluding execution of the electronic payment transaction associated with the electronic payment transaction amount when the other user input fails to re-enter the electronic payment transaction amount in the different format. Examples of such different formats include entering the electronic payment transaction amount in words or in math equations, although other alternate formats will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

Advantageously, embodiments of the disclosure alert the user and actively require a re-confirmation of an electronic payment transaction amount based upon predefined limits, historical context, locational context, or other factors. It prevents the sad situation from FIG. 7 from happening. Other advantages will be described below. Still others will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

To see how embodiments of the disclosure can operate, turn now to FIG. 1. Beginning at step 101, our friendly restaurant worker 706 is once again asking our satiated patron 700 to transfer eight dollars and seventy-nine cents in an electronic payment transaction. However, in FIG. 1, rather than trying to use the prior art electronic device (710) of FIG. 7, the patron 700 is armed with an electronic device 100 configured in accordance with one or more embodiments of the disclosure. Accordingly, the restaurant worker 706 is asking the patron 700 to initiate an electronic payment transaction using an electronic device 100 configured in accordance with one or more embodiments of the disclosure by defining an electronic payment transaction amount of eight dollars and seventy-nine cents. This electronic payment transaction will be directed to the point-of-sale device 708 belonging to Mac and Henry's Pub.

Once again, at step 102, the patron 700 obliges by initiating an electronic payment transaction using this electronic device 100 that is configured in accordance with one or more embodiments of the disclosure. Unfortunately, the patron 700 is again in a hurry, noting 709 that he must make this very quick because the patron 700 is already late for a meeting. Our restaurant worker 706 is still “in the weeds” and notes that tips would again be appreciated.

Due to this time pressure, the patron 700 once again delivers errant user input to the electronic device 100 when initiating an electronic payment transaction 711 from the Bank of Buster. As shown, the electronic payment transaction 711 defines an electronic payment transaction amount 712. Due to carelessness and time pressure, rather than delivering user input to the electronic device 100 defining the electronic payment transaction amount 712 to be $8.79, the patron 700 again mistypes the decimal point and defines the electronic payment transaction amount 712 to be $87.90, which is ten times the amount due.

At step 103, the user interface 112 of the electronic device 100, which is a touch-sensitive display in this example, receives user input 113 requesting the electronic payment transaction 711 and defining the electronic payment transaction amount 712. Decision 104 then determines, using one or more processors of the electronic device 100, whether the electronic payment transaction amount 712 triggers a secondary confirmation operation.

This determination made at decision 104 can be done in a variety of ways. In one or more embodiments, determining whether the electronic payment transaction amount 712 triggers a secondary confirmation operation comprises determining whether the electronic payment transaction amount 712 exceeds a predefined threshold. Illustrating by example, in one or more embodiments the patron 700 can use a menu and settings controls to define a predefine threshold, say, a thousand dollars for example, above which any electronic payment transaction would require a secondary confirmation operation.

In other embodiments, determining whether the electronic payment transaction amount 712 triggers a secondary confirmation operation comprises determining whether the electronic payment transaction amount 712 exceeds a predetermined average electronic payment transaction amount. For instance, if the patron 700 routinely uses the electronic device 100 to make electronic payment transactions, the one or more processors of the electronic device 100 can keep a running average of transactions, optionally with filters to eliminate outliers.

In one or more embodiments, the calculation of running average can also take into consideration additional factors like location, time of the day, recipient, and so forth, to provide a tailored running average specific to the context of the given situation. In one or more embodiments, when the user's transaction history is not available or sufficient, overall or for the given context, calculation of running average can also be based on the shared data of one or more other users with similar user profile. In one or more embodiments, when the electronic payment transaction amount 712 exceeds this running average, the one or more processors can determine that a secondary confirmation operation is required.

In still other embodiments, determining whether the electronic payment transaction amount 712 triggers a secondary confirmation operation comprises determining whether the electronic payment transaction 711 is requested at a predetermined time of day. Embodiments of the disclosure contemplate that when it is very early the patron 700 may be a bit groggy. Similarly, when it is very late the patron 700 may be tired or may have had a glass of wine with dinner, thereby compromising his concentration. Accordingly, in one or more embodiments a secondary confirmation operation is required when the electronic payment transaction 711 is requested at a predetermined time of day. In one or more embodiments, the predetermined times of day, or ranges of time during which secondary confirmation operations are required can be defined using user settings of the electronic device 100.

In still other embodiments, determining whether the electronic payment transaction amount 712 triggers a secondary confirmation operation comprises determining whether the electronic payment transaction is requested while the electronic device is situated in a predefined location. Recall the example above where Nakul was enjoying sweet, tasty coconuts purchased from a street-side vendor on the side of the highway. Since this location is not associated with a permanently situated merchant, in one or more embodiments a secondary confirmation operation would be triggered. The locations triggering secondary confirmation operations can be defined by the user, defined by predefined merchant locations known on public maps, and so forth. In other embodiments, the predefined location may be a bar or restaurant where the patron 700 may be consuming alcohol or other substances that may impair their ability to define the electronic payment transaction amount 712. When the electronic device 100 is situated in such locations when the user input 113 defining the electronic payment transaction 711 is received, in one or more embodiments cause a secondary confirmation operation to be triggered. Alternatively, in case of predetermined locations, user may define the safe locations which does not require secondary confirmation challenge and any location outside these predetermined location will trigger the secondary confirmation challenge.

In still other embodiments, determining whether the electronic payment transaction amount 712 triggers a secondary confirmation operation comprises determining whether the electronic payment transaction 711 is directed to a recipient to whom previous electronic payment transactions have occurred. In this example, our patron 700 dines at Mac and Henry's Pub three to five times a week. Accordingly, the one or more processors of the electronic device 100 and the Bank of Buster have historical logs indicating that Mac and Henry's Pub is a frequented location and, perhaps, is even a trusted merchant. However, Nakul's crooked coconut vendor was a one-off transaction with a vendor with whom Nakul had never done business. In one or more embodiments, decision 104 would trigger a secondary confirmation operation for the coconut vendor but would not trigger one for Mac and Henry's Pub because the latter is a recipient whom previous electronic payment transactions have occurred. However, since no previous electronic payment transactions had occurred with the coconut vendor, Nakul, and the poor guy been carrying an electronic device configured in accordance with embodiments of the disclosure, would have received a secondary confirmation challenge from a secondary confirmation operation.

It should be noted that these examples of how decision 104 could determine whether a secondary confirmation operation is triggered could be used alone or in combination. Additionally, these examples are illustrative only, as others will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

In this example, decision 104 determines whether a secondary confirmation operation is triggered by comparing the electronic payment transaction amount 712 with a running average of electronic payment transactions occurring with this particular merchant, namely, Mac and Henry's Pub. As noted above, our patron 700 dines at Mac and Henry's Pub, which specializes in Champagne and burger specials daily. His typical meal is the bubble burger de jour, which is a four ounce pour of sparkling wine with a burger cooked medium rare with extra pickles. Since Mac and Henry's Pub is a fair merchant trying to deliver excellent quality for a moderate price, this typically runs in the ten-to-twelve-dollar range. Today, our patron 700 stepped out of his comfort zone and tried the Cava Cheeseburger experience. As Cava is generally less expensive than Champagne, the tab was only eight dollars and seventy-nine cents.

Thus, at decision 104 the one or more processors of the electronic device 100 compare the electronic payment transaction amount 712 to an average of electronic payment transactions transacted with Mac and Henry's Pub. Had the patron 700 entered the correct amount, decision 104 would have determined no secondary confirmation operation was necessary because $8.79 is less than the ten-to-twelve-dollar average. Step 110 would have then transferred the eight dollars and seventy-nine cents to the point-of-sale device 708.

However, since the patron 700 did not enter the proper amount, decision 104 determines that eighty-seven dollars and ninety cents is way over the ten-to-twelve-dollar average of past electronic payment transactions with Mac and Henry's Pub. Accordingly, at step 105 the one or more processors of the electronic device 100 present a prompt comprising a secondary confirmation challenge. One example of such a prompt 114 and secondary confirmation challenge 115 is shown at step 106.

The secondary confirmation challenge 115 can take a variety of forms. In one or more embodiments, the secondary confirmation challenge 115 requires other user input 116 at the user interface 112 re-entering the electronic payment transaction amount 712 in a different format. Illustrating by example, the secondary confirmation challenge 115 of step 105 lists a plurality of user selectable amounts spelled out in words. One of the user selectable amounts spells out the electronic payment transaction amount 712 in the words, while other user selectable amounts of the plurality of user selectable amounts spell out transaction amounts other than the electronic payment transaction amount 712 in the words. This allows the patron 700 to deliver the other user input 116 selecting the electronic payment transaction amount 712 from the list to correctly answer the secondary confirmation challenge 115.

However, in other embodiments the secondary confirmation challenge 115 will take different forms. Illustrating by example, in another embodiment the secondary confirmation challenge 115 requests that the user type in the electronic payment transaction amount 712 in words. In still other embodiments, the secondary confirmation challenge 115 lists a plurality of user selectable math equations, with one user selectable math equation the plurality of user selectable math equations has a sum equal to the electronic payment transaction amount and other user selectable math equations of the plurality of user selectable math equations have other sums that are different from the electronic payment transaction amount. In still other embodiments, the secondary confirmation challenge 115 requests user to enter the electronic payment transaction amount 712 via audio.

In many embodiments, the secondary confirmation challenge 115 presents a list of user selectable options with only one user selectable option of the list corresponding to the electronic payment transaction amount 712, as is the case at step 105. In one or more embodiments, the secondary confirmation challenge 115 is different for each electronic payment transaction amount 712. Other examples of secondary confirmation challenges 115 will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

Once step 106 receives, at the user interface 112, the other user input 116 answering the secondary confirmation challenge 115, decision 107 determines whether the secondary confirmation challenge 115 was correctly answered. When decision 107 determines that the user input 116 answering the secondary confirmation challenge 115 correctly answers the secondary confirmation challenge 115, the one or more processors of the electronic device 100 complete, at step 108, the electronic payment transaction 711. However, in one or more embodiments, when decision 107 determines that the user input 116 answering the secondary confirmation challenge 115 incorrectly answers the secondary confirmation challenge 115 the one or more processors of the electronic device 100 preclude the completion of the electronic payment transaction 711.

In one or more embodiments, optional decision 109 gives the patron 700 another chance to correctly answer a secondary confirmation challenge when the initial secondary confirmation challenge 115 is failed. Said differently, in one or more embodiments the one or more processors of the electronic device 100 are further configured to present, on the user interface 112, another secondary confirmation challenge when the other user input 116 received by the user interface 112 in response to presentation of the secondary confirmation challenge 115 fails the secondary confirmation challenge 115.

In one or more embodiments, however, this process does not last forever. Accordingly, decision 109 determines whether a predefined number of secondary confirmation challenges has been exceeded by presentation of the prompt 114 comprising the secondary confirmation challenge 115. In one or more embodiments, the preclusion of allowing the electronic payment transaction 711 to complete occurs only when the predefined number of secondary confirmation challenges has not been exceeded by the presentation of the prompt 114 comprising the secondary confirmation challenge 115. In one or more embodiments, when the predefined number of secondary confirmation challenges is exceeded by the presentation of the prompt 114 comprising the secondary confirmation challenge 115, the method of FIG. 1 can return to step 105 where another prompt and another secondary confirmation challenge can be presented. In one or more embodiments, each secondary confirmation challenge that is presented is different from any previously presented secondary confirmation challenge.

In this illustrative example, the other user input 116 answering the secondary confirmation challenge 115 fails to correctly answer the secondary confirmation challenge 115. To wit, the electronic payment transaction amount 712 is $87.90, while the other user input 116 selected an electronic payment transaction amount of $8.79, thereby failing the secondary confirmation challenge 115. Accordingly, at step 111 the one or more processors of the electronic device 100 preclude completion of the electronic payment transaction 711. As shown, the patron 700 is delighted, as the electronic device 100 has just saved him nearly eighty bones by detecting his errant definition of the electronic payment transaction amount 712 and precluding the electronic payment transaction 711 from occurring. The patron 700 is therefore able to re-initiate the electronic payment transaction 711 with the correct electronic payment transaction amount.

In one or more other embodiments, when the user provides the wrong answer to secondary confirmation challenge, then alternatively, system can also update the electronic transaction payment to one of the amount selected (entered) by the user upon confirmation and proceed with the payment. Such an embodiment helps in not only identifying/preventing the mistake but also correcting the mistake and still making the payment seamless.

Turning now to FIG. 2, illustrated therein is one electronic device 100 configured in accordance with one or more embodiments of the disclosure. The electronic device 100 of this illustrative embodiment includes a user interface 112. In one or more embodiments, the user interface 112 comprises a display 201, which may optionally be touch-sensitive. The display 201 can serve as a primary user interface 112 of the electronic device 100.

Where the display 201 is touch sensitive, users can deliver user input to the display 201 by delivering touch input from a finger, stylus, or other objects disposed proximately with the display. In one embodiment, the display 201 is configured as an active-matrix organic light emitting diode (AMOLED) display. However, it should be noted that other types of displays, including liquid crystal displays, would be obvious to those of ordinary skill in the art having the benefit of this disclosure.

The explanatory electronic device 100 of FIG. 2 includes a housing 203. Features can be incorporated into the housing 203. Examples of features that can be included along the housing 203 include an imager 209, shown as a camera in FIG. 2, or an optional speaker port. A user interface component, which may be a button or touch sensitive surface, can also be disposed along the housing 203.

A block diagram schematic 200 of the electronic device 100 is also shown in FIG. 2. In one embodiment, the electronic device 100 includes one or more processors 206. In one embodiment, the one or more processors 206 can include an application processor and, optionally, one or more auxiliary processors. One or both of the application processor or the auxiliary processor(s) can include one or more processors. One or both of the application processor or the auxiliary processor(s) can be a microprocessor, a group of processing components, one or more Application Specific Integrated Circuits (ASICs), programmable logic, or other type of processing device.

The application processor and the auxiliary processor(s) can be operable with the various components of the electronic device 100. Each of the application processor and the auxiliary processor(s) can be configured to process and execute executable software code to perform the various functions of the electronic device 100. A storage device, such as memory 212, can optionally store the executable software code used by the one or more processors 206 during operation.

In this illustrative embodiment, the electronic device 100 also includes a communication device 208 that can be configured for wired or wireless communication with one or more other devices or networks. The networks can include a wide area network, a local area network, and/or personal area network. The communication device 208 may also utilize wireless technology for communication, such as, but are not limited to, peer-to-peer, or ad hoc communications such as HomeRF, Bluetooth and IEEE 802.11 based communication, or alternatively via other forms of wireless communication such as infrared technology. The communication device 208 can include wireless communication circuitry, one of a receiver, a transmitter, or transceiver, and one or more antennas 210.

The electronic device 100 can optionally include a near field communication circuit 207 used to exchange data, power, and electrical signals between the electronic device 100 and another electronic device. In one embodiment, the near field communication circuit 207 is operable with a wireless near field communication transceiver, which is a form of radio-frequency device configured to send and receive radio-frequency data to and from the companion electronic device or other near field communication objects.

Where included, the near field communication circuit 207 can have its own near field communication circuit controller in one or more embodiments to wirelessly communicate with companion electronic devices using various near field communication technologies and protocols. The near field communication circuit 207 can include—as an antenna—a communication coil that is configured for near-field communication at a particular communication frequency. The term “near-field” as used herein refers generally to a distance of less than about a meter or so. The communication coil communicates by way of a magnetic field emanating from the communication coil when a current is applied to the coil. A communication oscillator applies a current waveform to the coil. The near field communication circuit controller may further modulate the resulting current to transmit and receive data, power, or other communication signals with companion electronic devices.

In one embodiment, the one or more processors 206 can be responsible for performing the primary functions of the electronic device 100. For example, in one embodiment the one or more processors 206 comprise one or more circuits operable to present presentation information, such as images, text, and video, on the display 201. The executable software code used by the one or more processors 206 can be configured as one or more modules 213 that are operable with the one or more processors 206. Such modules 213 can store instructions, control algorithms, and so forth.

In one embodiment, the one or more processors 206 are responsible for running the operating system environment 214. The operating system environment 214 can include a kernel, one or more drivers, and an application service layer 215, and an application layer 216. The operating system environment 214 can be configured as executable code operating on one or more processors or control circuits of the electronic device 100.

The application service layer 215 can be responsible for executing application service modules. The application service modules may support one or more applications 217 or “apps.” Examples of such applications include a cellular telephone application for making voice telephone calls, a web browsing application configured to allow the user to view webpages on the display 201 of the electronic device 100, an electronic mail application configured to send and receive electronic mail, a photo application configured to organize, manage, and present photographs on the display 201 of the electronic device 100, and a camera application for capturing images with the imager 209. Collectively, these applications constitute an “application suite.” In one or more embodiments, these applications comprise one or more e-commerce applications 224 and/or banking applications 225 that allow electronic commerce orders to be placed and financial transactions to be made using the electronic device 100.

Illustrating by example, in one or more embodiments a user can deliver user input to an e-commerce application 224 or a banking application 225 to enter an electronic payment transaction 204 request defining an electronic payment transaction amount 205 or otherwise request an electronic payment transaction occur. In one or more embodiments, when this occurs, the one or more processors 206 are configured to present a secondary confirmation challenge 218 generated by a challenge generator 202 questioning the electronic payment transaction amount 205.

In one or more embodiments, the secondary confirmation challenge 218 presents a list 219 of user selectable options with only one user selectable option of the list 219 corresponding to the electronic payment transaction amount 205. In one or more embodiments, the user selectable options comprise electronic payment transaction amounts spelled out in words. In other embodiments, the user selectable options comprise math equations. Other user selectable options will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

In one or more embodiments, when other user input received by the user interface 112 in response to the presentation of the secondary confirmation challenge 218 fails the secondary confirmation challenge 218, the one or more processors 206 are configured to preclude the electronic payment transaction 204 from occurring, as previously described.

In one or more embodiments, the one or more processors 206 are responsible for managing the applications and all personal information received from the user interface 112 that is to be used by the e-commerce application 224 and/or banking application 225 after the electronic device 100 is authenticated as a secure electronic device and the user identification credentials have triggered an electronic payment transaction request 204. The one or more processors 206 can also be responsible for launching, monitoring, and killing the various applications and the various application service modules. In one or more embodiments, the one or more processors 206 are operable to not only kill the applications, but also to expunge any and all personal data, data, files, settings, or other configuration tools when the electronic device 100 is reported stolen or when the e-commerce application 224 and/or banking application 225 are used with fraudulent activity to wipe the memory 212 clean of any personal data, preferences, or settings of the person previously using the electronic device 100.

The one or more processors 206 can also be operable with other components 221. The other components 221, in one embodiment, include input components, which can include acoustic detectors as one or more microphones. The one or more processors 206 may process information from the other components 221 alone or in combination with other data, such as the information stored in the memory 212 or information received from the user interface.

The other components 221 can include a video input component such as an optical sensor, another audio input component such as a second microphone, and a mechanical input component such as button. The other components 221 can include one or more sensors 226, which may include key selection sensors, touch pad sensors, capacitive sensors, motion sensors, and switches. Similarly, the other components 221 can include video, audio, and/or mechanical outputs.

The one or more sensors 226 may include, but are not limited to, accelerometers, touch sensors, surface/housing capacitive sensors, audio sensors, and video sensors. Touch sensors may be used to indicate whether the electronic device 100 is being touched at side edges. The other components 221 of the electronic device can also include a device interface to provide a direct connection to auxiliary components or accessories for additional or enhanced functionality and a power source, such as a portable battery, for providing power to the other internal components and allow portability of the electronic device 100.

In one or more embodiments, the electronic device 100 comprises a prompt generator 230 as well. In one or more embodiments, the prompt generator generates a prompt 220 comprising a secondary confirmation challenge 218 when a secondary confirmation operation is triggered. Illustrating by example, the one or more processors 206 can present, on the user interface 112, a prompt 220 generated by the prompt generator 230 comprising a secondary confirmation challenge 218 requiring other user input at the user interface 112 re-entering the electronic payment transaction amount 205 in a different format, such as in different words, via math equations, via selection from a list 219, or by other techniques.

In one or more embodiments, the electronic device 100 also includes a transaction manager 211. In one or more embodiments, the transaction manager 211 and the prompt generator 230 can be operable with one or more processors 206, configured as a component of the one or more processors 206, or configured as one or more executable code modules operating on the one or more processors 206. In other embodiments, the transaction manager 211 and the prompt generator 230 can be standalone hardware components operating executable code or firmware to perform their functions. Other configurations for the transaction manager 211 and the prompt generator 230 will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

It is to be understood that FIG. 2 is provided for illustrative purposes only and for illustrating components of one electronic device 100 in accordance with embodiments of the disclosure and is not intended to be a complete schematic diagram of the various components required for an electronic device. Therefore, other electronic devices in accordance with embodiments of the disclosure may include various other components not shown in FIG. 2 or may include a combination of two or more components or a division of a particular component into two or more separate components, and still be within the scope of the present disclosure.

Turning now to FIG. 3, illustrated therein is one explanatory method 300 in accordance with one or more embodiments of the disclosure. Beginning at step 301, the method 300 receives, by a user interface, either user input or a QR-code scan or payment link defining an electronic payment transaction amount. Decision 302 then determines, by one or more processors operable with the user interface, whether the electronic payment transaction amount meets a predefined criterion triggering a secondary confirmation operation. Where no secondary confirmation operation is triggered, step 305 completes the electronic payment transaction.

Examples of such criteria include one or more of whether the electronic payment transaction amount exceeds a predefined threshold 308, whether the electronic payment transaction amount exceeds a predetermined average electronic payment transaction amount 309, whether the electronic payment transaction is requested at a predetermined time of day 310, whether the electronic payment transaction is requested while the electronic device is situated in a predefined location 311, and whether the electronic payment transaction is directed to a recipient 312 to whom previous electronic payment transactions have occurred. Others will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

Where the electronic payment transaction amount triggers a secondary confirmation challenge, step 303 comprises presenting a prompt comprising a secondary confirmation challenge. In one or more embodiments, the secondary confirmation challenge requires other user input at the user interface re-entering the electronic payment transaction amount in a different format. Other examples of secondary confirmation challenges were described above. Still others will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

Decision 304 determines whether other user input received by the user interface correctly answers the secondary confirmation challenge. Where it does, step 305 completes the electronic payment transaction. By contrast, where it does not, decision 306 determines whether a predefined number of secondary confirmation challenges have been failed. Where they have not, another prompt can optionally be presented at step 303. Otherwise, one or more processors of the electronic device preclude execution of the electronic payment transaction associated with the electronic payment transaction amount at step 307. In one or more embodiments, this occurs when the other user input answering the secondary confirmation challenge fails to re-enter the electronic payment transaction amount in a different format.

Turning now to FIGS. 4 and 5, illustrated therein are different examples of secondary confirmation challenges 415,515 in accordance with one or more embodiments of the disclosure. While the secondary confirmation challenge (115) of FIG. 1 presented a list of electronic payment transaction amounts in words, the secondary confirmation challenges 415,515 of FIGS. 4-5 take different forms.

Beginning with FIG. 4, in this example the secondary confirmation challenge 415 asks the patron 700 to enter the electronic payment transaction amount in words. Accordingly, the patron 700 would enter “eight dollars and seventy-nine cents” to answer the secondary confirmation challenge 415. If the patron did not enter “eighty-seven dollars and ninety cents,” the electronic payment transaction defining this electronic payment transaction amount would be precluded.

By contrast, the secondary confirmation challenge 515 of FIG. 5 asks the patron 700 to select the electronic payment transaction amount from a list listing various electronic payment transaction amounts as math equations. Unless the patron 700 selected the second option on the list, the electronic payment transaction associated with the electronic payment transaction amount would be precluded from completion. Again, the examples of FIGS. 1, 4, and 5 are illustrative only, as numerous others will be obvious to those of ordinary skill in the art having the benefit of this disclosure.

Turning now to FIG. 6, illustrated therein are various embodiments of the disclosure. The embodiments of FIG. 6 are shown as labeled boxes in FIG. 6 due to the fact that the individual components of these embodiments have been illustrated in detail in FIGS. 1-5, which precede FIG. 6. Accordingly, since these items have previously been illustrated and described their repeated illustration is no longer essential for a proper understanding of these embodiments. Thus, the embodiments are shown as labeled boxes.

At 601, a method in an electronic device comprises receiving, at a user interface, user input requesting an electronic payment transaction and defining an electronic payment transaction amount. At