US 12,450,673 B2
Method and system for efficient dispute resolution
Mark Woelfer, Aliso Viejo, CA (US); and Richard Stopic, San Francisco, CA (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Filed by Visa International Service Association, San Francisco, CA (US)
Filed on Jul. 16, 2019, as Appl. No. 16/512,977.
Claims priority of provisional application 62/745,252, filed on Oct. 12, 2018.
Prior Publication US 2020/0118230 A1, Apr. 16, 2020
Int. Cl. G06Q 50/18 (2012.01); G06Q 20/04 (2012.01); G06Q 20/38 (2012.01)
CPC G06Q 50/182 (2013.01) [G06Q 20/047 (2020.05); G06Q 20/388 (2013.01)] 6 Claims
OG exemplary drawing
 
1. A method comprising:
establishing, by a processing server with an authorization provider, a first application programming interface (API) for direct and secure communication between the processing server and the authorization provider,
receiving, by the processing server from the authorization provider over the first API, a first API call including a dispute request initiated on a client computing device pertaining to a conducted transaction, the dispute request including a transaction identifier associated with the conducted transaction, wherein the client computing device is associated with a legitimate user of an account used in the conducted transaction;
determining, by the processing server, a resource provider associated with the conducted transaction based on at least the transaction identifier;
preventing, by the processing server, the dispute request from being forwarded to an acquirer associated with the resource provider for at least a predetermined period of time;
providing, by the processing server to the resource provider via a direct communication link between the processing server and the resource provider, an alert notification indicating the dispute request, the alert notification including at least the transaction identifier, wherein the providing includes:
establishing, by the processing server, a second application programming interface (API) between the processing server and the resource provider, wherein the second API supports the direct communication link between the processing server and the resource provider without getting routed through the acquirer;
transmitting, by the processing server, the alert notification via a second API call over the second API to the resource provider, wherein the second API call is a direct communication between the processing server and the resource provider, without getting routed through the acquirer;
receiving, by the processing server from the resource provider over the second API, information about an authentication method performed by the resource provider in connection with the conducted transaction, the information comprising a copy of an obtained signature during the conducted transaction as part of the authentication method performed by the resource provider;
obtaining, by the processing server from the authorization provider, an electronic version of a signature of the legitimate user;
comparing, by the processing server, the electronic version of the signature to the obtained signature during the conducted transaction received from the resource provider;
calculating, by the processing server, a likelihood of success for the resource provider in the dispute request based on at least the comparing and historical data for similar disputes; and
providing, by the processing server to the resource provider, the likelihood of success;
upon receiving, by the processing server from the resource provider within the predetermined period of time, a credit notification:
monitoring settlement notices for a credit corresponding to the credit notification during a monitoring period; and
upon detecting the credit corresponding to the credit notification within the monitoring period, providing a response to the authorization provider indicating the credit thereby resolving the dispute request without going through the acquirer; and
releasing the dispute request to the acquirer associated with the resource provider upon determining at least one of:
failing to receive, by the processing server from the resource provider within the predetermined period of time, the credit notification, or
failing to detect, by the processing server, the credit corresponding to the credit notification within the monitoring period.