KR20140142344A - Third party token system for anonymous shipping - Google Patents

Abstract

A method and system of a third party token system for performing anonymous delivery is disclosed. A selected one of the one or more shipping service providers approved by the recipient is received. One or more tokens corresponding to the recipient's mailing address are generated. A token corresponding to the mailing address is sent to the delivery service provider approved by the addressee. The token is only valid for the shipping service provider selected by the recipient.

Description

[0001] THIRD PARTY TOKEN SYSTEM FOR ANONYMOUS SHIPPING [0002]

This application claims priority to U.S. Patent Application No. 13 / 436,496, filed March 30, 2012, the entire contents of which are incorporated herein by reference.

This application is generally related to the computer technology field and, in certain exemplary embodiments, relates to a third party token system that performs anonymous delivery.

Each time a sender sends a package to a recipient, the sender must correctly fill in the physical address of the sender and the recipient. The physical address includes the zip code and city name. The sender must be careful not to make any mistakes to avoid delivery delays.

When sending a package, the address label affixed to the package typically includes the address of the sender, the address of the addressee, and stamps indicating that the dispatcher has paid for shipping costs to the addressee. Read the address of the recipient from the address label and determine where to deliver the package. The address of the sender can be read to identify to the recipient where the package was sent, and / or to whom the package can be returned to.

In another scenario, the recipient may not want to share his mailing address with the sender.

In the accompanying drawings, the present invention is illustratively shown and not by way of limitation.
1 is a network diagram illustrating a network system according to one embodiment, having a client-server architecture configured to exchange data over a network.
Figure 2 (a) is a block diagram illustrating an exemplary embodiment of a universal addressing application.
2 (b) is a block diagram illustrating an exemplary embodiment of a delivery token application.
3 is a block diagram illustrating an exemplary embodiment of delivering an article using a universal addressing application.
4 is a block diagram illustrating another exemplary embodiment of a process for notifying a third party of a new physical address using a universal addressing application;
5 is a block diagram illustrating another exemplary embodiment of a process for validating a user's physical address using a universal addressing application.
Figure 6 is a flow diagram of one embodiment for identifying physical addresses and performing financial transactions based on email addresses.
7 is a flow diagram of one embodiment of a method of validating a physical address based on an email address.
8 is a flow diagram of one embodiment of a method for performing financial transactions based on email addresses.
9 is a flow diagram of one embodiment of a method for setting up a generic token system.
10 is a flow diagram of one embodiment of a method of operating a generic token system.
11 is a diagram illustrating a machine in the form of a computer system having a set of instructions that, when executed, may cause a machine to perform one or more of the methods described herein.

Although the embodiments of the present invention are described with reference to specific exemplary embodiments, various modifications and changes will be apparent to those skilled in the art without departing from the broader spirit and scope of the invention. Accordingly, the detailed description and drawings are to be regarded in an illustrative rather than a restrictive sense.

In an online marketplace, a buyer, or recipient, may be reluctant to provide personal information, such as his / her mailing address, to a seller. A token associated with the buyer's mailing address may be provided to the seller. Through a shipping service provider who will have access to the buyer's physical address information, the seller can use the token to deliver the goods to the buyer. However, the buyer may wish to further restrict the range of shipping service providers who are authorized to access their actual postal address information. The present disclosure provides a way to create a token and anonymize the delivery, allowing the buyer, or recipient, to control the extent of the person who can use the token in the delivery.

In various embodiments, a method and system of a third party token system for performing anonymous delivery is disclosed. A selected one of the shipping service providers approved by the recipient is received. A token corresponding to the recipient's mailing address is generated. A token corresponding to the recipient's mailing address is sent to the shipping service provider approved by the recipient. This token is only valid for the shipping service provider selected by the recipient.

Also, whenever a user has to present a verification of his / her residence / physical address to a third party, a centralized service that verifies the user's current physical address online and generates an evaluation is not existing Do not. For example, a user who orders an item on a web site can be inquired of his or her residence address. As another example, a user who wants to send an item to another user is prompted to enter the physical address of each party on the shipping service web site. As another example, a user who wishes to apply for a loan or credit card may be asked to enter his physical address. Those skilled in the art will recognize that many online services are requesting a user's physical address to perform a transaction. This disclosure discloses a method for using a financial institution (such as PayPal) as a service for verifying the address of any user registered with a financial institution. Accordingly, the financial institution may operate as an online gateway for the third party system to check and verify the identity of any user.

Whenever a credit score is generated by a third party system, online or through a physical form, the user must provide his / her social security number to confirm that his / her identity is not compromised . The present disclosure discloses a method by which a user registered with an entity providing a universal addressing service can generate a credit evaluation report by providing only his or her e-mail address or ID according to an embodiment of the present invention. The back-end gateway system of the Universal Addressing Service is responsible for generating a credit rating by interacting with a credit bureau. Thus, the user's identity is hidden and secure.

In various embodiments, a method and system of a universal addressing scheme is also disclosed. The physical address verification module retrieves and verifies the physical address associated with the email address received from the third party server. The financial transaction confirmation module retrieves the financial account associated with the e-mail address and performs financial transactions with the financial account. The third party authentication module communicates the physical address to the third party server to authenticate the third party server before performing the financial transaction. The physical address may be, for example, a road name and address, a city name, a country, a company, or other associated entity. In another embodiment, the physical address may include a post office mailbox or other personal mail service. As such, the universal addressing server allows the user to use his or her email address instead of the other physical address.

Figure 1 illustrates an exemplary system 100 in which a client machine 102 may communicate with a universal addressing server 106 and / or a third party server 108 via a network 104. [ The user operating the client machine 102 may use the services provided by the third party server 108 by communicating with the universal addressing server 106 and / or the third party server 108. The user can communicate with the universal addressing server 106 using the web client 103 or a programmatic client. For example, the third-party server 108 may include a delivery service in which the user requests delivery, delivery, or mail delivery of the article. This item can be postcard, letter, telegram, package, express mail, or other item sent through post office or courier company. As another example, the third party server 108 may include a credit evaluator server. The user operating the client machine 102 wants to update the physical address in his quotation. As another example, the third party server 108 may be a public entity (e.g., Department of Motor Vehicles) requesting a verification of the user's physical address to operate the client machine 102 or a private agency Evaluation agency).

Examples of the client machine 102 include a mail scanning device, a set top box (STB), a receiver card, a mobile phone, a PDA, a display device, a portable game machine, and a computing system, but other devices may be used.

The network 104 used by the client machine 102, the universal addressing server 106 and / or the third-party server 108 to communicate may be a Global System for Mobile Communications (GSM) network, an IP network, a WAP network, a WiFi Network or an IEEE 802.11 standard network, and various combinations thereof. Other conventional and / or future wired and wireless networks may be used.

The universal addressing server 106 may be used to verify the information provided by the third party server 108. The result confirmation of the verification may be provided by the universal addressing server 106 to the client machine 102 and / or the third party server 108.

As an example, the third party server 108 may be used to process mail to be delivered. The third party server 108 is used by the courier company or on behalf of the courier company to send and receive mail. The verification of the data on the mail item can be performed in the universal addressing server 106. [

The universal addressing server 106 may include a universal addressing application 110, a delivery token application 116 and a database 112. The universal addressing application 110 identifies the user's email address and physical address. The delivery token application 116 generates a token to be used for anonymous delivery. The database 112 stores user data that may include information about sender and recipient, token information, approved shipping service providers, users of third party server 108, and / or information of financial institution server 114 .

The universal addressing server 106 may communicate with the financial institution server 114 associated with the email address of the user of the client machine 102. As such, the universal addressing application 110 may also perform financial transactions with the financial account of the user of the financial institution server 114. [ It is assumed here that the user has previously set up a financial account in the financial institution server 114 using the same e-mail address.

The client machine 102, the universal addressing server 106 and / or the third party server 108 may use the universal addressing application 110 and the delivery token application 116 to determine that the user is associated with the source user data Verifying, processing mailings to be delivered based on user verification, and / or providing verification results of the verification. For example, the universal addressing application 110 may provide the verification result of the verification to the client machine 102 and / or the universal addressing server 106 and / or the third party server 108. The third party server 108 may process the mail item or the delivery item to be delivered after receiving the verification result of the user, that is, the verification from the universal addressing application 110. [ In another embodiment, the third party server 108 includes a server of the shipping service provider.

The financial institution server 114 may receive the payment request and provide payment confirmation to the client machine 102, the universal addressing server 106 and / or the third party server 108. The financial institution server 114 may also receive and provide payment. Financial institution server 114 may be, for example, PayPal in San Jose, Calif., USA. However, other payment providers may be used.

In one embodiment, financial institution server 114 includes a storage device configured to store a user name, a corresponding email address, a corresponding physical address, and a corresponding financial account.

In another embodiment, client machine 102 and third party server 108 include a universal addressing application program interface (API) (not shown) in communication with universal addressing application 110 of universal addressing server 106 can do. The client machine 102 and the third party server 108 may include a delivery token application interface (API) (not shown) in communication with the delivery token application 116 of the universal addressing server 106. The API may be implemented in any other device.

FIG. 2 (a) is a block diagram illustrating an exemplary embodiment of the universal addressing application 200. The universal addressing application 200 includes, for example, a third party interface 202, a physical address verification module 204, a financial transaction confirmation module 206, a third party authentication module 208 and a financial institution interface 210 do. The third party interface 202 is configured to communicate with a third party server, such as the third party server 108 of FIG. Financial institution interface 210 is configured to communicate with a financial institution server, such as financial institution server 114 of FIG.

The physical address verification module 204 retrieves the physical address associated with the e-mail address received from the third-party server 108. For example, the third party server 108 receives a request from a user of the client device 102 and performs an operation. The operation may be, for example, a request to deliver a product from a user, a request to confirm a user's physical address, or a request to update a user's physical address. The user of the client device 102 provides his or her e-mail address to the third party server 108 to perform the operation. To perform the operation, the third-party server 108 must retrieve the physical address corresponding to the user's email address. As such, the third-party server 108 provides the user's email address to the physical address verification module 204 of the universal addressing application via the third-party interface 202. The physical address validation module 204 communicates with the financial institution server 114 via the financial institution interface 210 to retrieve the physical address of the corresponding email address provided by the third party server 108. Upon receipt of the physical address information, the physical address verification module 204 returns the physical address information to the third party server 108 via the third party interface 202.

As another example, the third party server 108 receives a request from a user of the client device 102 and performs a financial transaction associated with the operation. For example, the financial transaction is to pay the transaction amount for the operation to the third party server 108. [ In other words, the user requests the third party server 108 to withdraw the specified amount from the bank account of the financial institution associated with the user.

In this case, the third-party server 108 receives the user's email address along with the specified transaction amount for its operation. The third party server 108 communicates with the financial transaction confirmation module 206 to perform a financial transaction for the transaction amount specified in the user's bank account. The financial transaction confirmation module 206 receives the e-mail address of the user and the specified transaction amount through the third-party interface 202. The financial transaction confirmation module 206 communicates with the financial institution server 114 via the financial institution interface 210. The financial transaction confirmation module 206 sends a request to the financial institution server 114 to cause a bank account associated with the user's email address to perform a financial transaction of the specified transaction amount. When the financial transaction confirmation module 206 receives the confirmation result indicating that the financial transaction has been completed, the financial transaction confirmation module 206 forwards the confirmation result to the third party server 108.

In another embodiment, the financial transaction confirmation module 206 retrieves a financial account associated with the user's email address and performs a financial transaction with a financial account associated with the user's email address.

The third party authentication module 208 authenticates the third party server 108 before performing the financial transaction. For example, the universal addressing server 106 should verify that the request from the third-party server 108 is a legitimate request from the user of the client device 102. In one embodiment, the third party server 108 has exchanged the public key and has already established authenticated communication with the universal addressing server 106. Those skilled in the art will appreciate that other authentication methods may be used to authenticate communication between the third party server 108 and the universal addressing server 106.

In another embodiment, the universal addressing server 106 may directly request the user of the client device 102 to confirm the financial transaction. For example, the universal addressing server 106 may send a text message or e-mail to the user of the requested financial transaction from the third party server 108.

FIG. 2 (b) is a block diagram illustrating an exemplary embodiment of a delivery token application 250. The delivery token application 250 includes a recipient interface 252, a sender interface 254, a trusted shipping service provider module 256, a token generator 258 and a shipping service provider interface 260.

The remittee interface 252 is configured to communicate with the recipient's client machine. The recipient can be, for example, a buyer who ordered the goods from the electronic marketplace to the seller.

The sender interface 254 is configured to communicate with the client machine of the sender. The sender can be, for example, the seller who ordered the purchase of goods from the buyer in the electronic market.

The shipping service provider interface 260 is configured to communicate with one or more various shipping service providers. The shipping service provider may be, for example, Fedex, UPS, DHL, USPS, and the like.

The trusted shipping service provider module 256 receives the selected one of the one or more shipping service providers approved by the recipient. In one embodiment, the trusted shipping service provider module 256 generates a list of shipping service providers to the buyer or recipient. The buyer, or recipient, can select and approve each of the shipping service providers he trusts or is convenient.

The token generator 258 generates one or more tokens corresponding to the recipient's mailing address. For example, the token may include a character code that identifies the recipient, but whose recipient's mailing address is anonymous to the seller. This character code may correspond to the recipient's identity, the recipient's mailing address, and the selected shipping service provider.

The token may only be decrypted by the consignee-approved shipping service provider. In other words, one or more tokens are valid only for one or more shipping service providers selected and approved by the addressee.

In one embodiment, the token generator 258 communicates, via the shipping service provider interface 260, one or more tokens corresponding to the recipient's mailing address to the selected shipping service provider.

In one embodiment, the token generator 258 may receive a request for a token associated with the remittee from the sender. The token generator 258 then communicates to the sender one or more tokens corresponding to the recipient's mailing address in response to the request.

In another embodiment, the token generator 258 identifies at least one of the selected shipping service providers to the sender. The token generator 258 communicates to the sender that one or more tokens are valid only for at least one of the selected shipping service providers.

In another embodiment, the token generator 258 receives a query from the sender to confirm whether the shipping service provider has been approved by the recipient. The token generator 258 communicates to the sender whether the shipping service provider has been approved by the recipient.

In another embodiment, the token generator 258 receives a request for the identity of the token and the shipping service provider associated with the remittee from the sender. The token generator 258 determines whether the shipping service provider identified by the sender has been approved by the recipient. If it is determined that the service provider identified by the sender has been approved by the recipient, the token generator 258 communicates the token associated with the identified shipping service provider to the sender.

In one embodiment, the storage device, including the database 112, stores information of the sender, information of the recipient, mailing address of the recipient, selected delivery service provider approved by the recipient, and one or more tokens corresponding to the selected delivery service provider .

In another embodiment, the token generator 258 associates one or more tokens with the sender. The token generator 258 may generate a disposable token that is used only once. The token generator 258 generates one or more tokens, and the sender applies one or more tokens to the delivery package instead of the recipient's mailing address.

3 is a block diagram illustrating an exemplary embodiment of delivering an article using the universal addressing server 106. As shown in FIG. The sender 302 wants to send the package 304 to the recipient 308. Package 304 may be labeled with a sender email address 316, a recipient email address 318, and a mailing address email address 320. The sender email address 316 includes one or more email addresses of the sender 302. Recipient email address 318 includes one or more email addresses of recipient 308. The postal mail address 320 includes one or more email addresses of the party to whom the package 304 should be paid for shipping. The sender 302 delivers the package 304 to the delivery service 306. The delivery service 306 may be, for example, a courier service.

In another embodiment, the email address may include a user name and a domain name. In yet another embodiment, the email address includes a unique identifier, or a username without a domain name.

The shipping service 306 determines from the label of the package 304 the physical address corresponding to the sender email address 316 and the recipient email address 318. [ In one embodiment, the delivery service 306 presents the sender e-mail address 316 and the recipient e-mail address 318 to the universal addressing server 310. The universal addressing server 310 communicates with the financial institution server 312 to retrieve the physical address corresponding to the email address of the sender and the recipient. The universal addressing server 310 returns the physical address of the sender and recipient to the delivery service 306.

The shipping service 306 calculates postage rates based on the physical address of the sender and recipient. The shipping service 306 then presents a request for a financial transaction to the financial account associated with the postal mail address 320, as much as the postage charge determined. In one embodiment, the postal address email address 320 may include a sender email address 316, a recipient email address 318, or any other email address associated with the shipping of the package 304. [

The universal addressing server 310 communicates with the financial institution server 312 to retrieve financial accounts associated with the postal mail address 320 and perform financial transactions. The result of the confirmation of the financial transaction may be returned to the delivery service 306. [ Upon receiving the confirmation of the financial transaction, the delivery service 306 proceeds with delivery of the package 304 to the remittee 308.

In yet another embodiment, the financial institution server 312 may perform financial transactions for the determined postage rates by communicating with other financial institutions.

4 is a block diagram illustrating another exemplary embodiment for notifying a third party of a new physical address of a user using a universal addressing application; In this example, the user 406 has moved his residence address from the physical address A 402 to the new physical address B 404. The user 406 notifies the universal addressing server 408 of its new physical address B 404. The universal addressing server 408 updates its database to associate the user's email address with the new physical address B 404.

In addition, the universal addressing server 408 may notify the financial institution server 410 of the updated new physical address 404 associated with the user's email address. In one embodiment, financial institution server 410 includes a user's email address, a corresponding physical address, and a database of corresponding financial accounts.

Financial institution server 410 may notify all other sides of the user's new physical address. For example, the financial institution server 410 notifies the bank server 412 of the updated new physical address 404 of the user. In another example, the financial institution server 410 notifies the third party server 414 of the new physical address 404 of the user. The third-party server 414 includes, for example, a credit rating agency, a car registry, a small business registered in a financial institution server 410, and the like.

5 is a block diagram illustrating another exemplary embodiment of a process for verifying a user's physical address using a universal addressing application. The user 502 sends his or her email address to the third party 504 along with a certificate that verifies and verifies his physical address based on the presented email address. For example, the third party 504 may be a lease, a car dealer, a small business, or the like.

The third party 504 presents the email address of the user 502 to the universal addressing server 506 along with the certificate. The universal addressing server 506 communicates with the financial institution server 508 to retrieve the user's financial information and the user's physical address based on the presented email address.

For example, a user may provide his or her e-mail address to the landlord as a lease application. The landlord presents the email address of the user in the written rental application to the universal addressing server 506 and searches the existing history of the user's physical address together with the user's financial information. The financial information includes, for example, a balance of the user's financial account, credit information, or the user's credit rating.

Figure 6 is a flow diagram of one embodiment for identifying physical addresses and performing financial transactions based on email addresses. In step 602, the universal addressing application receives the email address of the user. In step 604, the universal addressing application authenticates the third party server that has presented the user's email address. In step 608, the universal addressing application retrieves and verifies the physical address associated with the email address of the user received from the third party server. In step 610, the universal addressing application retrieves the financial account associated with the email address and performs a financial transaction with the financial account.

7 is a flow diagram of one embodiment of a method of validating a physical address based on an email address. In step 702, the universal addressing application receives an email address from a third party server. At step 704, the universal addressing application retrieves the physical address associated with the email address. In step 706, the universal addressing application, in response to receiving the email address from the third party server, communicates the physical address associated with the email address to the third party server.

8 is a flow diagram of one embodiment of a method for performing financial transactions based on email addresses. At step 802, the universal addressing application receives the email address and transaction amount from the third party server. In another embodiment, the universal addressing application is also authenticated for a transaction amount from a third party server. In step 804, the universal addressing application retrieves the financial account associated with the email address. In step 806, the universal addressing application trades the transaction amount to the financial account associated with the email address. At step 808, a confirmation result of the transaction amount is generated and communicated to the third party server at step 810.

9 is a flow diagram 900 of one embodiment of a method for setting up a generic token system. At act 902, a selected one of the one or more shipping service providers approved by the recipient is received. At operation 904, one or more tokens corresponding to the recipient's mailing address are generated. One or more tokens are only valid for one or more selected shipping service providers. At operation 906, one or more tokens corresponding to the recipient's mailing address are communicated to the selected shipping service provider.

10 is a flow diagram 100 of one embodiment of a method of operating a generic token system. At operation 1002, a request for a token for the shipping service provider is received from the sender. At operation 1004, the token generator determines whether the identified shipping service provider has been approved by the recipient. If the identified shipping service provider has been previously approved by the recipient, at operation 1006, the token corresponding to the approved shipping service provider is communicated to the sender.

If the identified shipping service provider has not previously been approved by the recipient, then at operation 1008, the token generator may recommend an alternate shipping service provider approved by the recipient. In another embodiment, the token generator may explicitly reject the token request and request the sender to re-present the request to identify another shipping service provider.

11 is a diagram illustrating a machine in the form of an exemplary computer system 1100 having a set of instructions that, when executed, may cause a machine to perform one or more of the methods described herein. In an alternative embodiment, the machine may operate as a standalone device or may be connected (e.g., networked) to another machine. In a networked manner, the machine may operate as a server or client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set top box (STB), a PDA, a cellular telephone, a web appliance, a network router, a switch or a bridge, or an instruction (sequential etc.) It may be any machine capable of executing the set. Also, although only one machine is shown, the term " machine " is intended to encompass a set of arbitrary machines that execute a set (or sets of instructions) of instructions that perform any one or more of the above- May be included.

Exemplary computer system 1100 includes a processor 1102 (e.g., a CPU or GPU or both), main memory 1104 and static memory 1106, which communicate with each other via bus 1108. The computer system 1100 may further include a video display unit 1110 (e.g., LCD, CRT). The computer system 1100 also includes a character input device 1112 (e.g., a keyboard), a UI navigation device 1114 (e.g., a mouse), a disk drive unit 1116, a signal generating device 1118 And a network interface device 1120.

The disk drive unit 1116 includes a machine readable medium 1122 that stores a set of one or more instructions and data structures (e.g., software 1124) that implement or are used by any one or more of the methods or functions described above. ). The software 1124 may be stored in the main memory 1104 and / or within the processor 1102 while being executed by the computer system 1100, the main memory 1104 and the processor 1102, which constitute a machine- , Wholly or at least partially.

The software 1124 may also be transmitted or received over the network 1150 via the network interface device 1120 using any one of a number of known transmission protocols (e.g., HTTP).

Although the machine-readable medium 1122 is shown as a medium in the exemplary embodiment, the term "machine-readable medium" refers to a medium or medium that stores one or more sets of instructions (e.g., Databases, and / or associated caches and servers). The term "machine-readable medium" may also be used to store, encode, or otherwise convey a set of instructions that are executed by a machine and cause the machine to perform any one or more of the methods described herein, , Or any medium capable of storing, encoding or delivering data structures associated with or used by a set of instructions. Thus, the term "machine readable medium" includes, but is not limited to, solid state memories, optical and magnetic media, and carrier signals.

The summary of this disclosure is provided in accordance with United States Code 37 CFR 1.72 (b), which requires the reader to quickly ascertain the nature of the technical description. It will be appreciated that this has not been used to interpret or limit the scope and meaning of the claims. Further, in the foregoing detailed description, it will be appreciated that various features are grouped in an exemplary embodiment to simplify the disclosure. The disclosed method should not be construed as reflecting a method as if the claimed embodiment requires features beyond those explicitly set forth in the respective claims. Conversely, as indicated by the following claims, the novel claimed subject matter is less than all the features of one disclosed embodiment. In addition, the following claims are included in the detailed description, and each claim is based on a separate embodiment.

Claims (19)

A system comprising at least one processor,
Wherein the at least one processor comprises:
A trusted shipping service provider module configured to receive a selection for one or more shipping service providers approved by the recipient;
A token generator configured to generate one or more tokens corresponding to the recipient's mailing address and to communicate the one or more tokens corresponding to the recipient's mailing address to the selected one or more shipping service providers,
Lt; / RTI >
Wherein the one or more tokens are valid only for the one or more selected shipping service providers
system.
The method according to claim 1,
Wherein the token generator is configured to receive a request for a token associated with the recipient from the sender and to communicate the one or more tokens corresponding to the recipient's mail address to the sender in response to the request,
The one or more tokens comprising a code of the recipient's mailing address
system.
3. The method of claim 2,
Wherein the token generator is configured to identify at least one of the selected shipping service providers to the sender and to communicate to the sender that the at least one token is valid only for at least one of the selected shipping service providers
system.
The method according to claim 1,
Wherein the token generator is configured to receive a query from a sender to confirm whether a shipping service provider has been approved by the recipient and to communicate to the sender whether the shipping service provider has been approved by the recipient
system.
The method according to claim 1,
Wherein the token generator receives from the sender a request for the identity of the token and the shipping service provider associated with the recipient and determines whether the shipping service provider identified by the sender has been approved by the recipient, And configured to communicate to the sender a token associated with the identified shipping service provider based on the determination that the identified shipping service provider has been approved by the recipient
system.
The method according to claim 1,
Further comprising a storage device configured to store the sender's information, the recipient's information, the recipient's mailing address, the selected delivery service provider approved by the recipient, and one or more tokens corresponding to the selected delivery service provider
system.
The method according to claim 1,
Wherein the one or more tokens comprise at least one token that includes an identifier of the recipient, a mailing address of the recipient, and a character code corresponding to the selected shipping service provider
system.
The method according to claim 1,
Wherein the token generator associates the one or more tokens with the sender
system.
The method according to claim 1,
The token generator generates a disposable token to be used only once
system.
The method according to claim 1,
The sender applies the one or more tokens to the delivery package instead of the recipient's mailing address, the token generator generates the one or more tokens
system.
Receiving a selection for one or more shipping service providers approved by the recipient;
Generating one or more tokens corresponding to the recipient's mailing address, wherein the one or more tokens are valid only for the one or more selected shipping service providers,
Communicating the one or more tokens corresponding to the recipient's mailing address to the selected shipping service provider
A computer implemented method.
12. The method of claim 11,
Receiving a request from the sender for a token associated with the recipient;
Communicating the one or more tokens corresponding to the recipient's mailing address to the sender in response to the request,
The one or more tokens comprising a code of the recipient's mailing address
A computer implemented method.
13. The method of claim 12,
Identifying at least one of the selected shipping service providers to the sender;
Further comprising communicating to the sender that the one or more tokens are valid only for at least one of the selected shipping service providers
A computer implemented method.
12. The method of claim 11,
Receiving a query from the sender confirming whether the shipping service provider has been approved by the recipient;
Further comprising communicating to the sender whether the shipping service provider has been approved by the recipient
A computer implemented method.
12. The method of claim 11,
Receiving a request from the sender for a token associated with the recipient and an identity of the shipping service provider;
Determining whether a shipping service provider identified by the sender has been approved by the recipient;
Further comprising communicating to the sender a token associated with the identified shipping service provider based upon determining that the shipping service provider identified by the sender has been approved by the recipient
A computer implemented method. 12. The method of claim 11,
Storing the sender's information, the recipient's information, the recipient's mailing address, the selected shipping service provider approved by the recipient, and one or more tokens corresponding to the selected shipping service provider in the storage device
A computer implemented method.
12. The method of claim 11,
Further comprising generating a one-time use token associated with the sender,
A computer implemented method.
12. The method of claim 11,
Further comprising generating the one or more tokens such that the sender applies the one or more tokens to the delivery package instead of the recipient's mailing address
A computer implemented method.

A non-volatile computer-readable storage medium for storing a set of instructions,
The instruction set, when executed by the processor, causes the processor to:
Receiving a selection for one or more shipping service providers approved by the recipient;
Generating one or more tokens corresponding to the recipient's mailing address, wherein the one or more tokens are valid only for the selected one or more shipping service providers;
And communicating the one or more tokens corresponding to the recipient's mailing address to the selected shipping service provider
Non-volatile computer readable storage medium.

Images