Getting Started
AiMT Singapore
Push payment integration for financial institutions, independent software vendors (ISVs), and payment service providers in Singapore. Push orders to dedicated payment terminals and integrate payment, refund, query, settlement, and cancellation operations with AiMT.
🔗 POST /appPush/tradePush 🌐 HTTPS / JSON / UTF-8 🔐 MD5 / SHA256 SignatureSolution Overview
Five core capabilities enabling end-to-end payment operations
Scope and Capabilities
For Singapore checkout systems pushing orders to enabled payment devices through AiMT. Your server signs requests, stores orders and confirms outcomes; the payment device displays and executes payments. API availability does not imply every channel, device or firmware supports every capability.
Checked: 2026-10-22 · Region: Singapore · Protocol: V2 signing · Sources and open items
Payment Methods and Environments
pay_type=1 is bank card, 2 is QR and 6 is customer-scans-merchant QR (C-scan-B). Use only enabled values. Reference value 3 is Huabei, not generic instalments; 4/5 are preauthorization. These values do not establish Singapore availability. Preauthorization cannot be freely combined with other types, and some firmware has different 2/6 mappings. Verify brands, SGD configuration, partial/repeated refunds, reversals and preauthorization for the actual merchant and device.
Obtain the test endpoint, merchant/device, platform public key, payment instruments and capability list before testing. The supplied Singapore endpoint https://api.aimt-horizon.com must not be assumed to be a non-charging sandbox. Separate test and production credentials, public keys and callback configuration.
Complete a First Test Payment
Download Python exampleComplete setup and caller activation first. Push each new business order once. Running push submits an actual API request to the configured environment.
- Configure. Load
AIMT_BASE_URL,AIMT_TERMINAL_SN,AIMT_TERMINAL_KEY,AIMT_TARGET_DEVICE_IDandAIMT_NOTIFY_URLfrom secure configuration/environment variables. SetAIMT_ORDER_ID, unique within the merchant and 1-32 ASCII letters/digits. Deploy the notification handler first. - Confirm testing scope. Verify the test merchant, SGD, device and enabled
pay_type=1,2,6before settingAIMT_TEST_CONFIRMED=1. The example submits"100", SGD 1.00. This local safeguard does not turn production into a sandbox. - Run the signature self-test, then push once. The Python 3 example uses only the standard library. Self-test needs no network. Expect
result_code="200"andbiz_response.result_code="PUSH_SUCCESS"; do not fulfill yet. - Pay on the device. Check the amount and order. Retain device evidence, await the server notification and run query with the same
AIMT_ORDER_ID. - Confirm. Match
client_sn, amount andPAYMENT / SUCCESS / PAID; persistsnandtsn. SetAIMT_ORDER_SNfor subsequent queries by platform ID. Follow recovery rules for unknown outcomes. - Verify refunds. Use the enabled refund route and retain the refund ID. Set
AIMT_REFUND_REQUEST_NOand query that specific refund. Keep payment and refund records separate.
Python 3: Complete Signing, Push and Query Example
Download aimt_example.py using the link at the start of this section. This example verifies ordinary push/query responses only, not activation, check-in or inbound notifications; those have separate rules. Output is limited to redacted identifiers and states.
Complete Python Source
- One collection only; push, query and notification identify the same order.
- Notification verification and the plain-text acknowledgment work; query and notification do not duplicate fulfillment.
- A device success screen or
PUSH_SUCCESSalone is insufficient.
Prerequisites — Before Activation
Complete these steps before calling any API
Submit Business Information
Provide the following to technical support:
Obtain Developer Parameters
After approval, you will receive:
Merchant Onboarding & Activation Code
Onboard merchants, generate store_sn, obtain activation codes (code), plan device_id naming, and implement signature algorithms (MD5 for API calls, RSA SHA256WithRSA for callback verification).
