Make

Overview

The /payments/make endpoint is designed to receive and initiate the processing of a transaction. This is the primary endpoint used to send the transaction data related to betting processes – such as placing bets, processing payouts, handling bet returns, or jackpot transactions.

The main objectives of the /payments/make method are:

Transaction Initiation: It serves as the entry point for Partners to submit transaction data to BETCORE, thereby initiating the processing of various bet-related transactions.

Accurate Transaction Handling: By including all relevant transaction details (such as the transaction type, amount, and identifiers), the endpoint helps ensure that every transaction is recorded, classified, and later reconciled with corresponding operations or errors.

Flexibility Across Transaction Types: This method accommodates different types of transactions (including standard bets, jackpot payouts, and transactions involving promo codes), making it a versatile tool for managing various aspects of bet processing within the BETCORE ecosystem.

In summary, the /payments/make endpoint is critical for initiating a secure, well-structured, and efficient process to handle transactions from the Partner's system to BETCORE, ensuring that all necessary transaction data is recorded and processed correctly.

Request Parameters

Parameter		Data type	Description	Required
JWT payload
data		json string	Request data.	Yes
	Amount	string	Amount in player's currency.	Yes
	TaxAmount	string	Tax Amount. The TaxAmount field will be included in the request if the "Tax On/Off" setting is enabled in the BETCORE Backoffice.	No
	BetId	number	Bet ID.	Yes
	PartnerUserId	string	Partner's user ID.	Yes
	TransactionType	number	Transaction type: -1 - accept bet 1 - payout (amount 0 means loss) 2 - bet return -2 - payout return 4 - jackpot payout	Yes
	PromoCode	string	Promo code.	No
	TagId	number	Identification tag for an embedded iFrame page element; relevant for Partners using WebFrame as a client. See more on Tags.	No

application/json

Body

ErrorCode

number

required

Error code of the response.

Message

string

required

Code description.

Example

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

Overview

Request Parameters

Request

Request samples

Responses

Make

Overview#

Request Parameters#

Request

Request samples

Responses

Overview

Request Parameters