Please try searching something.
After the Payment
You can create webhooks to set up callbacks and get notified about certain events from DECTA Gate. Once created, DECTA Gate will contact your servers whenever a hooked event fires. You do not need to do it for each individual order: setting up a webhook once will fire for all related events.
To receive callbacks as a Partner, you can select the “Partner webhooks” radio button in the “Webhooks type” section. After that, you need to select the connected merchants, for which you want to receive the callbacks, in the “Connected merchants” section. When a callback is received, the body of the callback will contain the merchant ID by which you can identify the particular connected merchant.
Supported Event Types
|an order has been issued
|customer has successfully paid for the order
|an error has occurred during the order payment
|funds for the order have been reserved
|an order has been cancelled; additionally, if funds were reserved for this order (
skip_capture = true), they will be returned
|an order has been issued and is being processed
|customer has viewed the invoice for this order
|merchant has refunded the invoice for this order
|merchant has reversed the invoice for this order
|an error occurred during the invoice refund
|a refund has been reversed
|an error has occurred during the process of initialization of a refund
|an error has occurred during the process of initialization of a reversal
|an error occurred during the invoice reversal
|an invoice refund is being processed
|an invoice reversal in being processed
|an order has been received
|an invoice has been rejected by the customer
|an order has expired
|a chargeback has been received
|a representation has been processed
|a retrieval request has been received
|a pre-arbitration has been received
|a good faith has been received
|a fraud advice has been received
|an OCT order has been issued
|an OCT transaction has been successfully executed
|an error has occurred during OCT transaction execution
|customer's card data has been saved
|customer's card data has been deleted
|customer's card data has been updated
You can alternatively set
true to hook all events to the same callback URL in one request.
Payment Response Analysis
Merchant Advice Code
merchant_advice_code provides additional information on a given transaction response decline. Merchant Advice Codes are supported by Mastercard to enable issuers to communicate insights to acquirers and merchants and thus let them optimize their subsequent retry strategies for declined transactions.
01 New account information available
02 Cannot approve at this time, try again later
03 Do not try again
04 Token requirements not fulfilled for this token type
21 Payment Cancellation
Merchant advice code values
21 are intended to send a clear message that a transaction should not be resubmitted for approval:
03is sent by issuers to indicate that an account is closed or fraudulent, and that no further approvals will be forthcoming;
21is sent by Mastercard Payment Cancellation Service (PCS) to indicate a cardholder canceled the agreement and instruct the merchant and acquirer to not retry the transaction.
In order to avoid unnecessary declines, pay close attention to the returned merchant advice code value.