An invoice forms the basis of a Tilia transaction. Tilia supports several types of invoices:

  • Standard invoice: A standard purchase invoice involves collecting funds from the buyer and transferring them directly to the recipient or seller.
  • Escrow invoice: An escrow purchase invoice involves collecting funds from the buyer and holding them in an escrow account, until an agreed-upon condition is met. Once escrowed, funds can either be transferred to the seller, or refunded back to the buyer.
  • Virtual token purchase: This type of invoice enables a user to purchase tokens from you for use in other transactions. Tokens can be spent using both standard invoices or escrow invoices.
  • Virtual token conversion: This is a special type of invoice that can be used to exchange a user's convertible tokens to fiat currency. Refer to Virtual Tokens for more information.
  • Payout: Payout invoices are used to request that funds be transferred from a user's fiat wallet to an external account (e.g. PayPal.) Refer to Payouts for more information.

Invoice properties

Each purchase invoice is associated with one or more payment methods. Supported payment methods include credit cards, Tilia Wallets, and PayPal.

Both Standard and Escrow invoices can have one or more line items, and each line item has a transaction type. Tilia supports the following transaction types:

  • User to user: Used when the customer is paying another user for a good or service.
  • User to integrator: Used when the customer is paying you for a good or service.

You can combine line items with different transaction types in a single invoice. For example, an invoice may have a user-to-user line item to compensate a seller, and a user-to-integrator line item to capture a fee you collect from the buyer for the transaction.

You can pass us information referencing the transaction in your system and other metadata related to your invoice.

Our Developer Guides walk you through the process of creating invoices for various transaction types.

Invoice lifecycle

A typical invoice moves through the following states: open, processing, and success.

If an invoice cannot be processed (for example, if the user's credit card is declined), it is assigned a state of failed.

An unprocessed invoice can also be cancelled, in which case it is assigned a state of cancelled.


Our webhooks enable you to keep track of an invoice throughout its lifecycle. Refer to our Webhooks documentation for more details.

You can also retrieve any invoice by its ID.