	US 12,462,259 B2
	Private label account number protection
Arthur Roca, Columbus, OH (US); Randall Piatt, Blacklick, OH (US); Tom Pugh, Powell, OH (US); and Rachit Sood, Columbus, OH (US)
Assigned to BREAD FINANCIAL PAYMENTS, INC., Columbus, OH (US)
Filed by BREAD FINANCIAL PAYMENTS, INC., Columbus, OH (US)
Filed on Oct. 26, 2017, as Appl. No. 15/795,164.
Claims priority of provisional application 62/526,936, filed on Jun. 29, 2017.
Prior Publication US 2019/0005498 A1, Jan. 3, 2019
Int. Cl. G06Q 20/08 (2012.01); G06Q 20/10 (2012.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01)

CPC G06Q 20/409 (2013.01) [G06Q 20/3825 (2013.01); G06Q 20/385 (2013.01)]

11 Claims

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.