A facial identity API any identity provider can trust.

Enroll a reference face, verify it on demand, and get back a signed assertion your backend — or NativeGuard, or Passly, or any IdP you already run — can verify offline. Only the face vector is stored, inside your tenant's Rekognition collection; the image itself never touches disk, log, or trace.

The use case

Prove it's the same person, without owning face recognition.

Fintechs that need step-up authentication, account recovery, or a capture component for onboarding all hit the same build-vs-buy decision: Amazon Rekognition Face Liveness is the easy part — assertion signing, replay protection, per-tenant data isolation, and an interface any IdP can consume are the hard part.

Where Native Biometrics fits in your stack

What's in the box

Enrollment, verification, and a portable assertion.

From zero to a verified user

Three calls: enroll, verify, trust the assertion.

Using `@swepay/biometrics-core` against the Native Biometrics API. Most apps enroll once per user, then verify on every step-up event afterward.

1. 0. Enroll a reference face

   Mount `<FaceEnroll />` (or call the client directly) once per user, right after signup or at the point your risk policy requires strong identity proof.

   Requestts

   import { BiometricsClient } from "@swepay/biometrics-core";
   
   const client = new BiometricsClient({
     apiBaseUrl: "https://api-biometrics-hml.swepay.com.br", // illustrative — no public host yet
     getAccessToken: () => getCurrentUserAccessToken(),
   });
   
   const enrollment = await client.createEnrollment({ userRef: "user_123" });
   const completion = await client.completeEnrollment(enrollment.enrollmentId);

   Responsejson

   {
     "status": "enrolled",
     "livenessConfidence": 98.4,
     "attemptsRemaining": null
   }

2. 1. Verify a face on a step-up event

   Open a verification session whenever your risk policy calls for proof-of-presence — a new device, a high-value transfer, a password reset.

   Requestts

   const verification = await client.createVerification({ purpose: "login" });
   const decision = await client.completeVerification(verification.verificationId, {
     livenessSessionId: verification.livenessSessionId,
   });

   Responsejson

   {
     "decision": "approved",
     "livenessConfidence": 98.1,
     "similarity": 96.4,
     "assertion": "eyJhbGciOiJFUzI1NiIsImtpZCI6IjIwMjYtMDktMDEifQ..."
   }

3. 2. Verify the assertion on your backend

   Any backend — yours, NativeGuard, or a third-party IdP — fetches the public JWKS once, caches it, and verifies the JWS offline. No call back to Native Biometrics on the hot path.

   Requestbash

   curl https://api-biometrics-hml.swepay.com.br/.well-known/jwks.json

   Responsejson

   {
     "keys": [
       { "kty": "EC", "crv": "P-256", "kid": "2026-09-01", "use": "sig", "x": "...", "y": "..." }
     ]
   }

`api-biometrics-hml.swepay.com.br` above is illustrative — Native Biometrics has no deployed public host yet (backend routes are implemented; onboarding onto the Marketplace Subscription Hub is pending). Full SDK reference: `@swepay/biometrics-react` and `@swepay/biometrics-core`. Technical questions: [email protected].

Security & compliance

What we store, and what we never do.

Facial data is sensitive personal data under LGPD (art. 5º, II). Native Biometrics is built to minimize what it retains.

Pricing

Usage dimensions, plus a monthly plan with included volume.

Billed entirely through AWS Marketplace — no separate invoice. Pick a monthly plan for predictable included volume, or pay per dimension if usage is irregular.

Usage dimensions

Every plan below includes a bundle of `bio_mau`; usage beyond the plan, or usage outside a plan entirely, is billed per dimension.

Monthly plans

Priced by monthly active user (MAU) — a user who completes at least one enrollment or verification in the billing month.

Which one do I need?

Native Biometrics vs. Native KYC

Independent products (ADR-0003) that solve different problems and integrate well together. Most fintechs start with whichever matches the moment: onboarding a new customer, or re-verifying one they already know.

Need both? Subscribe to each independently on AWS Marketplace — there's no bundled SKU, and no requirement to run one to use the other.

Frequently asked

Before you integrate.

Straight answers to the questions that come up most before a security or compliance review.

Two ways to start.