In short
Every LinxyPass site is set up from one place: lnxy.me/partner/start. It walks you through seven steps — your Linxy account, your site, proving your domain, your sign-in Mark, making your phone the owner key, adding LinxyPass to your site, and trying it before you go live. Your progress is saved, so you can stop and come back.
Two things surprise people. The site belongs to the Linxy account you are signed in with, so sign in with the account that should own it before anything else. And until you press Go live at the end, LinxyPass on your site works for you alone — everyone else is turned away, so nothing half-finished is ever shown to your members.
On this page
Before you start
You will need a phone with the Linxy App, a website where you can add a DNS record, a file or a meta tag, and an image for your sign-in Mark (or one of ours). If Linxy emailed you an invitation to set up a particular site, its link opens the same setup with the invitation ready to accept.
1. Your Linxy account
The site you set up is owned by the account you are signed in with, and only that account can finish setup, change its settings or enroll first. If you already have the Linxy App, choose Sign in with LinxyPass: scan the Mark on the sign-in page and approve on your phone, and you come straight back signed in as the account on that phone. If you are new, install the Linxy App, create your account there, then come back and sign in.
Signed in, the page tells you which account the site will belong to. If that is not the account you meant, sign out of lnxy.me and sign in with the right one.
2. Your site
Give the name your members will see — your business, not your own name — the sign-in page address where members sign in today, and what the site runs on:
| Choice | What happens in step 6 |
|---|---|
| WordPress | You install the LinxyPass plugin. No code |
| PHP | You or your developer add the LinxyPass PHP kit: Laravel, CodeIgniter, a custom app and others |
| Something else | Wix, Squarespace, Shopify, Node, Python and others. Linxy sets it up with you |
3. Prove your domain
Publish any one of three proofs, then press Check now. They are equally good; pick whichever your platform allows.
| Proof | Where | Best for |
|---|---|---|
| DNS TXT record | At _linxypass.your-domain, with the value shown | Anyone who manages their own DNS |
| A file | At /.well-known/linxypass-verify.txt on your site, containing only the token shown | cPanel, a VPS, anywhere you can place a file. Redirects are not followed |
| A meta tag | In the <head> of your home page | Wix, Squarespace, or any builder with a header or code box |
Your Mark is made only after this step, so nothing is created for an address you do not control. A DNS record can take a while to be seen; the file or meta tag is usually fastest. Subdomains of a proven domain (www, shop, app) are covered automatically; a second, separate domain is proven on its own. Proving the domain is also what lets your members be told they are signing in to an identity-verified business.
4. Your sign-in Mark
One image makes every size your site needs. Upload your own — a JPEG or PNG under 10 MB, at least 560 × 560 pixels — or use one of ours, then press Create my Mark.
- The Mark comes in card sizes of 560, 480 and 420 pixels, all carrying the same Mark. Your page picks the largest one that fits.
- An image of 1920 × 1200 or larger also makes a Full page Mark. Images are never enlarged.
- Texture carries the watermark; flat blocks of one color do not. A photograph, a product shot or patterned artwork reads well. Avoid heavy compression, and never re-export a Mark we generated.
Here you also choose the verification level — Standard (members approve with a tap or a watch) or LinxyPass Verified (a live face or fingerprint every time, for medical, financial or other personal data) — and how your sign-in page shows the Mark first. Both can be changed later from your dashboard without uploading again.
5. Your phone
This makes your phone the site’s owner key. Open your owner setup page, which shows your Mark at full scan size; scan it with the Linxy App, signed in as the account that owns the site; approve with Face ID or your fingerprint. The setup page notices and moves on.
Only the owning account can do this step. If the App on your phone is signed in to a different account, sign out of the App, sign in as the owner, and scan again.
6. Add to your site
| Platform | What you do |
|---|---|
| WordPress | Download LinxyPass Login, then in WordPress go to Plugins, Add New, Upload Plugin. After activating it, open Settings, LinxyPass, paste your Partner ID and API key, save, and press Test Connection. The plugin adds LinxyPass to your login page |
| PHP | Download the PHP kit and upload its linxypass folder to your site’s web root. Paste your API key into linxypass/config.php and choose the adapter for your site — plain (your site keeps the member’s id in its PHP session), codeigniter3 or altumcode; the kit’s README explains each. Then add one line to your sign-in page and one line to the page members use to manage their account. Your Partner ID is already filled in |
| Something else | Request setup help. Your request goes to your Linxy Platform Connection in the Linxy App, and Linxy replies there |
Your API key is shown once. Copy it when it appears. If you lose it, issue a new one from the Credentials section of your dashboard — the old key stops working at once, so paste the new one in straight away.
Your framework is not listed, or you would rather Linxy did it? Request setup help is offered on the PHP step too. Everything you did so far is saved.
7. Try it and go live
Sign in to your own site with LinxyPass before your members do. The last step ticks off what is done — Domain proved, Your sign-in Mark is made, Your phone is the owner key, LinxyPass found on your sign-in page, You signed in to your site with LinxyPass — and then offers Go live.
Going live lets members enroll and sign in with the Linxy App. Until then, only you can. You can take the site offline again from your dashboard; nobody is unenrolled and nothing is lost. If your own page is not ready yet, the dashboard’s Try it runs your real sign-in on a page Linxy hosts, for fifteen minutes.
How your members start
On a site using the PHP kit, a member signs in the usual way once, opens their account page, chooses Turn on LinxyPass and scans. From then on they sign in by scanning. The kit never creates accounts and never links one from the sign-in page. Who may enroll, and whether you approve each newcomer, is set on your dashboard; see LinxyPass for site owners. What members see is in Enrolling a site.
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| The site is set up under the wrong account | You were signed in to lnxy.me with a different account at step 1 | Sign out, sign in with the right account, and set the site up there |
| “Not found yet” after Check now | The proof is not visible yet — DNS still spreading, a file behind a redirect, or a tag not on the home page | Wait and check again, or use the file or meta tag instead |
| Only card sizes were made | The image is smaller than 1920 × 1200 | Upload a larger image if you want Full page |
| Step 5 waits for ever | The App is signed in to a different account, or you scanned a different Mark | Sign in to the App as the owner and scan the Mark on your owner setup page |
| “This site isn’t open to members yet” for your members | The site has not gone live | Finish step 7 and press Go live |
| I lost my API key | It is shown only once | Issue a new key from Credentials on your dashboard and paste it in |
Related reading: LinxyPass for site owners, Branding your Connection card, Enrolling a site, and What LinxyPass is.