The UseePay API uses x-merchant-no, x-api-key and x-app-id in the HTTP request header to authenticate requests. For x-merchant-no, x-api-key and x-app-id parameters, We define them as authentication headers.Your x-api-key carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.Use your authentication headers by setting it in the initial configuration of new \UseePay\UseePayClient(). The PHP library will then automatically send this key in each request.You can also set a per-request key with an option. This is often useful for Connect applications that use multiple API keys during the lifetime of a process. Methods on the returned object reuse the same API key.All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.1. x-merchant-no#
MC → Configuration Center → Secret Management → First row data2. x-api-key#
MC → Configuration Center → Secret Management → OpenApi Secret Key → Private Key (UseePay_SK_xxx)3. x-app-id#
MC → Configuration Center → Secret Management → Domain Management, the website domain/App English name added here is the appId.The appId must be approved by UseePay before you can call the APIs.
