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

PayIn

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

Overview#

The PayIn endpoint is used to register a user's bet when the Game Provider sends a request from their system to the Aggregator. Essentially, this method “accepts” the bet by deducting or locking the corresponding funds from a user’s account before the game outcome is determined. It represents the initial phase of the bet lifecycle, ensuring that the wagering amount is properly recorded and linked through a unique identifier.
The PayIn method allows to:
Accept the Bet: It registers the bet by deducting or earmarking the wagered amount from the user's account as the first step of processing a bet.
Link Cash Flow Transactions: The bet identifier provided by the Game Provider (via the field betId) is essential, as it unites all subsequent cash flow transactions (like payouts or refunds) to a single bet. This ensures consistency and traceability across the betting lifecycle.
Update User Balance: After the bet is accepted, the user’s account balance is updated accordingly, which is reflected in the response.

Security and Authentication#

The PayIn 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

🟠400Bad Request
Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request POST '/v1/sessions/{{sessionId}}/bets/pay-in' \
--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
}'
Response Response Example
200 - Successful response
{
  "transactionId": "388",
  "balance": 1588.5,
  "_responseCode": 1,
}
Previous
Bets
Next
PayOut
Built with