Systems, devices and methods for digital payments

Abstract

A system, apparatus, and method for performing a payment using a web browser. The payment is performed by activating a uniform resource locator (URL) linked to a website on a server, the website having an embedded payment program loaded with a predetermined payment amount, and installing the embedded payment program on a mobile device. The payment program is configured to transfer payment data to a payment terminal via a near field communication (NFC) radio. The payment program is deleted after the payment is performed.

Description

[Technical field]

[0001] Some embodiments described herein relate generally to digital payment methods and systems, and more particularly to digital payment methods and systems for transacting currency over a digital network. [Background technology]

[0002] A digital payment system may use a digital wallet to effect payments over the Internet and / or metered networks and / or stores. A digital wallet may have and / or contain a purchaser's credit card information and / or bank account information and / or any other payment method and / or balance. A digital wallet has access to such purchaser's payment account and / or account for purchasing goods over the Internet or in a brick-and-mortar store. Thus, storing credit card information in a digital wallet may raise a wide range of security issues.

[0003] There is a need to provide a solution for purchasing goods and services using a computing device without the use of a persistent digital wallet application. Summary of the Invention

[0004] DETAILED DESCRIPTION OF THE DISCLOSURE Embodiments of the present disclosure relate to systems, methods, and servers for managing payments configured to use a web browser to make payments for goods and services, and are described below by way of example only.

[0005] One embodiment may include a system for effecting a payment by using a web browser to make a payment for goods and services, the system comprising a mobile device configured to receive a text message from a server comprising a uniform resource locator (URL) linked to a website at the server, activate the URL, which opens a web page comprising an embedded payment program loaded with a predetermined payment amount, installing the embedded payment program on the mobile device, activate, transfer payment card data and the predetermined payment amount to a payment terminal via a near field communication (NFC) radio of the mobile device by the embedded payment program, and delete the embedded payment program and the payment card data by closing the web page at the end of the transaction after effecting the payment.

[0006] For example, the payment terminal may include a EuroPay, MasterCard, Visa (EMV) terminal.

[0007] For example, payment card data may comply with the EMV standard.

[0008] For example, the embedded payment program may include a digital wallet program.

[0009] For example, a web page may include a graphical representation of an embedded payment program and one or more information elements.

[0010] For example, the embedded payment program is configured to control an NFC radio.

[0011] For example, the payment card data comprises at least one of bank account details, payment card data account holder expiry date, and a total amount available for payment.

[0012] For example, the system may include a server for managing payments, the server configured to generate a URL linked to a website at the server, the website including an embedded payment program configured to perform payments based on payment card data, and to send the URL in a text message to the mobile device.

[0013] For example, the payment terminal is configured to transmit purchase status information to the server.

[0014] For example, the predetermined payment amount may be selected from a national currency, a cryptocurrency, loyalty club points, and a coupon of monetary value.

[0015] Another embodiment may include a method for performing a payment by using a web browser for payment of goods and services operating on a mobile device, the method comprising receiving a text message from a server comprising a uniform resource locator (URL) linked to a website at the server, activating the URL, which may open a web page that may include an embedded payment program loaded with a predetermined payment amount, installing the embedded payment program on the mobile device, activating the embedded payment program, performing the payment via the embedded payment program configured to transfer payment card data to a payment terminal via a near field communication (NFC) radio of the mobile device, and deleting the embedded payment program by closing the web page at the end of the transaction after performing the payment.

[0016] Another alternative embodiment may include a server for effecting a payment, the server configured to generate a text message comprising a uniform resource locator (URL) linked to a website at the server, the website comprising an embedded payment program loaded with a predetermined payment amount and payment card data, and to send the URL to a mobile device to be activated and effect the payment via the embedded payment program configured to transfer the payment card data to a payment terminal via a near field communication (NFC) radio.

[0017] For example, after a payment is made, the embedded program and payment card data are deleted by closing the web page at the end of the transaction.

[0018] For example, the embedded payment program may include a digital wallet program loaded with a predetermined payment amount. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram of a system for purchasing goods and services using a web browser in accordance with some demonstrative embodiments. [Diagram 2] 1 is a flowchart of a method for purchasing goods and services using a one-time use digital wallet application uploaded via a webpage according to some demonstrative embodiments. [Diagram 3] 1 is a block diagram of a web page in accordance with some demonstrative embodiments. [Figure 4] 1 is a frame of payment card data in accordance with some demonstrative embodiments. [Diagram 5] 1 is an illustration of a manufactured product in accordance with some demonstrative embodiments. [Figure 6]1 is a block diagram of a system for purchasing goods and services using a web browser and a method flow for purchasing goods and services, according to some demonstrative embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of some embodiments. However, it will be understood by those skilled in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and / or circuits have not been described in detail so as not to obscure the discussion.

[0021] For example, discussions made herein utilizing terms such as "processing," "calculating," "computing," "determining," "establishing," "analyzing," "examining," and the like may refer to operations and / or processes of a computer, computing platform, computing system, or other electronic computing device that manipulates and / or transforms data represented as physical (e.g., electronic) quantities in the computer's registers and / or memory into other data similarly represented as physical quantities in the computer's registers and / or memory, or other information storage medium that may store instructions for performing the operations and / or processes.

[0022] As used herein, the terms "plurality" and "a plurality" include, for example, "multiple" or "two or more." For example, "a plurality of items" includes two or more items.

[0023] References to "one embodiment," "an embodiment," "exemplary embodiment," "various embodiments," etc. indicate that the embodiment so described may include a particular feature, structure, or characteristic, but not all embodiments necessarily include the particular feature, structure, or characteristic. Moreover, repeated use of the phrase "in one embodiment" may, but does not necessarily, refer to the same embodiment.

[0024] As used herein, unless otherwise specified, the use of the ordinal adjectives "first," "second," "third," etc. to describe a common object is intended merely to indicate that different instances of a similar object are being referred to, and is not intended to imply that the objects so described must be in a given order, either in time, space, ranking, or in any other manner.

[0025] As used herein, the term "circuitry" may refer to, be a part of, or include application specific integrated circuits (ASICs), integrated circuits, electronic circuits, processors (shared, dedicated, or groups), and / or memories (shared, dedicated, or groups) that execute one or more software or firmware programs, combinatorial logic circuits, and / or other suitable hardware components that provide the described functionality. In some demonstrative embodiments, the circuitry may be implemented in one or more software or firmware modules, or functions associated with the circuitry may be implemented by one or more software or firmware modules. In some demonstrative embodiments, the circuitry may include logic that is at least partially operable in hardware.

[0026] The term "logic" may refer to, for example, computing logic embedded in circuitry of a computing device and / or stored in memory of a computing device. For example, the logic may be accessible by a processor of the computing device to execute the computing logic to perform computing functions and / or operations. In one example, the logic may be embedded in various types of memory and / or firmware, e.g., various chips and / or silicon blocks of a processor. The logic may be included in and / or implemented as part of various circuitry, e.g., radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, etc. In one example, the logic may be embedded in volatile and / or non-volatile memory, including random access memory, read-only memory, programmable memory, magnetic memory, flash memory, persistent memory, etc. The logic may be executed by one or more processors, for example, using memory, e.g., registers, stacks, buffers, etc., coupled to the one or more processors as necessary to execute the logic.

[0027] As used hereinafter, the term "module" is an object file that contains code that extends the running kernel environment.

[0028] As used herein, the term "software engine" as used hereinafter is an object file that contains code that extends the executing kernel environment.

[0029] The term "digital wallet" as used below is both a software component and an information component. The digital wallet may be stored on the client side. The digital wallet may transfer payments, for example using near field communication (NFC) on the smartphone, by touching the smartphone to a payment terminal at a store.

[0030] The term "EMV" as used below is a payment method based on technology standards for smart payment cards and for payment terminals and automated teller machines. EMV was originally an abbreviation for "EuroPay, Mastercard and Visa", the three companies that created the global payment standard.

[0031] As used hereinafter, the term "EMV terminal" is a payment terminal, also known as a point of sale (POS) terminal, credit card terminal, etc. An EMV terminal is a device that interfaces with payment cards, e.g., EuroPay, MasterCard, and Visa, to effect electronic funds transfers. Typically, the terminal consists of a secure keypad for entering a PIN, a screen, a means of obtaining information from the payment card, and a network connection to access the payment network for authorization.

[0032] In some demonstrative embodiments, the payment terminal may enable the merchant to obtain the necessary credit and / or debit card information and transmit this data to a merchant service provider and / or bank for authorization and transfer of funds to the merchant. The terminal may enable the merchant and / or its clients to swipe, insert, and / or hold a card near the device to capture the information.

[0033] The term "card" as used hereinafter may include, for example, prepaid cards, credit cards, debit cards, etc. created and issued by an issuer.

[0034] As used hereinafter, the term "customer credit card terminal" may include transaction terminals, EMV and / or non-EMV, that may be used by the customer platform to generate payment card data for each end-user credit card associated with a customer mobile application. For example, such terminals may reside with a payment gateway company or a processor company.

[0035] As used hereinafter, the term "customer mobile application" may include at least one application installed on a customer's computing device, such as a loyalty club application, an electronic wallet application, etc. The customer mobile application may include a digital wallet SDK and may interact with the digital wallet platform and the customer platform. The customer mobile application may be configured to run on a computing device operating system, such as iOS, Android, or React.

[0036] The term "payment card data" as used below may include unique placeholders called payment card data and / or payment data and / or payment elements, which are configured to include encrypted information of a user's payment capabilities, such as, for example, credit card, debit card, bank transfer information, etc. For example, the payment card data may be embedded in a payment card token. The payment card data may include a payment card number. For example, if the payment card number is 1234567887654321, the payment card data identifier may be, for example, E67TL8GC27X. In some demonstrative embodiments, the payment card data may be configured to, for example, access, obtain, and maintain a customer's credit card information, ensuring a higher level of security for both the customer and the business. The payment card data may be stored in a customer platform and / or a customer's single-use mobile application. In some demonstrative embodiments, the payment card data may include single-use payment card data.

[0037] As used below, the term Uniform Resource Locator (URL), sometimes colloquially referred to as a Web address, is a reference to a Web resource that specifies its location on a computer network and a mechanism for obtaining that location. A URL is a specific type of Uniform Resource Identifier (URI), but many people use the two terms interchangeably. URLs are most commonly used to reference Web pages (HTTP), but are also used for file transfer (FTP), electronic mail (mailto), database access (JDBC), and many other applications. For example, a Web browser may display the URL of a Web page above the page in the address bar. A URL may have the form http: / / www.example.com / index.html, which indicates the protocol (HTTP), the hostname (www.example.com), and the filename (index.html).

[0038] The term "Payment Card Data Service Provider (PCDSP)" as used hereinafter is an entity authorized by, for example, MasterCard, Visa, or any other issuer authorized to generate EMV data. A PCDSP may include an entity in a payment ecosystem configured to provide registered payment card data to a requester, such as a merchant that holds card credentials with a "surrogate" Primary Account Number (PAN) value, otherwise known as payment card data. For example, if desired, the service may be provided by a gateway service.

[0039] Reference is initially made to FIG. 1, which is a block diagram of a system 100 for purchasing goods and services using a web browser 130, in accordance with some demonstrative embodiments.

[0040] In some demonstrative embodiments, system 100 may include a computing device 110. For example, computing device 110 may include a smartphone, a tablet, a mobile computer, an electronic wallet, a dongle, a desktop computer, a computing device, etc.

[0041] In some demonstrative embodiments, computing device 110 may include processing circuitry 120. For example, processing circuitry 120 may include one or more processors having one or more cores, digital signal processors, graphics processors, communications processors, one or more memories, etc.

[0042] In some demonstrative embodiments, computing device 110 may include a near field communication (NFC) radio 125. For example, NFC radio 125 may be configured to transfer payment card data to a payment terminal 140 via a payment program 134. For example, the transfer of payment card data may occur by connecting computing device 110 to a payment terminal 140, e.g., at a point of sale (POS) (not shown) at a store, restaurant, service provider, office, etc.

[0043] In some demonstrative embodiments, payment program 134 may be embedded in web page 130 and may include temporary digital wallet software. For example, the temporary digital wallet software may load payment card data and control NFC radio 125 using processing circuitry 120. The processing circuitry may operate NFC radio 125 to transfer the payment card data and the payment to payment terminal 140.

[0044] In some demonstrative embodiments, system 100 may include a payment server 160. Payment server 160 may include a downloadable payment program 162, a URL generator 164, and a payment card data generator module 166.

[0045] In some demonstrative embodiments, payment card data generator 166 may be operably connected to a payment card issuer server 170. Payment card issuer server 170 may issue one or more payment cards 172, such as credit cards, debit cards, loadable cards, loyalty club cards, gift cards, etc.

[0046] The payment card issuer server 170 may receive the payment card data from the payment terminal 140 and may forward the payment to a merchant and / or a service provider, etc.

[0047] In some demonstrative embodiments, payment card data generator module 166 may generate payment card data 134 based on a payment card, e.g., a credit card 172, at an issuer server 170. For example, the payment card data may include a predetermined payment amount and / or credits used by a user.

[0048] For example, the predetermined payment amount may be selected from a national currency, a cryptocurrency, loyalty club points, and a coupon of monetary value.

[0049] In some demonstrative embodiments, URL generator module 164 may be configured to generate URL 150. URL 150 may include a link to a website that embeds payment program 162 and / or payment card data, e.g., payment card data 134.

[0050] In some demonstrative embodiments, the computing device 110 may receive the URL 150 as a text message, such as, for example, a short message service (SMS), and / or any other format used by one or more text applications. For example, by clicking on the URL, the web browser 132 may download a web page at the mobile device 110 that enables activation of the payment program 134 and payment data 134.

[0051] The use of a temporary digital wallet containing temporary payment card data has the advantage that it may improve the user's security against hacking and theft of payment card data. Furthermore, it is a new, easy and secure way to transfer money to the user. The user may use the payment card data on any device by clicking on the URL provided in the text message.

[0052] In some demonstrative embodiments, the payment program may remain installed until a payment session is in progress and may be deleted along with the payment card data once the payment session is over. Advantageously, this method of operation may apply the highest level of security to protect users from hacking, and payment card data is not left stored on the computing device.

[0053] In some demonstrative embodiments, a system 100 for managing payments may be configured to perform a payment for goods and services using a web browser 130. The system 100 may include a computing device 110, such as, for example, a mobile device. The computing device 110 may be configured to activate a URL 150. The URL 150 may be linked to a website on a server, which may include a payment program 162 and / or payment card data 134. The payment program 162 may be configured to perform a payment based on the payment card data 134. For example, the payment data 134 may be loaded into payment card data 168. The computing device 110 may perform the payment via the payment program 132.

[0054] For example, the payment card data may include at least one of bank account details, account holder details, available amount, and / or any other data.

[0055] In some demonstrative embodiments, the payment program 132 may be configured to transfer the payment data 134 to the payment terminal 140 via the NFC radio 125. The payment program 132 may be deleted after performing a payment. For example, deletion of the payment program 132 may occur by closing the web page and / or by closing the program and / or by closing the web browser 130.

[0056] In some demonstrative embodiments, payment terminal 140 may include a EuroPay, MasterCard, Visa (EMV) terminal, and / or any other terminal.

[0057] In some demonstrative embodiments, activation of URL 150 may cause web browser 130 to open a web page and activate payment program 132. For example, activation of URL 150 may trigger web browser 130 to download and install payment program 132. In some other demonstrative embodiments, payment program 132 may be embedded in a web page, for example, as an instance. The web page may be programmed in ActiveX and / or JavaScript and / or HTML language, and / or any other programming language.

[0058] In some demonstrative embodiments, payment program 132 may be configured to enable NFC radio 125 to transfer payment card data 134 to EMV terminal 140 and / or any other terminal. For example, payment program 132 may include a digital wallet program and / or any other type of payment program. It should be understood that the digital wallet program may be a temporary digital wallet program that may be deleted when the web page and / or web browser 130 is closed.

[0059] In some demonstrative embodiments, the web page may include a graphical representation of the URL 150 and one or more instructions on how to activate the URL and / or how to make a purchase using the payment program 132.

[0060] In some demonstrative embodiments, server 160 may include a server for managing payments, e.g., a payment server. Server 160 may be configured to generate URL 150, which may be linked to a resource at server 160, e.g., a website. For example, website may include embedded payment program 162, which may be configured to perform payment based on payment card data 168. Payment program 162 may be configured to perform payment based on payment data uploaded to payment card data 168. For example, server 160 may send URL 150 to computing device 110.

[0061] In some demonstrative embodiments, the payment data may include a predetermined payment amount. For example, the predetermined payment amount may be selected from a national currency, a cryptocurrency, loyalty club points, a coupon of monetary value, etc.

[0062] In some demonstrative embodiments, server 160 may be configured to send the URL to mobile device 110 in a text message 150 .

[0063] Reference is now made to FIG. 2, which is a schematic diagram of a flow chart of a method 200 for purchasing goods and services using a one-time use digital wallet application uploaded via a webpage, according to some demonstrative embodiments.

[0064] In some demonstrative embodiments, method 200 may be configured to perform a payment by using a web browser for payment of goods and services. Method 200 may be operated by a payment program, e.g., a digital wallet, installed on a mobile device, e.g., computing device 110 (FIG. 1).

[0065] In some demonstrative embodiments, method 200 is configured to receive, at computing device 110 (text box 210), a URL, e.g., URL 150 (FIG. 1), from a server, e.g., payment server 160 (FIG. 1). A user may activate URL 150, which may be linked to a resource at server 160. For example, the resource may include payment card data and a payment program. For example, the payment program, e.g., a digital wallet, may be configured to perform a payment based on the payment data uploaded to the payment card data.

[0066] In some demonstrative embodiments, activating the URL opens a web page in a web browser. The web page may include a payment program, e.g., payment program 162 (FIG. 1), and payment card data, e.g., payment card data 134 (text box 220).

[0067] In some demonstrative embodiments, the payment program may perform the payment by transferring payment card data via an NFC radio, e.g., NFC radio 125 (FIG. 1), to a payment terminal, e.g., payment terminal 140 (FIG. 1) (text box 230).

[0068] In other demonstrative embodiments, transfer of payment data to a payment terminal and / or directly to a merchant / merchant account may occur using any type of data transfer technology.

[0069] In some demonstrative embodiments, after transferring the payment to the merchant / seller's account and / or after completing the purchase session, the payment program may be deleted from the computing device when the web page and / or web browser is closed (text box 240).

[0070] Reference is now made to Figure 3, which illustrates a block diagram of a web page 300, according to some demonstrative embodiments. For example, the web page 300 may include one or more visual and / or interactive and / or informational elements 310, such as images, videos, text, forms, chat applications, and any other informational elements.

[0071] In some demonstrative embodiments, web page 300 may include a payment program 320. For example, payment program 320 may include a digital wallet application having payment card data. For example, the payment card data may be loaded with a predetermined payment amount and / or credits. The payment card data may be stored in the digital wallet program and / or application.

[0072] In other demonstrative embodiments, payment card data may be linked to digital wallet programs and / or applications.

[0073] Reference is now made to FIG. 4, which illustrates a frame of payment card data 400, according to some demonstrative embodiments.

[0074] In some demonstrative embodiments, payment card data 400 may include a header field 410, a payment card data field 420, a user data field 430, an expiration date field 440, an amount field 450, a credit field 460, and a footer field.

[0075] For example, payment card data field 420 may include data of the user's credit card, such as a credit card number, an expiration date, the user's bank account number, and a CCV number. User data field 430 may include, for example, the user's first name, the user's last name, a user identification number (ID), etc. Date field 440 may include, for example, an expiration date and / or time of payment card data 400. Total field 450 may include, for example, an amount the user can spend. Credit field 460 may include, for example, a credit limit for the user's payment card, and footer field 470 may include, for example, an authentication code for payment card data 400. It should be understood that in other embodiments, the payment card data may include different fields.

[0076] In some demonstrative embodiments, payment card data 400 may be encrypted when stored in payment program 132 (FIG. 1) and decrypted when transferred to payment terminal 140 (FIG. 1).

[0077] Reference is now made to FIG. 5, which is a schematic diagram of a manufacturing product 500, according to some demonstrative embodiments. The product 500 may include one or more tangible computer-readable non-transitory storage media 510, which may include computer-executable instructions 530, executed by a processing device 520, operable when executed by at least one computer processor to enable at least one processing circuitry 120 (FIG. 1) to execute one or more program instructions for purchasing goods and services using a payment program downloaded and installed by clicking on a link on a web page. At least one processing circuitry 120 (FIG. 1) may be configured to execute one or more program instructions and / or to perform, trigger, and / or implement one or more operations, communications, and / or functions described above with reference to FIGS. 1, 2, 3, 4, and 6. The phrase "non-transitory machine-readable medium" is intended to include all computer-readable media, except for transitory propagating signals.

[0078] In some demonstrative embodiments, the article 500 and / or the machine-readable storage medium 510 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or re-writable memory, etc. For example, the machine-readable storage medium 310 may include any type of memory, such as, for example, RAM, DRAM, ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, hard disk drive (HDD), solid state disk drive (SDD), fusion drive, etc. The computer-readable storage medium may include any suitable medium involved in downloading or transferring a computer program from a remote computer to a requesting computer, conveyed by a data signal embodied in a carrier wave or other propagation medium, via a communications link, for example, a modem, wireless communication, or a network connection.

[0079] In some demonstrative embodiments, processing device 520 may include logic. The logic may include instructions, data, and / or code that, when executed by a machine, may cause the machine to perform the methods, processes, and / or operations described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware, software, firmware, etc.

[0080] In some demonstrative embodiments, the processing device 520 may include or be embodied as software, firmware, software modules, applications, programs, subroutines, instructions, instruction sets, computing code, words, values, symbols, etc. The instructions 540 may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. The instructions may be implemented according to a predefined computer language, scheme, or syntax to instruct the processor to perform a particular function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled, and / or interpreted programming language, such as C, C++, C#, Java, Python, BASIC, Matlab, assembly language, machine code, etc.

[0081] Turning now to FIG. 6, which illustrates a block diagram of a system 600 for purchasing goods and services using a web browser 690 and method flow for purchasing goods and services in accordance with some demonstrative embodiments.

[0082] In some demonstrative embodiments, system 600 may include a server 675, a mobile device 680, and a payment terminal 685.

[0083] For example, the mobile device 680 may include a computing device 110 (FIG. 1), a mobile phone, a tablet, a laptop computer, etc.

[0084] In some demonstrative embodiments, server 675 may generate a payment URL (line 610). Mobile device 680 may receive a text message (not shown) (line 615) from server 675 that includes URL 150 (FIG. 1) that may be linked to a website at server 675. Mobile device 680 may activate URL 150 (FIG. 1) (line 625), which activation of URL 150 may open web page 690 (line 640).

[0085] For example, the web page 690 may include an embedded payment program 132 (FIG. 1) into which a predetermined payment amount may be loaded, and the embedded payment program may be installed on the mobile device (line 640). The mobile device 680 may be configured, via the embedded payment program, to transfer the payment card data 168 (FIG. 1) and the predetermined payment amount to the payment terminal 685 via the NFC radio 125 (FIG. 1) of the mobile device 680 (line 650), and, after making the payment, delete the embedded payment program and the payment card data by closing the web page at the end of the transaction (line 670).

[0086] For example, the predetermined payment amount may be selected from a national currency, a cryptocurrency, loyalty club points, a coupon of monetary value, and the like.

[0087] In some demonstrative embodiments, the mobile device 680 may be configured to transmit purchase status information to a server 675 (dotted line 660).

[0088] It should be understood that the system and / or method for effecting payments by using a web browser for payment of goods and services is described above by way of example only, and other embodiments may be implemented based on the detailed description and the following claims.

[0089] It should be understood that like numerals in the drawings represent like elements throughout the several drawings, and that not all components and / or steps described and illustrated with reference to the drawings are required for all embodiments or configurations.

[0090] It should also be understood that embodiments, implementations, and / or configurations of the systems and methods disclosed herein may be embodied as hardware, firmware, and / or software algorithms, applications, programs, modules, or code resident on a computer-usable medium (including software modules and browser plug-ins) that can be executed in a processor of a computer system or computing device to configure the processor and / or other elements to perform the functions and / or operations described herein.

[0091] It should be appreciated that, in accordance with at least one embodiment, the one or more computer programs, modules, and / or applications that, when executed, perform the methods of the present invention need not reside on a single computer or processor, but can be distributed in a modular manner among a number of different computers or processors to implement various aspects of the systems and methods disclosed herein.

[0092] Thus, exemplary embodiments and configurations of the present systems and methods provide computer-implemented methods, computer systems, and computer program products for processing code. The flowcharts and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments and configurations. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of code that comprises one or more executable instructions for implementing the specified logical function(s).

[0093] It should also be noted that in some alternative implementations, the functions shown in the blocks may occur in a different order than that shown in the figures. For example, two blocks shown in succession may be executed substantially simultaneously, or the blocks may be executed in the reverse order, depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by a special-purpose hardware-based system that performs the specified functions or operations, or by a combination of special-purpose hardware and computer instructions.

[0094] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the present invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly dictates otherwise. It will further be understood that the terms "comprises" and / or "comprising" as used herein specify the presence of described features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0095] Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of "including," "comprising," "having," "containing," "involving," and variations thereof herein are intended to encompass the items listed thereafter and equivalents thereof, as well as additional items.

[0096] The subject matter described above is provided for illustrative purposes only and should not be construed as limiting. Various modifications and changes can be made to the subject matter described herein without departing from the true spirit and scope of the invention as set forth in the following claims, without departing from the exemplary embodiments and applications shown and described.

Claims

1. 1. A system for effecting payments by using a web browser for making payments for goods and services, comprising: a mobile device, the mobile device comprising: receiving a text message from a server, the text message comprising a uniform resource locator (URL) linked to a website at said server; activating the URL, which opens a web page with an embedded payment program loaded with a predetermined payment amount, and installs the embedded payment program on the mobile device; transmitting, via the embedded payment program, payment card data and the predetermined payment amount to a payment terminal via a near field communication (NFC) radio of the mobile device; deleting the embedded payment program and the payment card data after effecting the payment and by closing the web page at the end of the transaction; The system is configured to:

2. The system of claim 1 , wherein the payment terminal comprises a EuroPay, MasterCard, Visa (EMV) terminal.

3. The system of claim 1 , wherein the payment card data complies with EMV standards.

4. The system of claim 1 , wherein the embedded payment program comprises a digital wallet program.

5. The system of claim 1 , wherein the web page comprises a graphical representation of the embedded payment program and one or more information elements.

6. The system of claim 1 , wherein the embedded payment program is configured to control the NFC radio.

7. 2. The system of claim 1, wherein the payment card data comprises at least one of bank account details, an account holder expiration date of the payment card data, and a total amount available for payment.

8. A server for managing settlement, the server comprising: generating the URL linked to a website on the server, the website comprising an embedded payment program configured to perform a payment based on payment card data; sending the URL in a text message to the mobile device; The system of claim 1 configured to:

9. The system of claim 1 , wherein the mobile device is configured to transmit purchase status information to the server.

10. The system of claim 1 , wherein the predetermined payment amount is selected from a national currency, a cryptocurrency, loyalty club points, and a coupon of monetary value.

11. 1. A method for performing payments by using a web browser for payment of goods and services operating on a mobile device, comprising: receiving a text message from a server, the text message comprising a uniform resource locator (URL) linked to a website at said server; activating the URL, which opens a web page with an embedded payment program loaded with a predetermined payment amount, and installs the embedded payment program on the mobile device; executing a payment with the embedded payment program configured to transmit payment card data to a payment terminal via a near field communication (NFC) radio of the mobile device; After executing the payment, deleting the embedded payment program by closing the web page at the end of the transaction. A method comprising:

12. The method of claim 11 , wherein the payment terminal comprises a EuroPay, MasterCard, Visa (EMV) terminal.

13. The method of claim 11 , wherein the payment card data complies with EMV standards.

14. The method of claim 11 , wherein the web page comprises a graphical representation of the embedded payment program and information related to a payment using the web page.

15. 12. The method of claim 11, wherein the payment card data comprises at least one of bank account details, account holder details, an expiry date of the payment card data, and a total amount available for payment.

16. The method of claim 11 , wherein the mobile device is configured to transmit purchase status information to the server.

17. The method of claim 11 , wherein the predetermined payment amount is selected from a national currency, a cryptocurrency, loyalty club points, and a coupon of monetary value.

18. A server for executing a payment, the server comprising: generating a text message with a uniform resource locator (URL) linked to a website on the server, the website having an embedded payment program loaded with a predetermined payment amount and payment card data; sending the URL to a mobile device to be activated; executing a payment with the embedded payment program configured to transmit payment card data to a payment terminal via a near field communication (NFC) radio; A server configured to:

19. 20. The server of claim 18, wherein after the payment is made, the embedded program and the payment card data are deleted by closing the web page at the end of the transaction.

20. 20. The server of claim 18, wherein the payment terminal comprises a EuroPay, MasterCard, Visa (EMV) terminal.

21. 20. The server of claim 18, wherein the payment card data complies with EMV standards.

22. 20. The server of claim 18, wherein the embedded payment program comprises a digital wallet program loaded with the predetermined payment amount.

23. 20. The server of claim 18, wherein the web page comprises a graphical representation of links for downloading software programs and information related to user payment card data.

24. 20. The server of claim 18, wherein the payment card data comprises at least one of bank account details, account holder details, an expiry date of the payment card data, and a total amount available for payment.

25. 20. The server of claim 18, configured to receive purchase status information from the mobile device configured to transmit to the server.

26. 20. The server of claim 18, wherein the predetermined payment amount is selected from a national currency, a cryptocurrency, loyalty club points, and a coupon of monetary value.

Images