Two-factor,to make changes.

Signing in to Payshen is a single-use link, so there is no password to steal. It also means the mailbox is the only thing in front of the account. From today, a person whose role can change how payments flow (providers and their credentials, routing, captures and refunds, API keys, webhooks, team members or settings) needs a second factor, a code from an authenticator app, to make those changes.

Nothing is locked away while you set it up: until it is on you can still see everything, and the console says what is needed before you try a change. It takes a minute in Settings, Security, with any authenticator app. Read-only roles may turn it on and need not.

Two more rules come with it. A session left alone for 15 minutes locks, and a code opens it again where you were. Ten wrong codes in a row lock the account for 30 minutes. Refused sign-ins and codes are now on your audit log, so a guessing run shows up there.

API keys and webhooks are not affected. We have also made sure no card data can be kept by mistake: a card number sent in any field of a payment is refused, and anything a provider sends us is stored without CVV, PIN or expiry.