Transaction API

Transaction API

Overview

The Transaction API facilitates real-time financial transactions between game providers and casino operators. It ensures secure, reliable, and auditable money movement for all player activities including wagers, wins, and promotional bonuses.

Every transaction is processed through standardized API calls that follow strict protocols for security, idempotency, and reconciliation. The API delivers fast, reliable, one-to-one interactions with predictable outcomes for both players and operators.

Transaction Endpoints

Base URL: https://{CasinoEndpoint}

HTTP Method: GET

Response Format: All responses are returned in JSON format

Transaction Flow

The transaction flow follows a logical sequence based on player actions within a game:

Transaction Types

The Transaction API supports several types of operations:

Security Features

• Signature Validation: HMAC-SHA256 request authentication for enhanced security

Authentication & Information Requests

• Get Account: Validates player information and session status
• Get Balance: Retrieves current player balance from the operator’s wallet

Financial Transactions

• Wager: Deducts funds from player balance for placing a bet
• Result: Adds winnings to player balance after game round completion
• Wager and Result: Combined operation for immediate bet and result processing
• Jackpot: Processes special jackpot wins
• Rollback: Reverses a previous wager transaction

Sportsbook Features

• Bet By Batch: Process multiple wagers in a single request
• Rollback on Result: Reverses a previous result transaction
• Rollback on Rollback: Reverses a previous rollback transaction

Implementation Guidelines

When implementing the Transaction API, follow these best practices:

1. Idempotency: Always implement proper idempotency handling using transaction IDs to prevent duplicate processing
2. Round Management: Ensure all rounds are properly closed with a ‘completed’ status
3. Error Handling: Implement comprehensive error handling with appropriate response codes
4. Reconciliation: Maintain detailed transaction logs for reconciliation purposes
5. Security: Validate all incoming requests using secure authentication methods
6. Signature Validation: Consider implementing HMAC-SHA256 signature validation for enhanced request authentication

Next Steps

Review the documentation for each transaction type to understand the specific parameters, request formats, and response structures required for implementation. Start with the Get Account and Get Balance endpoints which form the foundation of all player interactions.