Refund (Server)
Initiate server-side refunds when enabled for the merchant, channel and payment method. Partial/repeated refunds, time limits and fee handling are configuration-dependent.
API Information
- Endpoint: POST
https://api.aimt-horizon.com/upay/v2/refund - Signature: Uses terminal_sn + terminal_key
- Time Limit: Determined by merchant and overseas channel configuration; not a universal three-month window.
Request Parameters
Response Key Fields
- Use a new ID for a new refund and retain it for the same operation; ensure generated IDs stay within 31 characters.
- Check net_amount and serialize refunds per order locally. A balance query is not a concurrency lock.
- Query with the original refund_request_no on unknown outcomes. Successful IDs may be rejected as duplicates; response replay is not guaranteed.
- Fee refunds, refunded fees and customer credit timing depend on the channel, merchant agreement and active configuration.
KPay QR Partial Refund Example
A new SGD 0.10 refund against a paid SGD 1.00 KPay QR order. First confirm the remaining refundable amount and that partial refunds are enabled for this channel and merchant. The body uses sn, or client_sn with the original order value when sn is unavailable, not out_trade_no.
extended is a JSON object containing refund_mode. For KPay, an absent mode or any mode other than refund requires the full remaining refundable amount. KPay bank-card payments do not support partial refunds even in refund mode. These rules apply to both server and MIS refunds; supplying the mode is necessary but does not enable the channel capability.
Do not submit both this and a MIS refund for the same operation. For REFUND_IN_PROGRESS / REFUND_ERROR, query the original refund ID; only confirm completion after verifying that transaction. Customer credit timing remains channel-dependent.
