IP Library › Granted Patent US 12,450,673
Granted Patent B2
US 12,450,673 · App. 16/512,977 · Granted Oct 21, 2025

Method and system for efficient dispute resolution

Inventors: Mark Woelfer (Aliso Viejo, CA); Richard Stopic (San Francisco, CA)
Assignee: Visa International Service Association
G06Q50/182G06Q20/047G06Q20/388
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,450,673
App. No.
16/512,977
Granted
Oct 21, 2025
Kind
B2
Abstract

Described herein are systems and techniques for reducing the submission of disputes as well as increasing the efficiency of disputes processed via a dispute resolution process. The system enables additional information related to a conducted transaction to be provided via application programming interface calls made to a resource provider. In some embodiments, the system described receives a dispute request from client computing device pertaining to a conducted transaction, the dispute request including a transaction identifier associated with the conducted transaction, determines a resource provider associated with the conducted transaction, provides, to the resource provider, an alert notification indicating the dispute request, the alert notification including at least the transaction identifier, and receives, from the resource provider within the predetermined period of time, a credit notification for the conducted transaction.

Claims (48)

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.

2. The method of claim 1 , wherein the credit is determined to correspond to the credit notification via the transaction identifier.

3. The method of claim 1 , further comprising:

upon detecting the credit corresponding to the credit notification:

receiving, by the processing server, a second dispute request that includes the transaction identifier; and

automatically rejecting the second dispute request.

4. The method of claim 1 , wherein if the processing server receives a do not credit response from the resource provider within the predetermined period of time, the dispute request is released to the acquirer associated with the resource provider before the predetermined period of time expires.

5. A processing server comprising:

a processor; and

a memory including instructions that, when executed with the processor, cause the processing server to, at least:

establish, with an authorization provider, a first application programming interface (API) for direct and secure communication between the processing server and the authorization provider,

receive, 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 based on at least the transaction identifier, wherein the client computing device is associated with a legitimate user of an account used in the conducted transaction;

determine a resource provider associated with the conducted transaction;

prevent the dispute request from being forwarded to an acquirer associated with the resource provider for at least a predetermined period of time;

provide, 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 providing includes:

establishing 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 the alert notification via an second application programming interface call to the resource provider over the second API, wherein the second API call is a direct communication between the processing server and the resource provider, without getting routed through the acquirer;

receiving, 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, from the authorization provider, an electronic version of a signature of the legitimate user;

comparing the electronic version of the signature to the obtained signature during the conducted transaction received from the resource provider;

calculating 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, to the resource provider, the likelihood of success;

upon receiving, from the resource provider within the predetermined period of time, a credit notification for the conducted transaction:

monitor settlement notices for a credit corresponding to the credit notification during a monitoring period; and

upon detecting the credit corresponding to the credit notification during the monitoring period, provide a response to an authorization provider indicating the credit thereby resolving the dispute request without going through the acquirer; and

release the dispute request to the acquirer associated with the resource provider upon determining at least one of:

failing to receive, from the resource provider within the predetermined period of time, the credit notification, or

failing to detect the credit corresponding to the credit notification within the monitoring period.

6. The processing server of claim 5 ,

wherein the likelihood of success representing a probability that the resource provider will prevail in the dispute request.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2019
From: WOELFER, MARK; STOPIC, RICHARD
To: VISA INTERNATIONAL SERVICE ASSOCIATION
Reel/Frame 050744/0608 →
Continuity (2)
Provisional Application 62745252 · Oct 12, 2018
Related Publication 20200118230A1 · Apr 16, 2020
References Cited (60)
US 7356516B2 · Richey et al. · 2008 [cited by applicant]
US 8392288B1 · Miller · 2013 [cited by applicant]
US 8566235B2 · Katz et al. · 2013 [cited by applicant]
US 8612317B1 · Harman et al. · 2013 [cited by applicant]
US 8682793B2 · Carlson et al. · 2014 [cited by applicant]
US 8880431B2 · Ovick et al. · 2014 [cited by applicant]
US 9875385B1 · Humphreys · 2018 [cited by applicant]
US 20020141561A1 · Duncan et al. · 2002 [cited by applicant]
US 20040064373A1 · Shannon · 2004 [cited by applicant]
US 20040128155A1 · Vaidyanathan et al. · 2004 [cited by applicant]
US 20040220964A1 · Shiftan et al. · 2004 [cited by applicant]
US 20050177507A1 · Bandych · 2005 [cited by examiner]
US 20050178824A1 · Benson et al. · 2005 [cited by applicant]
US 20070094088A1 · Mastie et al. · 2007 [cited by applicant]
US 20090030710A1 · Levine · 2009 [cited by applicant]
US 20100145810A1 · Pourfallah et al. · 2010 [cited by applicant]
US 20100161457A1 · Katz et al. · 2010 [cited by applicant]
US 20100169194A1 · Richey · 2010 [cited by examiner]
US 20100257066A1 · Jones et al. · 2010 [cited by applicant]
US 20110196791A1 · Dominguez · 2011 [cited by applicant]
US 20110276475A1 · Godejohn et al. · 2011 [cited by applicant]
US 20120084391A1 · Patel et al. · 2012 [cited by applicant]
US 20120284175A1 · Wilson et al. · 2012 [cited by applicant]
US 20130080318A1 · Katz et al. · 2013 [cited by applicant]
US 20130132231A1 · Teudt · 2013 [cited by applicant]
US 20130218721A1 · Borhan et al. · 2013 [cited by applicant]
US 20140074675A1 · Calman et al. · 2014 [cited by applicant]
US 20140074690A1 · Grossman et al. · 2014 [cited by applicant]
US 20140180826A1 · Boal · 2014 [cited by applicant]
US 20140195361A1 · Murphy · 2014 [cited by applicant]
US 20140236714A1 · Fukasawa et al. · 2014 [cited by applicant]
US 20140244462A1 · Maenpaa et al. · 2014 [cited by applicant]
US 20140310160A1 · Kumar et al. · 2014 [cited by applicant]
US 20150012397A1 · Gotanda et al. · 2015 [cited by applicant]
US 20150012426A1 · Purves et al. · 2015 [cited by applicant]
US 20150186888A1 · Katz et al. · 2015 [cited by applicant]
US 20150332415A1 · Johansen et al. · 2015 [cited by applicant]
US 20150356522A1 · Matsumoto · 2015 [cited by applicant]
US 20150356541A1 · Hasegawa · 2015 [cited by applicant]
US 20160034906A1 · Stopic et al. · 2016 [cited by applicant]
US 20160155203A1 · Gotanda · 2016 [cited by applicant]
US 20160292677A1 · Karlsson · 2016 [cited by applicant]
US 20160300214A1 · Chaffin · 2016 [cited by examiner]
US 20170300881A1 · Weinflash et al. · 2017 [cited by applicant]
US 20200202309A1 · Whitelaw · 2020 [cited by applicant]
KR 20140029696 · 2014 [cited by applicant]
U.S. Appl. No. 14/814,188 , “Notice of Allowance”, Oct. 16, 2019, 8 pages. [cited by applicant]
PCT/US2018/032428 , “International Search Report and Written Opinion”, Sep. 17, 2018, 11 pages. [cited by applicant]
PCT/US2018/032428 , “International Preliminary Report on Patentability”, Nov. 21, 2019, 8 pages. [cited by applicant]
EP18798207.9 , “Extended European Search Report”, Apr. 8, 2020, 8 pages. [cited by applicant]
U.S. Appl. No. 16/609,181, “U.S. Non-Final Office Action”, Aug. 19, 2021, 24 pages. [cited by applicant]
U.S. Appl. No. 14/814,188 , “Final Office Action”, Apr. 18, 2019, 11 pages. [cited by applicant]
U.S. Appl. No. 14/814,188 , “Non-Final Office Action”, Sep. 20, 2018, 12 pages. [cited by applicant]
U.S. Appl. No. 14/814,188 , “Non-Final Office Action”, Feb. 8, 2018, 13 pages. [cited by applicant]
U.S. Appl. No. 14/814,188 , “Restriction Requirement”, Nov. 16, 2017, 6 pages. [cited by applicant]
U.S. Appl. No. 16/609,181 , Final Office Action, Mailed on Feb. 28, 2022, 18 pages. [cited by applicant]
U.S. Appl. No. 14/814,188 , “Advisory Action”, Jul. 18, 2019, 3 pages. [cited by applicant]
U.S. Appl. No. 16/609,181 , “Non-Final Office Action”, Jun. 17, 2022, 19 pages. [cited by applicant]
U.S. Appl. No. 16/609,181, Final Office Action, Mailed on Oct. 13, 2022, 19 pages. [cited by applicant]
U.S. Appl. No. 16/609,181, Non-Final Office Action, Mailed on Jan. 30, 2025, 20 pages. [cited by applicant]