takepayments · Authentication Profile

Takepayments Authentication

Authentication

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

PaymentsUnited KingdomPayment GatewayPayment ProcessingCard PaymentsCard MachinesIn-Person PaymentsE-CommercePSPAcquiring

Methods: oauth2, apiKey Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

TerminalApiOAuth2 oauth2

GatewayMerchantSignature apiKey

· in: body ()

Source

Authentication Profile

generated: '2026-07-24'
method: searched
source: https://developer.takepayments.com/documentation/authentication
summary:
  types: [oauth2, apiKey]
  oauth2_flows: [clientCredentials]
  api_key_in: [header]
  note: >-
    Two distinct APIs with two distinct auth models. The modern Terminal API
    uses OAuth 2.0 client-credentials issued by Microsoft Azure AD (JWT bearer).
    The legacy online payment Gateway API authenticates each SOAP/form-POST
    message with a merchant ID plus a pre-shared-key signature hash (not a
    bearer token).
schemes:
- name: TerminalApiOAuth2
  api: takepayments Terminal API
  type: oauth2
  flow: clientCredentials
  identity_provider: Microsoft Azure AD / Azure AD B2C
  token_endpoints:
    production: https://login.microsoftonline.com/0bdad8b5-fe48-4ccd-b807-e6b2662a6d0c/oauth2/v2.0/token
    sandbox: https://login.microsoftonline.com/cf77fc4a-626b-46ff-bd3a-3400a727352f/oauth2/v2.0/token
  tenants:
    production: takepaymentsintegratedprod.onmicrosoft.com
    sandbox: takepaymentsintegrated.onmicrosoft.com
  scope_format: 'https://takepaymentsintegratedprod.onmicrosoft.com/{ClientId}/.default'
  credentials: [client_id, client_secret, scope]
  request_header: 'Authorization: Bearer {JWT}'
  api_hosts:
    production: https://takepayments-integrated-prod-apim.azure-api.net/
    sandbox: https://takepayments-integrated-sandbox-apim.azure-api.net/
  discovery:
  - well-known/takepayments-openid-configuration-prod.json
  - well-known/takepayments-openid-configuration-sandbox.json
  sources: [https://developer.takepayments.com/documentation/authentication]
- name: GatewayMerchantSignature
  api: takepayments Gateway API
  type: apiKey
  in: body
  mechanism: >-
    Merchant ID plus a pre-shared-key (PSK) signature hash computed over the
    request fields; sent inside the SOAP v1.1 XML / HTTPS form-POST message
    rather than an HTTP header.
  sources: [https://www.takepayments.com/developer-support/]

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