Skip to main content
POST
/
pkr
/
pay
/
apply
PKR Disbursement Application
curl --request POST \
  --url https://uat-interface.haipay.asia/pkr/pay/apply \
  --header 'Content-Type: application/json' \
  --data '
{
  "appId": 123,
  "orderId": "<string>",
  "amount": "<string>",
  "bankCode": "<string>",
  "accountNo": "<string>",
  "name": "<string>",
  "phone": "<string>",
  "email": "jsmith@example.com",
  "subject": "<string>",
  "birth": "<string>",
  "partnerUserId": "<string>",
  "sign": "<string>",
  "notifyUrl": "<string>",
  "body": "<string>",
  "idCard": "<string>"
}
'
{
  "status": "<string>",
  "error": "<string>",
  "msg": "<string>",
  "data": {
    "orderId": "<string>",
    "orderNo": "<string>",
    "sign": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://doc.haipay.net/llms.txt

Use this file to discover all available pages before exploring further.

​
Secret Key & Private Key (Generate Signature)

Body

application/json
​
appId
integer
required

Business ID (obtained from the backend, must pass the corresponding business ID according to the currency in URL)

​
orderId
string
required

Merchant Order Number

Maximum string length: 48
​
amount
string
required

Transaction Amount (accurate to two decimals; no punctuation allowed, e.g., “,” is forbidden)

Pattern: ^\d+\.\d{2}$
​
accountType
enum<string>
required

Account Type: EWALLET (E-wallet), BANK_ACCOUNT (Bank)

Available options:
EWALLET,
BANK_ACCOUNT
​
bankCode
string
required
​
accountNo
string
required

User’s bank account number or wallet account number

​
name
string
required

Recipient’s Name

​
phone
string
required

Real Mobile Number

​
email
string<email>
required

Real Email

​
subject
string
required

Payment Note (transaction title, product name, reason for payment)

​
birth
string
required

Date of Birth, format: yyyy-MM-dd

Pattern: ^\d{4}-\d{2}-\d{2}$
​
gender
enum<string>
required

Gender, allowed values: MALE, FEMALE, or OTHER

Available options:
MALE,
FEMALE,
OTHER
​
partnerUserId
string
required

Unique user identifier (e.g., userId), used for risk control system, must be valid, otherwise it will affect the transaction. Format: digits, letters, or symbols -~!@#$%&*()_.

Pattern: ^[A-Za-z0-9\-~!@#$%&*()_]+$
​
sign
string
required

Signature

​
notifyUrl
string<uri>

Callback URL

​
body
string

Note Details

​
idCard
string

ID card number

Response

200 - application/json
​
status
string

1: Normal, 0: Exception

​
error
string

Error code

​
msg
string

Error description

​
data
object
Last modified on May 22, 2026