# Workflow
# Business Flow Lifecycle
The merchant creates a payment order through the
Create Payment Order
API;Hambit responds and returns the cashier page link;
The merchant displays the cashier page link to the consumer, and the consumer completes the payment on the cashier page;
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
- Initiate Request (with the merchant's AccessKey)
- System Status Check
- If the system service is abnormal ➜ Return:
SERVICE_UNAVAILABLE
- If the system service is abnormal ➜ Return:
- Request Header Validation
- If the request header format is incorrect ➜ Return:
HEADER_INVALID
- If the timestamp is inaccurate ➜ Return:
INACCURATE_TIMESTAMP
- If the request header format is incorrect ➜ Return:
- AccessKey Validation
- If the AccessKey does not exist or is incorrect ➜ Return:
ACCESS_KEY_INVALID
- If the AccessKey does not exist or is incorrect ➜ Return:
- AccessKey Permission Check
- If permission is insufficient ➜ Return:
ACCESS_KEY_PERMISSION_DENIED
- If permission is insufficient ➜ Return:
- 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
- If the access frequency is too fast ➜ Return:
- Parameter Format and HTTP Method Check
- If the parameters are incorrect ➜ Return:
PARAMS_INVALID
- If the parameters are incorrect ➜ Return:
- Signature Verification
- If the signature is incorrect ➜ Return:
SIGN_ERROR
- If the signature is incorrect ➜ Return: