NFC tap enrolment of the AmbiSecure card in Facebook Accounts Center
Quick 24-second clip showing the NFC tap-and-register flow for the AmbiSecure card with the Facebook mobile app.
Hosted on YouTube. Open in YouTube →
Registering the card on a Facebook account by NFC (phone)
On a phone the AmbiSecure card registers with the Facebook app by NFC tap. The two-factor settings are the same as on desktop, but you tap the card to the phone rather than plugging it in.
- In the Facebook app, open Menu → Settings & privacy → Settings → Password and security.
- Open Two-factor authentication and select Security keys → Add.
- Choose the NFC flow when prompted.
- Hold the AmbiSecure card against the phone's NFC antenna until the app confirms the tap.
- Name the key and finish — Facebook will request the tap on future logins.
Before you start
This is the shortest of the four flows, because the Facebook app does most of the work once NFC is available:
- Switch NFC on before opening the app. The two-factor screen will offer the security-key option regardless, but the tap will not be seen.
- Have another 2FA method enrolled. Facebook's prerequisite is the same on mobile as on the desktop flow — an authenticator app or SMS method must already be active.
- Remove a thick case for the enrolment tap, and note where the handset's NFC antenna sits.
- Keep your recovery codes to hand in case you need to get back in while testing.
What is specific to Facebook on a phone
Registration happens inside the Facebook app rather than in a browser, so the ceremony is brokered by the app and the system NFC service together. The practical consequence is that Android is the smoother path: the app can drive the tap directly. On iOS, security-key support in the Facebook app has been more limited than on Android, and the reliable route is to enrol from a mobile browser or from a desktop with a reader, then use the card for subsequent logins.
Because the account setting is shared, a key you enrol here is the same key the desktop site will ask for. If your Facebook and Instagram accounts share an Accounts Center, check which account the two-factor screen is configuring before you tap — the selector is easy to miss on a phone-sized layout.
If the tap is not detected
- The app never reacts — confirm NFC is enabled in system settings, then move the card slowly across the back of the phone to find the antenna.
- The security-key option is missing — two-factor authentication is not fully enabled on the account yet; finish that first, from either the app or a desktop browser.
- iOS will not complete the tap — enrol the card from a mobile browser or a desktop reader instead. The credential is account-level, so it works on the app afterwards.
Need a pilot, datasheet, or technical conversation?
Tell us the form factor, target deployment, and certification needs. Our engineering team will follow up directly.
Frequently asked questions
Do I need NFC switched on to add the AmbiSecure card to the Facebook app?
Yes. The two-factor screen will still show the security-key option, but without NFC enabled in system settings the phone cannot see the card when you tap it.
Does the AmbiSecure card work with the Facebook app on iPhone?
Security-key support in the Facebook iOS app has been more limited than on Android. The reliable route is to enrol the card from a mobile browser or a desktop reader; the credential is account-level, so it works for later logins.
Is a key registered on my phone also used when I log in on a desktop?
Yes. The security key is registered against the Facebook account rather than the device, so the desktop site asks for the same card.
Do I still need another two-factor method if I register a security key on mobile?
Yes. Facebook requires an active authenticator app or SMS method before accepting a security key, and keeps it enrolled as a fallback.
Do I have to use the Facebook app, or can I register from a mobile browser?
Either works, and the mobile browser is the fallback when the app cannot complete the tap. The credential is registered against the account rather than the app, so a key enrolled from a browser is still requested by the app on later logins.