Push Order
Push orders from the merchant system to dedicated payment terminals (e.g., supported P3, MT919, and other devices). Supports QR scanning and card payments.
API Information
- Endpoint: POST
https://api.aimt-horizon.com/appPush/tradePush - Signature: Uses terminal_sn + terminal_key
Request Parameters
Call Example
Business Flow
PUSH_SUCCESS only acknowledges acceptance; it does not prove that the device displayed the order or that payment succeeded. Apply the response and state rules before updating the local order.
Key Rules
- out_trade_no maps to client_sn for query/server refunds and is unique within the merchant. PUSH_SUCCESS normally does not return sn.
- target_device_id must be pre-registered (scan the TUSN barcode on the terminal).
- After PUSH_SUCCESS, wait for payment and query. On timeout query the original order; do not reuse notification delays as an automatic push retry schedule.
- Always pair with the Query API for proactive status confirmation — do not rely solely on callbacks.
Acceptance Response
Error fields may be null or omitted. This response normally has no sn and does not prove device display or payment. Keep the original out_trade_no for queries; see errors for recovery.
