System and method for secure transmission of credit card data through token generation

1 . A method of securely transmitting credit card payments, the method executed and performed by one or more computer processors, the method comprising:

transmitting, by a web-enabled device to a merchant server using a first wireless network protocol, a request to register a credit card;

in response to transmitting the request, receiving, at the web-enabled device from the merchant server by the first wireless network protocol, a credit card registration webpage requesting credit card data and customer data of a user;

transmitting, by the web-enabled device to a token server using a second wireless network protocol that is different from the first wireless network protocol, the credit card data;

in response to receiving the credit card data, generating, at the token server, a token representing the credit card data, and the merchant server is excluded from direct access to the token server without the token server being excluded from direct access to the merchant server;

receiving, at the web-enabled device from the token server by the second wireless network protocol, the token;

in response to receiving the token, transmitting, by the web-enabled device to the merchant server by the first wireless network protocol, the token and the customer data, the token being stored on the merchant server for processing subsequent credit card payment transactions;

transmitting, by the web-enabled device to the merchant server using the first wireless network protocol, a second request to conduct a subsequent credit card payment transaction, the second request including the customer data;

in response to transmitting the second request, receiving, at the web-enabled device from the merchant server by the first wireless network protocol, the token associated with the customer data;

in response to receiving the token, transmitting, by the web-enabled device to the token server using the second wireless network protocol, the token and a payment amount corresponding to the subsequent credit card payment transaction; and

receiving, at the merchant server from the token server, an indication of whether the subsequent credit card payment transaction is approved.

2 . The method of claim 1 , wherein the customer data and the token are received at the web-enabled device in response to receiving a request from the user to conduct a subsequent credit card payment transaction and provided by the web-enabled device to the token server for retrieving the credit card data.

3 . The method of claim 1 , wherein the customer data includes at least one of a billing address, a billing phone number, a desired nickname for the credit card, or a credit card company.

4 . The method of claim 1 , wherein the first wireless network protocol includes one of (i) a wireless telephony network, (ii) a Wi-Fi network, (iii) a WiMAX network, or (iv) a long-range wireless network, and the second wireless network protocol includes one of (i) a wireless telephony network, (ii) a Wi-Fi network, (iii) a WiMAX network, or (iv) a long-range wireless network.

5 . The method of claim 1 , wherein the credit card data includes at least one of a credit card number, a credit card expiration date, or a credit card service code.

6 . The method of claim 1 , wherein the token includes a 22-digit alphanumeric code.

7 . The method of claim 1 , wherein the token server complies with Payment Card Industry Data Security Standard (PCI-DSS) requirements.

8 . The method of claim 1 , further comprising:

receiving, from the user at the credit card registration webpage, a confirmation input to submit the credit card data and the customer data; and

in response to receiving the confirmation input, transmitting, by the web-enabled device to the token server, the credit card data.

9 . The method of claim 1 , wherein the customer data includes at least one of a billing address, a billing phone number, a desired nickname for the credit card, or a credit card company.

10 . A web-enabled system for securely transmitting credit card payments, the web-enabled system comprising:

a token server, wherein a merchant server is excluded from direct access to the token server without the token server being excluded from direct access to the merchant server, and wherein the token server includes:

one or more server processors, and

a non-transitory computer-readable server memory coupled to the one or more server processors and storing instructions thereon that, when executed by the one or more server processors, cause the token server to:

generate a token representing credit card data in response to receiving the credit card data; and

a web-enabled device including:

one or more processors, and

a non-transitory computer-readable memory coupled to the one or more processors and storing instruction thereon that, when executed by the one or more processors, cause the web-enabled device to:

transmit, to a merchant server using a first wireless network protocol, a request to register a credit card,

in response to transmitting the request, receive, from the merchant server by the first wireless network protocol, a credit card registration webpage requesting credit card data and customer data of a user,

transmit, to the token server using a second wireless network protocol that is different from the first wireless network protocol, the credit card data,

receive, from the token server by the second wireless network protocol, the token,

in response to receiving the token, transmit, to the merchant server by the first wireless network protocol, the token and the customer data for storage and processing subsequent credit card payment transactions,

transmit, to the merchant server using the first wireless network protocol, a second request to conduct a subsequent credit card payment transaction, the second request including the customer data,

in response to transmitting the second request, receive, from the merchant server by the first wireless network protocol, the token associated with the customer data,

in response to receiving the token, transmit, to the token server using the second wireless network protocol, the token and a payment amount corresponding to the subsequent credit card payment transaction, and

receive, from the token server by the second wireless network protocol, an indication of whether the subsequent credit card payment transaction is approved.

11 . The web-enabled system of claim 10 , wherein the customer data and the token are received at the web-enabled device in response to a request by the user to conduct a subsequent credit card payment transaction and provided by the web-enabled device to the token server for retrieving the credit card data.

12 . The web-enabled system of claim 10 , wherein the customer data includes at least one of a billing address, a billing phone number, a desired nickname for the credit card, or a credit card company.

13 . The web-enabled system of claim 10 , wherein the first wireless network protocol includes one of (i) a wireless telephony network, (ii) a Wi-Fi network, (iii) a WiMAX network, or (iv) a long-range wireless network, and the second wireless network protocol includes one of (i) a wireless telephony network, (ii) a Wi-Fi network, (iii) a WiMAX network, or (iv) a long-range wireless network.

14 . The web-enabled system of claim 10 , wherein the credit card data includes at least one of a credit card number, a credit card expiration date, or a credit card service code.

15 . The web-enabled system of claim 10 , wherein the token includes a 22-digit alphanumeric code.

16 . The web-enabled system of claim 10 , wherein the instructions further cause the web-enabled system to:

receive, from the user at the credit card registration webpage, a confirmation input to submit the credit card data and the customer data; and

in response to receiving the confirmation input, transmit, by the web-enabled device to the token server, the credit card data.

17 . The web-enabled system of claim 10 , wherein the customer data includes at least one of a billing address, a billing phone number, a desired nickname for the credit card, or a credit card company.

18 . The method of claim 1 , wherein generating the token representing the credit card data further comprises:

generating, at the token server, the token representing the credit card data by random numeric generation.

19 . The web-enabled system of claim 10 , wherein the instructions, when executed by the one or more server processors, cause the token server to:

generate the token representing the credit card data by random numeric generation.