IP Library Granted Patent US 12,387,213
Granted Patent B2
US 12,387,213 · App. 18/438,856 · Granted Aug 12, 2025

Third party products and services via ATM

Inventor: Ashish B. Kurani (Hillsborough, CA)
Assignee: Wells Fargo Bank, N.A.
G06Q20/4012G06Q20/102G06Q20/1085G06Q20/18G06Q20/3226
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,387,213
App. No.
18/438,856
Granted
Aug 12, 2025
Kind
B2
Abstract

A computer system and a transaction machine, such as an automated teller machine (ATM), can provide for any payor to make a payment to a payee at the transaction machine. The transaction machine provides the payor a user interface to enter a passcode that uniquely identifies the payment transaction. The passcode can be generated by a provider computing system associated with the transaction machine and provided directly to the payee or through the payor prior to the transaction. The transaction machine provides the payor a user interface to enter an amount. The transaction machine receives a cash deposit and provides a deposit user interface that displays deposit information based on at least one bill of the cash deposit.

Claims (83)

1. A method comprising:

receiving, at a transaction machine via a payment user interface, a request from a payor for a transaction to make a payment to a payee;

providing, by the transaction machine, a passcode user interface that allows receipt of a passcode input;

receiving, by the transaction machine via the passcode user interface, the passcode input;

determining, by the transaction machine, that the passcode input is valid;

providing, by the transaction machine, based on determining that the passcode input is valid, an amount user interface that requests an amount input associated with the request for the transaction;

receiving, by the transaction machine via the amount user interface, the amount input associated with the request for the transaction;

activating, by the transaction machine and in response to the amount input, a cash deposit mechanism to receive a cash deposit;

receiving, by the transaction machine via the cash deposit mechanism, the cash deposit;

scanning, by the transaction machine, at least one bill of the cash deposit to determine a denomination of the at least one bill;

determining, by the transaction machine and based on scanning the at least one bill, a sequence of user interfaces to be displayed on a display of the transaction machine; and

providing, by the transaction machine using the determined sequence, a deposit user interface that displays deposit information based on the at least one bill.

2. The method of claim 1 , further comprising displaying, via the deposit user interface, a progress of the scanning of the at least one bill.

3. The method of claim 1 , further comprising:

scanning, by the transaction machine, a plurality of bills of the cash deposit;

identifying, by the transaction machine, at least one denomination of the plurality of bills;

determining, by the transaction machine, a number of bills associated with the at least one denomination of the plurality of bills;

counting, by the transaction machine, a total amount of the cash deposit; and

displaying, by the transaction machine via the deposit user interface, at least one of a list of the at least one denomination of the plurality of bills, the number of bills associated with each of the at least one denomination of the plurality of bills, or the total amount of the cash deposit.

4. The method of claim 1 , further comprising:

providing, by the transaction machine via the deposit user interface, a total amount of the cash deposit.

5. The method of claim 1 , further comprising:

generating, by a provider computing system associated with the transaction machine, a passcode unique to the request from the payor;

transmitting, by the provider computing system, the generated passcode;

receiving, by the transaction machine from the provider computing system communicably coupled to the transaction machine, the generated passcode; and

determining, by the transaction machine, that the passcode input received via the passcode user interface matches the generated passcode received from the provider computing system.

6. The method of claim 1 , further comprising:

verifying, by the transaction machine based on receiving the amount input, that an amount associated with the amount input does not exceed a threshold value.

7. The method of claim 1 , further comprising:

generating, by a provider computing system associated with the transaction machine, a passcode unique to the request from the payor, wherein the generated passcode is generated based on a request received from an individual account holder.

8. The method of claim 7 , further comprising:

transmitting, by the provider computing system, the generated passcode to the payor via at least one of a text message or an email.

9. The method of claim 7 , further comprising:

transmitting, by the provider computing system, the generated passcode to the payee via at least one of a text message, an email, or an account webpage of the payee.

10. The method of claim 1 , further comprising:

transmitting, by the transaction machine to a provider computing system, a payment notification message including a payment amount and the passcode input.

11. The method of claim 1 , wherein the payor does not hold an account with a provider associated with the transaction machine.

12. A system comprising:

a transaction machine comprising one or more processors and a computer readable storage medium storing instructions that when executed cause the transaction machine to perform transaction machine operations comprising:

receiving, via a payment user interface, a request from a payor for a transaction to make a payment to a payee;

providing a passcode user interface that allows receipt of a passcode input;

receiving, via the passcode user interface, the passcode input;

determining that the passcode input is valid;

providing, based on determining that the passcode input is valid, an amount user interface that requests an amount input associated with the request for the transaction;

receiving, via the amount user interface, the amount input associated with the request for the transaction;

activating, in response to the amount input, a cash deposit mechanism to receive a cash deposit;

receiving, via the cash deposit mechanism, the cash deposit;

scanning at least one bill of the cash deposit to determine a denomination of the at least one bill;

determining, based on scanning the at least one bill, a sequence of user interfaces to be displayed on a display of the transaction machine; and

providing, using the determined sequence, a deposit user interface that displays deposit information based on the at least one bill.

13. The system of claim 12 , wherein the transaction machine operations further comprise:

displaying, via the deposit user interface, a progress of the scanning of the at least one bill.

14. The system of claim 12 , wherein the transaction machine operations further comprise:

scanning a plurality of bills of the cash deposit; and

displaying, via the deposit user interface, at least one of a list of denominations of the plurality of bills, a number of bills of each of the denominations, or a total amount of the cash deposit.

15. The system of claim 12 , wherein the transaction machine operations further comprise:

providing, via the deposit user interface, a total amount of the cash deposit.

16. The system of claim 12 , wherein the one or more processors are one or more first processors, the computer-readable storage medium is a first computer-readable storage medium, and the instructions are first instructions, the system further comprising:

a provider computing system comprising one or more second processors and a second computer readable storage medium storing second instructions that when executed cause the provider computing system to perform provider operations comprising:

generating a passcode unique to the request from the payor for the transaction to make the payment to the payee; and

transmitting the generated passcode; and

wherein the transaction machine operations further comprise:

receiving, from the provider computing system, the generated passcode; and

determining that the passcode input received via the passcode user interface matches the generated passcode received from the provider computing system.

17. The system of claim 16 , wherein the generated passcode is generated based on a request received from an individual account holder.

18. The system of claim 12 , wherein the transaction machine operations further comprise:

verifying, based on receiving the amount input, that an amount associated with the amount input does not exceed a threshold value.

19. A system comprising:

a transaction machine associated with a provider computing system, the transaction machine comprising one or more processors and computer readable storage medium storing instructions that when executed cause the transaction machine to perform transaction machine operations comprising:

providing a passcode user interface that allows receipt of a passcode input;

receiving, via the passcode user interface, the passcode input;

determining that the passcode input is valid;

providing, based on determining that the passcode input is valid, an amount user interface that requests an amount input associated with a transaction;

receiving, via the amount user interface, the amount input associated with the transaction;

activating, in response to the amount input, a cash deposit mechanism to receive a cash deposit;

receiving, via the cash deposit mechanism, the cash deposit;

scanning at least one bill of the cash deposit to determine a denomination of the at least one bill;

determining, based on scanning the at least one bill, a sequence of user interfaces to be displayed on a display of the transaction machine; and

providing, using the determined sequence, a deposit user interface that displays deposit information based on the at least one bill.

20. The system of claim 19 , wherein the transaction machine operations further comprise:

scanning a plurality of bills of the cash deposit;

displaying, via the deposit user interface, a progress of the scanning of the plurality of bills; and

displaying, via the deposit user interface, at least one of a list of denominations of the plurality of bills, a number of bills of each of the denominations, or a total amount of the cash deposit.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 2, 2025
From: KURANI, ASHISH B.
To: WELLS FARGO BANK, N.A.
Reel/Frame 071588/0775 →
Continuity (10)
Continuation 17960216 · Oct 5, 2022
Continuation 17689918 · Mar 8, 2022
Continuation 16943675 · Jul 30, 2020
Continuation In Part 16706157 · Dec 6, 2019
Continuation In Part 16239332 · Jan 3, 2019
Provisional Application 62881055 · Jul 31, 2019
Provisional Application 62798362 · Jan 29, 2019
Provisional Application 62614283 · Jan 5, 2018
Provisional Application 62672971 · May 17, 2018
Related Publication 20240185241A1 · Jun 6, 2024
References Cited (74)
US 5465206A · Hilt et al. · 1995 [cited by applicant]
US 5649117A · Landry · 1997 [cited by examiner]
US 5787403A · Randle · 1998 [cited by applicant]
US 5899982A · Randle · 1999 [cited by applicant]
US 5956700A · Landry · 1999 [cited by applicant]
US 6173272B1 · Thomas et al. · 2001 [cited by applicant]
US 6317745B1 · Thomas · 2001 [cited by examiner]
US 6341272B1 · Randle · 2002 [cited by applicant]
US 6996542B1 · Landry · 2006 [cited by examiner]
US 7076458B2 · Lawlor et al. · 2006 [cited by applicant]
US 7182252B1 · Cooper · 2007 [cited by examiner]
US 7200551B1 · Senez · 2007 [cited by applicant]
US 7240031B1 · Kight · 2007 [cited by examiner]
US 7287009B1 · Liebermann · 2007 [cited by examiner]
US 7370014B1 · Vasavada et al. · 2008 [cited by applicant]
US 7395241B1 · Cook · 2008 [cited by examiner]
US 7676431B2 · O'Leary et al. · 2010 [cited by applicant]
US 7813983B2 · Wottowa · 2010 [cited by examiner]
US 7979348B2 · Thomas et al. · 2011 [cited by applicant]
US 8005754B2 · McCoy et al. · 2011 [cited by applicant]
US 8042733B2 · Smith · 2011 [cited by examiner]
US 8190521B2 · O'Leary et al. · 2012 [cited by applicant]
US 8380622B2 · Bushman et al. · 2013 [cited by applicant]
US 8527381B2 · Gerstner · 2013 [cited by examiner]
US 8543506B2 · Grandcolas · 2013 [cited by examiner]
US 8554671B2 · Ballout · 2013 [cited by applicant]
US 8725632B2 · Tompkins · 2014 [cited by examiner]
US 8732044B2 · Lovelett et al. · 2014 [cited by applicant]
US 9520033B2 · Freedman et al. · 2016 [cited by applicant]
US 9633346B2 · Goodwin, III · 2017 [cited by applicant]
US 9652758B2 · Zhou et al. · 2017 [cited by applicant]
US 9773236B2 · Mohsenzadeh · 2017 [cited by applicant]
US 9842322B2 · Johnston et al. · 2017 [cited by applicant]
US 10354246B1 · Janiga · 2019 [cited by applicant]
US 11354632B1 · Hill et al. · 2022 [cited by applicant]
US 11429976B1 · Jain et al. · 2022 [cited by applicant]
US 20010032182A1 · Kumar · 2001 [cited by examiner]
US 20030105711A1 · O'Neil · 2003 [cited by examiner]
US 20030191711A1 · Jamison · 2003 [cited by examiner]
US 20030216960A1 · Postrel · 2003 [cited by applicant]
US 20060173779A1 · Bennett et al. · 2006 [cited by applicant]
US 20060206425A1 · Sharma · 2006 [cited by examiner]
US 20070011104A1 · Leger et al. · 2007 [cited by applicant]
US 20100114677A1 · Carlson et al. · 2010 [cited by applicant]
US 20110238573A1 · Varadarajan · 2011 [cited by applicant]
US 20110251956A1 · Cantley et al. · 2011 [cited by applicant]
US 20130046687A1 · Simpson, Jr. · 2013 [cited by applicant]
US 20130124411A1 · Kobres et al. · 2013 [cited by applicant]
US 20130232064A1 · Bosch · 2013 [cited by applicant]
US 20150199681A1 · Salgado et al. · 2015 [cited by applicant]
US 20150324768A1 · Filter et al. · 2015 [cited by applicant]
US 20160104140A1 · Harrow et al. · 2016 [cited by applicant]
US 20170124544A1 · Recriwal et al. · 2017 [cited by applicant]
US 20170161700A1 · Salgado et al. · 2017 [cited by applicant]
US 20170364899A1 · Watson et al. · 2017 [cited by applicant]
US 20180068281A1 · Johnston et al. · 2018 [cited by applicant]
US 20180204193A1 · Cacheria et al. · 2018 [cited by applicant]
Responsibility of Net-bank in Electronic Payment; 2008 International Symposium on Electronic Commerce and Security (pp. 771-775); Liu Han-xia, Li Rong-jun; Aug. 3, 2008. (Year: 2008). [cited by examiner]
Authorization mechanisms for mobile commerce implementations in enhanced prepaid solutions; Bell Labs Technical Journal (vol. 8, Issue: 4, pp. 121-131); Yigang Cai, Jack Kozik, Helmut L. Raether, John B. Reid, Guy H. St… [cited by examiner]
A generative solution for ATM cash management; 2010 International Conference of Soft Computing and Pattern Recognition; R Armenise, C Birtolo, E Sangianantoni, L Troiano; Dec. 7, 2010. (Year: 2010). [cited by applicant]
A secure mobile payment system using QR code; 2013 5th International Conference on Computer Science and Information Technology (pp. 111-114); Sana Nseir, Nael Hirzallah, Musbah Aqel; Mar. 27, 2013. (Year: 2013). [cited by applicant]
Adaptive & dynamic interfaces for automated teller machines using clusters; 2018 International Conference on Computing, Mathematics and Engineering Technologies (iCoMET) (pp. 1-6); Muhammad Imran, Aarij Mahmood Hussaan;… [cited by applicant]
Authorization mechanisms for mobile commerce implementations in enhanced prepaid solutions; Bell Labs Technical Journal (vol. 8, Issue: 4, pp. 121-131); Yigang Cai, Jack Kozik, Helmut L. Raether, John B. Reid, Guy H. St… [cited by applicant]
Boddupalli, P.; Al-Bin-Ali, F, Davies, N., Friday, A., Storz, 0., Wu, M., Payment support in ubiquitous computing environments; 2003 Proceedings Fifth IEEE Workshop on Mobile Computing Systems and Applications (pp. 110-… [cited by applicant]
Design of Embedded Based Dual Identification ATM Card Security System; 2019 9th International Conference on Emerging Trends in Engineering and Technology—Signal and Information Processing (ICETET-SIP-19) (pp. 1-5); Priy… [cited by applicant]
E-charging API: outsource charging to a payment service provider; IEEE Intelligent Network 2001 Workshop. IN 2001 Conference Record (Cat. No. 01TH8566) (pp. 216-222); K. Luttge; May 6, 2001. (Year: 2001). [cited by applicant]
Liu Han-xia, Li Rong-jun; Responsibility of Net-bank in Electronic Payment; 2008 International Symposium on Electronic Commerce and Security (pp. 771-775); Aug. 3, 2008 (Year: 2008). [cited by applicant]
P2P-Paid: A Peer-to-Peer Wireless Payment System; Second |EEE International Workshop on Mobile Commerce and Services (pp. 102-111); J. Gao, K. Edunuru, J. Cai, S. Shim; Jan. 1, 2005. (Year: 2005). [cited by applicant]
Payment support in ubiquitous computing environments; 2003 Proceedings Fifth IEEE Workshop on Mobile Computing Systems and Applications (pp. 110-120); Boddupalli, P.; Al-Bin-Ali, F, Davies, N., Friday, A., Storz, 0., Wu… [cited by applicant]
Research on E-Payment Model; 2010 International Conference on E-Business and E-Government (pp. 339-341); Zhu Junxuan; May 7, 2010. (Year: 2010). [cited by applicant]
S. Singh, Emergence of payment systems in the age of electronic commerce: The state of art; 2009 First Asian Himalayas International Conference on Internet (pp. 1-18); S. Singh; Nov. 1, 2009 (Year: 2009). [cited by applicant]
P2P-Paid: A Peer-to-Peer Wireless Payment System; Second IEEE International Workshop on Mobile Commerce and Services ( pp. 102-111); J. Gao, K. Edunuru, J. Cai, S. Shim; Jan. 1, 2005. (Year: 2005). [cited by applicant]
Sirbu et al., “NetBill: An Internet commerce system optimized for network delivered services,” 1995, Digest of Papers, COMPCON'95, Technologies for the Information Superhighway, pp. 20-25. [cited by applicant]
Singh et al., “Comparative study on various methods and types of mobile payment system,” 2012 International Conference on Advances in Mobile Network, Communication and Its Applications, pp. 143-148. [cited by applicant]