Invoice Payments (One-Time Transactions)

Invoice Payments

Invoice payments are designed for one-off transactions where a single payment request is created, paid, and reconciled as an individual record (an “invoice”).

This method is ideal for:

  • E-commerce checkouts
  • Manual payment requests
  • Pay-by-link flows
  • Any scenario where one payment = one transaction

How invoice payments work

  1. Create an invoice An invoice is generated via the dashboard or API with a defined amount and payment parameters.

  2. Customer completes payment The customer pays the invoice using the provided payment instructions or checkout page.

  3. On-chain detection & confirmation 3PAY monitors the selected blockchain network and waits for the required confirmations.

  4. Invoice completed Once confirmed, the invoice status updates and the merchant balance is credited.


Invoice lifecycle

An invoice progresses through the following states:

  • Initiated – Invoice generated, awaiting payment
  • Completed (Paid) – Payment confirmed and credited
  • Expired – Invoice expired before payment
  • Cancelled – Invoice cancelled before payment (if supported)
⚠️

Blockchain payments are irreversible once confirmed. Any refund is handled operationally and is not a blockchain reversal.


When to use invoice payments

Use invoice payments when:

  • The payment amount is known in advance
  • You need per-transaction reconciliation
  • You want a clean audit trail per payment

If you need persistent balances or repeated deposits per user, use Wallet Payments instead.

➡️ See: Wallet Payments (Per-User Wallets)


Sandbox testing

Invoice payments can be fully tested in the sandbox environment.

Network TypeAssetStandardTest Network
EthereumUSDTERC20Sepolia
TronUSDTTRC20Nile

If you need help generating a testnet wallet or obtaining testnet funds, please contact the 3PAY support team.


Integrating invoice payments

Invoice payments can be integrated in two ways:

Dashboard-based invoices

  • Create invoices manually from the dashboard
  • Best for low-volume or operational use cases

API-based invoices

  • Create and manage invoices programmatically
  • Best for checkouts, platforms, and automation

API reference links

Use the API Reference for implementation details.


Important notes

  • Invoice addresses are invoice-specific
  • Sending funds to an expired invoice may result in delays or manual review
  • Network mismatches (e.g. ERC20 vs TRC20) may cause payment failures