System and method for tokenizing information from a digital wallet host by an acquirer processor

1. A computer-implemented method, comprising:

generating a merchant-specific payment interface for a merchant;

transmitting the merchant-specific payment interface to the merchant to be displayed to a consumer via a merchant web page or a merchant mobile application;

receiving, by an acquirer processor from a digital wallet host by way of the merchant-specific payment interface, an encrypted payment payload including consumer financial data in response to a digital wallet based transaction initiated by the consumer;

generating, by the acquirer processor, a low value token devoid of the consumer financial data in response to receiving the encrypted payment payload from the digital wallet host;

transmitting, by the acquirer processor to the merchant, the low value token, devoid of the consumer financial data, corresponding to the digital wallet based transaction;

receiving, by the acquirer processor from the merchant, an authorization request for the digital wallet based transaction, the authorization request comprising the low value token; and

transmitting, by the acquirer processor, an authorization response to the merchant.

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

requesting, by the acquirer processor, authorization for the transaction from an issuer financial institution using the consumer financial data from the encrypted payment payload; and

receiving, by the acquirer processor, an authorization decision for the transaction from the issuer financial institution.

3. The computer-implemented method of claim 1 , wherein a high value token is further generated from the consumer financial data of a financial account of the consumer.

4. The computer-implemented method of claim 1 , wherein transmitting the low value token to the merchant comprises transmitting the low value token to the digital wallet host for transmission to the merchant.

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

generating, at the acquirer processor, the merchant-specific payment interface that includes a digital wallet interface for the digital wallet host;

transmitting the merchant-specific payment interface, by the acquirer processor to the merchant, for presentation to the consumer at a merchant presentation page; and

receiving the consumer financial data from the consumer at the digital wallet interface, wherein the consumer financial data is isolated from the merchant.

6. The computer-implemented method of claim 5 , wherein receiving an encrypted payment payload from the digital wallet host comprises receiving the encrypted payment payload at the merchant-specific payment interface.

7. The computer-implemented method of claim 5 , wherein the consumer financial data comprises login information to a digital wallet account.

8. A non-transitory computer readable medium having instructions stored thereon which when executed by a processor cause the processor to:

generate a merchant-specific payment interface for a merchant;

transmit the merchant-specific payment interface to the merchant to be displayed to a consumer via a merchant web page or a merchant mobile application;

receive, by an acquirer processor from a digital wallet host by way of the merchant-specific payment interface, an encrypted payment payload including consumer financial data in response to a digital wallet based transaction initiated by the consumer;

generate, by the acquirer processor, a low value token devoid of the consumer financial data in response to receiving the encrypted payment payload from the digital wallet host;

transmit, by the acquirer processor to the merchant, the low value token, devoid of the consumer financial data, corresponding to the digital wallet based transaction;

receive, by the acquirer processor from the merchant, an authorization request for the digital wallet based transaction, the authorization request comprising the low value token; and

transmit, by the acquirer processor, an authorization response to the merchant.

9. The non-transitory computer readable medium of claim 8 , wherein the instructions further cause the one or more processors to:

request, by the acquirer processor, authorization for the transaction from an issuer financial institution using the consumer financial data from the encrypted payment payload; and

receive, by the acquirer processor, an authorization decision for the transaction from the issuer financial institution.

10. The non-transitory computer readable medium of claim 8 , wherein transmitting the low value token to the merchant comprises transmitting the low value token to the digital wallet host for transmission to the merchant.

11. The non-transitory computer readable medium of claim 8 , wherein the instructions further cause the one or more processors to:

generate, at the acquirer processor, the merchant-specific payment interface that includes a digital wallet interface for the digital wallet host;

transmit the merchant-specific payment interface, by the acquirer processor to the merchant, for presentation to the consumer at a merchant presentation page; and

receive the consumer financial data from the consumer at the digital wallet interface, wherein the consumer financial data is isolated from the merchant.

12. The non-transitory computer readable medium of claim 11 , wherein receiving an encrypted payment payload from the digital wallet host comprises receiving the encrypted payment payload at the merchant-specific payment interface.

13. The non-transitory computer readable medium of claim 11 , wherein the consumer data comprises login information to a digital wallet account.

14. A payment processing system, comprising:

an acquirer processor computing system, the acquirer processor computing system comprising one or more processors executing instructions stored in memory, wherein the instructions cause the one or more processors to:

generate a merchant-specific payment interface for a merchant;

transmit the merchant-specific payment interface to the merchant to be displayed to a consumer via a merchant web page or a merchant mobile application;

receive from a digital wallet host by way of the merchant-specific payment interface an encrypted payment payload including consumer financial data in response to a digital wallet based transaction initiated by the consumer;

generate a low value token devoid of the consumer financial data in response to receiving the encrypted payment payload from the digital wallet host;

transmit the low value token, devoid of the consumer financial data, to the merchant, the low value token corresponding to the digital wallet based transaction;

receive from the merchant, an authorization request for the digital wallet based transaction, the authorization request comprising the low value token; and

transmit an authorization response to the merchant.

15. The payment processing system of claim 14 , wherein the instructions further cause the one or more processors to:

request authorization for the transaction from an issuer financial institution using the consumer financial data from the encrypted payment payload; and

receive an authorization decision for the transaction from the issuer financial institution.

16. The payment processing system of claim 14 , wherein the instructions causing the one or more processors to transmit the low value token to the merchant further comprise instructions for transmitting the low value token to the digital wallet host for transmission to the merchant.

17. The payment processing system of claim 14 , wherein the instructions further cause the one or more processors to:

generate the merchant-specific payment interface that includes a digital wallet interface for the digital wallet host; and

transmit the merchant-specific payment interface for presentation to the consumer at a merchant presentation page; and

receive the consumer financial data from the consumer at the digital wallet interface, wherein the consumer financial data is isolated from the merchant.

18. The payment processing system of claim 17 , wherein the instructions causing the one or more processors to receive the encrypted payment payload from the digital wallet host further comprise instructions to receive the encrypted payment payload at the merchant-specific payment interface.