Online Pre-authorisation Payment APIs
- Online Pre-authorisation Payment APIs
Common APIs
Instructions on general integration with the development environment is available on https://sdk.qfapi.com/#introduction
For instance you may find the following useful before you start the integration:
- API credentials to be used
- testing environments
- signature generation for api requests
- Common error codes
You can also find common APIs that are also applicable to pre-authorisation payments:
Creating and capturing payments
Step 1: Create Pre-Authorisation Payment
The Pre-authorisation Step has to be achieved using the Payment Element component. For details of the integration, please refer to the respective sessions in the payment element documentation.
Step 2: Capture payment for pre-authorised transactions
Capture the amount booked by the customer in pre-authorised transactions
Endpoint : /trade/v1/authtrade
Method : POST
Header:
| Header name | Mandatory | Description |
|---|---|---|
X-QF-APPCODE | Yes | app code |
X-QF-SIGN | Yes | app key |
Request Parameters
| Attribute | Mandatory | Description |
|---|---|---|
txamt | Yes | transaction amount |
txcurrcd | No | transaction currency |
mchid | No | mchid, merchant id |
syssn | Yes | original transaction ID from pre-authorised payment |
Response Parameters
{
"sysdtm": "2024-02-26 15:04:12",
"paydtm": "2024-02-26 15:04:12",
"udid": "qiantai2",
"txcurrcd": "HKD",
"txdtm": "2024-02-26 07:04:11",
"txamt": "500",
"resperr": "交易成功",
"respmsg": "Capture received",
"out_trade_no": "",
"syssn": "20240226180500020000014116",
"orig_syssn": "20240226180500020000014079",
"respcd": "0000",
"chnlsn": "",
"cardcd": ""
}
Unfreeze amount for PRE-AUTHORISED transactions
Only the non-captured (
pre-authorised amount - captured amount) amount in the transaction can be unfreezed (released back to the customer). This action can only be done ONCE.
Endpoint : /trade/v1/unfreeze
Method : POST
Header:
| Header name | Mandatory | Description |
|---|---|---|
X-QF-APPCODE | Yes | app code |
X-QF-SIGN | Yes | app key |
Request Parameters
| Attribute | Mandatory | Description |
|---|---|---|
txamt | Yes | transaction amount |
txdtm | Yes | transaction time |
syssn | Yes | original transaction ID |
out_trade_no | Yes | original merchant order id |
mchid | No | mchid, merchant id |
Response Parameters
{
"sysdtm": "2024-02-26 17:17:05",
"paydtm": "2024-02-26 17:17:06",
"udid": "qiantai2",
"txcurrcd": "HKD",
"txdtm": "2024-02-26 09:17:05",
"txamt": "2000",
"resperr": "交易成功",
"respmsg": "Void received",
"out_trade_no": "",
"syssn": "20240226180500020000014222",
"orig_syssn": "20240226180500020000014220",
"respcd": "0000",
"chnlsn": "",
"cardcd": ""
}
Refunding Completed (CAPTURED) Transactions
For integration, please refer to the "Common API" section of the documentation. Please note that the syssn used in the refund transaction should correspond to the syssn returned upon the /authtrade request.
Notifications
General notification rule applies. For details, please refer to the Asynchronous Notifications section in the documentations.
Upon successful execution of the following actions, you should be able to receive a notification
- payment completion (captured)
- unfreeze funds
- refund
These notifications will follow the same format as below. For different notification, the value of the field notify_type will differ
| Action Completed | notify_type value |
|---|---|
| Payment Captured | payment |
| Unfreeze funds | unfreeze |
| Refund | refund |
{
"status": "1",
"pay_type": "800101",
"sysdtm": "2020-05-14 12:32:56",
"paydtm": "2020-05-14 12:33:56",
"goods_name": "",
"txcurrcd": "HKD",
"txdtm": "2020-05-14 12:32:56",
"mchid": "",
"txamt": "10",
"exchange_rate": "",
"chnlsn2": "",
"out_trade_no": "YEPE7WTW46NVU30JW5N90H7DHD94N56B",
"syssn": "20200514000300020093755455",
"cash_fee_type": "",
"cancel": "0",
"respcd": "0000",
"goods_info": "",
"cash_fee": "0",
"notify_type": "payment",
"chnlsn": "",
"cardcd": ""
}