1. For Credit/Debit callbacs, what happens if we return a non-200 response (e.g. 400)?

• The transaction is marked as error
• The response body, headers, and status code are stored for debugging
• No retry is performed

This behavior is intentional to avoid accidental double awarding.

2. Do you retry Credit/Debit callbacks?

No.

• Both Credit and Debit callbacks are sent once only
• If a non-200 response is returned:
  • The transaction is marked as error
  • The response is stored for debugging
• No retry mechanism is applied

Optional (on request):

• Retries can be enabled (for example, multiple attempts with delays)

Requirements if retries are enabled:

• The client must implement idempotency
• The client must safely handle duplicate callbacks

It is recommended to implement idempotency regardless of retry configuration.

3. Can a game be part of multiple jackpots?

Yes, with constraints.

• A slot game can be associated with multiple jackpots across different brands