SALES METHODS, DELIVERY METHODS, CODE VERIFICATION METHODS, REPUDIATION RESOLUTION METHODS AND ARTICLES OF

MANUFACTURE

CLAIM FOR PRIORITY

This application claims priority to U.S. patent application No. 1 1/770,876 which was filed June 29, 2007, entitled "Sales Methods, Delivery Methods, Code Verification Methods, Repudiation Resolution Methods, and Articles of Manufacture" the entirety of which is hereby incorporated by reference herein.

TECHNICAL FIELD

The present disclosure, in various embodiments, relates to sales methods, delivery methods, code verification methods, repudiation resolution methods, and articles of manufacture.

BACKGROUND OF THE DISCLOSURE

The rise of the internet has led to an increase in the number of parcels shipped to customers who make purchases of goods online. Some customers attempt to repudiate online purchases claiming that they did not receive the goods purchased. Known shipping agencies attempt to mitigate repudiation by requiring a signature in exchange for delivery of a parcel and using the signature as evidence that the parcel was indeed received.

However, in some cases a delivery agent may forge the signature of a consignee of a parcel and keep the parcel rather than delivering it to the consignee. In other cases, a consignee may provide a signature to a delivery agent in exchange for a parcel and then later dishonestly claim that the signature provided is not his or her own signature. In either case, a credit provider that extended credit for the repudiated purchase may end up bearing the burden of reversing a charge made for the repudiated purchase.

SUMMARY OF THE DISCLOSURE

According to one aspect of the disclosure, a sales method includes accepting an order for goods from a customer, providing a code to the customer,

and receiving the code from the customer prior to delivering the goods. The code is associated with the goods.

According to another aspect of the disclosure, a delivery method includes accepting an order for goods from a customer, requesting that a verification agency provide a code to the customer, and providing the goods to a shipping agency. The code is associated with the goods and the shipping agency is instructed to deliver the goods to the customer after receiving the code from the customer.

According to another aspect of the disclosure, a code verification method includes providing a code to a customer. The code is associated with goods ordered by the customer. The method further includes receiving a verification request from a delivery agent tendering delivery of the goods to the customer. The verification request includes an asserted code provided by the customer. The method also includes determining whether the asserted code is the code previously provided to the customer.

If the asserted code is the code previously provided to the customer, the method includes informing the delivery agent that the asserted code has been verified. In contrast, if the asserted code is not the code previously provided to the customer, the method includes informing the delivery agent that the asserted code has not been verified.

According to another aspect of the disclosure, an article of manufacture includes media comprising programming configured to cause processing circuitry to perform code verification processing. The code verification processing includes receiving a verification request from a delivery agent tendering delivery of goods to a customer. The verification request includes an asserted code provided to the delivery agent by the customer. The code verification processing also includes determining whether the asserted code matches a code previously provided to the customer. The previously provided code is associated with the goods. The code verification processing includes informing the delivery agent that the asserted code has been verified if the codes match, and informing the delivery agent that the asserted code has not been verified if the codes do not match.

According to another aspect of the disclosure, a delivery method includes receiving goods ordered by a customer. The goods are associated with a code provided to the customer. The method also includes receiving an asserted code from the customer and transferring the goods to the customer only if the asserted code is the code provided to the customer.

According to another aspect of the disclosure, a repudiation resolution method includes receiving a request to reverse a credit charge from a customer, the credit charge resulting from a purchase of goods made by the customer. The method also includes determining whether the customer provided a code associated with the goods to a delivery agent in response to the delivery agent tendering delivery of the goods to the customer.

The method also includes refusing to reverse the credit charge if the customer provided the code to the delivery agent and reversing the credit charge if the customer did not provide the code to the delivery agent. According to another aspect of the disclosure, an article of manufacture includes media comprising programming configured to cause processing circuitry to perform code verification processing. The code verification processing includes receiving an asserted code from a delivery agent, the delivery agent having obtained the asserted code from a customer. The code verification processing also includes transmitting the asserted code to a verification system.

The verification system is configured to determine whether the asserted code matches a code previously provided to the customer. The previously provided code is associated with goods ordered by the customer.

The code verification processing also includes receiving a message from the verification system indicating whether the delivery agent is authorized to transfer the goods to the customer.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the disclosure are described below with reference to the following accompanying drawings.

Figure 1 illustrates a sales method in accordance with an aspect of the disclosure.

Figure 2 illustrates a code verification method in accordance with an aspect of the disclosure.

Figure 3 illustrates a delivery method in accordance with an aspect of the disclosure.

Figure 4 illustrates a repudiation resolution method in accordance with an aspect of the disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Sales methods, delivery methods, code verification methods, repudiation resolution methods, and articles of manufacture will be described below in relation to Figures 1 -4. Figure 1 illustrates a sales method involving a customer 102, a merchant

106, a shipping agency 1 12, a delivery agent 126, and a verification agency 1 16. According to the sales method, at 104, merchant 106 accepts an order for goods 1 10 from customer 102. In response, at 108, merchant 106 provides goods 1 10 to shipping agency 1 12 with the understanding that shipping agency 1 12 will deliver goods 1 10 to customer 102. Although depicted as a single parcel in

Figure 1 , merchant 106 may package goods 1 10 in a single parcel, a plurality of parcels, or a single parcel containing other goods associated with a different transaction between customer 102 and merchant 106.

Upon receiving goods 1 10 from merchant 106, shipping agency 1 12 may create a parcel identifier, such as a tracking number, uniquely identifying a parcel containing goods 1 10. Shipping agency 1 12 may communicate the parcel identifier to merchant 106 and/or customer 102 so that merchant 106 and customer 102 may track the location of goods 1 10. The parcel identifier may be unique in that it may be associated with goods 1 10 and might not be associated with any other parcel currently being processed by shipping agency 1 12.

A code 122 may be generated for goods 1 10 by verification agency 1 16. Shipping agency 1 12 may, at 1 14, request that verification agency 1 16 send code 122 to customer 102 per an arrangement with merchant 106. Alternatively, merchant 106 may request that verification agency 1 16 send code 122 to customer 102. Verification agency 1 16 may associate code 122 with goods 1 10 and may further associated code 122 with the parcel identifier.

At 1 18, verification agency 1 16 provides code 122 to customer 102 by sending a message 120 to customer 102 containing code 122. Message 120 may be an email message, a text message, a short-message-service message, a page, an instant message, a voice message, an automated voice message, a phone call, or other message capable of conveying code 122 to customer 102. Alternatively, message 120 may be programming configured to execute within a web browser. For example, verification agency 1 16 may send an email message to customer 102 containing a URL. In response to customer 102 clicking on the URL, verification agency 1 16 may send programming, such as HTML code, XML code, Java code, or other programming capable of being performed by a web browser to a web browser being used by customer 102. The programming, when performed by the web browser, may display code 122 to user 102.

Next, at 124, shipping agency 1 12 may provide goods 1 10 to delivery agent 126. Delivery agent 126 may be an employee of shipping agency 1 12 or may be an independent contractor with whom shipping agency 1 12 may contract to deliver goods 1 10 to customer 102.

Shipping agency 1 12 and delivery agent 126 may be instructed to deliver goods 1 10 to customer 102 but not to transfer goods 110 to customer 102 until after receiving and validating code 122 from customer 102. Delivery agent 126 may request code 122 from customer 102 because delivery agent 126 might not know code 122 prior to receiving code 122 from customer 102.

The fact that delivery agent 126 might not have code 122 prior to receiving code 122 from customer 102 may reduce fraud committed by delivery agent 126 since delivery agent is unlikely to be able to determine code 122 without receiving code 122 from customer 102.

Furthermore, the fact that customer 102 has code 122 and provides code 122 to delivery agent 126 may reduce fraud committed by customer 102 since customer 102 might not be able to credibly claim that he or she did not provide code 122 to delivery agent 126 after providing code 122 to delivery agent 126 since delivery agent 126 might not have any other way of receiving code 122 other than via customer 102.

At 130, delivery agent 126 may receive an asserted code 128 from customer 102. Asserted code 128 may be code 122. However, delivery agent 126 might not know whether asserted code 128 is code 122 until after verifying asserted code 128 with verification agency 116. Accordingly, at 132, delivery agent 126 may provide asserted code 128 to verification agency 1 16. Verification agency 1 16 may determine whether asserted code 128 is code 122 by comparing asserted code 128 with code 122. If the codes match, at 134, verification agency 1 16 may notify delivery agent 126 that the codes match. Alternatively, at 134, verification agency 1 16 may authorize delivery agent 126 to transfer goods 1 10 to customer 102. In other words, verification agency 1 16 might not explicitly tell delivery agent 126 whether the codes match, but instead may either authorize or not authorize the transfer of goods 1 10 to customer 102. If authorized by verification agency 1 16, delivery agent 126, at 136, may transfer goods 1 10 to customer 102. Figure 2 illustrates a code verification method in accordance with one aspect of the disclosure. At 202, verification agency 1 16 may receive a request to provide code 122 to customer 102 from shipping agency 1 12. In response, verification agency 1 16 may, at 204, acknowledge the request by sending a reply to shipping agency 1 12 indicating that verification agency 1 16 will provide code 122 to customer 102. In some embodiments, the request may include a parcel identifier associated with a parcel containing goods 1 10.

Alternatively, at 206, verification agency 1 16 may receive a request to provide code 122 to customer 102 from merchant 106. In response, verification agency 1 16 may, at 208, acknowledge the request by sending a reply to merchant 106 indicating that verification agency 1 16 will provide code 122 to customer 102. In some embodiments, the request may include a parcel identifier associated with a parcel containing goods 1 10. Merchant 106 may obtain the parcel identifier from shipping agency 1 12.

In response to the request, verification agency 1 16 may generate code 122. In doing so, verification agency 1 16 may store an association between code 122 and goods 1 10. In some embodiments, verification agency 1 16 may store an association between code 122 and the parcel identifier associated with goods 1 10. The association may be stored in a computer 200.

Code 122 may include a random or pseudo random arrangement of a plurality of characters. For example, code 122 may be a set of randomly selected letters and numbers. Alternatively, code 122 may be a picture, icon, or other visual identifier. For example, code 122 may be a bar code. Verification agency 1 16 may create a plurality of codes and may associate each of the plurality of codes with different goods. In one embodiment, verification agency 1 16 may ensure that each code of the plurality of codes is unique. In other words, each code may be associated with different goods and verification agency 1 16 may ensure that code 122 is only associated with goods 1 10.

In another embodiment, verification agency 1 16 may receive a parcel identifier associated with goods 1 10. Verification agency 1 16 may ensure that the combination of code 122 and the parcel identifier is unique. In other words, a same code may be used for more than one set of goods as long as the sets of goods have different parcel identifiers.

Code 122 may be a one-time use code meaning that code 122 may be associated with goods 1 10 and might not be associated with other goods in the future even after goods 1 10 have been transferred to customer 102.

At 210, verification agency 1 16 may provide code 122 to customer 102 via message 120. Next, at 212, verification agency 1 16 may receive a verification request from delivery agent 126. Delivery agent 126 may attempt to deliver goods 1 10 to customer 102 but may first need to verify that asserted code 128 provided by customer 102 is code 122. Accordingly, the verification request may include asserted code 128 and may also include a parcel identifier associated with goods 1 10. In some embodiments of the method, delivery agent 126 may receive the parcel identifier from shipping agency 1 12.

In some embodiments of the method, verification agency 1 16 may receive the verification request via a telephone call from delivery agent 126. Before receiving the telephone call, verification agency 1 16 may check a telephone number of a caller identification associated with the telephone call to see if the telephone number is a known, authorized telephone number. If the telephone number is an authorized number, verification agency 1 16 may answer the telephone call and may thereby receive the verification request. If the telephone number is not an authorized number, verification agency 1 16 might not answer the telephone call. This practice may prevent unauthorized parties from fraudulently attempting to verify asserted codes with verification agency 1 16.

Further steps may also be taken to prevent fraud. For example, if verification agency 1 16 receives an asserted code that does not match code 122, verification agency 1 16 may note that a failed match occurred. Additional failed matches may subsequently occur. Verification agency 1 16 may, after a predetermined number of failed matches or after a predetermined number of failed matches within a predetermined time period, invalidate code 122 since it may appear that someone is fraudulently trying to authorize a transfer of goods 1 10 by "guessing" code 122.

Verification agency may subsequently notify merchant 106 and may subsequently issue a new code to replace code 122. The new code may be sent to customer 102 in a manner similar to the manner in which code 122 was sent to customer 102. This approach may prevent fraudulent authorizations.

Instead of a phone call, verification agency 1 16 may receive the request electronically. For example, verification agency 1 16 may receive an email message from delivery agent 126 or other message electronically sent by delivery agent 126. In some embodiments, the electronic request may be received by computer 200.

In response to the request received at 212, verification agency 1 16 may compare asserted code 128 with code 122 to determine if asserted code 128 is code 122. If asserted code 128 matches code 122, verification agency 1 16 may make a record of the date and time when it determined that asserted code 128 matches code 122. The record may include other information as well. For example, the record may include an identifier identifying delivery agent 126, the parcel identifier associated with goods 1 10, an identifier identifying merchant 106, an identifier identifying customer 102, and/or other information.

If the codes match, verification agency 1 16 may send an authorization message to delivery agent 126 at 214. The authorization message may indicate that the codes match or may simply indicate that delivery agent 126 is authorized to transfer goods 1 10 to customer 102.

If the codes do not match, verification agency 1 16 may send a message to delivery agent 126 at 214 indicating that delivery agent 126 is not authorized to transfer goods 1 10 to customer 102. The message may further indicate that the codes do not match.

Verification agency 1 16 may take steps to ensure that shipping agency 1 12 and delivery agent 126 do not obtain code 122. For example, verification agency 1 16 may send code 122 only to customer 102 and not to shipping agency 1 12 or delivery agent 126. Verification agency 1 16 may also ensure that shipping agency 1 12 and delivery agent 126 cannot access code 122 via computer 200.

In some embodiments, verification agency 1 16 and merchant 106 may be part of a single business entity. In other cases, verification agency 1 16 may be independent of merchant 106 and may service many different merchants. In some embodiments, verification agency 1 16 may be part of shipping agency 1 12. For example, shipping agency 1 12 may offer verification services to customers. However, for this arrangement to be feasible, shipping agency 1 12 may need to assure merchant 106 that delivery agent 126 could not access code 122 even though verification agency 1 16 may be part of the same business entity as shipping agency 1 12.

The code verification method may be executed manually or semi- manually by verification agency 1 16. Alternatively, the code verification method may be implemented as code verification processing configured to be performed on processing circuitry. For example, according to another aspect of the disclosure, an article of manufacture includes media including programming configured to cause processing circuitry (e.g., a microprocessor) to perform processing that executes the code verification method. The programming may be embodied in a computer program product(s) or article(s) of manufacture, which can contain, store, or maintain programming, data, and/or digital information for use by or in connection with an instruction execution system including processing circuitry. In some cases, the programming may be referred to as software, hardware, or firmware.

For example, the media may be electronic, magnetic, optical, electromagnetic, infrared, or semiconductor media. Some more specific examples of articles of manufacture including media with programming include, but are not limited to, a portable magnetic computer diskette (such as a floppy diskette), zip disk, hard drive, random access memory, read only memory, flash memory, cache memory, and/or other configurations capable of storing programming, data, or other digital information. Figure 3 illustrates a delivery method in accordance with one aspect of the disclosure. Initially, delivery agent 126 receives goods 1 10 ordered by customer 102 from merchant 106. Customer 102, at 302, receives code 122 from verification agency 1 16.

Before transferring goods 1 10 to customer 102, delivery agent 126 requests code 122 from customer 102. At 304, customer 102 provides asserted code 128 to delivery agent 126. Delivery agent 126 may presume that asserted code 128 is code 122.

At 306, delivery agent 126 sends asserted code 128 to verification agency 1 16 and requests that verification agency 1 16 verify asserted code 128. In response, verification agency 1 16 compares asserted code 128 to code 122. At 308, if asserted code 128 matches code 122, verification agency 1 16 may authorize delivery agent 126 to transfer goods 1 10 to customer 102. Delivery agent 126 then transfers goods 1 10 to customer 102 at 312.

If asserted code 128 does not match code 122, verification agency 1 16, at 308 may inform delivery agent 126 that he or she is not authorized to transfer goods 1 10 to customer 102.

Delivery agent 126 may provide asserted code 128 to verification agency 1 16 via a telephone call. Alternatively, delivery agent 126 may be provided with a communications device 310 configured to provide asserted code 128 to verification agency 1 16. Communications device 310 may be substantially any device capable of electronically sending asserted code 128 to verification agency 1 16 and receiving messages from verification agency 1 16. For example, communications device 310 may be a laptop computer, a personal digital assistant, or a handheld computer.

Communications device 310 may be configured to perform processing related to verifying asserted code 128. The processing may be embodied as programming configured to perform the processing. The processing may include receiving asserted code 128 from delivery agent 126, transmitting asserted code 128 to verification agency 1 16, and receiving a message from verification agency 1 16 indicating whether delivery agent 126 is authorized to transfer goods 1 10 to customer 102. The processing may further include informing delivery agent 126 whether delivery agent 126 is authorized to transfer goods 1 10 to customer 102. In some cases, the processing may receive asserted code 128 via a keyboard or via a bar code reader.

The processing may be embodied as an article of manufacture including media including the programming. The programming may be embodied in a computer program product(s) or article(s) of manufacture, which can contain, store, or maintain programming, data, and/or digital information for use by or in connection with an instruction execution system including processing circuitry. In some cases, the programming may be referred to as software, hardware, or firmware.

For example, the media may be electronic, magnetic, optical, electromagnetic, infrared, or semiconductor media. Some more specific examples of articles of manufacture including media with programming include, but are not limited to, a portable magnetic computer diskette (such as a floppy diskette), zip disk, hard drive, random access memory, read only memory, flash memory, cache memory, and/or other configurations capable of storing programming, data, or other digital information.

Figure 4 illustrates a repudiation resolution method in accordance with one aspect of the disclosure. Initially, at 402, customer 102 orders goods 1 10 from merchant 106. In doing so, customer 102 may provide merchant 106 with credit card information by which customer 102 intends to pay for goods 1 10. Upon receiving the credit card information, merchant 106 may request, at 404, payment from a credit provider 402 associated with the credit card information. In response, credit provider 402 may authorize payment at 406. Merchant 106 may then, at 408, provide goods 1 10 to shipping agency

1 12 and instruct shipping agency 1 12 to deliver goods 110 according to one of the methods of the disclosure.

Credit provider 402 may subsequently, at 410, receive a request to reverse the credit charge from customer 102. Before reversing the credit charge, credit provider 402 may contact verification agency 1 16 to determine whether customer 102 provided code 122 to delivery agent 126. At 412, credit provider 402 may request that verification agency 1 16 provide verification information associated with goods 1 10. In doing so, credit provider 402 may provide a parcel identifier identifying goods 110 to verification agency 1 16. Verification agency 1 16 may, in response, retrieve recorded information related to goods 1 10 and at 414 provide the recorded information to credit provider 402.

The recorded information may indicate that verification agency 1 16 received asserted code 128 from delivery agent 126 and verified that asserted code 128 is code 122. In this case, credit provider 402 may assume that customer 102 received goods 1 10 from delivery agent 126 since presumably customer 102 provided code 122 to delivery agent 126 and delivery agent 126 did not have access to code 122 other than via customer 102. Accordingly, at 416, credit provider 402 may inform customer 102 that credit provider 402 will not reverse the credit charge.

Alternatively, the recorded information may indicate that verification agency 1 16 either received asserted code 128 from delivery agent 126 and determined that asserted code 128 is not code 122 or that verification agency 1 16 did not receive asserted code 128 from delivery agent 126. In this case, credit provider 402 may assume that customer 102 did not receive goods 1 10 from delivery agent 126. Accordingly, at 416, credit provider 402 may inform customer 102 that credit provider 402 will reverse the credit charge.

Credit provider 402 may subsequently attempt to recover the amount of the credit charge from shipping agency 1 12 if credit provider 402 can establish that merchant 106 did provide goods 1 10 to shipping agency 1 12.

This method may reduce the number of fraudulent repudiations asserted by customers thereby reducing costs for credit provider 402 and merchant 106.