Omise · Authentication Profile

Omise Authentication

Authentication

Omise secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

PaymentsPayment GatewayThailandSoutheast AsiaChargesTokensSourcesPromptPayCardsFintech
Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

secretKeyAuth http
scheme: basic
publicKeyAuth http
scheme: basic

Source

Authentication Profile

Raw ↑
generated: '2026-07-12'
method: derived
source: openapi/omise-openapi.yml
summary:
  types:
  - http
schemes:
- name: secretKeyAuth
  type: http
  scheme: basic
  description: >-
    HTTP Basic authentication against the core API host https://api.omise.co.
    The account secret key (skey_test_... in test mode, skey_... in live mode)
    is supplied as the Basic-auth username with an empty password. Used for all
    server-side operations - charges, customers, refunds, transfers, recipients,
    schedules, disputes, links, events, account, and balance.
  sources:
  - openapi/omise-openapi.yml
- name: publicKeyAuth
  type: http
  scheme: basic
  description: >-
    HTTP Basic authentication against the PCI-scoped vault host
    https://vault.omise.co (and permitted for creating Sources). The account
    public key (pkey_test_... / pkey_...) is supplied as the Basic-auth username
    with an empty password. Used client-side (typically via Omise.js) to
    tokenize card data so raw PAN never touches your server.
  sources:
  - openapi/omise-openapi.yml
notes: >-
  Both keys are found on the Opn Payments / Omise dashboard. API behavior can be
  pinned per-request with the optional Omise-Version header (for example
  2019-05-29); otherwise the account default API version applies. Keep the
  secret key server-side only.