requestAutocomplete API is designed to simplify the process of completing online purchase forms,
especially on mobile devices.
See the overview of
requestAutocomplete on HTML5Rocks.
What use cases are supported?
requestAutocomplete API has the potential to be useful for any form that requests any information outlined in the autocomplete spec, Chrome currently only supports using it for facilitating checkout flows that use a credit/debit/prepaid card as the payment method.
requestAutocomplete be used for digital goods, will-call tickets, or other sales that don’t require a shipping address?
Yes. If you don’t request any shipping details, Chrome won’t ask the user for a shipping address.
What if I only want an address?
If you only need an address, we currently recommend you stick with a normal web
<form> and mark your inputs with
I don’t need a phone number, why does Chrome ask for it anyway?
Since Chrome stores user-entered information to facilitate future purchases, it asks the user to enter all information that is generally relevant to checkout flows on the web. The upside is that if a user has used
requestAutocomplete before on any website, all the details your site needs will be stored and ready to go without needing to prompt for more information.
What if I need extra details that
requestAutocomplete doesn’t support?
You can ask for extra details, such as discount codes or rewards account numbers, on the confirmation page which your site shows before the order’s final placement.
What if the data I get back from Chrome doesn’t match my expectations?
Chrome applies standard data verification rules to the data it collects from users. For example, you can be sure the user’s email is in a valid format. However, Chrome does not guarantee the veracity of the information as it is supplied directly by the user. If you do have custom rules for the data values you expect (for example, if you only ship to some states), you should show the data and error messages to the user, and allow them to either fix the data or start over by trying
requestAutocomplete again. This flow chart covers how you can handle invalid data.
How do I calculate shipping costs before asking a user for their credit card?
If you want to calculate shipping costs before collecting complete payment information, we recommend embedding a zip/postcode-based shipping estimator in your site which is visible on the shopping cart page.
How should I handle a user canceling the
We recommend doing nothing. When a user presses cancel, we will dismiss the dialog and the user will be taken back to your checkout page.
requestAutocomplete and Google Wallet
Why are there references to Google Wallet in the UI?
The Chrome implementation of
requestAutocomplete allows users to choose Google Wallet for additional security and convenience features. With Google Wallet, users can access their payment information from any device, and the users’ saved credit or debit card information is never shared with merchants. If a customer uses Wallet, we’ll pass along a Google Wallet virtual card.
What is a Google Wallet virtual card?
To protect our users’ privacy and security, Chrome does not share a Google Wallet user’s full credit or debit card information with merchants. Instead, a Google Wallet virtual card is generated and used to complete purchases. Payment is authorized against the Google Wallet virtual card, and then Google charges the user’s credit or debit card for the same amount. See Google Wallet's help pages for more info.
Does the Google Wallet virtual card have to be handled differently than traditional credit cards?
No, you can use this card number exactly as you would any credit card supplied directly by the user.
Do I, as a developer, need to worry if a user uses Google Wallet or not?
No, you receive a fully functional credit card number regardless of whether or not your user uses Google Wallet.
requestAutocomplete (including Google Wallet) cost me anything?
No, this service is free.
We believes that facilitating transactions on the web is good for the entire ecosystem: users and merchants alike benefit.
Which browsers & devices support
requestAutocomplete is available on all up-to-date Chrome browsers: Windows, Mac, ChromeOS, Android, iOS, and Linux.
How can I give feedback or get more help?
There's more information at the Chromium wiki.
We also have a requestAutocomplete Google group. This is a public forum for developers to discuss Chrome’s implementation of
requestAutocomplete and ask questions.
Where can I see the list of known issues?
Chromium's bug tracker has a tag for