Get Data From Back End - minglepay/paystory_global GitHub Wiki
-
✔ Function of delivering result data from back-end is performed only when a payment or cancellation is successfully completed.
-
✔ Payment result with response indicating processing failure from merchant can be retransmitted up to ten times within one-hour period, at intervals determined by merchant.
-
✔ Notifications of successful payments are sent to the URL registered in the [
Account Management]-[Payment Configuration]-[Payment Notification] menu in the ⚡merchant admin system. -
✔ In the [
Payment Notification] menu, you can set the success cretiria for receiving payment success result to customize the success processing accroding to your merchant environment.- If you set “Receiving success criteria” to “json” in the [
Payment Notification] menu, the success response '{“resultCd”:”0000”}' is only output when the payment data DB processing is successful on the notification URL. If not, the payment result will be retransmitted until the success response is printed.
- If you set “Receiving success criteria” to “http” in the [
Payment Notification] menu, ifPayStoryreceives an HTTP 2xx code(Success Code) status code after calling the notification URL, it assumes that the merchant has successfully processed the payment result and does not retransmit it any more.
- If you set “Receiving success criteria” to “json” in the [
HTTPS POST content-type : application/x-www-form-urlencoded; charset=utf-8
Data Type : String
| Parameter | Description | Max Size (Byte) |
|---|---|---|
resultCd |
Payment result code 3001: success, Others failures (In case of card payment ) | 10 |
resultMsg |
Payment result message | 100 |
goodsName |
Goods name | 100 |
ordNo |
Merchant order ID | 40 |
goodsAmt |
Payment amount | 20 |
appNo |
Authorization number | 30 |
appDtm |
Authorization date (yyyymmddhhmmss) | 14 |
ordNm |
Buyer name | 30 |
cancelYN |
Transaction type N : authorization, Y : Cancellation |
1 |
fnNm |
Card issuer name | 20 |
payMethod |
Payment method (“CARD” fixed) | 4 |
authType |
Auhtentication Type (01:keyin, 02:ISP, 03:MPI) | 2 |
appCardCd |
Card issuer code | 2 |
acqCardCd |
Card acquirer code | 2 |
quota |
Installment months e.g. 00 (direct), 03 (3 months). | 2 |
cardNo |
Card number (6 digits in the middle of full number masked) | 20 |
mid |
Merchant ID | 10 |
tid |
Transaction ID | 30 |
ediDate |
Payment Request date (yyyymmddhhmmss) | 14 |
mbsReserved |
Reserved field for merchant | 255 |
cpCd |
Card code | 2 |
currencyType |
currency code (KRW, USD) | 3 |
mbsUsrId |
Merchant user Id | 20 |
hashStr |
Hash256 encrypted value Sha256 (mid + ediDate + goodsAmt + merchant key) | 256 |