1. 06 Webhook
YUNMO-API
  • API
    • 01 Preparations
      • 1.1 Protocol Specification
      • 1.2 Appendix
      • 1.3 Login authorization
    • 02 Customer
      • 2.1 Create Customer
      • 2.2 Query customer information
    • 03 KYC
      • 3.1 Submit KYC Information
      • 3.2 Get Liveness H5 Link
      • 3.3 Query Liveness Results
      • 3.4 Querying KYC Status
    • 04 Card
      • 4.01 Query available card samples
      • 4.02 Create virtual card
      • 4.03 Query customer card
      • 4.04 Customer card balance adjustment
      • 4.05 Customer card top-up order query
      • 4.06 Query customer card detail
      • 4.07 Destroy card
      • 4.08 Freeze card
      • 4.09 Unfreeze card
      • 4.10 Query card PAN-HTML
      • 4.11 Query card PAN
      • 4.12 Query card PIN
      • 4.13 Update phone number
      • 4.14 Update email
      • 4.15 Update card limit
      • 4.16 Bind physical card
      • 4.17 Activate physical card
    • 05 Transaction
      • 5.1 3DS Authorization Confirmation
    • 06 Webhook
      • 6.1 Notification Specification
      • 6.2 KYC callback
      • 6.3 3DS Notification
      • 6.4 Transaction Notification
    • Schemas
      • GetTokenVo
      • ApiResponse«GetTokenVo»
      • ApiRequest«GetTokenDto»
      • ApiRequest«CreateCardDto»
      • ApiRequest«CardRechargeDto»
      • ApiRequest«RechargeOrderQueryDto»
      • ApiRequest«CardDetailDto»
      • ApiRequest«CardStatusUpdateDto»
      • ApiRequest«CardPanHtmlDto»
      • ApiRequest«CardPanEncryptDto»
      • ApiRequest«CardQueryPinDto»
      • ApiRequest«CardPhoneDto»
      • ApiRequest«CardEmailDto»
      • ApiRequest«CardTradeLimitDto»
      • ApiRequest«BindCardDto»
      • ApiRequest«ActiveCardDto»
      • ApiRequest«CustomerAddDto»
      • ApiRequest«CustomerQueryDto»
      • ApiRequest«GetLivenessUrlDto»
      • ApiRequest«GetLivenessResultDto»
      • ApiRequest«KycDto»
      • ApiRequest«Confirm3DSDto»
      • CardSampleInfoVo
      • ApiRequest«Object»
      • ApiRequest«CardQueryDto»
      • ApiRequest«SubmitKycDto»
      • CreateCardDto
      • GetTokenDto
      • CardBenefitVo
      • ApiResponse«List«CardSampleInfoVo»»
      • CreateCardVo
      • ApiResponse«CreateCardVo»
      • CardQueryVo
      • ApiResponse«List«CardQueryVo»»
      • CardQueryDto
      • CardRechargeVo
      • ApiResponse«CardRechargeVo»
      • CardRechargeDto
      • RechargeOrderQueryVo
      • ApiResponse«RechargeOrderQueryVo»
      • RechargeOrderQueryDto
      • CardDetailVo
      • ApiResponse«CardDetailVo»
      • CardDetailDto
      • ApiResponse«Boolean»
      • CardStatusUpdateDto
      • ApiResponse«String»
      • CardPanHtmlDto
      • ApiEncryptVo
      • ApiResponse«ApiEncryptVo»
      • CardPanEncryptDto
      • CardQueryPinDto
      • CardPhoneDto
      • CardEmailDto
      • CardTradeLimitDto
      • BindCardVo
      • ApiResponse«BindCardVo»
      • BindCardDto
      • ActiveCardDto
      • CustomerAddVo
      • ApiResponse«CustomerAddVo»
      • CustomerAddDto
      • CustomerQueryVo
      • ApiResponse«CustomerQueryVo»
      • CustomerQueryDto
      • LivenessUrlQueryDto
      • ApiResponse«LivenessUrlQueryDto»
      • GetLivenessUrlDto
      • LivenessResultQueryDto
      • ApiResponse«LivenessResultQueryDto»
      • GetLivenessResultDto
      • SubmitKycDto
      • InHouseKycInfoVo
      • ApiResponse«InHouseKycInfoVo»
      • KycDto
      • Confirm3DSDto
  1. 06 Webhook

6.1 Notification Specification

Webhook#

The notification address is the callbackUrl configured in the unified merchant platform. If YUNMO is not specified, no notifications will be sent. For asynchronous notification interfaces, merchants must verify the signature to ensure transaction security.

1.Interface Specification#

Merchants must respond with “OK” when receiving YUNMO result notifications. If a merchant fails to return “OK” YUNMO will continue sending notifications, up to a total of 10 times.
Note: To avoid ambiguity in parameter verification, all fields in the notification parameters are of type String. For example, the amount should be specified as “20.00”. When verifying the signature, use “20.00” for verification, not 20.
Request Method:POST
Request Type:application/json

2.Notification Parameters#

paramrequiredtypedescription
merchantNoYStringAssigned merchant ID
requestTimeYLongResponse Timestamp
versionYStringInterface Version
nonceYString16-character random string
signYStringSignature
eventTypeYStringEvent Type
eventNameYStringEvent Name
dataYObjectCallback parameter details. For specific details, refer to the corresponding callback documentation.
通知示例
{
	"sign": "6bf642b5fc7b10a6eae3b8ab5e7bbea2",
	"nonce": "TW4P54uVulwRoc2y",
	"merchantNo": "BU078255558",
	"requestTime": 1770712296681,
	"eventType": "KYC",
	"eventName": "kyc_status",
	"version": "v1.0",
	"data": {
		"customerId": "test001",
		"auditState": 2,
		"auditRemark": "Biometric verification failed"
	}
}
Modified at 2026-02-12 03:36:37
Previous
5.1 3DS Authorization Confirmation
Next
6.2 KYC callback
Built with