Registering Entities

As a publisher that allows your users to sell virtual goods, it’s natural that some of your users may want to register as entities for tax purposes. In order to register, entities will need to complete a KYB (Know Your Business) application with Tilia. Registration creates the entity, which is tied to the user’s account.


Tilia uses the information collected during entity registration to run KYC for the associated user (also called the primary contact). A KYC status of ACCEPT will always be the indicator of whether or not a user can receive funds and initiate a payout. Entities that are approved via a KYB application do not need to also submit KYC and, instead, will inherit a KYC status from their entity status.

What is an entity?

An entity is a taxable organization that maintains a separate legal existence for tax purposes. It can be made of up to 6 individuals, including a primary contact, a control prong, and up to 4 beneficial owners.

  • The primary contact will always be the user you are registering and to which the entity’s wallet will be tied.
  • The control prong is the person with the most control and responsibility over the entity, like a CEO, COO, or company president.
  • Beneficial owners are parties that have 25% or more ownership in the entity.

Registration Requirements

Registering an entity with Tila requires the following:

  • An access token with the scope write_entities
  • The account_id of the the user’s account who wants to register their entity
  • The entity_name or legal name of the entity. This can be adjusted by the user within their application
  • The jurisdiction of the entity. This should have a value of domestic for US-based entities or a value of international for any entities outside the US

Refer to the Begin KYB application API reference for more information.

Register an Entity

To register an entity, submit a POST request with a request body containing the required information. You can also pass any optional registration information, as indicated in the API reference.

curl --location --request POST
--header 'Authorization: Bearer <Access_Token>' \
--header 'Content-Type: application/json' \

Request Body

    "entity_name": "Test Entity",
    "jurisdiction": "domestic"

Response Body

    "status": "Success",
    "message": null,
    "codes": null,
    "payload": {
        "entity_id": "ent_2EPau2TcGh8BlXUubpba9WBD2u2",
        "vendor_application_id": "12345",
        "application_url": "",
        "custom_application_id": "9a2beeb0-ed09-4c69-9627-786eb6d2df33"

Users will receive an email to complete their KYB application on successful request. You can also pass them the application_url in the case you would like to redirect them to the KYB application within your UI. The KYB application will request details about the business at large and about each individual within the entity (the primary contact, the control prong, and the up to 4 beneficial owners).


Upon submission, Tilia’s compliance team may need to contact the primary contact to gather missing information in order to approve the application. If no response is received, the application may land in a CANCEL state.

KYB Status Change Webhook

You may wish to implement a webhook to notify you when an entity’s KYB status changes. See the KYB Status Change webhook documentation for complete details.