Skip to main content

Payment Request

Request​

API URL: /merchant/v2/{GUID}/payment

Note

{GUID} Obtained from the merchant backend (API Docking -> GUID)

✅ Required ⭕ Optional ❌ Not used

HeaderContentDescription
Content-Typetext/plain
X-Transaction-Signature{transaction_signature}Please refer to Transaction Signature
ParamTypeRequiredSignDescription
user_idString✅✅Merchant identification
order_idString✅✅Payment order Id of merchant system. The order id should be unique.
amountString✅✅Transaction amount (Support up to 6 decimal places)
currencyString✅✅Please refer to Support Channel
channelString✅✅Please refer to Support Channel
timestampInteger✅✅Request timestamp (10 digits), If the time difference is allowed to be 5 seconds, it will fail.
detailsDetails⭕❌Details object depends on channel
callback_urlURL⭕❌The url to receive callback request from PTS when transaction complete.
redirect_urlURL⭕❌When the payment process finished, the client will be redirected to this URL.
error_urlURL⭕❌When the payment process failed, the client will be redirected to this URL.
remarkString⭕❌Remark
signString✅❌Signature string. Please refer to Data Signature and Verification

Details Object

ParamTypeDescription
phoneStringValidate phone number format, ex: 09123456789.
emailStringValidate email format.
first_nameStringClient's first name, cannot contain numbers. Max length: 20 characters, values exceeding this limit will be truncated.
last_nameStringClient's last name, cannot contain numbers. Max length: 20 characters, values exceeding this limit will be truncated.

Response​

There are three types of payment response methods.

tip

You should notify FTIPH customer service to configure this for you to match actual usage situation.

Redirect​

Return a javascript code with redirect_url, the user will be redirected to actual payment webpage automatically.

HTML​

Return a html input form to user with automatically submit javascript. You should forward entire response content to user and make sure html and javascript workable.

JSON​

Return request result in JSON format (when response code=1000)**

ParamTypeRequiredSignDescription
user_idString✅✅Merchant identification
order_idString✅✅Payment order Id of merchant system. The order id should be unique.
transaction_idString✅✅FTIPH transaction id
channelString✅✅Please refer to Support Channel
submit_currencyString✅✅Submit currency
submit_amountFloat✅✅Submit amount (Support up to 6 decimal places)
accept_currencyString✅✅The currency real paid
accept_amountFloat✅✅Paid amount of accept currency (Support up to 6 decimal places)
exchange_rateFloat✅✅Exchange rate
pay_urlURL✅✅The webpage which to pay the amount
wallet_addressString⭕❌Crypto exclusive, if need, please inform customer service staff
expired_atInteger⭕❌Crypto exclusive, if need, please inform customer service staff
qr_codeString⭕❌QR code for payment (QRPH, INSTAPAY channels only)
signString✅❌Signature string. Please refer to Data Signature and Verification

Response Example​

{
"code": "1000",
"message": "Accepted",
"data": {
"user_id": "28",
"order_id": "20240328184666",
"transaction_id": "P282321321321312389",
"channel": "MAYA",
"submit_currency": "PHP",
"submit_amount": 800,
"accept_currency": "PHP",
"accept_amount": 800,
"exchange_rate": 1,
"sign": "asiuyasoufhuioqpirjhiAUMwTgux9fTH53jNzNR..."
}
}