Accept

Overview

The /cashback-payments/accept endpoint is used to send the final outcome of cashback transactions.

While/payments/accepthandles standard betting transactions,/cashback-payments/acceptis tailored specifically for the nuances of cashback transactions.

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/cashback-payments/acceptrequest must be sent within 30 seconds after receiving the/cashback-payments/makerequest from BETCORE.

The main objectives of the /cashback-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 Code	Description
200	Success
102145	User not found
103801	Incorrect amount
102823	Error adding transaction
103779	User blocked
103804	Transaction already exists
103753	Request data 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 - cashback payment
-1 - cashback payment cancellation

CashbackId

number

required

Cashback ID in BETCORE.

PartnerUserId

string

required

Partner's user ID.

PartnerTransactionId

string

required

Transaction ID.

Examples

when transaction was successfully processedwhen transaction processing failedwhen error 103804 was received

/*Example of a request when a transaction was processed successfully*/
{
  "ErrorCode": 200,
  "Message": "Success",
  "Value": {
    "CashbackId": 480,
    "PartnerUserId": "188509"
    "PartnerTransactionId": "480-120730817",
    "TransactionType": 1,
    "Amount": 1000,
    "TaxAmount": 0
  }
}

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200Success

application/json

Body

ErrorCode

number

required

Error code of the response.

Message

string

required

Code description.

Examples

Successful responseExample 1Example 1

{
    "ErrorCode": 200,
    "Message": "Success"
}

⚪103752Incorrect request parameters

⚪102823Error accepting transaction

Overview#

Possible values for ErrorCode parameter sent in the body#

Request

Request samples

Responses

Overview

Possible values for ErrorCode parameter sent in the body