Specification Overview

Scope

This document provides an explanation of the integration of the BasicEx payment message exchange technical specifications and security requirements. It is intended for use by system analysts, system designers, system developers, and testers of merchants/channel partners.

This document provides detailed information on the working methods and development process of the BasicEx payment open API interface, covering topics such as integration preparation, communication methods, security requirements, and message structure. It can assist developers in quickly integrating with the BasicEx payment system and serve as a reference manual for interface parameters and their types.

Copyright Statement

This document is the property of BasicEx Payment. As the end user of this system, you have the right to use this document, but without written permission from our company, you are not allowed to lend, transfer, or publish this document to any third party.

Integration Preparation

1. Becoming a Merchant

Before registering as a merchant, ensure that you have registered as a BasicEx wallet user and have completed the advanced authentication. Otherwise, your application cannot proceed. After submitting the merchant application, wait for BasicEx Payment operations personnel to review the merchant's qualifications. Once confirmed as reliable, BasicEx Payment will grant the merchant access to their payment system.

2. Technical Integration

You can refer to the provided BasicEx Payment API/SDK and DEMO examples to complete the interface development. Currently, only a Java version is available, but you can integrate with other languages according to your needs.

3. Integration Testing

Contact the relevant integration personnel of BasicEx Payment to obtain test-related parameters, keys, etc., and perform interface integration testing in the testing environment.

4. Production Use

After the merchant has completed testing and confirmed that the code is correct, contact the relevant personnel at BasicEx Payment to obtain the formal merchant ID, configuration key, interface address, and other production parameters. Then, agree on a production verification schedule for deployment.

Technical Support

For any questions regarding integration, testing, production, or any other issues related to BasicEx Payment, please contact the website's customer service or the technical support department.

Communication Method

Communication is conducted over the internet using the standard HTTPS protocol, with requests sent to the BasicEx Payment gateway via the POST method. HTTPS uses the HTTP/2 protocol and does not support HTTP/1.1 or HTTP/1.0.

Message Description

1. Submissions are made using the POST method. Except for cashier payments (which are front-end transactions and are automatically redirected to the BasicEx cashier page through form submission), all other transaction messages use the JSON format (including asynchronous notifications), with the Content-Type set to application/json.

2. Parameter names and fixed values specified in the interface specification must be exactly matched (case-sensitive).

3. Spaces in the submitted data are considered valid characters and will be accepted. Merchants should be careful to control unnecessary spaces during development.

4. The messages use the HMAC-SHA512 signature method to sign and verify transaction data. Merchants need to obtain and configure keys from the merchant platform.