WO2025071626A1

WO2025071626A1 - Authenticated interaction for autonomous vehicles

Info

Publication number: WO2025071626A1
Application number: PCT/US2023/075609
Authority: WO
Inventors: Stephen James Douglass KIRK
Original assignee: Visa International Service Association
Current assignee: Visa International Service Association
Priority date: 2023-09-29
Filing date: 2023-09-29
Publication date: 2025-04-03
Anticipated expiration: 2026-03-29

Abstract

A method includes a central computer receiving, from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction. The resource request message can comprise a location of the autonomous vehicle and a resource provider identifier. After receiving the resource request message the central computer can validate the resource request message by comparing the location of the autonomous vehicle with a location of the access device. After validating the resource request message the central computer can process the transaction using a token associated with a credential. The credential can be associated with the autonomous vehicle.

Description

PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 AUTHENTICATED INTERACTION FOR AUTONOMOUS VEHICLES BACKGROUND [0001] It is predicted that by 2025, there will be 50 million autonomous vehicles operating globally. Autonomous devices introduce scenarios of device- initiated payments, and device to device payments. Such situations can raise data security issues since a human may not be present to verify the authenticity of the payments. Further, autonomous vehicle makers each have their own or no method of making payments, and there is a lack of interoperability between different vehicles and devices. This results in a poor experience for users. [0002] It is further difficult to verify that an autonomous vehicle and an access device are not interacting with an unauthorized party and/or are interacting when they shouldn’t be interacting. [0003] Another problem to be solved relates to data security. Since device initiated payments can be autonomous, there is a risk that credentials (e.g., primary account numbers) used to conduct automated payment transactions can be exposed to hacking and man-in-the-middle attacks. [0004] Embodiments of the disclosure address this problem and other problems individually and collectively. SUMMARY [0005] One embodiment is related to a method comprising: receiving, by a central computer from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier; after receiving the resource request message, validating, by the central computer, the resource request message by comparing the location of the autonomous vehicle with a location of the access device; and after validating the resource request message, processing, the transaction, using a token associated with a credential, the credential associated with the autonomous vehicle. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0006] Another embodiment is related to a central computer comprising: a processor; and a computer-readable medium coupled to the processor, the computer-readable medium comprising code executable by the processor for implementing a method comprising: receiving, from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier; after receiving the resource request message, validating the resource request message by comparing the location of the autonomous vehicle with a location of the access device; and after validating the resource request message, processing, the transaction, using a token associated with a credential, the credential associated with the autonomous vehicle. [0007] Another embodiment is related to a method comprising: providing, by an autonomous vehicle to a central computer, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier, wherein after receiving the resource request message, the central computer validates the resource request message by comparing the location of the autonomous vehicle with a location of the access device; receiving, by the autonomous vehicle from the central computer, a resource response message comprising access data; providing, by the autonomous vehicle to the access device, the access data; and receiving, by the autonomous vehicle from the access device, the resource. [0008] Further details regarding embodiments of the disclosure can be found in the Detailed Description and the Figures. BRIEF DESCRIPTION OF THE DRAWINGS [0009] FIG.1 shows a block diagram illustrating an authenticated interaction for autonomous vehicles system according to embodiments. [0010] FIG.2 shows a block diagram of components of a central computer according to embodiments. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0011] FIG.3 shows a block diagram of components of an autonomous vehicle according to embodiments. [0012] FIG.4 shows a flow diagram illustrating an overview of a remote interaction authorization for autonomous vehicles method according to embodiments. [0013] FIG.5 shows a flow diagram illustrating a first remote interaction authorization for autonomous vehicles method according to embodiments. [0014] FIG.6 shows a flow diagram illustrating a second remote interaction authorization for autonomous vehicles method according to embodiments. [0015] FIG.7 shows a block diagram of components of an access device according to embodiments. DETAILED DESCRIPTION [0016] Prior to discussing embodiments of the disclosure, some terms can be described in further detail. [0017] An “interaction” may include a reciprocal action or influence. An interaction can include a communication, contact, or exchange between parties, devices, and/or entities. Example interactions include a transaction between two parties and a data exchange between two devices. In some embodiments, an interaction can include a user requesting access to secure data, a secure webpage, a secure location, and the like. In other embodiments, an interaction can include a payment transaction in which two devices can interact to facilitate a payment. [0018] “Interaction data” can include data associated with an interaction. In some embodiments, interaction data can be transaction data of the network data. Transaction data can comprise a plurality of data elements with data values. [0019] A “user” may include an individual. In some embodiments, a user may be associated with one or more personal accounts and/or mobile devices. The user may also be referred to as a cardholder, account holder, or consumer in some embodiments. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0020] A “user device” may be a device that is operated by a user. Examples of user devices may include a mobile phone, a smart phone, a card, a personal digital assistant (PDA), a laptop computer, a desktop computer, a server computer, a vehicle such as an automobile, a thin-client device, a tablet PC, etc. Additionally, user devices may be any type of wearable technology device, such as a watch, earpiece, glasses, etc. The user device may include one or more processors capable of processing user input. The user device may also include one or more input sensors for receiving user input. As is known in the art, there are a variety of input sensors capable of detecting user input, such as accelerometers, cameras, microphones, etc. The user input obtained by the input sensors may be from a variety of data input types, including, but not limited to, audio data, visual data, or biometric data. The user device may comprise any electronic device that may be operated by a user, which may also provide remote communication capabilities to a network. Examples of remote communication capabilities include using a mobile phone (wireless) network, wireless data network (e.g., 3G, 4G or similar networks), Wi-Fi, Wi-Max, or any other communication medium that may provide access to a network such as the Internet or a private network. [0021] A “user identifier” can include any piece of data that can identify a user. A user identifier can comprise any suitable alphanumeric string of characters. In some embodiments, the user identifier may be derived from user identifying information. In some embodiments, a user identifier can include an account identifier associated with the user. [0022] An “autonomous vehicle” can include a vehicle used for transporting people or goods that operates without direct human control. An autonomous vehicle can be capable of sensing its environment and operating without human involvement. A human passenger is not required to take control of the vehicle at any time, nor is a human passenger required to be present in the vehicle at all. An autonomous vehicle can include any suitable type of vehicle (e.g., a car, a truck, a drone, a boat, etc.) An autonomous car can go anywhere a traditional car goes and do everything that an experienced human driver does. [0023] An “autonomous vehicle task” can include a task that an autonomous vehicle is to perform. An autonomous vehicle task can include information relating to PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 what task an autonomous vehicle is to perform, and how the autonomous vehicle is to perform a task. For example, an autonomous vehicle task can include a task to navigate from one location to another location. The autonomous vehicle task can include navigation information. As an illustrative example, a first autonomous vehicle task can include navigation information to proceed from a current location of the autonomous vehicle to a location of an access device (e.g., a charging station). A second autonomous vehicle task can include instructions to charge at the charging station until a battery of the autonomous vehicle is full. [0024] A “location” can include a particular place or position. A location can include a position of something (e.g., a user device, an autonomous vehicle, an access device, etc.) A location can include any suitable location information. For example, a location can include a longitude, a latitude, an altitude, a street address, etc. [0025] A “credentials” may comprise any evidence of authority, rights, or entitlement to privileges. For example, an access credential may comprise permissions to access certain tangible or intangible assets, such as a building or a file. Examples of credentials may include passwords, passcodes, or secret messages. In another example, payment credentials may include any suitable information associated with and/or identifying an account (e.g., a payment account and/or payment device associated with the account). Such information may be directly related to the account or may be derived from information related to the account. Examples of account information may include an “account identifier” such as a PAN (primary account number or “account number”), a token, a subtoken, a gift card number or code, a prepaid card number or code, a user name, an expiration date, a CVV (card verification value), a dCVV (dynamic card verification value), a CVV2 (card verification value 2), a CVC3 card verification value, etc. An example of a PAN is a 16-digit number, such as “4000123400001234”. In some embodiments, credentials may be considered sensitive information. [0026] An “access device” may be any suitable device that provides access to a remote system. An access device may also be used for communicating with a coordination computer, a communication network, or any other suitable system. An access device may generally be located in any suitable location, such as at the PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 location of a merchant. An access device may be in any suitable form. Some examples of access devices include charging stations, POS or point of sale devices (e.g., POS terminals), cellular phones, personal digital assistants (PDAs), personal computers (PCs), tablet PCs, hand-held specialized readers, set-top boxes, electronic cash registers (ECRs), vending machines, automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, and the like. [0027] An access device may use any suitable contact or contactless mode of operation to send or receive data from, or associated with, a mobile communication or payment device. For example, access devices can have card readers that can include electrical contacts, radio frequency (RF) antennas, optical scanners, bar code readers, or magnetic stripe readers to interact with portable devices such as payment cards. [0028] “Access data” can include information used to access something. Access data can include data that is to be provided to an access device to access a resource provided by the access device. Access data can include an order identifier or a token. [0029] An “order identifier” can be a value that corresponds to a particular order. An order identifier can be a numerical value, alphanumerical value, etc. that can uniquely identify an order. [0030] A “resource provider” may be an entity that can provide a resource such as goods, services, information, and/or access. Examples of resource providers includes merchants, data providers, transit agencies, governmental entities, venue and dwelling operators, etc. A “merchant” may typically be an entity that engages in transactions and can sell goods or services, or provide access to goods or services. [0031] An “authorization request message” may be an electronic message that requests authorization for an interaction. In some embodiments, it is sent to a transaction processing computer and/or an issuer of a payment card to request authorization for a transaction. An authorization request message according to some embodiments may comply with International Organization for Standardization PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 (ISO) 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a user using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with a payment device or payment account. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV (card verification value), a dCVV (dynamic card verification value), a PAN (primary account number or “account number”), a payment token, a user name, an expiration date, etc. An authorization request message may also comprise “transaction information,” such as any information associated with a current transaction, such as the transaction value, resource provider identifier, merchant location, acquirer bank identification number (BIN), card acceptor ID, information identifying items being purchased, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction. [0032] An “authorization response message” may be a message that responds to an authorization request. In some cases, it may be an electronic message reply to an authorization request message generated by an issuing financial institution or a transaction processing computer. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval -- transaction was approved; Decline -- transaction was not approved; or Call Center -- response pending more information, merchant must call the toll-free authorization phone number. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the transaction processing computer) to the merchant's access device (e.g., POS equipment) that indicates approval of the transaction. The code may serve as proof of authorization. [0033] An “authorizing entity” may be an entity that authorizes a request. Examples of an authorizing entity may be an issuer, a governmental agency, a document repository, an access administrator, etc. An authorizing entity may operate an authorizing entity computer. An “issuer” may refer to a business entity (e.g., a bank) that issues and optionally maintains an account for a user. An issuer PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 may also issue payment credentials stored on a user device, such as a cellular telephone, smart card, tablet, or laptop to the consumer, or in some embodiments, a portable device. [0034] The term “verification” and its derivatives may refer to a process that utilizes information to determine whether an underlying subject is valid under a given set of circumstances. Verification may include any comparison of information to ensure some data or information is correct, valid, accurate, legitimate, and/or in good standing. [0035] A “processor” may include a device that processes something. In some embodiments, a processor can include any suitable data computation device or devices. A processor may comprise one or more microprocessors working together to accomplish a desired function. The processor may include a CPU comprising at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. The CPU may be a microprocessor such as AMD's Athlon, Duron and/or Opteron; IBM and/or Motorola's PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). [0036] A “memory” may be any suitable device or devices that can store electronic data. A suitable memory may comprise a non-transitory computer readable medium that stores instructions that can be executed by a processor to implement a desired method. Examples of memories may comprise one or more memory chips, disk drives, etc. Such memories may operate using any suitable electrical, optical, and/or magnetic mode of operation. [0037] A “server computer” may include a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The server computer may comprise one or more computational apparatuses and may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0038] Embodiments of the disclosure allow for remote payment authorization for autonomous vehicles. Embodiments provide for systems and methods in which a central computer can facilitate interactions (e.g., transactions) between an autonomous device and an access device. As an example, the central computer can receive, from the autonomous device, a resource request message for a resource provided by the access device in a transaction. The resource request message can include a location of the autonomous vehicle and a resource provider identifier. The central computer can validate the resource request message by comparing the location of the autonomous vehicle with a location of the access device. The central computer can then process the transaction using a token associated with a credential. The credential can be associated with the autonomous vehicle. Further details of such systems and methods will be discussed herein. [0039] FIG.1 shows a system 100 according to embodiments of the disclosure. The system 100 comprises a central computer 102, an autonomous vehicle 104, an access device 106, a resource provider computer 108, a transport computer 110, a network processing computer 112, an authorizing entity computer 114, a user device 116, a token service provider computer 118, databases 120, and a resource provider locator computer 122. [0040] The central computer 102 can be in operative communication with the autonomous vehicle 104, the resource provider computer 108, the network processing computer 112, the user device 116, the token service provider computer 118, the databases 120, and the resource provider locator computer 122. The autonomous vehicle 104 can be in operative communication with the central computer 102, the access device 106, and the user device 116. The access device 106 can be in operative communication with the resource provider computer 108, which can be in operative communication with the transport computer 110. The network processing computer 112 can be in operative communication with the transport computer 110 and the authorizing entity computer 114. [0041] For simplicity of illustration, a certain number of components are shown in FIG.1. It is understood, however, that embodiments of the invention may include more than one of each component. In addition, some embodiments of the invention may include fewer than or greater than all of the components shown in FIG.1. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0042] Messages between at least the devices included in the system 100 in FIG.1 can be transmitted using a communications protocols such as, but not limited to, Secure Hypertext Transfer Protocol (HTTPS), SSL, ISO (e.g., ISO 8583) and/or the like. The communications network may include any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. The communications network can use any suitable communications protocol to generate one or more secure communication channels. A communications channel may, in some instances, comprise a secure communication channel, which may be established in any known manner, such as through the use of mutual authentication and a session key, and establishment of a Secure Socket Layer (SSL) session. [0043] The central computer 102 can be a server computer. The central computer 102 can communicate with a plurality of other devices to coordinate interactions (e.g., transactions) where the autonomous vehicle 104 navigates to an access device 106 to access a resource. The central computer 102 can register (e.g., enroll) the autonomous vehicle with an autonomous vehicle interaction system. The central computer 102 can later facilitate transactions within the autonomous vehicle interaction system. [0044] The autonomous vehicle 104 can include a vehicle used for transporting people or goods that operates without direct human control. The autonomous vehicle 104 can be a car, a truck, a drone, a boat, or other vehicle capable of movement. The autonomous vehicle 104 can, without human control, navigate from a first location to a second location. For example, the autonomous vehicle 104 can navigate from its current location to an access device location. [0045] The access device 106 can include a device operated by a resource provider. The access device 106, for example, can include an electric charging station (e.g., an energy supply terminal). If the access device 106 is an electric charging station, the access device 106 can comprise a charging cable to supply electricity to electric vehicles. In this regard, in some embodiments, the access PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 device 106 can automatically supply a resource to a vehicle or user. The access device 106 can also communicate with another device (e.g., a user device 116, the autonomous vehicle 104, etc.) to perform an interaction (e.g., through a charging cable). During an interaction, the access device 106 can provide interaction data to the resource provider computer 108 for authorization of the interaction. In some embodiments, the access device 106 can generate an authorization request message comprising at least the interaction data. The access device 106 can provide the authorization request message to the resource provider computer 108. [0046] During an interaction, the access device 104 can provide interaction data to the resource provider computer 106 for authorization of the interaction. In some embodiments, the access device 104 can generate an authorization request message comprising at least the interaction data. The access device 104 can provide the authorization request message to the resource provider computer 106. [0047] The resource provider computer 108 can include any suitable computational apparatus operated by a resource provider (e.g., a merchant). In some embodiments, the resource provider computer 108 may include one or more server computers that may host one or more websites associated with the resource provider (e.g., a merchant). In some embodiments, the resource provider computer 108 may be configured to send data to a network processing computer 112 via a transport computer 110 as part of a payment verification and/or authentication process for a transaction between the user (e.g., consumer) and the resource provider. The resource provider computer 108 may also be configured to generate authorization request messages for transactions between a resource provider and a user, and route the authorization request messages to an authorizing entity computer 114 for transaction processing. [0048] The transport computer 110 can include a server computer. The transport computer 110 may be associated with an acquirer, which may be an entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Some embodiments may encompass such single entity issuer-acquirers. [0049] The network processing computer 112 can include a server computer. The network processing computer 112 may be disposed between the transport PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 computer 110 and the authorizing entity computer 114. The network processing computer 112 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. For example, the network processing computer 112 may comprise a server coupled to a network interface (e.g., by an external communication interface), and databases of information. The network processing computer 112 may be representative of a transaction processing network. An exemplary transaction processing network may include VisaNet™. Transaction processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services. The network processing computer 112 may use any suitable wired or wireless network, including the Internet. [0050] The authorizing entity computer 114 can include a server computer operated by an authorizing entity. The authorizing entity computer 114 may be associated with an authorizing entity, which may be an entity that authorizes a request. An example of an authorizing entity may be an issuer, which may typically refer to a business entity (e.g., a bank) that maintains an account for a user. An issuer may also issue and manage an account associated with a user device 116. [0051] The user device 116 can initiate interactions (e.g., transactions) with resource provider computers such as the resource provider computer 108. For example, the user device 116 can access a website hosted and/or operated by the resource provider computer 108 to select one or more items for the interaction. For example, the user of the user device 116 can navigate to the resource provider website using an Internet browser installed on the user device 116, select one or more items provided by the resource provider computer 108, and submit the interaction (e.g., checkout) for approval. [0052] The token service provider computer 118 can include a computer programmed to facilitate requesting, determining (e.g., generating) and/or issuing tokens, as well as maintaining an established mapping of tokens to credentials (e.g., primary account numbers) in a repository (e.g., token vault). The token service PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 provider computer 118 may include or be in communication with a token vault where the generated tokens are stored. The token service provider computer 118 may support token processing of interactions submitted using tokens by de-tokenizing the tokens to obtain the actual credentials. In some embodiments, a token service provider computer 118 may include a tokenization computer alone, or in combination with other computers such as the processing network computer 112. [0053] The databases 120 can include any suitable database. Each database may be a conventional, fault tolerant, relational, scalable, secure database such as those commercially available from Oracle™ or Sybase™. [0054] The databases 120 can include a plurality of databases. For example, the databases 120 can include a cryptographic key database, a token database, a device settings database, and an autonomous vehicle tasks database. [0055] The cryptographic key database can store cryptographic key pairs. The cryptographic key database can store cryptographic key pairs that are meant for provisioning to autonomous vehicles. [0056] The token database can store tokens. The token database can store tokens in association with credentials that are issued to users. The token database can return a token based on a received credential. The token database can return a credential based on a received token. [0057] The device settings database can store device settings set by user devices for autonomous vehicles. The device settings can include settings regarding to the interaction system and what permissions the autonomous vehicles might have. For example, the device settings can include an option that allows for autonomous vehicles to request charging and initiate transaction without authorization from the user of the user device. [0058] The autonomous vehicle tasks database can store autonomous vehicle tasks. An autonomous vehicle task can include a task that the autonomous vehicle is to perform. For example, an autonomous vehicle task can include a task to navigate from one location to another location. The autonomous vehicle task can include navigation information. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0059] The resource provider locator computer 122 can include a computer or a server computer. The resource provider locator computer 122 can identify locations of access devices of resource providers that are registered with the resource provider locator computer 122. The resource provider locator computer 122 can identify an access device location that is near to an autonomous vehicle location. [0060] FIG.2 shows a block diagram of a central computer 102 according to embodiments. The exemplary central computer 102 may comprise a processor 204. The processor 204 may be coupled to a memory 202, a network interface 206 and a computer readable medium 208. The computer readable medium 208 can comprise a geographical location evaluation module 208A, an autonomous vehicle task module 208B, an interaction processing module 208C, and a database module 208D. [0061] The memory 202 can be used to store data and code. For example, the memory 202 can store tokens, cryptographic keys, order identifiers, autonomous vehicle locations, resource provider locations, tasks, etc. The memory 202 may be coupled to the processor 204 internally or externally (e.g., cloud based data storage), and may comprise any combination of volatile and/or non-volatile memory, such as RAM, DRAM, ROM, flash, or any other suitable memory device. [0062] The computer readable medium 208 may comprise code, executable by the processor 204, for performing a method comprising: receiving, by a central computer from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier; after receiving the resource request message, validating, by the central computer, the resource request message by comparing the location of the autonomous vehicle with a location of the access device; and after validating the resource request message, processing, the transaction, using a token associated with a credential, the credential associated with the autonomous vehicle. [0063] The geographical location evaluation module 208A can comprise code or software, executable by the processor 204, for identifying and validating locations. The geographical location evaluation module 208A, in conjunction with the processor PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 204, can obtain two geographical locations from different sources and can compare the two geographical locations. The geographical location evaluation module 208A, in conjunction with the processor 204, can determine whether or not the two geographical locations match. [0064] For example, the geographical location evaluation module 208A, in conjunction with the processor 204, can obtain a first geographical location, which can be a location of an autonomous vehicle. The geographical location evaluation module 208A, in conjunction with the processor 204, can obtain a second geographical location, which can be a location of an access device. The first geographical location and the second geographical location can include location data such as latitude, longitude, altitude, street address, zip code, city name, and/or any other data that can identify a position. [0065] The geographical location evaluation module 208A, in conjunction with the processor 204, can compare the first geographical location to the second geographical location. In some embodiments, the geographical location evaluation module 208A, in conjunction with the processor 204, can determine a distance (e.g., < 0.1 miles, 5 miles, etc.) between the first geographical location and the second geographical location. The geographical location evaluation module 208A, in conjunction with the processor 204, can determine that the first geographical location and the second geographical location match if the distance is less than a distance threshold. The distance threshold can be a predetermined or dynamic threshold that indicates a maximum amount that the two geographical locations may be from one another and still be considered to match. [0066] The autonomous vehicle task module 208B may comprise code or software, executable by the processor 204, for processing autonomous vehicle tasks. The autonomous vehicle task module 208B, in conjunction with the processor 204, can generate autonomous vehicle tasks for an autonomous vehicle. [0067] The autonomous vehicle task module 208B, in conjunction with the processor 204, can generate autonomous vehicle tasks that relate to navigation. The autonomous vehicle tasks can include tasks to navigate from one location to another location and can include navigation information. The autonomous vehicle task module 208B, in conjunction with the processor 204, can generate the PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 autonomous vehicle tasks based on determining a route from the first geographical location to the second geographical location. The autonomous vehicle task module 208B, in conjunction with the processor 204, can generate the route in any suitable manner. As an example, the autonomous vehicle task module 208B, in conjunction with the processor 204, can access a dataset that includes road segments with distances, intersections, and speed limits. The road segments and intersections can be structured as a graph of edges and vertices. The autonomous vehicle task module 208B, in conjunction with the processor 204, can determine an optimal route based on distance, speed, cost, or other suitable metric by determine a path using the graph data. [0068] The interaction processing module 208C may comprise code or software, executable by the processor 204, for processing interactions. The interaction processing module 208C, in conjunction with the processor 204, can obtain access data (e.g., a token or an order identifier) for an interaction (e.g., a transaction) and can process it. [0069] The database module 208D comprise code or software, executable by the processor 204, for communicating with databases to obtain data and store data. The database module 208D, in conjunction with the processor 204, can communicate with a cryptographic key database, a token database, a device settings database, and an autonomous vehicle tasks database. The database module 208D, in conjunction with the processor 204, can obtain data and store data into any of the aforementioned databases. [0070] The network interface 206 may include an interface that can allow the central computer 102 to communicate with external computers. The network interface 206 may enable the central computer 102 to communicate data to and from another device (e.g., the autonomous vehicle 104, the resource provider computer 108, the network processing computer 112, the user device 116, the token service provider computer 118, the databases 120, the resource provider locator computer 122, etc.). Some examples of the network interface 206 may include a modem, a physical network interface (such as an Ethernet card or other Network Interface Card (NIC)), a virtual network interface, a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, or the like. The PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 wireless protocols enabled by the network interface 206 may include Wi-Fi^TM. Data transferred via the network interface 206 may be in the form of signals which may be electrical, electromagnetic, optical, or any other signal capable of being received by the external communications interface (collectively referred to as “electronic signals” or “electronic messages”). These electronic messages that may comprise data or instructions may be provided between the network interface 206 and other devices via a communications path or channel. As noted above, any suitable communication path or channel may be used such as, for instance, a wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, a WAN or LAN network, the Internet, or any other suitable medium. [0071] FIG.3 shows a block diagram of an autonomous vehicle 104 according to embodiments. The exemplary autonomous vehicle 104 may comprise an in- vehicle computing system 300 comprising a processor 304. The processor 304 may be coupled to a memory 302, a computer readable medium 308, and a user interface 320. The computer readable medium 308 can comprise a geographical location module 308A, an access module 308B, and a navigation application 308C. The autonomous vehicle 104 can also include a wireless communication subsystem 306, a positioning satellite receiver 322, an engine/motor control unit 310, a transmission control unit 312, a battery system 314, a charge interface 316, and sensors 318. [0072] The autonomous vehicle 104 can be, for example, an electric vehicle. Although the autonomous vehicle 104 may be described as an automobile, it should be understood that in some embodiments, the techniques described herein can also be applied to other types of vehicles such as motorcycles, boats, aircrafts, or other types of powered machines that are used to transport from one location to another. [0073] The autonomous vehicle 104 may include the in-vehicle computing system 300 with which a user of the autonomous vehicle 104 can interact. The in- vehicle computing system 300 can be an infosystem, infotainment system, or other instrumentation system. The in-vehicle computing system 300 can be mounted in the center console, dashboard, rear console, or other locations in the autonomous vehicle 104 that is convenient for a user to access the in-vehicle computing system 300. In some embodiments, the in-vehicle computing system 300 can be coupled to PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 a vehicle communication bus to receive vehicle status information from electronic control units (ECUs) and the sensors 318. [0074] The user interface 320 may include an input interface such as any number of buttons, knobs, microphone and/or a touchscreen that can receive user input, and an output interface such as a display (may be part of a touchscreen) and/or speakers. The display of the user interface 320 can be integrated with the housing of the in-vehicle computing system 300, or can be a separate component coupled to the in-vehicle computing system 300 but mounted at a different location than the in-vehicle computing system 300. For example, the display of the user interface 320 can be mounted on the surface of the center console, on the dashboard, on the surface of the rear console, behind the headrest, on the interior ceiling, on the visor, or other suitable location in vehicle, and may display various types of information including information such as vehicle status information (e.g., speed, fuel economy, engine temperature, etc.), environmental information (e.g., inside/outside temperature, weather, etc.), navigation information (e.g., maps, routes, places of interests, etc.), entertainment such as videos or titles of audio selections or radio stations, energy level information (e.g., amount of charge present and needed to fill to capacity, amount of gas present and needed to fill to capacity), transaction information, energy terminal information, etc. [0075] The memory 302 can be used to store data and code and may be similar to the memory 202 as described herein. For example, the memory 302 can store tasks, order identifiers, cryptographic keys, etc. [0076] The computer readable medium 308 may comprise code, executable by the processor 304, for performing a method comprising: providing, by an autonomous vehicle to a central computer, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier, wherein after receiving the resource request message, the central computer validates the resource request message by comparing the location of the autonomous vehicle with a location of the access device; receiving, by the autonomous vehicle from the central computer, a resource response message comprising access data; providing, by the autonomous vehicle to the access device, PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 the access data; and receiving, by the autonomous vehicle from the access device, the resource. [0077] The geographical location module 308A can comprise code or software, executable by the processor 304, for obtaining and processing location information. The geographical location module 308A, in conjunction with the processor 304, can obtain a current location of the autonomous vehicle 104. The current location of the autonomous vehicle 104 can be a GPS location, a street address, etc. The geographical location module 308A, in conjunction with the processor 304, can obtain the current location using a global positioning satellite system or other suitable means of obtaining a location. [0078] The access module 308B may comprise code or software, executable by the processor 204, for communicating with and using access devices. The access module 308B, in conjunction with the processor 304, can communicate with the access device to obtain a resource provider identifier of a resource provider computer associated with the access device. The access module 308B, in conjunction with the processor 304, can receive the resource provider identifier via a wired connection or a wireless connection. [0079] For example, in some embodiments, the resource provider identifier can be embedded into a QR code that is on a physical surface of the access device. The access module 308B, in conjunction with the processor 304, can capture an image that includes the QR code using a camera of the autonomous vehicle 104. The autonomous vehicle 104 can obtain the resource provider identifier from the QR code. [0080] In some embodiments, the access module 308B, in conjunction with the processor 304, can communicate with the access device using a Bluetooth™ communication channel. The access module 308B, in conjunction with the processor 304, can receive the resource provider identifier form the access device 106 via a Bluetooth™ connection. [0081] In other embodiments, the access module 308B, in conjunction with the processor 304, can obtain the resource provider identifier from a physical connection made with the access device 106. For example, when the access module 308B, in PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 conjunction with the processor 304, can connect to the access device using a data transmission cable. The data transmission cable can transmit data between the autonomous vehicle 104 and the access device according to the International Organization for Standardization (ISO) 15118. [0082] The navigation application 308C can be part of a positioning or navigation subsystem of the autonomous vehicle 104, and may provide navigation functionalities such as mapping and routing functions. A user of the autonomous vehicle 104 may input a desired location into the in-vehicle computing system 300, and the navigation application 308C can determine a current location of the autonomous vehicle 104 using the positioning satellite receiver 322, and provide directions to travel to the desired location. In some embodiments, the navigation application 308C may display a map on the user interface 320 and highlight a route to a desired destination. In other embodiments, the navigation application 308C, in conjunction with the processor 304, can communicate provide navigation instructions to the in-vehicle computing system 300 to proceed to a destination. [0083] The autonomous vehicle 104 may include various electronic control units (ECUs) to operate and control the electrical system or other subsystems of the autonomous vehicle 104, and may include the sensors 318 that the ECUs can monitor. Each ECU may include a microcontroller and one or more memories (e.g., any combination of SRAM, EEPROM, Flash memories, etc.) to store one or more executable programs for the ECU. Examples of ECUs may include the engine / motor control unit 310, the transmission control unit 312, etc. In some embodiments, autonomous vehicle 104 may include additional ECU(s) not specifically shown, omit one or more ECUs, and/or integrate any of the functionalities of different ECUs into a single ECU. [0084] The autonomous vehicle 104 can also include a battery system 314 comprising one or more batteries and a charge interface 316 for charging the one or more batteries. The battery system 314 and the charge interface 316 can be in communication with and coupled to the in-vehicle computing system 300 and its processor 304. [0085] The engine / motor control unit 310 may control the actuators, valves, motor, and/or other components of the engine of the autonomous vehicle 104, or an PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 electric motor of the autonomous vehicle 104. The transmission control unit 312 may control the gear shifting and the transmission modes (e.g., park, drive, neutral, reverse) of the autonomous vehicle 104. The battery system 314 may include electronics that can control the electrical voltage and current supplied by its one or more batteries to the various components of the autonomous vehicle 104. The sensors 318 may include vehicle speed sensors (e.g., wheel sensors) to detect the speed of the autonomous vehicle 104, temperature sensors to detect the operating temperature of the vehicle’s various components, air sensors to detect oxygen level in the engine, sensors to detect the amount of energy currently (e.g., electricity, gas, etc.) present with the vehicle or the available capacity of any energy storage devices such batteries, cameras to observe the surroundings of the autonomous vehicle 104, etc. The various ECUs, devices, and sensors may communicate with one another via a vehicle communication bus. Examples of the vehicle communication bus may include a controller area network (CAN) bus, a local interconnect network (LIN) bus, a vehicle area network (VAN) bus, or other suitable signal buses for vehicle communication. [0086] The autonomous vehicle 104 may also include various radio frequency (RF) transceivers to allow the autonomous vehicle 104 to receive and transmit RF signals with other devices. For example, the autonomous vehicle 104 may include the positioning satellite receiver 322 such as a GPS receiver to receive satellite signals that can be demodulated and decoded to determine the location of the autonomous vehicle 104. The positioning satellite receiver 322 can be used by a positioning or navigation subsystem of the autonomous vehicle 104 to perform routing and mapping functions. [0087] The autonomous vehicle 104 may also include a wireless communication subsystem 306 to enable network connectivity for the autonomous vehicle 104. The wireless communication subsystem 306 may include one or more wireless transceivers that use WiFi, WiMax, or other types of wireless network communication protocols to connect the autonomous vehicle 104 to an external network (e.g., the Internet) such that the autonomous vehicle 104 can communicate with remote servers. The wireless communication subsystem 306 may also include one or more short or near range wireless transceivers such as RFID, Bluetooth™ or PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 Bluetooth™ Low Energy, NFC, beacon, infrared transmitters and/or receivers that can be used to communicate with an access device in proximity to the autonomous vehicle 104. [0088] Embodiments can use the systems and apparatuses described herein to at least perform authenticated interactions for autonomous vehicles. FIGs.4-6 describe some examples of such methods. [0089] FIG.4 shows a flow diagram illustrating an overview of a remote interaction authorization for autonomous vehicles method according to embodiments. The method illustrated in FIG.4 describes an overview of the remote interaction authorization method. The method is further described in detail in FIGs. 5-6. [0090] The method illustrated in FIG.4 will be described in the context of an autonomous vehicle 104 that is a self-driving car that is electrically charged. The autonomous vehicle 104 can communicate with a central computer 102 to determine an access device 106 that is a charging station. The autonomous vehicle 104 can navigate to the access device 106 to charge a battery in the autonomous vehicle 104. The central computer 102 can facilitate in the interaction between the autonomous vehicle 104 and the access device 106 and may process the interaction. The interaction can be a transaction between a user of the autonomous vehicle 104 and a resource provider of the access device 106. [0091] It is understood, however, that the invention can be applied to other circumstances. For example, the interaction can be an interaction in which the autonomous vehicle is attempting to park in a paid parking spot and is to transact with an access device to access the parking spot. As another example, the interaction can include a situation where the autonomous vehicle is attempting to drive down a toll road and is to transact with an access device that is a toll both to continue down the road. [0092] At step 402, the central computer 102 can receive a resource request from the autonomous vehicle 104. The resource request can be a request for a resource provided by the access device 106 in a transaction. The resource request can comprise a location of the autonomous vehicle 104 and a resource provider PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 identifier. In some embodiments, the resource request can include a autonomous vehicle identifier. [0093] The location of the autonomous vehicle 104 can be a global positioning system (GPS) location (e.g., latitude and longitude), a street address, and/or any suitable data that identifies a position. [0094] The resource provider identifier can include an identifier that identifies the resource provider. The resource provider identifier can be an alphanumeric value that can be unique to a particular resource provider. The resource provider identifier can identify the resource provider that is associated with the access device 106 and the resource provider computer 108. In some embodiments, the resource provider identifier can be a resource provider public key or other secure data element. [0095] At step 404, after receiving the resource request, the central computer 102 can validate the resource request. For example, the central computer 102 can communicate with the resource provider location computer 122 to determine a location of the access device 106 using the resource provider identifier. The resource provider location computer 122 can identify the location of the access device 106 using a data table, or other suitable data, that associates the resource provider identifier with the location of the access device 106. [0096] Upon determining the location of the access device 106, the central computer 102 can validate that the location of the autonomous vehicle 104 matches the location of the access device 106. If the locations do not match, then the central computer 102 can deny the resource request. If the locations match, then the central computer 102 can proceed to step 406. [0097] At step 406, after validating the resource request, the central computer 102 can process the interaction (e.g., the transaction). The central computer 102 can process the transaction using a token associated with a credential, where the credential is associated with the autonomous vehicle 104. The central computer 102 can identify a credential associated with the autonomous vehicle 104 (e.g., associated with an autonomous vehicle identifier). PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0098] In some embodiments, the central computer 102 can store the token in association with the credential and/or the autonomous vehicle identifier. The central computer 102 can retrieve the token using the credential and/or the autonomous vehicle identifier. [0099] In other embodiments, the central computer 102 can communicate with a token service provider computer 118 to obtain a token using the credential. For example, the central computer 102 can generate a token request message comprising the credential. The central computer 102 can provide the token request message to the token service provider computer 118. The token service provider computer 118 can identify the token using the credential and generate a token response message comprising the token. The token service provider computer 118 can provide the token response message to the central computer 102. [0100] The central computer 102 can initiate processing of the transaction using the token. In some embodiments, the central computer 102 can provide the token to the autonomous vehicle 104, where the autonomous vehicle 104 provides the token the access device 106 for processing. In other embodiments, the central computer 102 can provide the token to the resource provider computer 108 for processing. Processing of the transaction will be further described in reference to FIGs.5-6. [0101] FIG.5 shows a flow diagram illustrating a first remote interaction authorization for autonomous vehicles method according to embodiments. The method illustrated in FIG.5 will be described in the context of an autonomous vehicle 104 that is a self driving electric car that navigates to an access device 106, which is a electric car charging station. The autonomous vehicle 104 can receive a resource provider identifier from the access device 104 and can then communicate with a central computer 102 to process a transaction to obtain a resource (e.g., electric charge) from the access device 104. Upon verification, the central computer 102 can provide a token to the autonomous vehicle 104 for the transaction. It is understood, however, that the invention can be applied to other circumstances. [0102] At step 1, a user of a user device 116 can register the autonomous vehicle 104, which is owned and/or operated by the user, with the central computer 102. The user device 116 can register the autonomous vehicle in an autonomous PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 vehicle interaction system. The user device 116 can generate a registration request message comprising a user device identifier and an autonomous vehicle identifier. The registration request message can also include user identifying data such as a credential (e.g., a primary account number, a user identifier, a token, etc.). The user device 116 can provide the registration request message to the central computer 102. [0103] At step 2, after receiving the registration request message, the central computer 102 can obtain a public/private cryptographic key pair to provision to the autonomous device 104. The central computer 102 can obtain and/or generate the public/private cryptographic key pair in any suitable manner. For example, the central computer 102 request a cryptographic key pair from a cryptographic key database of the databases 120 that stores a plurality of cryptographic key pairs. [0104] The central computer 102 can generate a cryptographic key pair request message. The central computer 102 can provide the cryptographic key pair request message to the cryptographic key database of the databases 120 (e.g., query the cryptographic key database of the databases 120). [0105] After receiving the cryptographic key pair request message, the cryptographic key database of the databases 120 can retrieve a cryptographic key pair from memory. The cryptographic key database of the databases 120 can generate and provide a cryptographic key pair response message comprising the cryptographic key pair to the central computer 102. [0106] At step 3, after receiving the cryptographic key pair response message, the central computer 102 can provision the cryptographic key pair to the user device 116. [0107] At step 4, after receiving the cryptographic key pair from the central computer 102, the user device 116 can provide the cryptographic key pair to the autonomous vehicle 104. The user device 116 can provide the cryptographic key pair to the autonomous vehicle 104 over any suitable communication channel (e.g., via Bluetooth, via a wired connection, via an autonomous vehicle application installed on the user device 116, etc.). PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0108] After receiving the cryptographic key pair, which can comprise an autonomous vehicle public key and an autonomous vehicle private key, the autonomous vehicle 104 is enrolled in the autonomous vehicle interaction system. [0109] At step 5, at a later point in time, the autonomous vehicle 104 can be located at a location of the access device 106 to receive a resource from the access device 106. The autonomous vehicle 104 may be occupied or unoccupied. The access device 106 can provide the autonomous device 104 with a resource provider identifier. The resource provider identifier can identify a resource provider computer 108 associated with the access device 106. [0110] The autonomous vehicle 104 can obtain the resource provider identifier in any suitable manner. The autonomous vehicle 104 can receive the resource provider identifier via a wired connection or a wireless connection. For example, in some embodiments, the resource provider identifier can be embedded into a QR code that is on a surface of the access device. The autonomous vehicle 104 can capture an image that includes the QR code. The autonomous vehicle 104 can obtain the resource provider identifier from the QR code. [0111] In some embodiments, the autonomous vehicle 104 can receive the resource provider identifier form the access device 106 via a Bluetooth™ connection. [0112] In other embodiments, the autonomous vehicle 104 can obtain the resource provider identifier from a physical connection made with the access device 106. For example, when the autonomous vehicle 104 arrives next to the access device 106, the access device 106 can extend a cable that can plug into the autonomous vehicle 104. The cable can be capable of both transferring data between the autonomous vehicle 104 and the access device 106 as well as charging a battery of the autonomous vehicle 104. The access device 106 can provide the resource provider identifier via the cable to the autonomous vehicle 104. In some embodiments, communication between the access device 106 and the autonomous vehicle 104 can be made according to the International Organization for Standardization (ISO) 15118. [0113] At step 6, after receiving the resource provider identifier, the autonomous vehicle 104 can communicate with the central computer 102 to initiate PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 and perform an interaction to charge the battery of the autonomous vehicle using the resource provider identifier. The autonomous vehicle 104 can generate a resource request message comprising the resource provider identifier and a location of the autonomous vehicle 104. The location of the autonomous vehicle can be a current geographical location of the autonomous vehicle 104 (e.g., a GPS location). The resource request message can also include the autonomous vehicle identifier. [0114] In some embodiments, the autonomous vehicle 104 can digitally sign the resource request message using the autonomous vehicle private key, which was received during step 4. [0115] At step 7, after receiving the resource request message from the autonomous vehicle 104, the central computer 102 can validate the digital signature of the resource request message using the autonomous vehicle public key. If the digital signature is not valid, then the central computer 102 can terminate the process. If the digital signature is valid, then the central computer 102 can generate a location verification request message comprising the resource provider identifier and the location of the autonomous vehicle 104. [0116] The central computer 102 can provide the location verification request message to the resource provider locator computer 122. The resource provider locator computer 122 can include a database of resource provider identifiers and associated locations. Each resource provider identifier can correspond to a location. The resource provider identifiers and the corresponding locations can be obtained from resource providers that enroll in the autonomous vehicle interaction system. The resource provider locator computer 122 can search the database for the received resource provider identifier. [0117] If no stored resource provider identifier matches the received resource provider identifier, then the resource provider locator computer 122 can generate a location verification response message that indicates that no matching resource provider identifier could be found. [0118] If the resource provider locator computer 122 finds a stored resource provider identifier that matches the received resource provider identifier, then the resource provider locator computer 122 can compare the received location to the PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 stored location that is stored in association with the stored resource provider identifier. Comparing the received location and the stored location can indicate whether or not the autonomous vehicle 104 is at the correct geographic location for the access device 106. [0119] If the stored location does not match the received location, then the resource provider locator computer 122 can generate a location verification response message that indicates that the locations do not match. [0120] If the stored location matches the received location, then the resource provider locator computer 122 can generate a location verification response message that indicates that the locations match. [0121] At step 8, the resource provider locator computer 122 can provide the location verification response message to the central computer 102 in response to the location verification request message. [0122] At step 9, if the location verification response message indicates no matches, then the central computer 102 can terminate the process. If the location verification response message indicates that the locations match, then the central computer 102 can proceed with processing the interaction. [0123] In some embodiments, during step 9, the central computer 102 can request authorization of the interaction from the user device 116. For example, the central computer 102 can generate a user authorization request message comprising the resource provider identifier and/or the location of the access device 106 and the autonomous vehicle identifier. The central computer 102 can provide the user authorization request message to the user device 116. [0124] After receiving the user authorization request message, the user device 116 can present the user authorization request message to the user of the user device 116. The user can decide to authorize the interaction or to decline the interaction. In some embodiments, the user authorization request message can include a request for a password, a one-time password, or other information known by the user of the user device 116 and the central computer 102. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0125] The user device 116 can generate a user authorization response message comprising the user’s selection. The user device 116 can provide the user authorization response message to the central computer 102. [0126] After receiving the user authorization response message from the user device 116, the central computer 102 can terminate the process if the user authorization response message indicates to decline the interaction. [0127] At step 10, the central computer 102 can generate a token request message comprising the user identifying data (e.g., a credential), which was stored in association with the autonomous device identifier during enrollment. The central computer 102 can provide the token request message to a network processing computer 112. [0128] The network processing computer 112 can obtain a token that corresponds to the credential in the token request message. For example, the network processing computer 112 can provide the token request message to a token service provider computer (not shown). The token service provider computer can maintain a database that stores a plurality of credentials and a plurality of tokens. Each credential is stored in relation to a token. The token service provider computer can obtain a token that is stored in association with a stored credential that matches the received credential. [0129] The token service provider computer can generate a token response message comprising the token. The token service provider computer can provide the token response message to the network processing computer 112. The network processing computer 112 can provide the token response message to the central computer 102 in response to the token request message. [0130] At step 11, after receiving the token, the central computer 102 can generate a resource response message comprising access data (e.g., the token). The central computer 102 can provide the resource response message to the autonomous vehicle 104 in response to the resource request message (received at step 6). In some embodiments, the central computer 102 can encrypt the token using the autonomous vehicle public key. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0131] At step 12, the autonomous vehicle 104 can provide the token to the access device 106. In some embodiments, if the token is encrypted using the autonomous vehicle public key, then the autonomous vehicle 104 can decrypt the token using the autonomous vehicle private key. [0132] At step 13, after receiving the token from the autonomous vehicle 104, the access device 106 can provide the token to the resource provider computer 108 that is associated with the access device 106. For example, the resource provider computer 108 can be a merchant computer that manages transactions for one or more access devices (e.g., charging stations). [0133] At step 14, after receiving the token from the access device 106, the resource provider computer 108 can generate an authorization request message comprising the token. In some embodiments, the authorization request message can include an amount (e.g., $40) for the interaction. In other embodiments, the amount may be unknown until after the autonomous vehicle finishes charging. In such a case, the amount can later be included in a settlement and/or clearance process as known to one of skill in the art. In some embodiments, the authorization request message can include additional data relating to the interaction (e.g., a time, a date, a location, a resource provider computer identifier, etc.). In some embodiments, the authorization request message can be an ISO 8583 – 0100 authorization request message. [0134] The resource provider computer 108 can provide the authorization request message to a transport computer 110. [0135] At step 15, after receiving the authorization request message from the resource provider computer 108, the transport computer 110 can provide the authorization request message to the network processing computer 112. [0136] At step 16, after receiving the authorization request message, the network processing computer 112 can modify the authorization request message to include the credential that is associated with the token. For example, the network processing computer 112 can generate a credential request message comprising the token. The network processing computer 112 can provide the credential request message to the token service provider computer (not shown). The token service PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 provider computer can identify the credential that corresponds to the token. The token service provider computer can generate a credential response message comprising the credential. The token service provider computer can provide the credential response message to the network processing computer 112. The network processing computer 112 can modify the authorization request message to include the credential by inserting the credential into the authorization request message or by replacing the token with the credential. [0137] The network processing computer 112 can provide the authorization request message to the authorizing entity computer 114 for authorization of the interaction. [0138] After receiving the authorization request message, the authorizing entity computer 114 can determine whether or not to authorize the interaction. The authorizing entity computer 114 can determine whether or not to authorize the interaction based on an account of the user maintained by the authorizing entity computer 114 The authorizing entity computer 114 can generate an authorization response message comprising an indication of whether or not the interaction is authorized. The authorization response message can also comprise the credential and the interaction data. [0139] At step 17, the authorizing entity computer 114 can provide the authorization response message to the network processing computer 112. [0140] After receiving the authorization response message, the network processing computer 112 can modify the authorization response message to remove the credential. For example, the network processing computer 112 can generate a token request message comprising the credential. The network processing computer 112 can provide the token request message to a token service provider computer (not shown). The token service provider computer can obtain a token that is stored in association with a stored credential that matches the received credential. The token service provider computer can generate a token response message comprising the token. The token service provider computer can provide the token response message to the network processing computer 112. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0141] At step 18, after modifying the authorization response message to include the token rather than the credential, the network processing computer 112 can provide the authorization response message to the transport computer 110. [0142] At step 19, the transport computer 110 can provide the authorization response message to the resource provider computer 108. [0143] At step 20, after receiving the authorization response message from the transport computer 110, the resource provider computer 108 can indicate to the access device 106 that the resource (e.g., the electric charge) can be provided to the autonomous vehicle 104. [0144] At step 21, the access device 106 can begin charging the autonomous vehicle 104 over the cable or via any suitable charging means. The charging can stop once the cost of the charging reaches a predetermined amount or once the battery gets filled to a certain level (e.g., full). [0145] In some embodiments, after charging is complete, the access device 106 can indicate to the autonomous vehicle 104 that charging is complete and that it is safe to drive away. [0146] At the end of the day or any other suitable period of time, a clearing and settlement process for the transaction can be conducted between the entities (e.g., an acquirer) that operate the transport computer 110, the network processing computer 112, and the authorizing entity computer 114. [0147] FIG.6 shows a flow diagram illustrating a second remote interaction authorization for autonomous vehicles method according to embodiments. The method illustrated in FIG.6 will be described in the context of an autonomous vehicle 104 that is a self driving electric car that requests navigation instructions to an access device 106, which is a electric car charging station. The autonomous vehicle 104 can receive a resource provider identifier from the access device 104 and can then communicate with a central computer 102 to process a transaction to obtain a resource (e.g., electric charge) from the access device 104. Upon verification, the central computer 102 can provide a token to a resource provider computer 108 associated with the access device 104 for the transaction. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0148] At step 1, a user of a user device 116 can register the autonomous vehicle 104, which is owned and/or operated by the user, with the central computer 102. The user device 116 can register the autonomous vehicle in an autonomous vehicle interaction system. The user device 116 can generate a registration request message comprising a user device identifier and an autonomous vehicle identifier. The registration request message can also include user identifying data such as a credential (e.g., a primary account number, a user identifier, a token, etc.). The user device 116 can provide the registration request message to the central computer 102. [0149] At step 2, after receiving the registration request message, the central computer 102 can obtain a token from the token service provider computer 118 using the user identifying data (e.g., the credential). For example, the central computer 102 can generate a token request message comprising the token. The central computer 102 can provide the token request message to the token service provider computer 118. The token service provider computer 118 can identify a token that is stored in association with the credential in a token database maintained by the token service provider computer 118. The token service provider computer 118 can generate a token response message comprising the token. The token service provider computer 118 can provide the token to the central computer 102. [0150] At step 3, after receiving the token from the token service provider computer 118, the central computer 102 can store the token in a token database of the databases 120. In some embodiments, the central computer 102 can store user device settings into a device settings database of the databases 120. The device settings can be selected by the user device 116. For example, one setting can indicate that the autonomous vehicle 104 is authorized to request charging. [0151] In some embodiments, the central computer 102 can generate a registration response message that indicates that the user device 116 was successfully registered and enrolled in the autonomous vehicle interaction system. The central computer 102 can provide the registration response message to the user device 116. [0152] At a later point in time, at step 4, the autonomous vehicle 104 can generate a charging request message that indicates that the autonomous vehicle PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 104 needs to charge at an access device. The charging request message can include a current location of the autonomous vehicle 104 (e.g., a GPS location). The charging request message can also include the autonomous vehicle identifier. The autonomous vehicle can provide the charging request message to the central computer 102. [0153] At step 5, after receiving the charging request message, the central computer 102 can validate the charging request message. For example, the central computer 102 can communicate with the user device settings database of the databases 120 to verify that the setting indicate that the autonomous vehicle 104 is authorized to request charging. If the autonomous vehicle 104 is authorized to request charging, then the central computer 102 can proceed to step 6. If the autonomous vehicle 104 is not authorized to request charging, then the central computer 102 can terminate the process. [0154] In some embodiments, at step 6, the central computer 102 can communicate with the user device 116 to obtain user authorization of the autonomous vehicle 104 proceeding to a charging station and interacting to obtain a charge. For example, the central computer 102 can generate a user authorization request message requesting authorization from a user of the user device 116. The central computer 102 can provide the user authorization request message to the user device 116. [0155] Upon receiving the user authorization request message, the user device 116 can present the user authorization request message to the user of the user device 116. The user can select whether or not the user authorizes the autonomous vehicle 104 to proceed to an access device and perform an interaction. The user device 116 can generate a user authorization response message comprising the user’s selection. The user device 116 can provide the user authorization response message to the central computer 102. [0156] After receiving the user authorization response message, the central computer 102 can evaluate the user’s selection. If the user’s selection indicates that the autonomous vehicle is not authorized to proceed to an access device and perform an interaction, then the central computer 102 can terminate the process. If the user’s selection indicates that the autonomous vehicle is authorized to proceed PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 to an access device and perform an interaction, then the central computer 102 can proceed to step 7. [0157] At step 7, the central computer 102 can communicate with the resource provider locator computer 122 to identify the access device 106 with which the autonomous vehicle 104 can interact. For example, the central computer 102 can generate an access device location request message comprising the current location of the autonomous vehicle 104. The central computer 102 can provide the access device location request message to the resource provider locator computer 122. [0158] After receiving the access device location request message, the resource provider locator computer 122 can search for access devices that are registered with the resource provider locator computer 122 that have a location within a distance (1 mile, 2 miles, 10 miles, etc.) of the current location of the autonomous vehicle 104. The resource provider locator computer 122 can identify the access device 106 and the location of the access device 106 as being within the distance of the autonomous vehicle 104. The resource provider locator computer 122 can also obtain a resource provider identifier that is stored in association with the access device location. [0159] The resource provider locator computer 122 can generate an access device location response message comprising the location of the access device 106 and the resource provider identifier. The resource provider locator computer 122 can provide the access device location response message to the central computer 102. [0160] After receiving the access device location response message, the central computer 102 can generate an autonomous vehicle task. The autonomous vehicle task can include navigation information to proceed from the current location of the autonomous vehicle 104 to the location of the access device 106. The autonomous vehicle task can include navigation information that includes the most energy efficient route, the fastest route, the cheapest route, etc. The navigation information can be determined using any suitable navigation routing process. [0161] The navigation information can include a plurality of navigation steps. For example, the navigation information can include a first step of continuing to drive PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 down a first road to a first intersection. A second step can be to take a right turn at the first intersection onto a second road. A third step can be to continue straight down the second road for two miles. A fourth step can be to pull over to a parking spot next to an access device on the side of the second road. [0162] At step 8, after generating the autonomous vehicle task, the central computer 102 can store the autonomous vehicle task in an autonomous vehicle tasks database of the databases 120. The central computer 102 can store the autonomous vehicle task, the autonomous vehicle identifier, and the resource provider identifier into the autonomous vehicle tasks database. [0163] At step 9, the central computer 102 can provide the autonomous vehicle task to the autonomous vehicle 104. The autonomous vehicle 104 can execute the autonomous vehicle task. For example, the autonomous vehicle 104 can drive to the location of the access device 106 as indicated in the navigation information included in the autonomous vehicle task. [0164] At step 10, after the autonomous vehicle 104 navigates to the location of the access device 106, the autonomous vehicle 104 can obtain a resource provider identifier from the access device 106. The autonomous vehicle 104 can obtain the resource provider identifier in any suitable manner described herein. [0165] At step 11, after receiving the resource provider identifier from the access device 106, the autonomous vehicle 104 can generate a resource request message comprising the resource provider identifier. The resource request message can also include a current location of the autonomous vehicle 104. The autonomous vehicle 104 can provide the resource request message to the central computer 102. [0166] At step 12, after receiving the resource request message, the central computer 102 can validate the resource provider identifier of the resource request message. For example, the central computer 102 can communicate with the autonomous vehicle tasks database of the databases 120 to validate the resource provider identifier. [0167] The central computer 102 can generate a validate task request message comprising the resource provider identifier and the autonomous vehicle PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 identifier. The central computer 102 can provide the validate task request message to the autonomous vehicle tasks database of the databases 120. [0168] The autonomous vehicle tasks database can identify a most recent task for the autonomous vehicle 104 using the autonomous vehicle identifier. The autonomous vehicle tasks database can then compare the received resource provider identifier with the resource provider identifier included in the autonomous vehicle task. The autonomous vehicle tasks database can generate a validate task response message comprising an indication of whether or not the received resource provider identifier and the resource provider identifier included in the autonomous vehicle task match. The autonomous vehicle tasks database can provide the validate task response message to the central computer 102. [0169] Upon receiving the validate task response message, if the validate task response message indicates that the resource provider identifiers do not match, then the central computer 102 can terminate the process. If the validate task response message indicates that the resource provider identifiers match, then the central computer 102 can proceed to step 13. [0170] At step 13, the central computer 102 can generate an order identifier (e.g., a unique numeric value) for the interaction. The central computer 102 can store the order identifier in the autonomous vehicle tasks database of the databases 120 in association with the current autonomous vehicle task (e.g., the task for the autonomous vehicle 104 to proceed to the access device location). [0171] At step 14, after generating the order identifier, the central computer 102 can generate a resource response message. The resource response message can include access data. The access data can include the order identifier. The central computer 102 can provide the resource response message to the autonomous vehicle 104. [0172] At step 15, after receiving the order identifier, the autonomous vehicle 104 can provide the order identifier to the access device 106. For example, in some embodiments, the autonomous vehicle 104 and the access device 106 can communicate using a Bluetooth™ communication channel. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0173] At step 16, the access device 106 can provide the order identifier to the resource provider computer 108 for processing. [0174] At step 17, after receiving the order identifier from the access device 106, the resource provider computer 108 can accept the interaction associated with the order identifier by providing the order identifier to the central computer 102. The order identifier can be provided to the central computer 102 in an interaction acceptance message. The interaction acceptance message can also include the resource provider identifier. [0175] At step 18, after receiving the order identifier from the resource provider computer 108, the central computer 102 can validate the order identifier. For example, the central computer 102 can communicate with the autonomous vehicle tasks database of the databases 120 to validate the order identifier and the resource provider identifier. [0176] For example, the central computer 102 can provide the order identifier and the resource provider identifier to the autonomous vehicle tasks database. The autonomous vehicle tasks database can search through stored autonomous vehicle tasks for an autonomous vehicle task that includes both the order identifier and the resource provider identifier. If there exists an autonomous vehicle task that includes both the order identifier and the resource provider identifier, then the autonomous vehicle tasks database can provide a response message, to the central computer 102, comprising an indication that the order identifier and the resource provider identifier are valid along with the autonomous device identifier. If there is no autonomous vehicle task that includes both the order identifier and the resource provider identifier, then the autonomous vehicle tasks database can provide a response message, to the central computer 102, comprising an indication that the order identifier and the resource provider identifier are not valid. [0177] If the central computer 102 receives a response indicating that the order identifier and the resource provider identifier are valid, then the central computer 102 can request the token from the token database of the databases 120 using the autonomous vehicle identifier. The token database can identify the token using the autonomous vehicle identifier and can provide the token the to central computer 102. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0178] In some embodiments, the resource provider computer 108 and the central computer 102 can communicate using a trusted communication channel. The trusted communication channel may be a preestablished communication channel between the central computer 102 and the resource provider computer 108. The trusted communication channel can be established when the resource provider computer 108 enrolls in the autonomous vehicle interaction system. [0179] At step 19, after obtaining the token, the central computer 102 to provide the token to the resource provider computer 108 for the interaction. [0180] At step 20, after receiving the token from the central computer 102, the resource provider computer 108 can generate a charging allowed message that indicates to the access device 106 that charging the autonomous vehicle 104 is allowed. The resource provider computer 108 can provide the charging allowed message to the access device 106. [0181] At step 21, after receiving the charging allowed message, the access device 106 can begin charging the autonomous vehicle 104 (e.g., the access device 106 can provide the resource to the autonomous vehicle 104). [0182] In some embodiments, at step 22, the autonomous vehicle 104 can provide autonomous vehicle metrics to the central computer 102 during and/or after charging of the autonomous vehicle 104. For example, the autonomous vehicle metrics can include battery charge level, length of time spent charging the battery, maximum battery charge level, etc. [0183] At step 23, after charging of the autonomous vehicle 104 is complete, the access device 106 can indicate to the resource provider computer 108 that charging is complete. The access device 106 can also provide qualitative data relating to the charging to the resource provider computer 108. For example, the qualitative data relating to the charging can include an amount of electric charge provided to the autonomous vehicle 104, a length of time spent charging, a cost of the amount of electric charge provided, etc. In some embodiments, the access device 106 can generate an authorization request message for the interaction. The authorization request message can include interaction data such as an amount. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0184] At step 24, after receiving the indication that the charging is complete, the resource provider computer 108 can generate an authorization request message. The authorization request message can comprise the token, which was received during step 19. The authorization request message can also comprise interaction data related to the interaction (e.g., a date, a time, a security value, an amount, a resource provider identifier, etc.). [0185] After generating the authorization request message, the resource provider computer 108 can provide the authorization request message to the transport computer 110. [0186] At step 25, after receiving the authorization request message, the transport computer 110 can provide the authorization request message to the network processing computer 112. [0187] At step 26, after receiving the authorization request message from the transport computer 110, the network processing computer 112 can modify the authorization request message. The network processing computer 112 can modify the authorization request message to comprise a credential that is associated with the token. For example, the network processing computer 112 can generate a credential request message comprising the token. The network processing computer 112 can provide the credential request message to the token service provider computer (not shown). The token service provider computer can identify the credential that corresponds to the token. The token service provider computer can generate a credential response message comprising the credential. The token service provider computer can provide the credential response message to the network processing computer 112. The network processing computer 112 can modify the authorization request message to include the credential by inserting the credential into the authorization request message or by replacing the token with the credential. [0188] At step 27, the network processing computer 112 can provide the authorization request message to the authorizing entity computer 114 for authorization of the interaction. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 [0189] After receiving the authorization request message, the authorizing entity computer 114 can determine whether or not to authorize the interaction. The authorizing entity computer 114 can determine whether or not to authorize the interaction. The authorizing entity computer 114 can based the determination on any suitable data related to the interaction, related to an account of the user maintained by the authorizing entity computer 114, related to the resource provider computer 108, etc. The authorizing entity computer 114 can generate an authorization response message comprising an indication of whether or not the interaction is authorized. The authorization response message can also comprise the credential and the interaction data. [0190] At step 28, the authorizing entity computer 114 can provide the authorization response message to the network processing computer 112. [0191] At step 29, after receiving the authorization response message, the network processing computer 112 can modify the authorization response message to remove the credential. For example, the network processing computer 112 can generate a token request message comprising the credential. The network processing computer 112 can provide the token request message to a token service provider computer (not shown). The token service provider computer can obtain a token that is stored in association with a stored credential that matches the received credential. The token service provider computer can generate a token response message comprising the token. The token service provider computer can provide the token response message to the network processing computer 112. [0192] At step 30, after modifying the authorization response message to include the token rather than the credential, the network processing computer 112 can provide the authorization response message to the transport computer 110. [0193] At step 31, the transport computer 110 can provide the authorization response message to the resource provider computer 108. [0194] Upon receiving the authorization response message, the resource provider computer 108 can complete the interaction with the autonomous vehicle 104. In some embodiments, the resource provider computer 108 can generate and PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 provide an interaction complete message to the autonomous vehicle 104 via the access device 106. [0195] At the end of the day or any other suitable period of time, a clearing and settlement process for the transaction can be conducted between the entities (e.g., an acquirer) that operate the transport computer 110, the network processing computer 112, and the authorizing entity computer 114. [0196] FIG.7 shows a block diagram of an access device 106 according to embodiments. The access device 106 can be an energy supply terminal. The access device 106 can comprise a processor 702. The access device 106 may also comprise a computer readable medium 704 including a communication module 704A, an energy regulation module 704B, an authentication module 704C, and an access data module 704D. [0197] The access device 106 can also comprise a short range communication interface 706, an actuator 708, a vehicle interface 710, a long range communication interface 714, and a memory 716 coupled to the processor 702. An energy source 712 can be coupled to the actuator 708 and the vehicle interface 710. The actuator 708 may be a pump or switch (e.g., an electrical or mechanical switch) that allows the energy source 712 to provide energy to the vehicle interface 710 and then to a connected vehicle. The energy source 712 could be an electrical line or conduit, or it could be a fuel tank. [0198] The communication module 704A can include code, executable by the processor 702 to allow the access device 106 to communicate with external devices such as an autonomous vehicle, a resource provider computer, or a central computer. The communication module 704A, in conjunction with the processor 702, can utilize the short range communication interface 706 and the long range communication interface 714 to communicate with other devices. [0199] The energy regulation module 704B can include code, executable by the processor 702 to analyze and adjust energy levels. The energy regulation module 704B, in conjunction with the processor 702, can determine how much energy is needed or should be provided to a vehicle. The energy regulation module PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 704B, in conjunction with the processor 702, can control the actuator 708 to control the flow of energy to the vehicle interface 710 and to a connected vehicle. [0200] The authentication module 704C can include code, executable by the processor 702 to authenticate connected vehicles and/or users of the connected vehicles. The authentication module 704C, in conjunction with the processor 702, can authenticate a user and/or a vehicle that may be connected to the access device 106. [0201] The access data module 704D can include code, executable by the processor 702 to obtain access data. The access data module 704D, in conjunction with the processor 702, can obtain access data from an autonomous vehicle. The access data can include a token or an order identifier. The access data module 704D, in conjunction with the processor 702, can obtain the access data during an interaction with the autonomous vehicle. In some embodiments, the access data module 704D, in conjunction with the processor 702, can generate an authorization request message comprising the access data. The access data module 704D, in conjunction with the processor 702, can transmit the authorization request message to a resource provider computer associated with the access device 106. [0202] Embodiments of the disclosure have a number of advantages. For example, embodiments provide for autonomous vehicles that can securely transact with access devices without the need for human intervention. [0203] Specifically, embodiments solve a technical problem of verifying that the autonomous vehicle is transacting with the correct access device (and not a fraudulent access device). The central computer can verify the autonomous device in several different manners. For example, the central computer can verify that a resource request message received from the autonomous vehicle is digitally signed by an autonomous vehicle private key that was issued by the central computer to the autonomous vehicle. As another example, the central computer can verify that the location of the autonomous vehicle matches a previously stored location of the access device as identified by the resource provider identifier. As yet another example, the central computer can generate an order identifier for the interaction, where the order identifier is provided to the autonomous vehicle. The autonomous vehicle can provide the order identifier to the access device to initiate the interaction. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 The access device can provide the order identifier to the resource provider computer. The resource provider computer can then send an interaction acceptance method to the central computer along with the order identifier via a trusted communication channel. The central computer can verify the order identifier and return a token for the interaction via the trusted communication channel. [0204] In addition, in embodiments of the invention, tokens and/or order identifiers are mostly used to process the transactions instead of real credentials. [0205] Although the steps in the flowcharts and process flows described above are illustrated or described in a specific order, it is understood that embodiments of the invention may include methods that have the steps in different orders. In addition, steps may be omitted or added and may still be within embodiments of the invention. [0206] Any of the software components or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C, C++, C#, Objective-C, Swift, or scripting language such as Perl or Python using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium for storage and/or transmission, suitable media include random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. The computer readable medium may be any combination of such storage or transmission devices. [0207] Such programs may also be encoded and transmitted using carrier signals adapted for transmission via wired, optical, and/or wireless networks conforming to a variety of protocols, including the Internet. As such, a computer readable medium according to an embodiment of the present invention may be created using a data signal encoded with such programs. Computer readable media encoded with the program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer readable medium may reside on or within a single computer product (e.g. a hard drive, a CD, or an entire computer system), and may be present on or within PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 different computer products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user. [0208] The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents. [0209] One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention. [0210] As used herein, the use of "a," "an," or "the" is intended to mean "at least one," unless specifically indicated to the contrary.

Claims

PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 WHAT IS CLAIMED IS: 1. A method comprising: receiving, by a central computer from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier; after receiving the resource request message, validating, by the central computer, the resource request message by comparing the location of the autonomous vehicle with a location of the access device; and after validating the resource request message, processing, the transaction, using a token associated with a credential, the credential associated with the autonomous vehicle. 2. The method of claim 1, wherein processing the transaction using the token comprises: transmitting, by the central computer, the token to the autonomous vehicle, wherein the autonomous vehicle provides the token to the access device, which initiates generation and transmission of an authorization request message comprising the token to a network processing computer. 3. The method of claim 1, wherein the autonomous vehicle is a self-driving car, the resource is electricity, and the access device is a charging station. 4. The method of claim 1, wherein processing the transaction using the token comprises: transmitting the token to the access device or a resource provider computer associated with the access device, which initiates generation and transmission of an authorization request message comprising the token to a network processing computer. 5. The method of claim 4 further comprising, before transmitting the token: PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 obtaining, by the central computer, an order identifier associated with the resource request message; transmitting, by the central computer, the order identifier to the autonomous vehicle, wherein the autonomous vehicle provides the order identifier to the access device or the resource provider computer associated with the access device; and receiving, by the central computer, the order identifier from the access device or the resource provider computer associated with the access device. 6. The method of claim 1 further comprising: prior to receiving the resource request message, receiving, by the central computer from the autonomous vehicle, a charging request message comprising a current location of the autonomous vehicle and an autonomous vehicle identifier; generating, by the central computer, an access device location request message comprising the current location of the autonomous vehicle; providing, by the central computer, the access device location request message to a resource provider locator computer, wherein the resource provider locator computer searches for access devices that are registered with the resource provider locator computer that have a location within a distance of the current location of the autonomous vehicle, and identifies the access device, a location of the access device, and a stored resource provider identifier associated with the access device; receiving, by the central computer an access device location response message comprising the location of the access device and the stored resource provider identifier; generating, by the central computer, an autonomous vehicle task based on the location of the access device and the current location of the autonomous vehicle; and providing, by the central computer, the autonomous vehicle task to the autonomous vehicle. 7. The method of claim 6 further comprising: PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 after receiving the charging request message, verifying, by the central computer, with a user device settings database that a setting indicates that the autonomous vehicle is authorized to request charging. 8. The method of claim 6 further comprising: after receiving the charging request message, generating, by the central computer, a user authorization request message requesting authorization from a user of a user device; providing, by the central computer, the user authorization request message to the user device, wherein the user device presents the user authorization request message to the user of the user device and receives a selection of whether or not the user authorizes the autonomous vehicle to proceed to the access device and perform the transaction; and receiving, by the central computer, a user authorization response message from the user device comprising the selection. 9. The method of claim 6, wherein the autonomous vehicle task includes navigation information for the autonomous vehicle to proceed from the current location of the autonomous vehicle to the location of the access device. 10. The method of claim 6 further comprising: after generating the autonomous vehicle task, storing, by the central computer, the autonomous vehicle task, the autonomous vehicle identifier, and the resource provider identifier into an autonomous vehicle tasks database, wherein validating the resource request message further comprises: generating, by the central computer, a validate task request message comprising the resource provider identifier and the autonomous vehicle identifier; providing, by the central computer, the validate task request message to the autonomous vehicle tasks database, wherein the autonomous vehicle tasks database identifies a most recent task for the autonomous vehicle using the autonomous vehicle identifier, compares the resource provider identifier of the validate task request message with the resource provider identifier of the most recent task, generates a validate task response PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 message comprising an indication of whether or not the resource provider identifier of the validate task request message with the resource provider identifier of the most recent task match; and receiving, by the central computer, the validate task response message comprising the indication of whether or not the resource provider identifier of the validate task request message with the resource provider identifier of the most recent task match. 11. A central computer comprising: a processor; and a computer-readable medium coupled to the processor, the computer- readable medium comprising code executable by the processor for implementing a method comprising: receiving, from an autonomous vehicle, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a resource provider identifier; after receiving the resource request message, validating the resource request message by comparing the location of the autonomous vehicle with a location of the access device; and after validating the resource request message, processing, the transaction, using a token associated with a credential, the credential associated with the autonomous vehicle. 12. The central computer of claim 11, wherein processing the transaction using the token comprises: transmitting the token to the autonomous vehicle, wherein the autonomous vehicle provides the token to the access device, which initiates generation and transmission of an authorization request message comprising the token to a network processing computer, or transmitting the token to the access device or a resource provider computer associated with the access device, which initiates generation and transmission of the authorization request message comprising the token to the network processing computer. PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 13. The central computer of claim 11, wherein prior to receiving the resource request message, the method further comprises: receiving a registration request message comprising a user device identifier and an autonomous vehicle identifier from a user device associated with the autonomous vehicle; obtaining a public/private cryptographic key pair from a cryptographic key database that stores a plurality of cryptographic key pairs, wherein the public/private cryptographic key pair comprises an autonomous vehicle public key and an autonomous vehicle private key; and providing the public/private cryptographic key pair to the user device, wherein the user device provides the public/private cryptographic key pair to the autonomous vehicle. 14. The central computer of claim 13, wherein the autonomous vehicle digitally signs the resource request message using the autonomous vehicle private key to obtain a digital signature, wherein the method further comprises: verifying the digital signature using the autonomous vehicle public key that corresponds to the autonomous vehicle private key. 15. The central computer of claim 13, wherein processing the transaction comprises: generating a resource response message comprising access data, wherein the access data comprises the token; encrypting the resource response message using the autonomous vehicle public key; and providing the encrypted resource response message to the autonomous vehicle in response to the resource request message, wherein the autonomous vehicle decrypts the encrypted resource response message using the autonomous vehicle private key. 16. A method comprising: providing, by an autonomous vehicle to a central computer, a resource request message for a resource provided by an access device in a transaction, the resource request message comprising a location of the autonomous vehicle and a PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 resource provider identifier, wherein after receiving the resource request message, the central computer validates the resource request message by comparing the location of the autonomous vehicle with a location of the access device; receiving, by the autonomous vehicle from the central computer, a resource response message comprising access data; providing, by the autonomous vehicle to the access device, the access data; and receiving, by the autonomous vehicle from the access device, the resource. 17. The method of claim 16, wherein the access data comprises a token or an order identifier. 18. The method of claim 16, wherein after providing the access data to the access device, the access device provides the access data to a resource provider computer, wherein the resource provider computer generates an authorization request message comprising the access data and provides the authorization request message to a network processing computer via a transport computer, wherein the network processing computer provides the authorization request message to an authorizing entity computer for authorization of the transaction, wherein the authorizing entity computer generates an authorization response message comprising an indication of whether or not the transaction is authorized and provides the authorization response message to the network processing computer, wherein the network processing computer provides the authorization response message to the resource provider computer via the transport computer. 19. The method of claim 16 further comprising: prior to providing the resource request message to the central computer, receiving, by the autonomous vehicle, the resource provider identifier from the access device via a wired connection or a wireless connection. 20. The method of claim 16 further comprising: PATENT Attorney Docket No.: 079900-1395615 Client Reference No.: 6826WO01 prior to providing the resource request message, generating, by the autonomous vehicle, a charging request message comprising a current location of the autonomous vehicle and an autonomous vehicle identifier; providing, by the autonomous vehicle, the charging request message to the central computer, wherein the central computer generates an access device location request message comprising the current location of the autonomous vehicle, provides the access device location request message to a resource provider locator computer, wherein the resource provider locator computer searches for access devices that are registered with the resource provider locator computer that have a location within a distance of the current location of the autonomous vehicle, and identifies the access device, a location of the access device, and a stored resource provider identifier associated with the access device, wherein the central computer receives an access device location response message comprising the location of the access device and the stored resource provider identifier, wherein the central computer generates an autonomous vehicle task based on the location of the access device and the current location of the autonomous vehicle; receiving, by the autonomous vehicle, the autonomous vehicle task from the central computer, wherein the autonomous vehicle task includes navigation information for the autonomous vehicle to proceed from the current location of the autonomous vehicle to the location of the access device; and navigating, by the autonomous vehicle, using the autonomous vehicle task, from the current location of the autonomous vehicle to the location of the access device.