Mobile on-card in-app commerce

1. A computer-implemented method, comprising:

displaying, by a publisher application, content on a display of a computing device;

transmitting, 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;

receiving, 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

rendering, 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;

receiving, at the publisher application and from a payment provider, payment information of the user for an order;

encrypting, using the backend public key, the payment information; and

transmitting, through the in-app SDK to the backend service, the encrypted payment information and order.

2. The computer-implemented method of claim 1 , wherein the in-app commerce SDK sends user-specific information as part of the request to the backend service including one or more of a current location of the user, a user identifier, or user account information for the user at the at least one service provider.

3. The computer-implemented method of claim 1 , further comprising analyzing the content as contextual predictive input data.

4. The computer-implemented method of claim 3 , further comprising predicting the at least one predicted next-action of the user based on the analyzed content.

5. The computer-implemented method of claim 3 , further comprising determining the at least one service provider capable of fulfilling the at least one predicted next-action.

6. The computer-implemented method of claim 1 , further comprising:

presenting, by the publisher application, a status of the order to the user.

7. 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.

8. The non-transitory, computer-readable medium of claim 7 , wherein the in-app commerce SDK sends user-specific information as part of the request to the backend service including one or more of a current location of the user, a user identifier, or user account information for the user at the at least one service provider.

9. The non-transitory, computer-readable medium of claim 7 , further comprising one or more instructions that cause the computer system to analyze the content as contextual predictive input data.

10. The non-transitory, computer-readable medium of claim 9 , further comprising one or more instructions that cause the computer system to predict the at least one predicted next-action of the user based on the analyzed content of the webpage.

11. The non-transitory, computer-readable medium of claim 9 , further comprising one or more instructions that cause the computer system to determine at least one service provider capable of fulfilling the at least one predicted next-action.

12. The non-transitory, computer-readable medium of claim 7 , further comprising one or more instructions that cause the computer system to:

present, by the publisher application, a status of the order to the user.

13. 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.

14. The computer-implemented system of claim 13 , wherein the in-app commerce SDK sends user-specific information as part of the request to the backend service including one or more of a current location of the user, a user identifier, or user account information for the user at the at least one service provider.

15. The computer-implemented system of claim 13 , wherein one or more operations analyze the content as contextual predictive input data.

16. The computer-implemented system of claim 15 , further comprising one or more operations to:

predict the at least one predicted next-action of the user based on the analyzed content of the webpage; and

determine at least one service provider capable of fulfilling the at least one predicted next-action.

17. The computer-implemented system, of claim 13 , wherein one or more operations:

present, by the publisher application, a status of the order to the user.