Solutions / Ecommerce
The customer’s task is shopping, checking an order or managing an account. PasswordFree® makes registration and return part of that experience, with mutual authentication behind the sign-in.
Plugin setup, registration and returning access.
Get the WordPress plugin
App-based LoginFree™ for enrolled returning customers.
Explore BigCommerce
Documented legacy customer-account integration. Check your account model first.
Check your account setupA customer who has connected their authentication method can return without remembering another password. In the app-based experience, the enrolled app checks the authentication service and the customer recognizes the request before deciding to continue.
Try the BigCommerce LoginFree example to see the QR scan, picture-and-number comparison and browser approval.
Illustrative workflow. Explore the steps and the decisions behind them.
PasswordFree · BigCommerce LoginFree · interactive example
An enrolled customer chooses PasswordFree to return to their account. Try the sign-in button in the store.
Your orders. Your account.
Open the enrolled app and point the phone at the store’s QR code. Here, select Scan QR code in the phone’s viewfinder.
Point your camera at the store
Compare the black picture and code on the two screens. If they match, select Accept in the store. If anything looks wrong, select Decline.
Do the picture and number match your phone?
501Compare with the store
501If they match, select Accept in the store. Otherwise, select Decline.
The store opens the customer account and the phone shows a green confirmation.
Try the highlighted button or use the controls below.
| Moment | A useful customer experience |
|---|---|
| First visit | Explain why an account is useful and guide enrollment. |
| Return | Recognize the service, complete the supported sign-in and reach the account. |
| Changed device | Offer a clear restoration and support path. |
Compare the current WordPress, BigCommerce and Shopify routes for the selected store. Keep each platform’s documented account-model and commercial requirements; do not assume identical support.
Before installing, agree who owns enrollment, account recovery, revocation and support. Test the existing customer journey and a lost-device scenario in a store test environment. Authentication does not determine purchase authorization or guarantee conversion. Review customer access.
Your next step
Help returning shoppers get back to the account they came for.
First check the supported platform and customer-account model, then plan enrollment, recovery and support around that experience.
Agree who owns enrollment, recovery and the approval decision before you expand the workflow.
An enrolled shopper can complete the supported sign-in flow. If the shopper declines, the request expires or the device is unavailable, the store keeps the account closed for that request and offers its recovery path. The merchant still owns order permissions, payment checks and fraud decisions.
