Skip to main content

API INQUIRY STATUS

smilepayz teamsAbout 2 min

Request

The Transaction Status Inquiry API enables merchants to retrieve real-time transaction status information. Supported transaction types include Pay-in transactions, Payout transactions, and other transaction types.

Request Path:

sandbox: https://sandbox-gateway.smilepayz.com/v2.0/inquiry-status
production: https://gateway.smilepayz.com/v2.0/inquiry-status

Header Parameters

FieldRequiredTypeDescription
Content-TypeMStringHTTP content type specification
Fixed value: application/json
Required for proper request parsing
X-TIMESTAMPMStringISO 8601 datetime format with timezone offset
Format: yyyy-MM-ddTHH:mm:ss±HH:mm
Example: 2020-12-17T10:55:00-05:00
Note: Must be current server time within ±5 minutes
X-SIGNATUREMStringDigital signature for request authentication
See Signature Generation
X-PARTNER-IDMStringUnique merchant identifier assigned by the platform
Format: Alphanumeric string
Used for merchant authentication and transaction routing
Please enter merchantID

Body Parameters

FieldRequiredTypeDescription
tradeTypeMNumberTransaction type specification
Format: Integer value
Values: 1 (Payin), 2 (Payout)
Used to identify the transaction category for status inquiry
orderNoCString(32)Merchant transaction identifier
Format: Alphanumeric string
Maximum length: 32 characters
Used when querying by merchant's transaction reference
tradeNoCString(32)Internal transaction identifier
Format: Alphanumeric string
Maximum length: 32 characters
Used when querying by system's transaction reference

Important Requirement

Transaction Identifier Required: At least one of tradeNo or orderNo must be provided for transaction status inquiry

Example Body – Inquiry Status Request:

Content-type: application/json
X-TIMESTAMP: 2020-12-17T10:55:00-05:00
X-SIGNATURE: 85be817c55b2c135157c7e89f52499bf0c25ad6eeebe04a986e8c862561b19a5
X-PARTNER-ID: 20001

Response

HTTP Response

FieldRequiredTypeDescription
Content-TypeMStringHTTP response content type specification
Fixed value: application/json
Indicates JSON response format
X-TIMESTAMPMStringISO 8601 datetime format with timezone offset
Format: yyyy-MM-ddTHH:mm:ss±HH:mm
Example: 2020-12-17T10:55:00-05:00

Body Parameters

FieldRequiredTypeDescription
codeMStringAPI response status code indicating operation result
Format: Two-digit string
Success: "00", Error: Other codes
Used for programmatic response handling
messageMStringHuman-readable response status description
Format: UTF-8 encoded string
Provides detailed information about the operation result
Localized based on request language
tradeNoOStringInternal transaction reference number for system tracking
Format: System-generated alphanumeric string
Used for internal transaction management and support
tradeTypeONumberTransaction type specification
Format: Integer value
Values: 1 (Payin), 2 (Payout)
Indicates the transaction category that was queried
paymentMethodOStringPayment method used for transaction processing
Format: Predefined payment method codes
Examples: BCP, INTERBANK
Indicates the actual payment channel used
See Payment Method List
moneyOObjectTransaction amount details with currency specification
Contains confirmed transaction amount and currency
See Money Model
    currencyMStringISO 4217 currency code specification
Fixed value: PEN (Peruvian Sol)
Determines payment processing rules and settlement currency
    amountMNumberTransaction amount in smallest currency unit
Format: Integer value
Example: 20000 represents PEN 20000
Range: 100-999999999
statusOStringCurrent transaction processing status
Format: Predefined status codes
Examples: PROCESSING, SUCCESS, FAILED, CANCELLED
Indicates the current state of the transaction
See Status Model
remarkOStringAdditional transaction information or notes
Format: UTF-8 encoded string
Contains supplementary details about the transaction status
Content-type: application/json 
X-TIMESTAMP: 2020-12-17T10:55:00-05:00
Last update: