BETCORE Aggregator
Provider IntegrationCasino IntegrationFeed Integration
Provider IntegrationCasino IntegrationFeed Integration
Visit Betcore website
Follow Betcore on Instagram
Follow Betcore on LinkedIn
Follow Betcore on Youtube
  1. Bets
  • PLEASE READ: Getting Started
  • Integrate BETCORE Games
    • Integrate BETCORE Games
    • WebFrame Connection
    • BETCORE API
      • Authentication
        • Token
          POST
        • Verify
          POST
        • Jwks
          GET
      • Payments
        • Accept
          POST
      • Cashback
        • Accept
          POST
    • PARTNER API
      • Users
        • Auth
          POST
        • Data
          POST
      • Payments
        • Info
          POST
        • Make
          POST
        • Make-list
          POST
        • Close
          POST
      • Cashback
        • Make
          POST
  • Integrate YOUR Games
    • Integrate as Games Provider
    • PARTNER API
      • Games
        • Games
          GET
        • Launch
          POST
    • BETCORE API
      • Get Balance
        • Balance
          GET
      • Bets
        • PayIn
          POST
        • PayOut
          POST
        • PayInOut
          POST
        • Refund
          POST
  • Feed Integration
    • Feed Integration
    • REST API
      • Authorization
        • Token
          POST
      • Games
        • List
          GET
        • Info
          GET
        • Translations
          GET
      • Jackpot
        • Accumulated
          GET
    • Websocket
      • SubOnWholeGamesInfo
Provider IntegrationCasino IntegrationFeed Integration
Provider IntegrationCasino IntegrationFeed Integration
Visit Betcore website
Follow Betcore on Instagram
Follow Betcore on LinkedIn
Follow Betcore on Youtube
  1. Bets

PayInOut

POST
/v1/sessions/{{sessionId}}/bets/pay-in-out

Overview#

The PayInOut endpoint is designed to handle both the acceptance of a bet and the immediate processing of its outcome in a single request. This combined operation is especially useful in scenarios where the game result is known almost instantly after the bet is placed. By merging the functionalities of PayIn (bet acceptance) and PayOut (processing the win/loss outcome) into one call, the endpoint streamlines the betting workflow and reduces the latency of transaction processing.
The main objectives of the PayInOut method are:
Simultaneous Processing: It allows both the acceptance of the user's bet (deducting or earmarking the bet amount) and the payout (crediting the winnings or confirming a loss) to be processed in one atomic call.
Efficiency in Rapid Outcome Scenarios: The method is best suited for games where the result is determined at the same moment the bet is placed, thereby eliminating the need for two separate API calls.
Transaction Linking: The use of a unique bet identifier (betId) ensures that all cash flow transactions (both debit and credit parts) remain linked throughout the betting lifecycle. The system returns separate transaction IDs for the bet and the payout components, ensuring complete traceability.

Security and Authentication#

The PayInOut endpoint, like other API requests within this integration, requires strict authentication to ensure that only authorized parties can interact with it. This is achieved through the use of mandatory HTTP headers. Please see the required headers below in the Header Params section.
📌
Signature of the request shall be calculated using HMAC-SHA256 algorithm and sent in "X-Sign" header of the request.
Please see How to calculate the X-Sign value.

Path Parameters#

ParameterTypeRequiredDescription
sessionIdstringYesGame Session id.

Request

Header Params

Body Params application/json

Examples

Responses

🟢200Success
application/json
Body

🟠402Bad Request
Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request POST '/v1/sessions/{{sessionId}}/bets/pay-in-out' \
--header 'X-Counterparty-Id: 933a215f-a9e6-4f88-9d91-52a87cd50499' \
--header 'X-Timestamp: 1719766120806' \
--header 'X-Request-Id: 5a0679b6e5fa48f6892c777b0fa92392' \
--header 'X-Sign: c4d62f77cdfaadb6690b3bcbe5a0ca9ef1e5bf41d746d361a1269558eeb7ccd1' \
--header 'Content-Type: application/json' \
--data-raw '{
  "betId": "4178696881",
  "gameRoundId": "c5dfa465-93fc-4e8e-a643-954747f74ca1",
  "betAmount": 10.5,
  "winAmount": 55.25,
  "winOdd": 11.05
}'
Response Response Example
200 - Successful response
{
  "betTransactionId": "390",
  "winTransactionId": "391",
  "balance": 1588.5,
  "_responseCode": 1,
}
Previous
PayOut
Next
Refund
Built with