BETA AGDor Pay direct wallet payments
Login
AGDor Pay

Documentation

There are two different scenarios. One for projects that work via API and webhooks. The second for operators who create invoices manually from the panel and send the ready payment page or builder view to the client.

Via API Via Panel
API Flow Automatic Integration For websites, SaaS, Telegram bots and client projects where invoice is created programmatically and status is received via webhook. project_code, api_key, wallet_code, invoice.confirmed Dashboard Flow Manual Invoices from Panel For operators, managers and administrators who create invoices themselves, configure templates and send a link or ready text to the client. Project, wallet, templates, payment page, builder view

Manual flow via Dashboard

This scenario does not require API integration from the client side. The operator creates the invoice in the panel, gets the ready payment page, builder view and sends them to the client manually.

1

Sign in via Google

Open the login page and authenticate. After login, the workspace is located in Dashboard.

2

Create a project

A project is needed even for manual invoices, because it is linked to invoices, allowed wallets and webhooks. The API key for manual flow can be unused.

3

Add a wallet

Name the wallet as convenient for you in the panel, then configure the address or Binance ID. After that, link the wallet to the desired project.

4

Create manual invoice

In the Invoices tab, open the invoice creation modal, select project, wallet, amount and add templates if necessary.

5

Send the ready page to the client

After creation, you can open the builder view, payment page or take the text from the template and send it to the client via Telegram, email or messenger.

Projects

What is stored in the project

  • human-readable project name
  • project_code for API scenario
  • webhook_secret for event signature
  • Webhook URL, if callback to external service is needed
  • list of allowed wallets

What is important to remember

  • for manual invoices the API key is not required in daily work
  • if the project does not need webhook, URL can be left empty
  • the same wallet can be assigned to multiple projects

Wallets

In the Wallets tab you create payment acceptance methods that are then available to projects.

Scenario What the operator specifies How the service verifies payment
Crypto Wallet / Other Name, currency, network, address Direct on-chain check via provider APIs
Crypto Wallet / Binance Name, currency, network, address, personal Binance API keys First on-chain, then fallback via Binance deposit history
Binance ID Name, Binance ID, personal Binance API keys Check via Binance transfer history to ID
`Wallet name` is needed for your panel. This is an internal name by which you quickly understand which wallet is used in the project or manual invoice.

Manual invoice creation

What needs to be filled

  • project
  • requested amount
  • wallet / network
  • invoice TTL
  • external_id and customer_id if necessary

What the service does automatically

  • generates unique exact amount
  • creates `invoice_id`
  • prepares payment page
  • saves history and starts checker flow

What you get as output

  • builder view with ready invoice
  • payment page for the client
  • text templates for sending
  • invoice in the list with status and actions

Invoice templates

Invoice Builder is needed for cases when the invoice needs to be nicely packaged: Telegram text, HTML document, instructions for the client, company details and so on.

Telegram / Markdown

Suitable for manual sending of invoice in chat, Telegram bot or email, when you need a compact and quickly readable format.

HTML document

Suitable for branded page, PDF printing or sending the client a beautiful document with payment instructions.

When to use multiple templates

One invoice can have multiple representations: for example, short text for Telegram and a separate payment page for the client's browser.

Tracking and actions

After invoice creation, all further work is done in the Invoices, Transactions and Webhooks tabs.

Section What is visible What can be done
Invoices Status, amount, network, wallet, deadlines Open builder view, payment page, manual confirm, cancel, late payment check
Transactions Found txid and provider Check which source the service used to record the payment
Webhooks Send queue, status, target URL Resend webhook, mark as sent, integration control

Tools

Docs for API clients

If the project eventually transitions from manual mode to automatic, use the adjacent documentation flow.

Open API docs

Webhook tester

In the Integration tab you can send a test `invoice.confirmed` to any webhook URL and check the signature without a real payment.