## Credit The Credit request is used for providing information about the win result of the game for the player. Even if the player doesn't win anything, the Credit request is sent with zero amount. If the Credit request fails due to a non-business problem, such as a connection timeout, unavailable resource, network problems, etc., RubyPlay will retry this Credit request until the success to make sure that possible winning was credited. The initial retry will be done a maximum 10 times with pauses for a fixed period of time equal to 1 second between the attempts. If the last 10th attempt fails, the error dialog will be displayed. Then the request will be retried with pauses for a fixed period of time equal to 60 seconds until successful processing without retry number limitation. The Credit request on the Operator side must be idempotent (see the note in the Overview section of this document). It means if several same Credit requests come, the response must be with the same result and should not contain the error of duplicated transaction ID. In case of non-determined (unpredicted) HTTP server errors with **HTTP Status Code 5xx (500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 511)** from the wallet's side, RubyPlay will also retry this Credit request until the success. It is also possible to explicitly trigger the Credit request retry apart from responding with HTTP Status Code 5xx. For this purpose, the response to the Credit request must contain HTTP Status Code 200 "OK" and the HTTP body must contain a "code" property equal to "501" (Retry / cancel triggered). If the Credit request receives the response with the HTTP Status Code 200 "OK" and the response's "code" (described in the Response Codes) is considered failed (100, 101, 102, 103, 104, 105, 106, 107), RubyPlay will not retry the Credit request (because the Operator has already responded with the description of the problem). The player session will be blocked, so the player won't be able to play that particular game until manual cleanup by the Support team, results will be sent for manual correction. **API Call Sample:** **Request Schema:** **Response Schema:**