US 11,972,431 B2
Systems and methods for virtual certification number registration
Kelly Jo Brown, Rockville, MD (US); Jesse Emery, Arlington, VA (US); Jonathan Blocksom, Reston, VA (US); Swapna Mandala, Glen Allen, VA (US); Todd Safford, Bethesda, MD (US); Victoria Yang, Fairfax, VA (US); Brian Glowniak, McLean, VA (US); Edward Husa, McLean, VA (US); Calvin Sun, McLean, VA (US); and Audrey Zhang, McLean, VA (US)
Assigned to Capital One Services, LLC, McLean, VA (US)
Filed by Capital One Services, LLC, McLean, VA (US)
Filed on Nov. 23, 2022, as Appl. No. 18/058,456.
Claims priority of provisional application 63/374,693, filed on Sep. 6, 2022.
Prior Publication US 2024/0078553 A1, Mar. 7, 2024
Int. Cl. G06Q 20/40 (2012.01); G06F 21/33 (2013.01); G06F 21/62 (2013.01); G06Q 30/018 (2023.01); H04L 9/32 (2006.01)
CPC G06Q 20/4016 (2013.01) [G06F 21/33 (2013.01); G06F 21/6218 (2013.01); G06Q 30/018 (2013.01); H04L 9/3213 (2013.01); H04L 9/3263 (2013.01)] 14 Claims
OG exemplary drawing
 
1. A method for registering use of virtual certification numbers (VCNs) for a primary account number (PAN) at a secure entity, the method comprising:
receiving, at an external gateway, a registration request comprising an external request code and the PAN, wherein the external request code is generated at and provided by an external entity and is unique to the secure entity, the registration request being a request to register use of VCNs for the PAN at the secure entity;
receiving, by a registration endpoint, a tokenized PAN based on the PAN;
identifying, at a certification mechanism tools module, a secure entity account identifier by:
applying the tokenized PAN to a certification mechanism tool application programing interface (API);
converting the tokenized PAN into a secure entity readable format without extracting the PAN from the tokenized PAN;
comparing the tokenized PAN converted into the secure entity readable format to a plurality of known secure entity account identifiers; and
identifying the secure entity account identifier that matches the tokenized PAN converted into the secure entity readable format based on the comparing;
generating, at the certification mechanism tools module, a certification mechanism reference identifier by encrypting a certification mechanism identifier associated with the identified secure entity account identifier and the tokenized PAN;
associating the certification mechanism reference identifier with the external request code by updating a database;
generating a registration authentication for the external request code in response to receiving the registration request and to associating the certification mechanism reference identifier with the external request code;
receiving a first VCN request to generate a first VCN corresponding to only a first source portal, the first VCN request comprising a first external request code and a first source portal identifier associated with the first source portal;
in response to receiving the first VCN request, determining that the first external request code matches the external request code having the registration authentication;
in response to determining that the first external request code matches the external request code, generating the first VCN based on the first source portal identifier;
receiving a second VCN request to generate a second VCN corresponding to only a second source portal, the second VCN request comprising a second external request code and a second source portal identifier associated with the second source portal;
in response to receiving the second VCN request, determining that the second external request code is unregistered for VCN use; and
in response to determining that the second external request code is unregistered for VCN use, rejecting the second VCN request.