Tap Payments · Authentication Profile

Tap Payments Authentication

Authentication

Tap Payments secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

PaymentsFintechPayment GatewayMENAMiddle EastOnline PaymentsChargesCardsKNETmadaFinancial Infrastructure
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-12'
method: derived
source: openapi/tap-payments-openapi.yml
summary:
  types:
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: 'Secret API key passed as a Bearer token: `Authorization: Bearer [example key]`
    (test) or `Authorization: Bearer [example key]` (live). Keys are issued from the
    Tap dashboard, with separate keys per mode. The secret key must remain
    server-side; a publishable key (pk_test_ / pk_live_) is used for client-side
    tokenization only.'
  sources:
  - openapi/tap-payments-openapi.yml
  - https://developers.tap.company/reference/api-endpoint