Documentation Overview
The purpose of this documentation is to show how to integrate any project with Trybit and start accepting cryptocurrency payments.
This documentation is intended for the specialist responsible for connecting Trybit on the business side: a developer, a technical specialist or a project owner who sets up the integration on their own. It describes API methods, request and response formats, payment notifications and ready-made no-code tools. Dashboard settings and user scenarios are covered in detail in the Knowledge Base.
What is Trybit
Trybit is a crypto payment gateway for online businesses that need stable payment acceptance and timely payouts under any load. The service accepts payments in popular cryptocurrencies and stablecoins — Bitcoin, Ethereum, Litecoin, USDT and others — from customers worldwide, without banking barriers.
Every incoming transaction undergoes an AML/KYT check: suspicious deposits are flagged and blocked before they are credited to the balance, which reduces the risk of funds being frozen when withdrawn to an exchange. For projects with a steady payment flow, auto-conversion to stablecoins, withdrawals via API, static wallets and white-label payment acceptance without redirection (H2H) are available.
Which integration method to choose
Method
Developer required
When it fits
Learn more
API
Yes
You need full control over the payment flow: creating invoices, checking statuses, withdrawing funds from your system
Host2Host (H2H)
Yes
The customer pays on your website, without being redirected to the Trybit payment page
CMS plugins
No / minimal
Your website runs on a popular CMS: WooCommerce, OpenCart, Tilda, GetCourse and others
For a "Telegram bot" project, only API integration is available. Payment status notifications via POSTBACK can be received with any method except "HTML widget (without postback)". A detailed comparison of methods is available on the Integration Methods page in the Knowledge Base.
How to start accepting payments
Sign up. Create an account in the Trybit dashboard. → Registration and Account Access
Add a project. In the "Add project" section, select the project type — "Website" or "Telegram bot", fill in the project details and confirm ownership of the domain or bot. The project type, domain and bot link cannot be changed after creation. → Adding a Project
Choose an integration method. The method is selected at the "Integration and API" step of the project adding process. It determines the set of fields and whether a POSTBACK check is required.
Get your keys. At the "Keys and test payments" step, the project is issued an API KEY, SHOP ID and SECRET KEY. → Getting API Keys
Set up the integration and notifications. Connect the selected method, specify the notification URL and the POSTBACK format. → How the Integration Works, Automatic POSTBACK
Test the integration. Create an invoice the same way a customer would, confirm it without payment and make sure the POSTBACK is delivered to your server. → Testing the Integration
Submit a request to exit test mode. The request is submitted at the "Review and submit" step. Review takes up to 24 hours; the request status is shown in the dashboard, and the result is sent by email. → Requirements and Restrictions
Accept real payments. Once the request is approved, invoices are confirmed only by actual payment, and funds are credited to the balance.
API capabilities
API V2 covers the full payment cycle — from issuing an invoice to withdrawing funds:
Create invoice — issue an invoice to a customer and get a payment link or payment details.
Cancel invoice — cancel a created invoice.
Invoice list — get all invoices of a project.
Invoice information — status and details of invoices by INV number.
Balance — account balances.
Statistics — payment statistics.
Withdrawals — create a withdrawal request.
Automatic POSTBACK — invoice payment notifications sent to your server.
Static wallets — a permanent address for payments without creating a new invoice.
H2H integration — display payment details in your own interface.
Basic API information
Base URL: https://api.trybit.com/v2/
Requests are sent using the POST method.
Authorization: the API KEY is passed in the Authorization header of every request; no separate authorization request is needed.
Request examples in cURL, Python, JavaScript and PHP are available on the Request Authorization page. A ready-made archive for working with the API is available in the SDK for the API section.
Key concepts
Term
Meaning
Project
A separate payment acceptance point — a website or a Telegram bot — with its own keys, settings and statistics
API KEY
Key for authorizing API requests
SHOP ID
Project identifier; passed when creating an invoice and in the widget code
SECRET KEY
Key for verifying the authenticity of POSTBACK notifications
Invoice (INV)
A payment request with a unique number in the INV-XXXXXXXX format
TXID
Transaction hash in the blockchain
POSTBACK
A notification Trybit sends to the notification URL after an invoice is paid
Test mode
Integration testing mode: invoices are confirmed without payment and do not affect the balance
Supported currencies
The list of cryptocurrencies and networks available for payment is provided on the Currencies, Networks and Limits page in the Knowledge Base. The invoice amount currency is passed in the currency parameter — see the list of codes on the Create Invoice page.
Where to get help
Last updated
Was this helpful?
