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.
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.

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.
Connect custody users to your platform’s own identifiers. Keep account creation in the integration rather than requiring operators to create users manually.
Review the payment request and related transaction when investigating an account. Keep request creation distinct from a completed payment.
Inspect user activity and transaction details in the custody section. Your backend remains responsible for player access and account-credit rules.
Start with the payment model that fits your business. Connect the right records, guide your customers and follow the confirmed result.
Discuss your platform requirements and service eligibility with the team. Define the identifiers and payment states your backend will use.
Your server creates custody user records and payment requests. Keep the platform reference available for reconciliation and support.
Confirm the payment outcome and prevent the same payment from being credited twice. Use the dashboard to review the related custody records.
Keep each payment request associated with the correct platform user.
Review request state and transaction activity when checking an account discrepancy.
Locate a user’s payment record without manually rebuilding their account history.
Understand the payment flow and the role of your business before choosing an integration.
Discuss your requirementsNo. Users and their payment requests are created through your API integration. The dashboard provides listing and inspection.
Your platform defines how verified payment activity affects player balances. Keep crediting logic and duplicate-payment protection in your backend.
No. A request begins a payment flow. Review the confirmed payment result before recording received funds in your platform.
No. Review your platform requirements, applicable obligations and Coino Live service eligibility with the team before integration.
Tell us how your business works and choose a payment route that fits.