NZ774345B2 - Tap to autofill card data - Google Patents
Tap to autofill card data Download PDFInfo
- Publication number
- NZ774345B2 NZ774345B2 NZ774345A NZ77434520A NZ774345B2 NZ 774345 B2 NZ774345 B2 NZ 774345B2 NZ 774345 A NZ774345 A NZ 774345A NZ 77434520 A NZ77434520 A NZ 77434520A NZ 774345 B2 NZ774345 B2 NZ 774345B2
- Authority
- NZ
- New Zealand
- Prior art keywords
- field
- account number
- autofill
- eeeeee
- cvv
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3278—RFID or NFC payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/352—Contactless payments by cards
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/356—Aspects of software for card payments
- G06Q20/3567—Software being in the reader
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4018—Transaction verification using the card verification value [CVV] associated with the card
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/409—Device specific authentication in transaction processing
- G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners
- G06Q20/40975—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners using encryption therefor
Abstract
Various embodiments are generally directed to autofilling card data from a contactless card to a form of a computing device. An application may determine that a payment field of a form has received focus. The application may then receive encrypted data from a communications interface of a contactless card associated with an account. The application may then receive, from a server, verification of the encrypted data. The application may then receive, from the server, an encrypted account number associated with the account, and decrypt the encrypted account number to yield the account number. An autofill service of an operating system (OS) executing on the processor circuit, may then autofill the account number to the payment field of the form.
Claims (20)
1. A method, comprising: determining, by an application executing on a device, that a payment field of a form has received focus; outputting, by the application based on the determination that the payment field has received focus, an indication specifying to tap a contactless card to the device; receiving, by the ation, encrypted data from a contactless card associated with an account; transmitting, by the application, the encrypted data to a server; determining, by the ation based on a result received from the server, that the server verified the encrypted data; receiving, by the application from one of the contactless card or the server, an account number associated with the account; providing, by the application, the t number to an ll service; and autofilling, by the autofill service, the account number to the payment field of the form.
2. The method of claim 1, wherein the application ines the payment field of the form has received focus based on a metadata attribute of the payment field, wherein the account number is autofilled to the payment field based on r metadata attribute of the payment field.
3. The method of claim 1, further comprising: determining, by the application, that the received account number is encrypted; and decrypting, by the application, the encrypted account number prior to providing the account number to the autofill service.
4. The method of claim 1, r comprising: ining, by the application, that the form includes the payment field, an expiration date field, a billing address field, and a card cation value (CVV) field.
5. The method of claim 4, further comprising: receiving, by the application, an expiration date, a billing address, and a CVV associated with the account number; providing, by the application, the expiration date, the billing address, and the CVV to an application programming interface (API) of the ll service; and autofilling, by the autofill service, the expiration date to the expiration date field of the form, the billing address to the billing address field of the form, and the CVV to the CVV field of the form.
6. The method of claim 1, further comprising: modifying, by the application, the autofill service based on at least one of: (i) completion of a purchase, or (ii) expiration of a predetermined amount of time, wherein ing the autofill service comprises one or more of: (i) removing the account number from the autofill service, or (ii) copying random data to the autofill service.
7. The method of claim 1, wherein the ted data is based on a cryptographic algorithm and a diversified key, wherein the diversified key is based on a master key and a counter value.
8. A computer-readable storage medium including instructions that when executed by a processor of a device, cause the processor to: determine that a t field of a form has received focus; output, based on the ination that the t field has received focus, an indication specifying to tap a contactless card to the device; receive encrypted data from a contactless card associated with an account; transmit the encrypted data to a server; determine, based on a result received from the server, that the server verified the encrypted data; receive an account number associated with the account from one of the contactless card or the server; provide the account number to an autofill service; and autofill, by the autofill service, the account number to the payment field of the form.
9. The computer-readable e medium of claim 8, wherein the ination that the payment field of the form has ed focus is based on a metadata attribute of the payment field, wherein the account number is autofilled to the payment field based on another metadata attribute of the payment field.
10. The computer-readable storage medium of claim 8, wherein the ctions r configure the er to: determine that the received account number is encrypted; and decrypt the encrypted account number prior to providing the account number to the autofill service.
11. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: determine that the form includes the payment field, an expiration date field, a billing address field, and a card verification value (CVV) field.
12. The computer-readable storage medium of claim 11, wherein the instructions further cause the processor to: receive an expiration date, a billing address, and a CVV associated with the account number; provide the tion date, the g address, and the CVV to an application programming interface (API) of the autofill e; and autofill, by the autofill service, the expiration date to the tion date field of the form, the billing address to the billing address field of the form, and the CVV to the CVV field of the form.
13. The computer-readable storage medium of claim 8, wherein the instructions further cause the processor to: modify the autofill service based on at least one of: (i) completion of a se, or (ii) expiration of a predetermined amount of time, wherein modifying the autofill e comprises one or more of: (i) removing the account number from the autofill service, or (ii) copying random data to the autofill service.
14. The computer-readable storage medium of claim 8, wherein the ted data is based on a cryptographic algorithm and a diversified key, wherein the diversified key is based on a master key and a counter value.
15. A ing tus comprising: a sor; and a memory storing instructions that, when executed by the processor, cause the processor to: determine that a payment field of a form has received focus; output, based on the determination that the payment field has received focus, an indication specifying to tap a contactless card to the apparatus; receive encrypted data from a contactless card associated with an account; transmit the encrypted data to a server; ine, based on a result received from the server, that the server verified the encrypted data; receive an account number associated with the account from one of the contactless card or the server; e the account number to an autofill service; and autofill, by the autofill e, the account number to a payment field of a form.
16. The computing apparatus of claim 15, wherein the determination that the t field of the form has received focus is based on a metadata attribute of the payment field, wherein the account number is autofilled to the payment field based on another metadata attribute of the payment field.
17. The computing apparatus of claim 15, wherein the instructions further cause the processor to: determine that the received account number is encrypted; and decrypt the encrypted account number prior to providing the account number to the autofill e.
18. The computing apparatus of claim 15, wherein the instructions further cause the processor to: ine that the form es the payment field, an expiration date field, a billing address field, and a card verification value (CVV) field.
19. The computing apparatus of claim 18, wherein the instructions further cause the processor to: receive an tion date, a billing address, and a CVV associated with the account; provide the expiration date, the billing address, and the CVV to an ation programming interface (API) of the autofill service; and autofill, by the autofill service, the expiration date to the expiration date field of the form, the billing address to the billing address field of the form, and the CVV to the CVV field of the form.
20. The computing apparatus of claim 15, wherein the encrypted data is based on a cryptographic algorithm and a diversified key, wherein the diversified key is based on a master key and a counter value, n the instructions further cause the processor to: modify the ll service based on at least one of: (i) completion of a purchase, or (ii) expiration of a predetermined amount of time, wherein modifying the autofill service comprises one or more of: (i) removing the account number from the autofill e, or (ii) copying random data to the autofill service. W0 54600 WWW mam. m mg. mm m WWW $me WWWWWWWW WWWWWWWWWWWWWWWWWWWWWWWWWWWW maWWWWWWWWWWW WWW WWWWWWWWWW Em «WEE mema? WWWWWWWWWWWW 28E WWWWWWWWW WWW.. .WWWWWWWWWW.. WWWWWWWWW W W WWW W WWWWWWWWWWW : WWWWWWWWW. .WWWWWWWWWWWWWWWWWWWWWWW gnaw E.z?mnmwm wwm?w? WWmmm? 83$me WWW: WWWWWWWWWW MWWWWWWWWWWWWWWWW SUBSTITUTE SHEET (RULE 26) m. mm $3 zm??smmq mm $53wa m: mm $2353 Emma Mm?mwmmu mammm?ng E wzw?wmam?? amm?m?mm? EEEEW m mam. Emma» «Em mmmamzw. mm «z m:.3 Wm mt m mm ma?a @w??mmq mm 2% wwgmmm WEEm mamm?s? mum Mm Ww?mwm mm? $3 «Em ?g .Eummwmq Em?“ Wamm? Egg ?g $3 $39 Mama ?gmmmmmwww? $3 mm???zmw SUBSTITUTE SHEET (RULE 26) @ SMART CARD 1234 56278 1234 5678 CARDHOLD ER NAME EXPERATEON DATE SUBSTITUTE SHEET (RULE 26) @ SMART CARD "2234 5678 1234 56178 CARDHQLDER NAME EXPERATEON DATE SUBSTITUTE SHEET (RULE 26) @ SMART CARD "2234 5678 1234 56178 CARDHQLDER NAME. EXPERATEON DATE SUBSTITUTE SHEET (RULE 26) @ SMART CARD ”2234 5678 1234 56m CARDHOLDER NAM E TION DATE SUBSTITUTE SHEET (RULE 26) EXPERATEGE {BATE AUTGFELEEE}? .......................... @ SMART CARD 1234 56178 1234 56178 CARDHOLDER NAME. TSON DATE SUBSTITUTE SHEET (RULE 26) @ SMART CARD 1234 56278 1234 56178 LD ER NAME EXPERATEON DATE SUBSTITUTE SHEET (RULE 26) SERVTCE PRQVTDER SMART CARD 1234 5678 1234 5678 CARDHOLDER NAME TEON DATE SUBSTITUTE SHEET (RULE 26) MEMGRY G? A?PLET SUBSTITUTE SHEET (RULE 26) EE/EE : EEEEE EEEEEEEEEEEE EEEEEEEEE EEEEEE EEE EEEEEEE EEEEEEEEE EEEEEEE ............................................................................................... EEE EEEEEEEEEEEE EEEEE EEE EEEEEEEE EEEEEE E0 EEEEEE EEEEEEEEEESE EEEEE E0 EEEE ~ ................................................................................ EEEEEEEE, EE EEEEEEEEEEESE EEEEE, EEEEEEEEEEE EEEEEE ESEEEE EEEEEEE KEE EEEEE EEEEEEEEEEEEEEE ~ ................................................... EEEEEEEE, EE EEEEEEEEEEESE EEEEEE, EEEEE EEEEEE EEEEEEEEEEEEE EEE EEEEE EEEEEEEEEEEEEEEE ................................................................................... z 525 EEEEEEEEEE, EE EEEEEEEEEEEEE EEEEEE, EEEEEEEEEEE EEEE EEE EE EEEEEE . EEE EEEEEEE, EE EEEEEE, EEEEEEEEEE EEEEEE EEEEEEEE EEEEEEE EEE EEEEE EEEEEEEE EEEEEEEEEEE ~~ ................................................................ EEEEEEE, E‘E EEEEEE, EEEEEEEEEEE EEEE EEE EEEEEE EEEEEEEEEEEE EEEEE EEEEEE ...................................... . EEE EEEEEEEE, EE EEEEEE, EEEEEEEEEEE EEEE REEEEEEEE} EEEEEE EEEEEEEEEEEEE EEEE EEE EEEEEEEE .~~ EEEEE E .3 55% TRAEESMEE, BY SERVER, CARE} EMA Ti) MEEBEEE BEVECE AND MEN? (QENEER VAEEEE . 555 YRANSMEE, 3E MGBELE EE‘E’ECE, CARE} mm 16 AFE {BF ASTUFEEE SERVKE ‘ ; 56E} AUEGFEEE, 3‘! AUEBFEEE SERVEEE, {ARE} DATA m E’A‘E’MENE NEED SF EGRM SUBSTITUTE SHEET (RULE 26) GP- K239 TA? EGNTAGLESS {ARE} H} MSBELE BEVEEE EN‘ZRYFT, IY CGNMCTEESS {ARE}, VERTUAL AKGUNT NEMBER AND GENERATE EMRYPTED ‘ {HSTOMER ED, TRANSMH TE} MGBELE BEVKE MGBEFT, E? EQNFAETLESS {ARE}, SWEET} VERTEML AEEQH 2we MEMBERS "m REHEET REM) ~' 0? VERTUM AEEGUE‘H NSMBER SUBSTITUTE SHEET (RULE 26) SUBSTITUTE SHEET (RULE 26) § __________________Km 3 3 _____Q?EE._@E§§§_§¥WV3______._§ ij'j________________5332 H APPEBEATEGNS : ........ ASAPYGR ENPUT {EEWEE ‘ " ‘ ENTERWE ’ ~~ WAN " REMQTE ....................................................................... {0M?UFER{S) SUBSTITUTE SHEET (RULE 26)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US16/256,983 US11037136B2 (en) | 2019-01-24 | 2019-01-24 | Tap to autofill card data |
| PCT/US2020/014963 WO2020154600A1 (en) | 2019-01-24 | 2020-01-24 | Tap to autofill card data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| NZ774345A NZ774345A (en) | 2024-07-05 |
| NZ774345B2 true NZ774345B2 (en) | 2024-10-08 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240338686A1 (en) | Method and system for transaction processing with complete cryptographic auditability | |
| AU2021204210B2 (en) | Method and system for validation of hashed data via acceptance frames | |
| CN111581210A (en) | Data importing method and system | |
| US10810588B2 (en) | Method and system for authorization using a public ledger and encryption keys | |
| WO2019125664A1 (en) | Method and system for outside guarantees for a blockchain transaction | |
| EP3779760B1 (en) | Blockchain-based data processing method and apparatus, and electronic device | |
| US12229752B2 (en) | Method and system for regulation of blockchain transactions | |
| US11915228B2 (en) | Method and system for prevention of lost currency in blockchain networks to missing wallets | |
| KR101737559B1 (en) | Apparatus and method for generating identification information for replacing account number, and computer program for the same | |
| US12386815B2 (en) | Method and system for dynamic addition of blocks in a blockchain | |
| CN110111208A (en) | Declaration form data processing method, device, computer equipment and storage medium | |
| CN108537520B (en) | Method and device for accessing third-party payment transaction | |
| KR20230004271A (en) | Method for uploading and managing a single data with a capacity larger than the maximum block size on the blockchain | |
| CN109726249B (en) | Decentralized chip research and development transaction data storage method and system | |
| US20210174317A1 (en) | Method and system for modified mining probabilities based on fees | |
| NZ774345B2 (en) | Tap to autofill card data | |
| US11875357B2 (en) | Method and system of using miner commitment to reward proofs | |
| NZ774345A (en) | Tap to autofill card data | |
| CN114693438A (en) | Service processing method and device, electronic equipment and readable storage medium | |
| CN117255139A (en) | Message transmission method and device, electronic equipment and storage medium | |
| CN111737262B (en) | Data processing method and device | |
| EP4409838A1 (en) | Method and system for blockchain-based transactions for the atomic exchange of assets | |
| CN112184453A (en) | Block chain based information processing method, block chain link point and storage medium | |
| CN110852864A (en) | Method and device for processing digital resource amount and storage medium | |
| US20250299165A1 (en) | Method and system for artificial intelligence dynamic pricing recommendation model for cross-border transactions |