Workflow

Business Flow Lifecycle

1. The merchant creates a payment order through the Create Payment Order API;

2. Hambit responds and returns the cashier page link;

3. The merchant displays the cashier page link to the consumer, and the consumer completes the payment on the cashier page;

4. After the consumer completes the payment, they are redirected to the link provided by the merchant. Hambit notifies the transaction result of the order through the Payment Callback.

   

Technical Parameters Integration Process

1. Initiate Request (with the merchant's AccessKey)

2. System Status Check

   • If the system service is abnormal ➜ Return: SERVICE_UNAVAILABLE

3. Request Header Validation

   • If the request header format is incorrect ➜ Return: HEADER_INVALID

   • If the timestamp is inaccurate ➜ Return: INACCURATE_TIMESTAMP

4. AccessKey Validation

   • If the AccessKey does not exist or is incorrect ➜ Return: ACCESS_KEY_INVALID

5. AccessKey Permission Check

   • If permission is insufficient ➜ Return: ACCESS_KEY_PERMISSION_DENIED

6. QPS Rate Check & IP Permission Check

   • If the access frequency is too fast ➜ Return: ACCESS_SPEED_TOO_FAST

   • If the IP is unauthorized ➜ Return: IP_LIMITED_PERMISSIONS

7. Parameter Format and HTTP Method Check

   • If the parameters are incorrect ➜ Return: PARAMS_INVALID

8. Signature Verification

   • If the signature is incorrect ➜ Return: SIGN_ERROR