Solutions / iGamingACCOUNT ACTIVITY FOR GAMING PLATFORMS

Payment activity.
Connected to each player.

Use an API-driven account model to connect users, payment requests and transactions. Give your operations team a focused custody view while your platform controls account creation and balance rules.

Gaming controller, chips and secure account cube for platform payments
BUILT FOR IGAMING

Your platform creates the records. Your team reviews them.

An account-based platform needs to follow a payment beyond a single checkout screen. Custody brings API-created users, requests and transactions into a reviewable account view. Your platform creates the users and payment requests programmatically; the merchant dashboard is the place to inspect activity, find the related record and follow the payment status.

01

User records created through the API

Connect custody users to your platform’s own identifiers. Keep account creation in the integration rather than requiring operators to create users manually.

02

Requests linked to account activity

Review the payment request and related transaction when investigating an account. Keep request creation distinct from a completed payment.

03

A focused operations workspace

Inspect user activity and transaction details in the custody section. Your backend remains responsible for player access and account-credit rules.

FROM SETUP TO CONFIRMATION

A practical path to your first payment.

Start with the payment model that fits your business. Connect the right records, guide your customers and follow the confirmed result.

  1. 01

    Review the required account model

    Discuss your platform requirements and service eligibility with the team. Define the identifiers and payment states your backend will use.

  2. 02

    Create users and requests through the API

    Your server creates custody user records and payment requests. Keep the platform reference available for reconciliation and support.

  3. 03

    Verify activity before updating balances

    Confirm the payment outcome and prevent the same payment from being credited twice. Use the dashboard to review the related custody records.

Read the integration guide
PUT IT TO WORK

Where this solution fits.

Player account payments

Keep each payment request associated with the correct platform user.

Operations reconciliation

Review request state and transaction activity when checking an account discrepancy.

Support investigations

Locate a user’s payment record without manually rebuilding their account history.

BEFORE YOU START

Your questions,
answered.

Understand the payment flow and the role of your business before choosing an integration.

Discuss your requirements
Can operators create custody users manually?

No. Users and their payment requests are created through your API integration. The dashboard provides listing and inspection.

Does custody determine player balances?

Your platform defines how verified payment activity affects player balances. Keep crediting logic and duplicate-payment protection in your backend.

Is a created request the same as a deposit?

No. A request begins a payment flow. Review the confirmed payment result before recording received funds in your platform.

Does this page establish regulatory approval?

No. Review your platform requirements, applicable obligations and Coino Live service eligibility with the team before integration.

YOUR PAYMENT TOOLKIT

The services behind this solution.

Build the right flow for igaming.

Tell us how your business works and choose a payment route that fits.

Talk to our team