Security & controls

Built the way finance teams expect.

PayShore is designed for the controls and audit posture finance teams require (from small business through mid-market and enterprise), across access, approvals, audit, encryption, and bank credentials.

Access
Role-based access control with MFA enforced at sign-in
Approvals
Multi-stage approvals that block single-person money movement and out-of-band manipulation
Audit
Append-only event log, timestamped per action
Credentials
Bank credentials encrypted with per-customer keys; access scoped and logged
The posture

Seven pillars finance and IT both review.

PayShore is built around the controls auditors already test for. The pillars below are how we describe that posture to security reviewers and prospect IT teams.

01 · Access

Role-based access. MFA by default.

Every PayShore account ships with multi-factor authentication on by default. Roles scope what individuals and teams can see and do, so a treasury analyst, an AP clerk, and a CFO each get the access their work requires, and no more.

  • MFA enforced on every account
  • Role-based permissions across visibility, approvals, payments
  • Sessions expire on idle
  • Password rotation enforced on a regular schedule
02 · Approvals

Maker-checker-and-double-checker, with thresholds you configure.

Transfers, payments, and counterparty changes route through tiered approval chains: initiator, first reviewer, and a second sign-off where the policy demands it. Approvals happen inside PayShore (not over email, chat, or phone), so the control and the action stay attached.

  • Configurable thresholds per workflow
  • Multi-level approval chains: maker, checker, double-checker
  • Approvals recorded against the action they authorized
03 · Fraud defense

Built for the threats that actually happen.

PayShore's structure is the defense. Maker-checker-and-double-checker approval chains mean no single person can move money, even an administrator. Approvals happen inside PayShore, not over email, phone, or video call, so a manipulated executive, a deepfake on a video call, or a duress request can't bypass the workflow. Every approval is anchored to the specific action it authorized, so any attempted manipulation leaves a record.

  • No single-person money movement, even for admins
  • Approvals happen in-platform, not over email, phone, or video
  • Configurable thresholds force additional sign-off at the dollar amounts where the risk lives
  • Deepfake-resistant by design: the approver has to click through PayShore, not respond to a video call
  • Insider fraud leaves a record: every action recorded against the specific approval that authorized it
04 · Audit

Immutable, timestamped, exportable.

Every meaningful action (approvals, executions, configuration changes) is recorded in an audit log that is timestamped, tamper-evident, and exportable for your auditors and your downstream systems.

  • Immutable record of who did what, when
  • Designed to support standard finance-team review processes
05 · Encryption

Encrypted in transit. Encrypted at rest.

Traffic between your team, PayShore, and your banks is encrypted in transit. Data at rest is encrypted. Sensitive secrets are managed in a dedicated key-management service rather than living alongside application data.

  • Encryption across browser, app, and bank connections
  • Encryption at rest
  • Keys managed in a dedicated KMS
  • US-based infrastructure
06 · Bank credentials

Encrypted bank tokens. No stored bank passwords.

PayShore does not store your bank passwords. Where continuous service operation requires bank-issued tokens or similar credentials, they are stored encrypted and access-controlled. Connections use revocable bank-issued tokens, and credential rotation and revocation stay where they belong — with you and with the bank.

  • Bank-issued tokens, not stored passwords
  • Encrypted at rest and access-controlled
  • Revocable at any time, coordinated by PayShore
  • No shared service accounts on PayShore's side
07 · AI & data

AI is a priority. Principles set ahead of features.

AI is a priority for PayShore and a meaningful part of where the platform is headed. As AI features are introduced, they will be governed by the same principles the rest of the platform already runs on — set today, so security teams can count on them regardless of when each feature arrives.

  • Customer data will never be used to train third-party or foundation models
  • AI features will run inside your tenant boundary, with the same access controls as the rest of the platform
  • Human-in-the-loop for any payment, approval, or balance-affecting action
  • Every AI-assisted action will land in the same immutable audit log
Compliance posture

Built around the controls security teams already review.

PayShore is structured around the access, change-management, and audit controls that security and finance reviewers expect to see when evaluating a finance operations platform.

For more information or specific security questions, reach out to our security team directly.

Security contact security@payshore.com