Failed transactions can be dealt with in two ways:
-
Through automatic patching (also known as the Retry Feature)
-
Or by manual patching
By default, all new integrations will use manual patching method.
To enable the automatic patching method, please contact your Account or Integrations Manager.
|
Automatic Patching |
Manual Patching |
|---|---|
|
No additional development required on the operator side. |
The operator needs to deploy a service to regularly fetch the list of failed transactions from MG+. |
|
Upon wager (debit) failure, a rollback transaction is sent to the agent’s rollback callback method. |
Upon wager (debit) failure, a rollback transaction is placed in the failed transactions queue for the agent to process. An agent will check if this debit needs to be refunded to the player or not, then confirm the transaction by patching it. |
|
Upon payout (credit) failure, a credit transaction is sent to the agent’s updatebalance callback method |
Upon payout (credit) failure, a credit transaction is placed in the failed transactions queue for the agent to process. An agent will check if the player’s wallet needs to be funded or not, then confirm the transaction by patching it. |