Hi Clover Product Team and Community,

As a remote merchant managing back-office operations and payroll via the Web Dashboard, I'm writing to request a crucial modernization of Clover's login authentication.

My primary request is for native Passkey (WebAuthn) support, complemented by a much-needed adjustment to trusted device session limits to match real-world business accounting cycles.

1. Primary Request: Native Passkey Support (WebAuthn) Leading Fintech and commerce platforms—such as ****** and ****** *****—have successfully standardized Passkey authentication.

Integrating Passkey (Touch ID, Face ID, Windows Hello, or hardware security keys) into the Clover Merchant Portal provides a massive win-win:

Superior, Phishing-Resistant Security: Modern biometric and hardware-bound keys offer far stronger security than traditional SMS, email, or TOTP 2FA.

Frictionless Workflow: Allows account owners to authenticate securely in seconds without manually entering codes every time.

1. The Operational Issue: 14-Day Limits vs. 15/16-Day Payroll Cycles Many businesses, including mine, operate on a semi-monthly accounting and payroll schedule (every 15 or 16 days) depending on the month and cutoff dates.

Currently, the Web Dashboard enforces a strict 14-day re-authentication limit for trusted devices. Because real-world payroll cycles run on 15 or 16-day intervals, a 14-day expiration window guarantees that sessions expire right before every single payroll run. This forces unnecessary 2FA friction precisely when executing routine administrative tasks.

Summary & Request
Implement Passkey Support as the modern authentication standard for Clover merchants.

Until Passkey is fully rolled out, please extend the Trusted Device session duration to at least 30 days to properly accommodate standard 15/16-day and monthly operational rhythms.

If you also find your sessions expiring right before your 15-day or 16-day payroll runs, please upvote this thread!

Thanks for your time and consideration.