Custom Betslip

With this approach the application of the integrator manages the full bet placement experience through its own betslip.

When a user initiates a bet from the emBET overlay, the emBET SDK notifies the application of the integrator. The integrator then takes over by displaying its own betslip and eventually handles the bet placement flow.

When using a custom betslip, bet placement events (markets, stakes, outcomes) must be shared with the SDK to enable product analytics and performance tracking.

For a comparison with the embedded approach, see Betslip overview.

Handling Bets

Once the user selects an outcome, the SDK will send an outcome_selected event through the Event Manager.

Payload Object

The SDK sends the following payload to the outcome_selected event:

• marketId: ID of the selected market.
• outcomeId: ID of the selected outcome.
• specifiers: Specifier string to identify the correct market.

After the bet placement flow has finished the integrator needs to call the notifyBetPlaced function from the SDK to track product analytics and performance.

Payload Object

The integrator sends the following payload to the notifyBetPlaced function:

• betResult: String representing success or error state according to our Bet States.
• error: Error message indicating what went wrong.
• marketId: ID of the selected market.
• outcomeId: ID of the selected outcome.
• stake: Number representing the stake.

embet.notifyBetPlaced({
  betResult: "success",
  error: null,
  marketId: "sr:market:1",
  outcomeId: "sr:outcome:1",
  stake: 10
});