Alternatives to Email Magic Links and SMS Login Codes
For a returning customer, the ideal sign-in method gets them back to their task while giving them a recovery path they can actually use. Start by comparing the customer’s enrolled credential, the device or channel they need and the method’s behavior when that device changes.
Compare the customer journey
| Method | What the customer uses | Where it helps | What to evaluate |
|---|---|---|---|
| Email magic link | Access to the mailbox receiving a one-time sign-in link | Familiar enrollment and a simple fallback for some customers | Mailbox access, delivery delays, expiry and cross-device behavior |
| SMS one-time code | A phone number able to receive the code | Broad device reach and a familiar interaction | Delivery cost, number changes, recovery and resistance to phishing |
| WebAuthn passkey | A registered public-key credential made available by the customer’s platform or security key | Sign-in with relying-party binding, including implementations that support phishing resistance | Device support, account registration, portability, fallback and recovery |
| Enrolled-app QR flow | A connected app and a QR scan, followed by the configured comparison or confirmation | A returning customer who already enrolled the app | Cross-device experience, accessibility, trusted service relationship, phone loss and fallback |
A QR code is an interaction entry point. Security comes from the credential, service relationship and configured checks around that code. Keep that distinction in customer copy and give the user an obvious path when a camera or phone is unavailable.
How to choose for commerce
- Separate first registration from repeat sign-in. People who have already connected an app may have a smooth QR return experience. New customers may prefer a credential they can establish on their current device.
- Decide who can reach the fallback and what it verifies. Plan for a new phone, inaccessible mailbox, lost number and a change to the platform account model.
- Make the comparison in the same workflow. Ask customers to register, return, recover and contact support on representative devices. Measure completion, time, abandonment and support contacts before committing to a benefit estimate.
- Evaluate accessibility. Test keyboard access, screen reader instructions, zoom, timing and a route that does not rely on a camera. Make sure the fallback is easy to find from the same screen.
Where PasswordFree fits
The documented BigCommerce LoginFree™ experience lets a returning enrolled customer scan the store’s QR, compare the picture and number across screens and accept in the browser. That configured flow removes the email-entry step for those customers. The available PasswordFree journey depends on the store, platform and account model. The published Shopify guide targets legacy customer accounts; confirm a different account model before choosing an integration. Review the current plugin listing and your hosting requirements for WordPress.
Start with one returning-customer journey and a real recovery test. Review PasswordFree, BigCommerce LoginFree, Shopify account-model guidance, WordPress integration, and NIST SP 800-63B-4. Bring your platform and enrollment requirements to the integration discussion.
