IP Library Granted Patent US 12,462,259
Granted Patent B2
US 12,462,259 · App. 15/795,164 · Granted Nov 4, 2025

Private label account number protection

Inventors: Arthur Roca (Columbus, OH); Randall Piatt (Blacklick, OH); Tom Pugh (Powell, OH); Rachit Sood (Columbus, OH)
Assignee: BREAD FINANCIAL PAYMENTS, INC.
G06Q20/409G06Q20/3825G06Q20/385
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,462,259
App. No.
15/795,164
Granted
Nov 4, 2025
Kind
B2
Abstract

A system and method for private label account number protection is described. A method receives, at a retail computing system, a private label credit account number being proffered to make a private label credit purchase. A request for authorization for the purchase is provided from the retail computing system to a private label credit account provider over a dedicated connection between the retail computing system and the private label credit account provider. The retail computing system receives an authorization token from the credit account provider and stores the authorization token in place of the private label credit account number.

Claims (58)

1 . A method for protecting a consumer's private label card number at a retailer database, said method comprising:

receiving, at a retail computing system, a private label credit account number;

generating, at said retail computing system, a purchase request, said purchase request comprising:

requesting authorization for said private label credit account number; and

indicating how said private label credit account number was presented to said retail computing system, said indicating comprising a channel and a device;

providing, from said retail computing system, said purchase request to a private label credit account provider computing system;

generating, at said private label credit account provider computing system, an authorization token, said authorization token not including said private label credit account number, said authorization token comprising a token limited scope, said token limited scope:

identifying said channel and said device, and

restricting said token usage to only said channel and said device such that an attempt to utilize said authorization token in a manner inconsistent with said channel and said device will be declined;

providing, from said private label credit account provider computing system, said authorization token to said retail computing system;

receiving, at said retail computing system, said authorization token from said private label credit account provider computing system;

replacing, at said retail computing system, said private label credit account number with said authorization token;

storing, at said retail computing system, said authorization token;

not storing, at said retail computing system, said private label credit account number;

linking, at said retail computing system, a detail of a goods purchased with said stored authorization token; and

performing, at said retail computing system, a return utilizing said stored authorization token stored at said retail computing system in conjunction with said detail of said goods purchased linked with said stored authorization token without requiring said private label credit account number.

2 . The method of claim 1 , further comprising:

linking, at a database of said private label credit account provider computing system, said authorization token with said private label credit account number.

3 . The method of claim 2 , further comprising:

tallying, at said database of said private label credit account provider computing system, a plurality of metrics for every authorization token linked with said private label credit account number.

4 . The method of claim 3 , further comprising:

calculating a rewards information for said private label credit account number utilizing a result of said tallying of one or more of said plurality of metrics for every authorization token linked with said private label credit account number.

5 . The method of claim 1 , further comprising:

receiving said private label credit account number at said retail computing system during a physical in-store interaction;

said purchase request comprising:

an indication that said private label credit account number was received at said retail computing system during said physical in-store interaction.

6 . The method of claim 5 , wherein said physical in-store interaction is selected from a group consisting of: a physical card swipe, a physical card chip read, a scan of a display screen of a customer's mobile device, and a wireless transmission of said private label credit account number from said customer's mobile device.

7 . The method of claim 1 , further comprising:

receiving said private label credit account number at said retail computing system during an e-commerce interaction;

said purchase request comprising:

an indication that said private label credit account number was received at said retail computing system during said e-commerce interaction.

8 . A system comprising:

a retail computing system, said retail computing system comprising:

a retail database; and

a retail processor, said retail processor configured to:

receive a private label credit account number;

generate a purchase request, said purchase request comprising:

a request for authorization for said private label credit account number; and

an indicator identifying how said private label credit account number was presented to said retail computing system, said indicator comprising a channel and a device; and

provide said purchase request to a private label credit account provider computing system;

said private label credit account provider computing system, said retail computing system comprising:

a private label credit account provider processor, said private label credit account provider processor configured to:

generate an authorization token linked to said private label credit account number, said authorization token not including said private label credit account number, said authorization token comprising a token limited scope, said token limited scope:

identifying said channel and said device, and

restricting said token usage to only said channel and said device such that an attempt to utilize said authorization token in a manner inconsistent with said channel and said device will be declined; and

provide said authorization token to said retail computing system;

said retail processor of said retail computing system configured to:

receive said authorization token from said private label credit account provider computing system;

replace, at said retail database, said private label credit account number with said authorization token;

store, at said retail database, said authorization token;

not store, at said retail database, said private label credit account number;

link, at said retail database, a detail of a goods purchased with said stored authorization token; and

utilize said stored authorization token stored at said retail database to perform a customer refund system in conjunction with said detail of said goods purchased linked with said stored authorization token without requiring said private label credit account number.

9 . The system of claim 8 , wherein said private label credit account provider computing system is further configured to:

tally a plurality of metrics for every authorization token linked with said private label credit account number; and

calculate a rewards information for said private label credit account number from a result of said tally.

10 . The system of claim 8 , wherein said channel is selected from a group consisting of: a physical in-store interaction at a point of sale (POS), and an e-commerce interaction.

11 . The system of claim 10 , wherein said physical in-store interaction at said POS is selected from a group consisting of: a physical card swipe, a physical card chip read, a scan of a display screen of a customer's mobile device, and a wireless transmission of said private label credit account number from said customer's mobile device.

Assignments (2)
MERGER AND CHANGE OF NAME Recorded Mar 21, 2023
From: COMENITY LLC; BREAD FINANCIAL PAYMENTS, INC
To: BREAD FINANCIAL PAYMENTS, INC.
Reel/Frame 063125/0756 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2017
From: ROCA, ARTHUR; PIATT, RANDALL; PUGH, TOM; SOOD, RACHIT
To: COMENITY LLC
Reel/Frame 043963/0695 →
Continuity (2)
Provisional Application 62526936 · Jun 29, 2017
Related Publication 20190005498A1 · Jan 3, 2019
References Cited (38)
US 4320260A · Lechner · 1982 [cited by examiner]
US 6502747B1 · Stoutenburg · 2003 [cited by examiner]
US 7861930B2 · Esplin et al. · 2011 [cited by applicant]
US 8060413B2 · Castell et al. · 2011 [cited by applicant]
US 8682802B1 · Kannanari · 2014 [cited by applicant]
US 9195984B1 · Spector · 2015 [cited by examiner]
US 9342832B2 · Basu · 2016 [cited by examiner]
US 9524501B2 · Weber · 2016 [cited by applicant]
US 10176478B2 · Griggs · 2019 [cited by examiner]
US 10318932B2 · Bower · 2019 [cited by examiner]
US 10713660B2 · Awasthi · 2020 [cited by examiner]
US 11120430B2 · Metral · 2021 [cited by examiner]
US 11257076B2 · Gulak · 2022 [cited by examiner]
US 20080114699A1 · Yuan et al. · 2008 [cited by applicant]
US 20090233579A1 · Castell et al. · 2009 [cited by applicant]
US 20100153221A1 · Esplin et al. · 2010 [cited by applicant]
US 20110161233A1 · Tieken · 2011 [cited by examiner]
US 20120101881A1 · Taylor · 2012 [cited by examiner]
US 20120150669A1 · Langley et al. · 2012 [cited by applicant]
US 20130031006A1 · McCullagh et al. · 2013 [cited by applicant]
US 20130198080A1 · Anderson et al. · 2013 [cited by applicant]
US 20140143075A1 · Eason, Jr. et al. · 2014 [cited by applicant]
US 20150112870A1 · Nagasundaram · 2015 [cited by examiner]
US 20150112871A1 · Kumnick · 2015 [cited by applicant]
US 20150254648A1 · Clements et al. · 2015 [cited by applicant]
US 20150254698A1 · Bondesen et al. · 2015 [cited by applicant]
US 20150254699A1 · Bondesen et al. · 2015 [cited by applicant]
US 20150278799A1 · Palanisamy · 2015 [cited by applicant]
US 20160034900A1 · Nelsen · 2016 [cited by examiner]
US 20160162884A1 · Bondesen et al. · 2016 [cited by applicant]
US 20160253651A1 · Park et al. · 2016 [cited by applicant]
US 20160275474A1 · Kim et al. · 2016 [cited by applicant]
US 20160335641A1 · White et al. · 2016 [cited by applicant]
US 20170293916A1 · Humphrys · 2017 [cited by examiner]
US 20180255142A1 · Benantar · 2018 [cited by examiner]
US 20200034837A1 · Narayan · 2020 [cited by examiner]
Ron White, How Computers Work, Oct. 2003, QUE, Seventh Edition (Year: 2003). [cited by examiner]
Mian et al., Enhancing Communication Adaptability Between Payment Card Processing Networks, IEEE Communications Magazine, Mar. 2015 (Year: 2015). [cited by examiner]