Frame
Selects which credential authenticates a Frame API request.
The Frame Android SDK is publishable-key first: client-safe endpoints (tokenization, config, charge confirm) authenticate with your publishable key (pk_). A publishable key is safe to embed in an app binary — it can only tokenize and retrieve/confirm objects the client already owns.
Warning: Secret sends your secret key (
sk_), which grants full merchant privileges. A secret key must never ship inside an app binary; serve it only from your backend. The SDK emits a one-time runtime warning the first time Secret is used.
Inheritors
Types
Authenticate with a server-minted, per-object client secret used as a Bearer token.
Authenticate with the publishable key (pk_), unless an onboarding session is active — the session token then takes precedence. Account-scoped client-safe reads use this: mid-session they need the session token for the server to return PII-gated fields such as profile.
Authenticate with the publishable key (pk_) unconditionally, never overridden by an active onboarding session. Merchant-level endpoints (sonar, configuration, wallet config) use this — they are not account-scoped and the backend rejects an onb_sess_ token on them ("Client secret is not permitted for this endpoint.").
Authenticate with the secret key (sk_). Server-only — avoid shipping this in an app binary.