Ping++ · Authentication Profile

Ping Authentication

Authentication

Ping++ secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyPaymentsAggregated Payment聚合支付FinTechPayment GatewaySplit SettlementWeChat PayAlipayUnionPayChinaPayouts
Methods: apiKey Schemes: 1 OAuth flows: API key in: basic-auth-username

Security Schemes

ApiKeyBasicAuth apiKey
scheme: http-basic

Source

Authentication Profile

ping-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.pingxx.com/api/%E8%AE%A4%E8%AF%81.html
docs: https://docs.pingxx.com/api/
summary:
  types: [apiKey]
  scheme: http-basic
  api_key_in: [basic-auth-username]
  oauth2_flows: []
schemes:
- name: ApiKeyBasicAuth
  type: apiKey
  scheme: http-basic
  description: >-
    Ping++ API uses HTTP Basic authentication. The merchant API Key is supplied as the
    Basic-auth username; the password is left empty. All requests must be sent over HTTPS —
    plain HTTP is rejected by the Ping++ servers. The API Key is managed in the merchant
    dashboard under 企业面板 → 开发参数.
  key_prefixes:
    live: sk_live_
    test: sk_test_
  modes:
    - mode: live
      description: Real transaction environment (真实交易环境).
    - mode: test
      description: >-
        Test environment (模拟测试交易环境). Test-mode keys simulate transactions and webhooks
        without any real money movement or fees; live and test modes can be switched in real time.
  example: 'curl https://api.pingxx.com/v1/charges -u sk_test_XXXXXXXXXXXXXXXXXXXXXXXX:'
notes: >-
  Ping++ does not use OAuth or OpenID Connect — there is no scope surface, so no scopes/ artifact
  is emitted. Authorization is coarse-grained via the merchant API Key. Multi-tier merchant setups
  scope calls to a sub-merchant via the app[id] request parameter rather than a distinct credential.