Undo Approve Pool Payment

Service Address

/PaymentDealer/UndoApprovePoolPayment

Request Parameters

PaymentDealerAuthentication

Parameter	Explanation
DealerCode(string)	Dealer code issued by the Moka system
Username (string)	Api username given by Moka system
Password (string)	Api password given by Moka system
CheckKey (string)	The control key (DealerCode + "MK" + Username + "PD" + Password) is created by passing this information, combined as a String, through the SHA-256 hash algorithm. Click here to go to the trial screen.

PaymentDealerRequest

Parameter	Explanation
VirtualPosOrderId (string)	It is the transaction number information returned as a result of the payment transaction. It is the number returned with the name trxCode in 3D payments. Key: trxCode Value: ORDER-17131QQFG04026575
OtherTrxCode (string)	It is the unique transaction number given by the dealer when sending the payment transaction. If VirtualPosOrderId is given, you can send this number blank. Or if you want to use your own unique number, you can send this field and perform a transaction.

Sample Request (JSON)


{
	"PaymentDealerAuthentication": {
		"DealerCode": "xxx",
		"Username": "xxx",
		"Password": "xxx",
		"CheckKey": "ff4a6ee22aeafe87f7930f84b5ce2ad9655bfc6b5e430644a88c5b75a09fdee1"
	},
	"PaymentDealerRequest": {
		"VirtualPosOrderId": " ORDER-17131QMlH04026199",
		"OtherTrxCode": ""
	}
}

Successful Request Result

If the sent request data has been processed successfully in Moka, "Success" information is written in the "ResultCode" field of the return object . In the "Data" field, there is the transaction information that Moka returns to you. The "IsSuccessful" field in "Data" will return true. The "VirtualPosOrderId" field contains the code of the payment transaction. This process can be performed before the end of the day, before the dealer statement is created.

Successful Result Example


{
	"Data": {
		"IsSuccessful": true,
		"ResultCode": "",
		"ResultMessage": "",
		"VirtualPosOrderId": "ORDER-17131QMlH04026199"
	},
	"ResultCode": "Success",
	"ResultMessage": "",
	"Exception": null
}

Failed Request Result

If the sent request data could not be processed in Moka streams, the "ResultCode" field of the return object contains one of the error codes in the table below.
When an unexpected software error occurs, EX is written in the "ResultCode" field and the error message (Exception) is displayed in the "ResultMessage" field
In both cases, the "Data" object arrives as null.

ResultCode	Explanation
PaymentDealer.CheckPaymentDealerAuthentication.InvalidRequest	The CheckKey may be bad, or the object may be bad, or the JSON may be corrupt.
PaymentDealer.UndoApprovePoolPayment.DealerPaymentNotFound	No payment record was found for the information entered to be confirmed.
PaymentDealer.UndoApprovePoolPayment.OtherTrxCodeAndVirtualPosOrderIdNotMatch	OtherTrxCode and VirtualPosOrderId do not match.
PaymentDealer.UndoApprovePoolPayment.OtherTrxCodeOrVirtualPosOrderIdMustGiven	Incomplete data sent. OrderId or OtherTrxCode must be entered.
PaymentDealer.UndoApprovePoolPayment.PaymentNotApprovedYet	This payment has not yet been confirmed.
PaymentDealer.UndoApprovePoolPayment.PaymentIsNotPoolPayment	This payment is not a pool payment.
PaymentDealer.UndoApprovePoolPayment.PaymentNotApprovedYetForSubDealer	The pool payment for the sub-dealer has not yet been approved.
EX	An unexpected error has occurred

Example of Failed Result


{
	"Data": null,
	"ResultCode": "PaymentDealer.UndoApprovePoolPayment.PaymentIsNotPoolPayment ",
	"ResultMessage": "",
	"Exception": null
}