Sign-in flow & verification
The typical Uphold sign-in begins with your email or username and password submitted on the official site. After credential verification, Uphold will apply any account-level policies you have configured — most commonly, a second factor for authentication. If 2FA is enabled, the platform will request a one-time code from an authenticator app or send an SMS code to your registered phone number. For stronger protection, we recommend using a TOTP authenticator app (like Authy or Google Authenticator) or hardware security keys when supported.
Device recognition reduces friction by allowing the platform to mark a browser or device as trusted for a limited period. Only enable this option on personal, secure devices. When signing in from a new or untrusted device, Uphold will challenge additional verification — this is expected behavior designed to protect your account from unauthorized access.
Programmatic & API access
For programmatic integrations, manage API keys with least privilege and rotate them periodically. Use restrictive scopes and monitor usage logs to detect anomalies. If using server-to-server integrations, secure keys behind environment secrets and avoid embedding them in client-side code or public repositories.