1. Online payments scenes
EVO Payment Gateway API
  • Gateway Integration
    • Version Record
    • CardInfoLink Gateway API Integration Guide
      • Online payments scenes
        • DCC
        • Tokenization
        • Payment
        • 3DS Authentication
        • Capture
        • Cancel
        • Refund
        • Merchandise Credit
        • Network token management
        • Cancel or Refund
        • Recapture
        • Recurring
      • Security Requirements and Message Header
        • Message protocol
        • Signature
        • Card Information Encryption
        • PIN Encryption
      • Offline payments scenes
        • Pre-authorization
        • Payment
        • Capture
        • Refund
        • Merchandise Credit
        • Cancel
        • Reversal
        • DCC
        • Recurring
      • Appendix
        • Response code
        • FAQ
        • Mastercard-Merchant Advice Code
        • Product Code
    • Offline API Specification
      • Payment
        • Payment
        • Payment
      • StandaloneCapture
        • StandaloneCapture
        • StandaloneCapture
      • Reversal
        • Reversal
      • MerchandiseCredit
        • MerchandiseCredit
        • MerchandiseCredit
      • Capture
        • Capture
        • Capture
      • TipsAdjustment
        • TipsAdjustment
        • TipsAdjustment
      • Cancel
        • Cancel
        • Cancel
      • MultipleCapture
        • MultipleCapture
        • MultipleCapture
      • FXRateInquiry
        • FXRateInquiry
        • FXRateInquiry
      • Refund
        • Refund
        • Refund
      • DCCToNon-DCC
        • DCCToNon-DCC
        • DCCToNon-DCC
      • ZPK
        • ZPK
      • Notification
        • Asynchronous notification for StandaloneCapture
        • Asynchronous notification for MultipleCapture
        • Asynchronous notification for Payment
        • Asynchronous notification for Capture
        • Asynchronous notification for Refund
        • Asynchronous notification for MerchandiseCredit
        • Asynchronous notification for Cancel
    • Online API Specification
      • PaymentMethod
        • PaymentMethod
        • PaymentMethod
        • PaymentMethod
        • PaymentMethod
      • Payment
        • Payment
        • Payment
        • Payment
      • Refund
        • Refund
        • Refund
      • Cancel
        • Cancel
        • Cancel
      • Capture
        • Capture
        • Capture
      • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
      • MerchandiseCredit
        • MerchandiseCredit
        • MerchandiseCredit
      • CancelOrRefund
        • CancelOrRefund
        • CancelOrRefund
      • TransactionHistoryInquiry Copy
        • TransactionHistoryInquiry
      • MultipleCapture
        • MultipleCapture
        • MultipleCapture
      • Cryptogram
        • Cryptogram
        • Cryptogram
      • StandaloneCapture
        • StandaloneCapture
        • StandaloneCapture
      • Recapture
        • Recapture
        • Recapture
      • AsynchronousNotification
        • Asynchronous notification for Multiple Capture
        • Asynchronous notification for PaymentMethod
        • Asynchronous notification for PaymentInstrument
        • Asynchronous notification for Payment
        • Asynchronous notification for Merchandise Credit
        • Asynchronous notification for Refund
        • Asynchronous notification for Capture
        • Asynchronous notification for Cancel
        • Asynchronous notification for Recapture
        • Asynchronous notification for Cryptogram
        • Asynchronous notification for Network Token update
        • Asynchronous notification for Standalone Capture
        • Asynchronous notification for Network Token authentication finished
      • HealthCheck
        • HealthCheck
      • FX Rate inquiry
        • FXRateInquiry
        • FXRateInquiry
  1. Online payments scenes

Merchandise Credit

Merchandise Credit#

If you want to refund funds without the original payment or after the refund validity period has expired, you need to call the POST Merchandise Credit interface.
The main process is as follows:
1.
When calling the POST Merchandise Credit interface, you need to include, but not limited to, the following parameters. For field details, refer to the API documentation:
paymentMethod.type: This indicates the payment method; use card for card transactions.
paymentMethod.card: This is a structure containing consumer card information and terminal information. This field is required when paymentMethod.type is card.
transAmount: This is a structure that contains the transaction amount and currency.
merchantTransInfo: This is a structure that contains the merchant order number.
pspInfo: This is a structure that contains card organization qualification information.
2.
Check the merchandiseCredit.status field in the EVO Cloud response. If the value of this field is Success, it indicates that the refund was successful; otherwise, you need to check result.code and result.message to find out the reason for the transaction failure.
3.
If you do not receive a response from EVO Cloud, you need to call GET Merchandise Credit to query the transaction result. When you receive the query response, you should also check the merchandiseCredit.status field to determine the transaction result, using the same judgment method as in step 2. If the transaction fails, you need to check merchandiseCredit.failureCode and merchandiseCredit.failureReason to find out the reason for the failure.
4.
If you included a webhook in the POST Merchandise Credit request and the transaction's merchandiseCredit.status is Success, you can also obtain the transaction result through asynchronous notification, where the eventCode is MerchandiseCredit. Again, you should check the merchandiseCredit.status field to determine the transaction result, using the same judgment method as in step 2.
Previous
Refund
Next
Network token management
Built with