Wallet application for interacting with a secure element application without a trusted server for authentication

A payment device, comprising:

• a secure element embedded within a chip, the secure element comprising:
• a first memory,
• a second memory,
• a control applet,
• a first sharable interface object (SIO) within the first memory and owned by the control applet,
• a plurality of card applets,
• a second SIO within the second memory and owned by one of the plurality of card applets,
• a firewall operable to separate the first SIO within the first memory and the second SIO within the second memory and to support secure data access and transfer between the first SIO within the first memory and the second SIO within the second memory through the firewall, and
• a registered list of the card applets, wherein the registered list comprises an application identifier (AID) for each of the card applets resident in the secure element,
• a software application midlet that receives an input of a selection of at least one of the plurality of card applets to configure from the registered list of card applets, and
• a secure channel via which the selected card applet's AID and a computer-coded instruction for a selected function to be performed on the selected card applet are communicated to the control applet on the secure element,
• wherein the control applet requests data access to the second SIO across the firewall and invokes process method function calls of a card runtime environment, wherein the process method function calls are defined by a card issuer corresponding to the selected card applet to perform the selected function on the selected card applet, and
• wherein the card runtime environment executes the process method function calls, thereby performing the selected function on the selected card applet.

A payment device, comprising:

• a secure element embedded within a chip of a device used for payments;
• a first memory embedded within the secure element, the first memory operable to store a control application and a first sharable interface object (SIO) within and owned by the control application;
• a second memory embedded within the secure element, the second memory operable to store a card application and a second SIO within and owned by the card application;
• a secure firewall embedded within the secure element operable to separate the first SIO and the second SIO, the secure firewall being further operable to support secure data transfer between the first SIO and the second SIO through the firewall in response to the control applet requesting data access from to the second SIO through the secure firewall;
• and
• a card runtime environment operable to receive, from a remote trusted service manager (TSM), a received application identifier (AID) code and one or more computer-coded instructions, wherein the one or more computer coded instructions support performing a function upon the card application through the secure firewall in response to the received AID corresponding to an AID associated with the card application.