Business capabilities and availability
Use the capabilities enabled for the signed-in account. An API endpoint existing in the platform does not mean it is enabled for your account, network or payment route.
| Capability | Integration boundary |
|---|---|
| Payments and payouts | Transaction API, configured route, permitted instrument and environment |
| Heth receiving links | A receiving URL generated in the app; sharing does not create a charge |
| Managed payment links and products | Separate business resources; require enabled account access |
| Merchant subscriptions | Agreements billed to your customers; require supported payment methods and customer authorization |
| A payer's own subscription permissions | Separate customer authorization and explicit approval/revocation |
| Refund or cancellation | Only if supported by the original transaction and payment method; a blockchain transfer is not generically reversible |
| Wallets, @usernames, gift cards, webhooks | Account functions may require the user's session and additional confirmation |
| Donations | Platform/author flow with its own recipient, minimum, fee and expiry |
The public token registry returns configuration, not an entitlement to pay with every listed asset. Match the asset to the network and the effective account configuration. For example, USDT/ETH and USDT/TRX cannot be interchanged.
Documentation boundaries
The transaction reference covers request formats for the documented flows. Do not obtain operator credentials or change terminals/routing to resolve a rejected request. Contact support with the transaction identifier when an account route is unavailable.
The AI connection guide explains permissions and confirmation for functions available to your account.