Shieldpay · Authentication Profile

Shieldpay Authentication

Authentication

Shieldpay secures its APIs with mutualTLS, apiKey, and requestSignature across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyPaymentsEscrowLegal TechnologyFintechComplianceKYCBanking
Methods: mutualTLS, apiKey, requestSignature Schemes: 4 OAuth flows: API key in: header

Security Schemes

mutualTLS mutualTLS
apiKey apiKey
· in: header ()
requestSignature http
scheme: signature
ipWhitelist networkControl

Source

Authentication Profile

shieldpay-authentication.yml Raw ↑
generated: '2026-07-21'
method: searched
source: https://developers.shieldpay.com/getting-started/api-fundamentals/authentication-and-security
docs: https://developers.shieldpay.com/getting-started/api-fundamentals/authentication-and-security/authentication-mtls-and-api-keys
summary:
  types: [mutualTLS, apiKey, requestSignature]
  api_key_in: [header]
  api_key_header: Authorization
  transport_security: mutual-TLS
  oauth2_flows: []
  note: >-
    No OAuth2/OIDC. Access is layered: mutual TLS establishes the channel, an API
    key identifies the organisation, and every request is signed and IP-gated.
schemes:
- name: mutualTLS
  type: mutualTLS
  description: >-
    Client and server verify each other with certificates over an encrypted mTLS
    channel. The integrator generates a Private Key and CSR; Shieldpay issues one
    Signed Certificate per organisation at a time. Certificate lifecycle requests
    go to integrationsupport@shieldpay.com.
- name: apiKey
  type: apiKey
  in: header
  parameter_name: Authorization
  description: >-
    A unique secret token identifying the organisation, sent in the Authorization
    header of every request. API keys do not expire but can be deactivated; an
    organisation may hold multiple active keys. Registration/deactivation via
    integrationsupport@shieldpay.com.
- name: requestSignature
  type: http
  scheme: signature
  parameter_name: DigitalSignature
  algorithm: RSA-SHA256
  description: >-
    Every request must carry a DigitalSignature header. The signature is an
    RSA-SHA256 signature (Base64) over the concatenation, in order and with no
    separators, of: Request URL (no query string) + API Key + RequestID +
    Timestamp + raw Request Body, signed with the client Private Key.
- name: ipWhitelist
  type: networkControl
  description: >-
    All requests must originate from a whitelisted IP. Sandbox and Production
    maintain separate whitelists. Changes via integrationsupport@shieldpay.com,
    actioned within hours to two UK business days.

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/shieldpay-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.

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