G06Q20/4018

CARDHOLDER SELECTED CARD VALIDATION CODE FOR CARD-NOT-PRESENT TRANSACTIONS

Systems and methods for managing a user-selected card verification code (CVC2) value for a payment card are disclosed. A sever is coupled to a payment card database and a hardware security module. The server is programmed to receive a request from a user to change the CVC2 value of the payment card to the user-selected CVC2 value. Based upon the request, the server retrieves from a payment card table stored on the database a payment card record associated with the payment card. The server transmits the user-selected CVC2 value, and, from the payment card record, a primary account number, a payment card expiry date, and a first service code to a hardware security module. The server subsequently receives from the hardware security module a second service code associated with the user-selected CVC2 value. The server updates the first service code in the payment card record to the second service code.

Hosted sensitive data form fields for compliance with security standards

Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Credit card and operating method therefor
11275869 · 2022-03-15 · ·

An operating method for a credit card, the method comprising: step S1, a microprocessor is powered on to perform system initialization; step S2, the microprocessor hibernates and is awakened when a preset interruption is detected so as to execute step S3; and step S3, the microprocessor executes preset interruption processing by entering a preset interruption processing flow, and exits the preset interruption processing flow when the preset interruption processing is finished, then returns to step S2. Alternatively, the method comprises: step s1, the microprocessor is powered on to perform system initialization; step s2, the microprocessor checks whether a preset interruption marker is set, and if so, the preset interruption marker is reset so as to execute the preset interruption processing, otherwise the microprocessor executes step s3; and step s3, the microprocessor hibernates, is awakened when detecting the preset interruption so as to set the preset interruption marker, and then returns to step s2. The present invention may reduce the risk of credit card fraud.

Systems and methods for image capture vector format lasering engine
11301867 · 2022-04-12 · ·

A transaction card construction and computer-implemented methods for a transaction card are described. The transaction card has vector formatted visible information lasered onto its surface. In some embodiments, systems and methods are disclosed for enabling the sourcing of visible information using a scalable vector format. The systems and methods may receive a request to add a first plurality of visible information to a transaction card and capture an image of the first plurality of visible information. The systems and methods may also map the image to a bounding box and convert the mapped image into vector format. In addition, the systems and methods may provide the converted image to a laser machine.

Secure transfer of tokens between devices

Various embodiments are generally directed to the secure transfer of account tokens between devices. For example, a first device may receive an account token stored on a second device using web Bluetooth application programming interfaces (APIs). As another example, the second device may push the account token to the first device.

Proximity interaction system including secure encryption scheme
11283781 · 2022-03-22 · ·

A method is disclosed for conducting a transaction between a computing device and an access device. A server computer may be utilized to facilitate data exchanges between the computing device and the access device. These data exchanges may utilize high-frequency sound signals. The server computer may encrypt at least some portion of data that is then transmitted to the access device via the computing device. The server computer may verify data received from the access device prior to generating and transmitting an authorization request message for the transaction.

AGGREGATED TRANSACTION ACCOUNTS
20220114588 · 2022-04-14 ·

Disclosed are various embodiments for using aggregated transaction accounts to make purchases. A transaction authorization request for a transaction is received from a merchant device, the transaction authorization request comprising an aggregated transaction account identifier, a transaction amount, and a merchant identifier. Multiple linked transaction accounts associated with an aggregated transaction account identified by the aggregated transaction account identifier are then identified or selected. At least a portion of the transaction amount is debited from each of the multiple linked transaction accounts. Then, an authorization response is sent to the merchant device, the authorization response indicating that the transaction is authorized for the transaction amount.

AGGREGATED TRANSACTION ACCOUNTS
20220114589 · 2022-04-14 ·

Disclosed are various embodiments for using aggregated transaction accounts to make purchases. A transaction authorization request for a transaction is received from a merchant device, the transaction authorization request comprising an aggregated transaction account identifier, a transaction amount, and a merchant identifier. Multiple linked transaction accounts associated with an aggregated transaction account identified by the aggregated transaction account identifier are then identified or selected. At least a portion of the transaction amount is debited from each of the multiple linked transaction accounts. Then, an authorization response is sent to the merchant device, the authorization response indicating that the transaction is authorized for the transaction amount.

Cardholder selected card validation code for card-not-present transactions

Systems and methods for managing a user-selected card verification code (CVC2) value for a payment card are disclosed. A sever is coupled to a payment card database and a hardware security module. The server is programmed to receive a request from a user to change the CVC2 value of the payment card to the user-selected CVC2 value. Based upon the request, the server retrieves from a payment card table stored on the database a payment card record associated with the payment card. The server transmits the user-selected CVC2 value, and, from the payment card record, a primary account number, a payment card expiry date, and a first service code to a hardware security module. The server subsequently receives from the hardware security module a second service code associated with the user-selected CVC2 value. The server updates the first service code in the payment card record to the second service code.

Dynamic code payment card verification

Embodiments described herein disclose methods and systems for authorizing a payment card transaction using dynamic codes. The system can receive a request for authorization of a transaction using the payment card. The request can identify a verification code associated with the payment card and an identifier of the payment card, and the payment card can have an associated dynamic code accessible to a user via a channel. The verification code can be compared with a value of the dynamic code at the time of the transaction. The system can determine whether the user of the payment card accessed the channel within a time period prior to receiving the request for authorization. In response to the verification code matching the dynamic code at the time of the transaction and determining that the user accessed the channel within the time period prior to receiving the request, the system can authorize the transaction.