Methods and systems are provided for making secure financial transactions, such as purchase payments, using rich Internet applications (RIA) running an RIA runtime (also referred to as a platform or framework) on the user's smart phone or other mobile device. Embodiments differ from the usual way of re-directing a user from a third-party application and authenticating the user by providing secure in-line payments from a rich Internet application running on an RIA runtime. A system includes: a mobile device executing a rich Internet application running on an RIA runtime; a payment library communicating with the RIA runtime and a service provider, for which the payment library communicates with the service provider to authenticate the rich Internet application; and in response to authentication by the service provider, facilitates secure financial transactions via the rich Internet application.

An applications programming interface (API) or other interface may be configured for use with a plurality of e-commerce applications and/or a plurality of payment systems. The API may be associated with an operating system of a client or may be otherwise located in an e-commerce system or network. The API may receive a call regarding a purchase transaction. The purchase transaction may be examined to determine if a payment method is synchronous or asynchronous. An appropriate payment system may be activated to perform the purchase transaction based at least in part on the determination made by the examination of the purchase transaction. A result of the purchase transaction may be sent to the e-commerce program. By revision of the API, developers of e-commerce applications are freed from the burden of revising code in response to the need to utilize additional or differently operated payment systems.

There are provided systems and methods for software development kits for point-of-sale device and mobile device interactive frameworks. A service provider, such as a payment provider, that offers online and cloud based digital wallet services may configure flexible software frameworks for a merchant's point-of-sale device and a user's mobile device. A framework for a merchant's device may allow for user check-in with the merchant, and may utilize multiple different communication protocols to receive tenders and non-tenders from the user's mobile device. Thus, the user's mobile device may communicate with the merchant device to provide tokens that may be resolved by the merchant using the payment provider and/or a payment host to receive payment processing confirmation. Moreover, the frameworks may allow for a transaction to be synchronized to the user's mobile device so that the user may receive updates after processing of the tokens.

Example embodiments of systems and methods for contactless card verification include a contactless card including a substrate, a processor, and a memory, wherein the memory contains a first applet and a second applet, and a recipient device in data communication with the contactless card, wherein the second applet is configured to retrieve one or more parameters from the first applet via an interface; and wherein the second applet is configured to transmit the one or more parameters to the recipient device for verification.

This disclosure relates to systems and methods for processing electronic payments for customer purchases. In some implementations, a system receives a payment request from a merchant, and transmits payment information to a mobile computing device associated with the merchant. The payment information includes a transaction ID to identify the purchase, a purchase amount, and instructions that cause the mobile computing device to activate a card reader, present a notification of the purchase amount to the customer, receive an acceptance of the purchase amount from the customer, and authorize the card reader to process an electronic payment for the purchase amount. The system receives payment confirmation from the mobile computing device, and provides the parameter confirmation to the merchant.

This disclosure relates to systems and methods for processing electronic payments for customer purchases. In some implementations, a mobile computing device receives a payment request identifying a sales transaction between a merchant and a customer. The payment request indicates a purchase amount owed by the customer to the merchant, and carries a set of instructions. The mobile computing device activates a card reader based at least in part on the set of instructions, receives customer authorization for electronic payment of the purchase amount, instructs the card reader to process a credit card for the purchase amount based on receiving the customer authorization, and receives confirmation of payment of the purchase amount from the card reader.

A Digital Transaction Processing Unit (DTPU) operable to host one or more transaction applications, each transaction application for digitally transacting with a Digital Transaction Device (DTD), the DTPU further operable to be reversibly placed into a disabled state such that the DTPU is inoperable for a digital transaction with a DTD.

An apparatus for a Digital Payment Device (DPD) operable for a digital transaction with a Digital Transaction Device (DTD), the apparatus being operable to provide transaction application identifier information for communication from the DPD to the DTD in a digital transaction, the apparatus including: an application selection module; on the DPD, a Digital Transaction Processing Unit (DTPU) operable to host one or more Personalized Digital Transaction Packages (PDTPs), each PDTP associated with at least one transaction application having a transaction application identifier; the DPD being operable to select at least one hosted PDTP to be operable for a digital transaction with the DTD; wherein the apparatus is operable to receive one or more commands to cause the application selection module to be set with a transaction application identifier for each transaction application associated with the selected at least one PDTP, such that the application selection module is operable to include, in the transaction application identifier information, the transaction application identifier for each transaction application associated with the selected at least one PDTP.

A Digital Transaction Processing Unit (DTPU) including one or more transaction applications operable for a digital transaction with a Digital Transaction Device (DTD), each of the one or more transaction applications being associated with identifying information, the identifying information being capable of identifying a subset of at least one transaction application within the one or more transaction applications, wherein the DTPU is operable, when conducting a transaction with the DTD, to communicate to the DTD the identifying information associated with one of the one or more transaction applications involved in the transaction.

A provisioning agent for provisioning a Digital Payment Device (DPD) which includes a Digital Transaction Processing Unit (DTPU) operable to host one or more transaction applications, the DTPU being further operable to adopt at least one transaction application selected from the one or more transaction applications, the DPD operable for a digital transaction with a Digital Transaction Device (DTD) using the adopted at least one transaction application, the provisioning agent being operable to provide provisioning data to the DPD, the DPD further including apparatus operable to receive the provisioning data, the provisioning data being operable to provide one or more functions to the DPD, the provisioning agent being operable to: prepare one or more first digital objects, receive one or more second digital objects from a second provisioning agent, include at least one of the one or more first digital objects and at least one of the one or more second digital objects in the provisioning data.