Refund

It is applicable to both EC and In-Store Scenario.

If you want to return the funds to your user, for example, if the user returns an item, you need to refund the payment.

You can only refund a payment after it has already been captured. Payment not captured yet has to be cancelled instead. See chapter Cancel for more details.

You can refund either the full captured amount or a part of the captured amount. You can also perform multiple refunds partially, if the summary doesn't exceed the captured amount.

The maximum refund time frame is 365 days from when the payment is completed.

The number of partial refunds for a single payment order cannot exceed 50 times.

Multiple refund requests for the same payment order must be spaced at least 1 minute apart.

Make a refund request

Step 1: Make a refund request

When you get a capture result with payment.status with Captured, you can make an HTTP POST request from your server to EVO Cloud endpoint

/g2/v1/payment/mer/{sid}/refund

to refund the initial payment and specify the parameters below.

Query Parameter	Required	Description
`merchantTransID`	M	The `merchantTransInfo.merchantTransID` of the initial payment.

Body Parameter	Required	Description
`merchantTransInfo`	M	The reference for the refund, including a unique `merchantTransID` and `merchantTransTime` to specify the time you initiate the request.
`transAmount`	M	The currency and value of the refund payment. The value must follow the currency's minor unit.
`initiatingReason`	O	You can state the reason for this request in this field.
`webhook`	O	The URL to receive notification. Specify this to get the notification from EVO Cloud after the payment succeeds.
`metadata`	O	A self-defined reference information that you can specify in the request and will be echoed back in the response.

Here is an example of making a 10 USD refund:

If the request is successful, you will receive the response with a refund object and a payment object to show the status and related information for the refund and the original payment.

More details about refund object:

refund.status: The status of this refund, required. The value can be Success, Failed, or Received. If you get a refund.status with Received, you need to either make another HTTP GET request to get the final status of this refund (see Step 2 for more details), or wait for the notification webhook from EVO Cloud.

refund.transAmount: The currency and value of the refund, required. It is echoed back from your request.

refund.merchantTransInfo: The object that is a reference for the refund, generated by your host, required. It is echoed back from your request.

refund.evoTransInfo: The object that is a reference for the refund, generated by EVO Cloud, required. It contains evoTransID, evoTransTime, and traceNum (optional) and retrievalReferenceNum for some PSPs such as Visa or Mastercard.

refund.pspTransInfo: The object that is a reference for the refund, generated by PSP, optional. It contains pspTransID, pspTransTime, and authorizationCode. EVO Cloud forwards this information from PSP to your host if PSP returns.

refund.billingAmount and refund.billingFXRate: The user's billing currency and value of the capture, and the FX rate between refund.transAmount.currency and refund.billingAmount.currency, optional. EVO Cloud forwards this information from PSP to your host if PSP returns. This is applied to some E-Wallet payment when PSP conducts the currency conversion, or to some card payment when you enable the DCC feature. You can contact EVO Cloud account manager for more details.

refund.convertTransAmount and refund.convertTransFXRate: The currency and value calculated by EVO Cloud based on transAmount and the FX rate from transAmount.currency to a different currency when the transaction is sent out to PSP, and the FX rate between refund.transAmount.currency and refund.convertTransAmount.currency, optional. The FX rate will be provided if you enable currency conversion feature in EVO Cloud and this capture applies currency conversion. You can contact EVO Cloud account manager for more details.

Here is an example of a successful response:

Step 2: Retrieve the refund result

If you get a refund.status with Received and you don't use the notification webhook, you can retrieve the final result from EVO Cloud.

From your server, make an HTTP GET request to EVO Cloud endpoint

/g2/v1/payment/mer/{sid}/refund

Query Parameter	Required	Description
`merchantTransID`	M	The `merchantTransInfo.merchantTransID` of the initial refund.

The following example shows how you retrieve the refund result:

Here is an example of the GET response. The POST response is similar to the GET response.

Make a cancel instead

If you initiate a refund request and get the B0012 result.code, double check the original transaction status in payment.status in the response message. If it is authorised, it means the payment has NOT been captured yet thus you fail to refund the payment. In this case, you need to initiate a cancel instead. See chapter Cancel for more details.

Error handling

For HTTP POST request to EVO Cloud: It is suggested to wait at least 45 seconds after the request is sent to EVO Cloud. If you don’t get the response within the time frame, you need to retrieve the result from EVO Cloud. See Step 2 to initiate the request.
For HTTP GET request to EVO Cloud: You can initiate the request several times until get the result, and it is suggested to wait at least 45 seconds before you initiate the next request. If you still fail to get the result after several times of the request, you can initiate another cancel request instead.

Make a refund request#

Step 1: Make a refund request#

Step 2: Retrieve the refund result#

Make a cancel instead#

Error handling#

Make a refund request

Step 1: Make a refund request

Step 2: Retrieve the refund result

Make a cancel instead

Error handling