MG+ K2 Common Wallet API Integration Manual
Breadcrumbs

Wallet Transactions

Wallet transactions represent financial transactions to and from the player’s wallet on the MG+ platform. MG+ will perform the internal balance transfers between products according to game launch requests.

Deposit/Withdraw

This flow is used to change the player’s balance on the MG+ platform.

The operation is idempotent. To ensure and enforce idempotency please create a unique identifier for every transaction from your side, and place this ID in the idempotencyKey field of the request body. This is not the same as externalTransactionId which is used for referencing the transaction on the agent's internal systems. The idempotencyKey is used to ensure that the transaction will only be executed once, even if multiple calls are received. This allows you to retry the same transaction while ensuring that no duplicated transfers will occur.

In the case of a transaction for which the agent did not explicitly provide an idempotencyKey, MG+ Common Wallet will use the externalTransactionId value as the idempotencyKey.

There are 2 transaction types available (see the DevPortal for the exact types of codes):

  • Deposit: Add funds of a specified amount to the player’s balance.

  • Withdraw:

    • In a scenario where the amount parameter is empty or omitted from the request - removes all available funds from the player’s balances across all products.

    • In a scenario where the amount specified is more than zero - MG+ will attempt to withdraw the requested amount (also known as a partial withdrawal).

    • Open bets (“bets on table”), bonus funds, and other “non withdrawable” funds will not be removed or affected.

image-20240417-082750.png

Wallet Transaction Details

In the response of the Deposit/Withdraw method, an identifier for the transaction is returned. You can query the full transaction details by using this Wallet Transaction Details operation.

The walletTransactionId is the ID returned in the response of the Deposit/Withdraw operation.

Another option is to query using idempotencyKey which is the transactionId that was sent by the operator in the Deposit/Withdraw request.

Retrieving transaction details using idempotencyKey is only possible within 24 hours of the transaction’s creation date.


image-20240417-083734.png