Wink Developers
Home Wink Core
Wink Core

Biometric identity + payment APIs

Wink Core is the REST surface every developer surface at Wink is built on — authentication (face / voice / palm / WinkPIN), user profile, and payment authorization. Every SDK, MCP tool, and POS integration Wink ships eventually reaches this API. Use it directly for full control, or reach for one of the SDKs above when you want the ergonomics.

Protocol REST + JSON Login host stagelogin-api.winkapis.com Payment host stagepayments-api.winkapis.com Auth Basic + Bearer

What is Wink Core

Wink Core is a set of REST APIs that expose the biometric identity + payment primitives Wink built for its consumer products. External developers can hit them directly to build any surface — a native app, a web checkout, a POS terminal, an MCP tool — while every Wink-owned surface (WinkKey, WinkPay, the MCP server) is itself just an app on top of the same APIs.

  • Identity — enroll and recognize users by face, voice, palm, WinkPIN, or any combination. Multi-factor step-up, consent capture, and profile CRUD are first-class.
  • Wallet — save cards + addresses per user; served from the Payment host on /V1/wallet/*.
  • Payment — create and authorize payment sessions against a real card network, or return external tokens if the merchant owns the charge.

Where to next

Pick the surface that matches how you plan to integrate:

Other products built on Core

Every other Wink product is a specialized packaging of the Core APIs. If your use case matches one, reach for it — you'll get the ergonomics for free.

  • WinkPay — Android POS SDK: face + palm biometric checkout with dual-display, EMV integration, and customer-display routing baked in.
  • Wink MCP — MCP server that exposes 25 Wink tools to any MCP client (Claude, Cursor, custom agents). Handles OAuth + tool discovery.
  • WinkKey — Wink's own passkey-adjacent login built on Core's biometric primitives. Used inside consumer products; the same primitives are what you'll use to build one for yourself.
i

New to the platform? Start with the API console — it walks the full enroll → authenticate → charge flow interactively against your saved credentials, and every operation has a "Try in console" button that pre-fills request bodies. Once you know the shape, drop into the SDK for your platform.