Error handling for requests from devices

Patent metadata

Field	Value
Publication number	US-2018239561-A1
Application number	US-201715436703-A
Country	US
Kind code	A1
Filing date	Feb 17, 2017
Priority date	Feb 17, 2017
Publication date	Aug 23, 2018
Grant date	—

Abstract

A server transaction processing service implemented on the apparatus receives requests to authorize user sessions on multi-function print devices. A server application service implemented on the apparatus receives service task requests, which are requests for services that may be at least partially performed at one or more external servers. The application service then sends the service task requests to the appropriate external servers. The transaction processing service receives requests to end active user sessions. Then the transaction processing service is configured to determine whether any service task requests from user sessions were unsuccessfully executed and generate a subset of unsuccessfully executed service task requests. The transaction processing service may generate refund requests for each user session that contained unsuccessfully executed service task requests and send the refund requests to an authorization and capture service for processing.

First claim

What is claimed is:

1 . An apparatus comprising:
one or more processors; and one or more memories storing instructions which, when processed by one or more processors, cause:
a server transaction processing service, executing on a server computer, receiving two or more transaction authorization requests from two or more devices;
wherein the two or more transaction authorization requests represent requests to authorize payments of service transactions using user payment information supplied in the two or more transaction authorization requests;
in response to receiving the two or more transaction authorization requests from the two or more devices, generating two or more transaction records for the two or more transaction authorization requests, wherein the two or more transaction records are used to track transaction status of the transactions associated with the two or more transaction authorization requests;
generating and sending two or more transaction record authorization requests to a authorization and capture service configured to authorize and process transaction requests, wherein the two or more transaction record authorization requests are based upon the two or more transaction records generated from the two or more transaction authorization requests from the two or more devices;
receiving, from the authorization and capture service, two or more transaction authorization request acknowledgements for the two or more transaction authorization requests;
in response to receiving the two or more transaction authorization request acknowledgements for the two or more transaction authorization requests, updating the two or more transaction records based on the two or more transaction authorization request acknowledgements received;
receiving two or more transaction fee requests from the two or more devices, corresponding to the two or more transaction authorization requests, from the two or more devices, wherein each of the two or more transaction fee requests each comprise a request to charge a transaction amount for services rendered on the two or more devices;
in response to receiving the two or more transaction fee requests from the two or more devices, updating the two or more transaction records, associated with the two or more transaction authorization requests corresponding to the two or more transaction fee requests received from the two or more devices, to reflect a pending transaction fee amount;
generating and sending two or more transaction amount capture requests to the authorization and capture service, wherein the two or more transaction amount capture requests are based upon the two or more transaction fee requests received from the two or more devices;
receiving, from the authorization and capture service, two or more transaction capture acknowledgements for the two or more transaction amount capture requests, wherein the two or more transaction capture acknowledgements each comprise a transaction capture description that conveys whether the transaction amount capture request was successful or unsuccessful;
wherein a successful transaction amount capture request for a particular transaction record causes an amount specified in the successful transaction amount capture request to be applied to an account associated with the particular transaction record;
in response to receiving the two or more transaction capture acknowledgements for the two or more transaction amount capture requests, updating the two or more transaction records, associated with the two or more transaction fee requests, with the transaction capture description associated with each of the two or more transaction capture acknowledgements;
determining if a subset of transaction records of the two or more transaction records contain unsuccessful transaction capture descriptions;
generating and sending retry transaction amount capture requests to the authorization and capture service for each transaction record within the subset of transaction records;
receiving, from the authorization and capture service, retry transaction capture acknowledgements for the retry transaction amount capture requests, wherein the retry transaction capture acknowledgements each comprise transaction capture descriptions that convey whether the retry transaction amount capture request was successful or unsuccessful;
in response to receiving the retry transaction capture acknowledgements for the retry transaction amount capture requests, updating the subset of transaction records associated with the retry transaction capture acknowledgements with the transaction capture description.

2 . The apparatus of claim 1 , wherein each of the two or more devices are managed by a distinct vendor administrator.

3 . The apparatus of claim 1 , wherein updating the two or more transaction records based on the two or more transaction authorization request acknowledgements received comprises setting an authorization status value for a particular transaction record of the two or more transaction records to either:
a success value, if a particular transaction authorization request acknowledgement of the two or more transaction authorization request acknowledgements, corresponding to the particular transaction record, contains a successful authorization description value, a failure value, if the particular transaction authorization request acknowledgement of the two or more transaction authorization request acknowledgements contains a denied authorization description value, or a retry value, if none of the two or more transaction authorization request acknowledgements correspond to the particular transaction record.

4 . The apparatus of claim 3 , wherein the one or more memories storing instructions which, when processed by one or more processors, further cause:
in response to updating the two or more transaction records based on the two or more transaction authorization request acknowledgements received, generating and sending two or more transaction authorization responses to the two or more devices; wherein the two or more transaction authorization responses comprise a response message of either:
an authorization success message that informs a particular device of the two or more devices to authorize services for a user associated with a particular transaction authorization request of the two or more authorization requests, or
an authorization denied message that informs the particular device of the two or more devices to deny services for the user associated with the particular transaction authorization request of the two or more authorization requests.

5 . The apparatus of claim 1 , wherein the one or more memories storing instructions which, when processed by one or more processors, further cause generating and sending the retry transaction amount capture requests to the authorization and capture service for each transaction record within the subset of transaction records further comprises, incrementing a retry count value within each of the transaction records within the subset of transaction records, wherein the retry count value is used to track number of times a retry transaction amount capture request is sent for a particular transaction record.

6 . The apparatus of claim 5 , wherein the one or more memories storing instructions which, when processed by one or more processors, further cause if a particular retry count value for a particular transaction record exceeds a configured maximum retry value, then sending an alert message to a vendor administrator associated with the particular transaction record.

7 . The apparatus of claim 1 , wherein the one or more memories storing instructions which, when processed by one or more processors, further cause in response to generating and sending the t

Assignees

• Nuggehalli Jayasimha
• Nadkarni Bhushan
• Narasimhan Srikrishan
• Lu Zhenyu
• Ricoh Co Ltd

Inventors

• Nuggehalli Jayasimha
• Nadkarni Bhushan
• Narasimhan Srikrishan
• Lu Zhenyu

Classifications

• G06Q20/085

  involving remote charge determination or related payment systems · CPC title

• G06F3/1273

  Print job history, e.g. logging, accounting, tracking · CPC title

• H04N1/4433 Primary

  to an apparatus, part of an apparatus or an apparatus function · CPC title

• G06F3/1285

  Remote printer device, e.g. being remote from client or server · CPC title

• G06Q20/047

  using payment protocols involving electronic receipts · CPC title