A deposit is a transfer of a specified amount of money TO an identity account.
Request
| PARAMETER | DESCRIPTION | FORMAT | EXAMPLE |
| partnerID | Identification of Integration casino in the customer system | GUID | D61A14AE-0A0C-464B-B7AB-5900BE7462F9 |
| sign | Parameters: partnerID, name, amount, currency, reference, sessionID, gameRoundID, gameModule, type, fgbCampaignCode, isRoundEnd (for more information see Creating Data Sign) | string (64) |
5E0A0349AE36AD67CD21D891AB124CCE 8CC4171C5BD7EF5B 26FCA86DB71F500A |
| name |
Identity name Identity name name of user in partners system |
string (48) | Player1 |
| amount | Transaction amount the value can have a maximum of 2 decimal places. | decimal (2) | 3.40 |
| currency | Player’s currency in ISO 4217 format. | string (10) | EUR |
| reference | Reference for the transaction. It must be a unique identifier. | long | 123456789 |
| sessionID | The ID of the session that is associated with the deposit. This parameter is optional, the default value is 0. | long | 123456789 |
| gameRoundID | Game round ID. Optional, default is 0. | long | 123456789 |
| gameModule |
Game module key. This parameter is optional, the default value is an empty string. |
string (50) |
VS243Crystal_TNP |
| type | Types of deposit:
|
int | 0 |
| fgbCampaignCode |
Free Games Bonus campaign ID. This parameter is optional, the default value is NULL. But if the transaction is made during an FGB campaign it will contain the identification code of that campaign. |
string (32) | campaign1 |
| isRoundEnd | This parameter is optional, the default value is NULL, check with Support on what to include in the request. | String (10) | True/False |
Request example:
REST JSON
POST https://casino.com/THE/WalletService/Deposit HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Content-Length: 123456
Host: staging.tomhorngames.com
{
"partnerID" : "JsonTestCustomer1",
"sign" : "B62C0C860E7A20D139C2D38814C80FC1F23BA3E322DB17DE21EAF16D4D11360D",
"name" : "test_EUR",
"amount" : 0.30,
"currency" : "EUR",
"reference" : 1749,
"sessionID" : 669356,
"gameRoundID" : 1589,
"gameModule" : "VSlotBM",
"type" : 0,
"fgbCampaignCode" : "",
"isRoundEnd" : "True"
}
SOAP
<Deposit>
<partnerID>C66B9778-574C-4B88-BBA5-2EFD362365E4</partnerID>
<sign>13DFBD6A3057DD4EB5309505A3033F5B17EFF0546D75C40672DAB7A8EA3B7EF8</sign>
<name>Player123</name>
<amount>0.50</amount>
<currency>EUR</currency>
<reference>401047</reference>
<sessionID>29649</sessionID>
<gameRoundID>1000</gameRoundID>
<gameModule>VSlotBM</gameModule>
<type>0</type>
<fgbCampaignCode></fgbCampaignCode>
</Deposit>
Response
|
PARAMETER |
DESCRIPTION |
FORMAT |
EXAMPLE |
| Code | Result codes : 0, 1, 2, 3, 4, 5, 8, 11 (See Result Codes) | Number | 0 |
| Message | Description of the error, if one has occurred. This value is filled only in the event that an error occurs. | string (256) | Cannot find specified identity |
| Transaction | This field is set only if the result code is 0 (success) or 11 (duplicate reference) | ||
| ID | Transaction ID – a unique identifier | varchar(100) | 123456789 |
| Balance | Balance on the target account after the transaction is completed. | decimal | 14.50 |
| Currency | Player’s currency in ISO 4217 format (expressed with 3 letters). | string (10) | EUR |
Response example:
REST JSON
{
"Code": 0,
"Message": "",
"Transaction":
{
"Balance": 22982.07,
"Currency": "EUR",
"ID": 10700550300
}
}
SOAP
<DepositResult>
<Code>0</Code>
<Message></Message>
<Transaction>
<ID>123456</ID>
<Balance>12.25</Balance>
<Currency>USD</Currency>
</Transaction>
</DepositResult>
NOTE: when getting a duplicate reference (one that has already been received in the previous communication), the Wallet Service must return error code 11 and provide the details of the original transaction: its transactionID and the balance at the time it happened.
Comments
0 comments
Article is closed for comments.