Sytems and methods to perform registration operations with contactless cards
AssigneeCapital One Services, LLC
InventorsKevin Osborn, Narmeen Rahman, Marianne Huang, John Jones
Life of this patent
Estimating the term…
Abstract
Embodiments cover registering, deregistering, and checking the status of contactless cards. A personalization system creates card data, including identifiers, for new and replacement cards, which are registered or deregistered as needed. A validation system verifies card activity and validity by processing queries with identifiers and encrypted data. Embodiments further include a system that manages contactless card registrations and billing via a card registration database to maintain card data, an API for registration and status updates, and a billing module to calculate charges for issuers.
Claims20
A method, comprising:
- generating, by a personalization system, card data comprising an issuer identifier and a unique identifier for a new contactless card, the issuer identifier to identify the issuer of the contactless card, and the unique identifier to identify the contactless card;
- sending, by the personalization system, the card data to a registration system to register the new contactless card with the registration system comprising a card registration database, the registration system configured to separately manage and secure registrations for a plurality of independent issuers;
- and
- providing, by the personalization system, the card data to the new contactless card.
A method for validating a contactless card operation, the method comprising:
- establishing, by a switchboard node of a central switchboard system, a secure session for a request to perform an operation from a computing device including generating a nonce and a session token;
- receiving, by a validation system coupled with the central switchboard system and from the computing device, a validation request initiated by a tap of a contactless card against the computing device, the validation request including the nonce, the session token, encrypted data generated by and obtained from the contactless card, an issuer identifier associated with an issuer of the contactless card, and a unique identifier associated with the contactless card;
- verifying, by the validation system, the session token, and the nonce to associate the tap with the secure session;
- determining, by the validation system, an active registration status for the contactless card by performing a lookup using the received issuer identifier and the received unique identifier against stored registration data;
- authenticating, by the validation system, the received encrypted data originating from the contactless card;
- and
- authorizing, by the validation system, the operation associated with the tap upon determining that the registration status is active and that the encrypted data is successfully authenticated.
A system for managing contactless card registrations and associated billing within a multi-issuer computing environment, the system comprising:
- a processor;
- and
- a memory storing instructions that, when executed by the processor, configure the system to provide:
- a card registration database configured to store registration data for contactless cards associated with a plurality of independent issuers, the registration data including at least an issuer identifier, a unique card identifier, and a registration status;
- a card registration application programming interface (API) configured to receive registration requests and deregistration requests from the plurality of independent issuers and update the registration data in the card registration database;
- a registered API configured to receive status queries comprising an issuer identifier and a unique card identifier, query the card registration database based on the received identifiers, and return an indication of the registration status;
- and
- a bill module configured to access the card registration database, determine billable events based on changes in registration status or predefined schedules, calculate charges based on a pricing table, and generate billing data for the plurality of issuers.
Dependencies are inferred from the claim text.