Payments

​

• This endpoint will let you trigger based on deposits & withdrawals.

• These events contribute to the segmentation model for any payment activity e.g. Deposit Count, Last Deposit Date, Average Deposit Amount.

• You can publish this message both when the payment has been initiated and when it has been completed, the more statuses provided, the better.

• The bare minimum to send should be events of approved deposits.

Notes

• exchange_rate - In case the currency of the event is not Base Currency, exchange_rate needs to be sent to convert the amount back to the Base Currency by multiplying the amount with the exchange_rate. This will make segmentation correct in a single currency in case multiple are used.

• status - Requested, Approved, Rejected, Rollback, Cancelled.

A Requested payment event can be followed by either an Approved, Rejected, or Cancelled event for the same payment_id. If an Approved payment is rolled back, a payment event with the same payment_id and status Rollback should be sent. In terms of segmentation data:

• Whenever a payment event with type Credit status Approved is received the player’s deposit amount is increased by the amount specified in the event.

• Whenever a payment event with type Credit status Rollback is received the player’s deposit amount is decreased by the amount specified in the event.

• Whenever a payment event with type Debit status Approved is received the player’s withdrawal amount is increased by the amount specified in the event.

• Whenever a payment event with type Debit status Rollback is received the player’s withdrawal amount is decreased by the amount specified in the event.

Request