Autofill support

Follow

Petar Na

October 25, 2017 17:45

Browsers such as Chrome 43+ support helping users checkout faster using autofill (https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill).

Chrome can also provide the user payment details through the Payment Request API. (https://developers.google.com/web/fundamentals/payments/)

Another use case would be supporting autofill through common password managers such as LastPass or 1Password.

• Is it possible to add these custom html attributes required for autofill to the credit card or cvv fields?
• Is there a way to manually set the credit card/cvv fields programmatically?

 

1

• Official comment

  

  Permanently deleted user April 22, 2021 12:59 (Edited April 22, 2021 13:00)

  Update: Auto-fill for the iFrame and Express payment forms is supported by most browsers and password managers. 

  Please let us know if this functionality doesn't work as expected and we'd be happy to investigate further.

  Comment actions Permalink
• 

  Todd Derr September 17, 2021 21:07

  @... we are using the iframe form (v1) and see that the card number gets filled in but none of the other fields (expiration, cvv, name, etc).
  
  Almost all sites I visit (one example: https://www.redcross.org/donate/donation.html/) do fill the expiration and CVV as well as the card number, so this is what I'd expect to happen.  I do have the attributes in my own form tagged with the proper "autocomplete" values per the spec but I suspect it's refusing to cross the iframe boundary, which unfortunately makes me suspect there is no real solution without rearchitecting the whole thing (but I'd be glad to be proven wrong!)
  
  I don't see any discussion of autocompletion in the docs but I did click through to your sample form and live app and it has the same behavior.
  
  I hoped the express form would work, but it does not, although I see it still uses iframes for the number and cvv so it's really no different than my own forn.

  2

  Comment actions Permalink
• 

  Andrei Vintila December 08, 2021 10:35

  We are also facing the same issue and we have narrowed it down to IOS Safari autofill is not working.

  1

  Comment actions Permalink
• 

  Javier López May 23, 2022 11:14

  We are facing the same issue as Todd Derr, we are using the iFrame, but only the credit card number field is being auto filled since the browser cannot bypass the iFrame autocomplete. It belongs to another form and thus it doesn't auto fill external input/form data.
  
  This also happens with the Express Payment Form.
  The only real solution is to use the JavaScript API but it is not a solution since we'd need "an increased amount of PCI scope".
  
  Hopefully you can find a way to find a PCI compliant solution with autocomplete. So far there is no way to get autocomplete to work on multiple fields (even Card Number/CVV from each of Spreedly's iFrames).

  1

  Comment actions Permalink
• 

  Permanently deleted user October 25, 2017 19:16 (Edited October 25, 2017 19:17)

  Hi Petar!

  Thanks for posting. I definitely understand how autofill makes it easier for customers to check out on a site that doesn't already have their credit card stored, it's a very useful addition for many businesses!

  We currently do not support Chrome Autofill on our iFrame and Express solutions due to our PCI Compliance restrictions, but, if you were to build out your own custom payment form (using a Spreedly solution other than iFrame/Express), you would be free to develop it to work with Chrome autofill guidelines.
  
  Let me know if you have additional questions!

  0

  Comment actions Permalink

Please sign in to leave a comment.