Carouseller
Home
  • 🚀Getting started
    • Payment glossary
  • Cashier integration
    • Key obtaining
    • Cashier opening
      • iFrame
      • Native version
    • Cashier opening 2.0
      • iFrame
    • Payment processing
    • Webhooks
      • Successful transaction conditions
      • Notification parameters
    • Report request
    • Tracking user's activity in the cashier
    • User reset conditions
    • Signature
  • Payment API
    • API 1.0
      • Key obtaining
      • Deposit
      • Payout
      • Transaction status
    • API 2.0
      • Payment Page Integration
      • Transaction statuses
    • 3DS handler
  • Transaction types
  • Payment methods
  • Test card numbers
Powered by GitBook
On this page

Cashier integration

In this section you will learn how to integrate Carouseller into your project.

PreviousPayment glossaryNextKey obtaining

Last updated 1 year ago

Key Obtaining: Describes how to request and obtain an API key needed for authentication. This involves sending a request with parameters like site_id, site_login, customer_ip, currency, and a SHA-1 signature to a specified endpoint​.

Cashier Opening: Covers two methods for opening the cashier: using an iFrame or a native integration. The iFrame method embeds the cashier interface within your site, while the native version integrates it directly, providing more control over the user experience but requiring more development effort.

Payment Processing: Explains the processes for checking deposit and payout possibilities. This involves sending specific requests (check_deposit for deposits and request_payout for payouts) to the gaming server, which then responds with approval or error codes based on the request parameters.

Webhooks: Details the setup for receiving notifications (callbacks) about transaction statuses. After a transaction is confirmed by the payment system, a POST request is sent to the specified address with the transaction details. The system continues to send notifications until a successful response is received.

Report Request: Outlines the asynchronous process for requesting transaction reports. Clients must first request the report, check the report status, and then download the completed report. This ensures efficient handling of large data sets.

Tracking User's Activity in the Cashier: Discusses how user actions within the cashier are tracked and transmitted to the parent window. This includes actions like selecting a menu item, changing payment amounts, or opening a payment method.

User Reset Conditions: Describes how to reset user information via API. A POST request with site_id, site_login, and signature parameters is sent to reset user rotation, with the server responding with success or error messages.

Signature: Explains the algorithm for generating request signatures using the SHA-1 hash function. It covers the rules for constructing the signature string from query parameters to ensure data integrity and authenticity​.

Key obtaining
Cashier opening
Payment processing
Webhooks
Report request
Tracking user's activity in the cashier
User reset conditions
Signature
Page cover image