Skip to main content
This page documents the common data structures and types used across all v2 OpenAPI endpoints.

Core Models

Amount

Represents a monetary amount in minor units.
FieldTypeRequiredDescription
currencyStringYesThree-character ISO-4217 currency code (max 3 chars)
valueStringYesPositive integer in smallest currency unit (max 16 chars)
{
  "currency": "EUR",
  "value": "1000"  // Represents €10.00
}
The value field represents the amount in the smallest unit of the currency. For EUR, 1000 = €10.00. For currencies without decimal places, use the full amount.

Result

Standard response result object included in all API responses.
FieldTypeRequiredDescription
resultStatusStringNoStatus code: S (success), F (failed), U (unknown), A (accepted)
resultCodeStringNoResult code identifier (max 64 chars)
resultMessageStringNoDetailed description of the result (max 256 chars)
{
  "resultStatus": "S",
  "resultCode": "SUCCESS",
  "resultMessage": "Success"
}

Order

Contains order and transaction details.
FieldTypeRequiredDescription
orderDescriptionStringYesDescription for user consumption records (max 256 chars)
orderCreateTimeDatetimeNoOrder creation time, ISO 8601 format (max 32 chars)
merchantMerchantNoMerchant information object
buyerBuyerNoBuyer information (optional for pre-creation)
envEnvNoEnvironment/device information
extendInfoStringNoExtended data for special use cases (max 2048 chars)
{
  "orderDescription": "Premium subscription - Monthly",
  "orderCreateTime": "2024-01-10T12:00:00+01:00",
  "merchant": {
    "merchantName": "Acme Store",
    "store": {
      "externalStoreId": "STORE_001"
    }
  }
}

Merchant

Merchant business information.
FieldTypeRequiredDescription
merchantMCCStringNoMerchant category code (max 32 chars)
merchantNameStringNoMerchant name (max 256 chars)
storeStoreNoStore details object

Store

Physical or virtual store information.
FieldTypeRequiredDescription
externalStoreIdStringNoExternal store identifier (max 64 chars)
storeNameStringNoStore name (max 256 chars)
storeMCCStringNoStore business category code (max 32 chars)
storeTerminalIdStringNoStore terminal unique identifier (max 64 chars)
storeOperatorIdStringNoStore operator unique identifier (max 64 chars)

Buyer

Buyer/customer information.
FieldTypeRequiredDescription
referenceBuyerIdStringNoBuyer unique identification (max 64 chars)
buyerNameUserNameNoBuyer name object
buyerPhoneNoStringNoMobile phone number (max 24 chars)

UserName

User name components.
FieldTypeRequiredDescription
firstNameStringNoFirst name (max 32 chars)
lastNameStringNoLast name (max 32 chars)

Env

Environment and device information for risk assessment.
FieldTypeRequiredDescription
terminalTypeStringNoTerminal type (enum: TerminalType)
osTypeStringNoOperating system type (enum: OSType)
userAgentStringNoUser agent string (max 1024 chars)
deviceTokenIdStringNoDevice token identifier (max 128 chars)
clientIpStringNoClient device IP address (max 128 chars)
cookieIdStringNoUser cookie identifier (max 128 chars)
storeTerminalIdStringNoStore terminal identifier (max 64 chars)
storeTerminalRequestTimeStringNoStore terminal request time (max 32 chars)
extendInfoStringNoExtended information (max 2048 chars)

RedirectActionForm

Redirect URL information for authorization flows.
FieldTypeRequiredDescription
redirectUrlStringYesRedirect URL (max 2048 chars)

ContentTemplate

Template for notification content.
FieldTypeRequiredDescription
templateParametersMapNoJSON key-value pairs for template variables
languageStringNoRFC 1766 format (e.g., zh-CN, en-US)

VoidDetail

Void transaction details.
FieldTypeRequiredDescription
voidIdStringNoVoid request unique identifier (max 64 chars)
voidAmountAmountNoPayment void amount object
voidedTimeDatetimeNoVoid processing time (ISO 8601 format)
voidSourceStringNoVoid request source (enum: VoidSource)
voidStatusStringNoCurrent void status (enum: VoidStatus)

Enumerations

OSType

Operating system types.
ValueDescription
IOSiOS operating system
ANDROIDAndroid operating system

TerminalType

Terminal/client application types.
ValueDescription
MINI_APPMini program application
APPMobile application
WEBBrowser web application
WAPMobile WAP browser
SYSTEMSystem/backend call

VoidSource

Source of void request.
ValueDescription
MERCHANTMerchant-initiated void
TIMEOUTTimeout-triggered void
LAST_CONFIRMLast confirmation void

VoidStatus

Status of void operation.
ValueDescription
INITInitial status
SUCCESSVoid successfully processed
FAILEDVoid processing failed
PENDINGAwaiting manual handling

ResultStatus

Standard result status codes.
ValueDescription
SSuccess - Operation completed successfully
FFailed - Operation failed
UUnknown - Result unknown, may need retry or inquiry
AAccepted - Request accepted, processing asynchronously

Date and Time Format

All datetime fields follow the ISO 8601 standard:
YYYY-MM-DDTHH:mm:ss.sssZ
YYYY-MM-DDTHH:mm:ss+HH:mm
Examples:
  • 2024-01-10T12:00:00Z (UTC)
  • 2024-01-10T13:00:00+01:00 (CET)
  • 2024-01-10T12:00:00.123Z (with milliseconds)
Request-Time headers require at least second-level precision. Millisecond precision is recommended for better accuracy.