Mobile on-card in-app commerce

A non-transitory, computer-readable medium storing one or more instructions, that when executed by a computer system, cause the computer system to:

• display, by a publisher application, content on a display of a computing device;
• transmit, by the publisher application over a network through an in-application (in-app) commerce software development kit (SDK), a request to a backend service for at least one predicted next-action, the at least one predicted next-action being contextually relevant to the content;
• receive, by the publisher application and from the backend service, at least one predicted next-action relevant to the publisher application, at least one service provider associated with, and capable of fulfilling, the at least one predicted next-action, and a backend public key, wherein the backend public key is received through the in-app SDK;
• and
• render, by the publisher application, the at least one predicted next-action, wherein a user's interaction with the rendered at least one next-action enables the user to view inventory information provided from the at least one service provider and to place an order for one or more items from the inventory with the at least one service provider;
• receive, at the publisher application and from a payment provider, payment information of the user for an order;
• encrypt, using the backend public key, the payment information;
• and
• transmit, through the in-app SDK to the backend service, the encrypted payment information and order.

A computer-implemented system, comprising:

• one or more computers;
• and
• one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, cause the computer system to:
• display, by a publisher application, content on a display of a computing device;
• transmit, by the publisher application over a network through an in-application (in-app) commerce software development kit (SDK), a request to a backend service for at least one predicted next-action, the at least one predicted next-action being contextually relevant to the content;
• receive, by the publisher application and from the backend service, at least one predicted next-action relevant to the publisher application, at least one service provider associated with, and capable of fulfilling, the at least one predicted next-action, and a backend public key, wherein the backend public key is received through the in-app SDK;
• render, by the publisher application, the at least one predicted next-action, wherein a user's interaction with the rendered at least one next-action enables the user to view inventory information provided from the at least one service provider and to place an order for one or more items from the inventory with the at least one service provider;
• receive, at the publisher application and from a payment provider, payment information of the user for an order;
• encrypt, using the backend public key, the payment information;
• transmit, through the in-app SDK to the backend service, the encrypted payment information and order;
• and
• present, by the publisher application, a status of the order to the user.