PayStand · Authentication Profile

Paystand Authentication

Authentication

PayStand secures its APIs with oauth2, apiKey, and http across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials, authorizationCode, and password flow(s).

CompanyPaymentsB2B PaymentsAccounts ReceivableAccounts PayableFintechBlockchainACHBillingCheckout

Methods: oauth2, apiKey, http Schemes: 4 OAuth flows: clientCredentials, authorizationCode, password API key in: header

Security Schemes

oauth2 oauth2

· flows: clientCredentials, authorizationCode

Authorization http

scheme: bearer

X-CUSTOMER-ID apiKey

· in: header (X-CUSTOMER-ID)

X-PUBLISHABLE-KEY apiKey

· in: header (X-PUBLISHABLE-KEY)

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://api.paystand.com/.well-known/openid-configuration
docs: https://developers.paystand.com/reference/getting-api-access
summary:
  types: [oauth2, apiKey, http]
  api_key_in: [header]
  oauth2_flows: [clientCredentials, authorizationCode, password]
notes: >-
  Authenticated Paystand API calls use an OAuth2 access token in the
  Authorization header ("Bearer <token>") plus an X-CUSTOMER-ID header. Access
  tokens are minted at the token endpoint with grant_type=client_credentials
  using the application clientId/clientSecret (scope "auth"). Non-authenticated
  (public checkout) calls use the X-PUBLISHABLE-KEY header carrying the
  customer's publishable key.
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.paystand.com/v3/api/v3/oauth/token
    scopes: [auth]
  - flow: authorizationCode
    authorizationUrl: https://api.paystand.com/v3/api/v3/oauth/authorize
    tokenUrl: https://api.paystand.com/v3/api/v3/oauth/token
    scopes: [auth]
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post]
  source: https://api.paystand.com/.well-known/openid-configuration
- name: Authorization
  type: http
  scheme: bearer
  description: "Bearer <access_token> for authenticated calls."
  source: https://developers.paystand.com/reference/headers
- name: X-CUSTOMER-ID
  type: apiKey
  in: header
  parameter: X-CUSTOMER-ID
  description: Customer id, required for authenticated calls.
  source: https://developers.paystand.com/reference/headers
- name: X-PUBLISHABLE-KEY
  type: apiKey
  in: header
  parameter: X-PUBLISHABLE-KEY
  description: Customer's publishable API key, required for non-authenticated (public) calls.
  source: https://developers.paystand.com/reference/headers

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/paystand-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.