piSun Technologies
Secure Operating Platform
piSun Patron · Device-specific downloadsChoose your piSun Patron downloadOpen Patron Access PointOpen piSun Wallet
piSun Profile Digit

Submit and validate Profile Digit through your protected device.

The portal does not collect Profile Digit touch data. Capture occurs only inside piSun Patron on the approved device after Home Domain authorization. The resulting biometric evidence is routed to the Patron DataCar and the authorized comparison path.

First enrollment

Store this device's Profile Digit

Use the approved piSun Patron device that is already connected to your Home Domain and Mirror. The DataCar issues the capture directive; the phone collects the touch-behavior sample and returns it for derivation and protected storage.

1
Continue Patron onboarding
Complete the existing Patron/device handoff. Do not create another Patron, Home Domain, or DataCar for an already established identity.
2
Open piSun Patron 0.13.4
In the app, open biometric enrollment and choose Enroll Profile Digit.
3
Complete the requested touch captures
Follow the Profile Digit capture surface shown by the app. The device collects the behavioral touch evidence requested by the DataCar.
4
Wait for durable confirmation
Enrollment is complete only when the app receives the DataCar result with the protected reference committed. Android touch interaction by itself is not a completed piSun enrollment.
Continue Patron onboarding
Validation

Validate a fresh Profile Digit

Validation always uses a fresh capture. The portal never accepts an uploaded Profile Digit sample and never treats a browser click as a biometric approval.

1
Start an authorized PSOP request
Site access, merchant authorization, or another PSOP service requests a biometric authorization through the Home Domain.
2
Approve the request on your trusted device
piSun Patron receives a one-time Profile Digit candidate capture request bound to that operation and this device.
3
Capture a fresh Profile Digit
The phone returns only the current operation's transient capture to the resident DataCar path. The stored Profile Digit reference remains associated with the correct DataCar and device profile.
4
Use the comparison decision
The DataCar supplies the authorized derived candidate and its stored derived reference to Lehi Comparison. Lehi returns MATCH, NO_MATCH, or INDETERMINATE. An inconclusive result can require face, voice, or another approved factor.
Open Patron Access Point
Merchant and service authorization

Profile Digit uses the same PSOP authorization boundary as other biometrics.

A merchant, website, or PSOP application should request an authorization result rather than biometric material. Profile Digit capture and reference handling stay behind the trusted device, Home Domain, and DataCar boundary. The normal production path sends only the authorized derived comparison artifacts to Lehi Comparison. The merchant or service receives the permitted authorization outcome, not the Patron's raw touch sample or stored reference.

Do not upload Profile Digit files to this website.

If a page ever asks you to paste, upload, or manually type Profile Digit biometric data, do not use that path. Profile Digit enrollment and validation belong to the trusted piSun Patron capture flow.