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

Accept

POST
/mis-api/api/v2/payments/accept

Overview#

The /payments/accept endpoint is used to send the final outcome of bet-related transactions (e.g., bet acceptance, payouts, jackpot results, or bet returns).
It is recommended to implement a mechanism for resending requests in case of a network error occurred during a request or in case of receiving a response with an error.
The/payments/acceptrequest must be sent within 30 seconds after receiving the/payments/makerequest from BETCORE.
The main objectives of the /payments/accept method are:
Transaction Outcome Communication: It communicates whether a transaction (such as bet acceptance, cash flow, or other related operations) has been successfully processed or if errors occurred. The method returns structured information, including an error code and descriptive messages.
Asynchronous Processing Coordination: Since the transaction processing might be completed asynchronously on the Partner's side, the method ensures that BETCORE receives the result promptly – typically within 30 seconds of the original transaction request.
Data Consistency and System Updates: By sending transaction details – including identifiers like BetId, PartnerTransactionId, transaction type, amounts, and any applicable taxes – the endpoint helps maintain system integrity and ensures that both parties’ records are synchronized.
Error Handling and Recovery: In cases where the transaction fails or an issue is detected (e.g., duplicate transactions, incorrect amounts, or processing errors), the endpoint provides specific error codes. This allows BETCORE to trigger appropriate error handling procedures and, if necessary, enable a re-submission of the transaction.

Possible values for ErrorCode parameter sent in the body#

Error CodeDescription
200Success
102145User not found
103801Incorrect amount
103Not enough funds for bet. Please deposit your account
102823Error adding transaction
102913Bet transaction not found
103779User blocked
103804Transaction already exists
103753Request data error
19Promo code has already been used
20The specified promo code was not found
21Not enough user registration data to use the promo code
22Promo code promotion has ended
23The user is prohibited from using this promo code
103902Player bet limit reached
103905Maximum odds threshold reached
103799API system error
📌
In case error 103804 was received, please pass the contents of Value.

Request

Authorization
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
Body Params application/json
ErrorCode
number 
required
Error code of the response.
Message
string 
required
Code description.
Value
object 
required
Request parameters.
Amount
string 
required
Amount in player's currency
TaxAmount
string 
optional
Tax Amount.
The TaxAmount field will be included in the request if the "Tax On/Off" setting is enabled in the BETCORE Backoffice.
TransactionType
number 
required
Transaction type:
-1 - accept bet
1 - payout (amount 0 means loss)
2 - return bet
-2 - return payout
4 - jackpot payout
BetId
number 
required
Bet ID.
PartnerTransactionId
string 
required
Transaction ID.
Examples
/*Example of a request when a transaction was processed successfully*/
{
    "ErrorCode": 200,
    "Message": "Success",
    "Value": {
        "BetId": 120730817,
        "PartnerTransactionId": "-1-120730817",
        "TransactionType": -1,
        "Amount": 10,
        "TaxAmount": 0
    }
}

Request samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
cURL
curl --location --request POST 'https://mock.apidog.com/m1/820627-0-default/mis-api/api/v2/payments/accept' \
--header 'Content-Type: application/json' \
--data-raw '/*Example of a request when a transaction was processed successfully*/
{
    "ErrorCode": 200,
    "Message": "Success",
    "Value": {
        "BetId": 120730817,
        "PartnerTransactionId": "-1-120730817",
        "TransactionType": -1,
        "Amount": 10,
        "TaxAmount": 0
    }
}'

Responses

🟢200Success
application/json
Body
ErrorCode
number 
required
Error code of the response.
Message
string 
required
Code description.
Example
{
    "ErrorCode": 200,
    "Message": "Success"
}
⚪103752Incorrect request parameters
⚪102823Error accepting transaction
Previous
Token
Next
Accept
Built with