Skip to main content

Request

smilepayz teamsAbout 2 min



Tips

Welcome to the smilepayz Pay API documentation page. Integrate this API to start transacting using smilepayz on your
site.
smilepayz API is a third party API that functions as a payment gateway system.
smilepayz API helps you in terms of receiving online payments from your customers.
With just one smilepayz API, you can accept payments from a variety of available payment methods.

Tips

smilepayz API is a restful Web service, which enables programmatic communication between you and smilepayz
paymentsystem. You can easily integrate to any of your internet-capable system (Web, App, PoS, IoT, etc.) and can fully
build & customize the payment UI, on your side without smilepayz hosted payment UI. smilepayz Core API is suitable for
medium size as well as large size businesses.


Tips

HTTP Request

Header Format Structure Components – inquiry status

Service Code92
NameAPI Inquiry Status
Version1.0
HTTP MethodPOST
Path.../{version}/inquiry-status

Tips

Header Parameters

API Header Format Structure for inquiry status:

AreaFieldAttributeTypeDescription
HeaderContent-TypeMandatoryStringString represents indicate the media type of the resource (e.g. application/json, application/pdf)
AuthorizationMandatoryStringString starts with keyword “Bearer ” followed by access_token (e.g. Bearer eyJraWQiOi...Jzc29zIiiY)
X-TIMESTAMPMandatoryStringMerchant's current local time in yyyy-MM-ddTHH:mm:ssTZD format
X-SIGNATUREMandatoryStringRepresents signature of a request.Identify Signature Type used
ORIGINOptionalStringOrigin Domain www.yourdomain.comopen in new window
X-PARTNER-IDMandatoryStringMerchant_ID. Unique ID for a partner as merchant_id
X-EXTERNAL- IDMandatoryStringNumeric String. Reference number that should be unique in the same day
CHANNEL-IDMandatoryStringFixed value: 95221

Notes: X-SIGNATURE

  1. HMAC_SHA512 (merchantSecret, stringToSign) with formula stringToSign = HTTPMethod +”:“+ EndpointUrl +":"+
    AccessToken +":“+ Lowercase(HexEncode(SHA-256(minify(RequestBody))))+ ":“ + TimeStamp
  2. Complete URL endpoint including all parameters in related URL (Relative path, example: Path in general information
    of each API service)
  3. For the minify(Request Body) parameter, in case there is no Request Body then an empty string is used.

Tips

Example Header – inquiry status Request:


POST .../v1.0/inquiry-status HTTP/1.2

Content-type: application/json
Authorization: Bearer gp9HjjEj813Y9JGoqwOeOPWbnt4CUpvIJbU1mMU4a11MNDZ7Sg5u9a"
X-TIMESTAMP: 2020-12-17T10:55:00+07:00
X-SIGNATURE: 85be817c55b2c135157c7e89f52499bf0c25ad6eeebe04a986e8c862561b19a5
ORIGIN: www.hostname.com
X-PARTNER-ID: 10001
X-EXTERNAL-ID: 41807553358950093184162180797837
CHANNEL-ID: 95221

Body Parameters



AreaFieldAttributeTypeDescription
BodytradeTypeMandatorynumbertradeType payin/payout Refer to Data Trade Type
orderNoMandatoryString(32)String merchant transaction Unique ID

Tips

Example Body – inquiry status Request:


POST .../v1.0/inquiryStatus HTTP/1.2

Content-type: application/json
Authorization: Bearer gp9HjjEj813Y9JGoqwOeOPWbnt4CUpvIJbU1mMU4a11MNDZ7Sg5u9a"
X-TIMESTAMP: 2020-12-17T10:55:00+07:00
X-SIGNATURE: 85be817c55b2c135157c7e89f52499bf0c25ad6eeebe04a986e8c862561b19a5
ORIGIN: www.hostname.com
X-PARTNER-ID: 82150823919040624621823174737537
X-EXTERNAL-ID: 41807553358950093184162180797837
CHANNEL-ID: 95221

{
    "tradeType": 1,
    "orderNo": "M-2373282627238237"
}

Last update: