Selling entities

Gain a better understanding of selling entities and how to use them in your integration

As the authorized reseller of your products and services, Digital River engages with multiple local selling entities.

These entities play a role in determining a transaction's eligible payment methods, payment processors, and fulfillment models. In addition, we use them when computing taxes and deciding whether tax identifiers and tax certificates can be applied to purchases.

A sellingEntity gets dynamically assigned during the checkout process:

Checkout

{
    ...
    "sellingEntity": {
        "id": "DR_IRELAND-ENTITY",
        "name": "Digital River Ireland Ltd."
    },
    ...
}

How Digital River selects a sellingEntity depends on whether the checkout's items[] are physical or digital. If items[] contains physical goods, we compare the checkout's shipFrom.address.country to its shipTo.address.country. Otherwise, we look at billTo.address.country.

In addition, we analyze your eligible entities, which are determined by your trading patterns and your contract with Digital River.

Specific eligible entities can be enabled in your contract depending on your needs.

You can use selling entities to configure front-end methods that display required disclosures and validate customer-submitted data.

Supported selling entities

The Digital River APIs support the following selling entities:

• Digital River, Inc.

• DR globalTech, Inc.

• Digital River Ireland Ltd.

• Digital River UK

• DR Japan

• Digital River Taiwan

• DR Korea

Using selling entities

Once Digital River has enough data points to make a determination, we populate the checkout's sellingEntity.

Checkout

{
    "id": "d794759b-85df-424d-b6ac-9133e09ea3da",
    ...
    "shipFrom": {
        "address": {
            ...
            "country": "TW"
        }
    },
    ...
    "sellingEntity": {},
    ...
}

Updated checkout

{
    "id": "d794759b-85df-424d-b6ac-9133e09ea3da",
    ...
    "shipTo": {
        "address": {
            ...
            "country": "TW"
        },
        ...
    },
    "shipFrom": {
        "address": {
            ...
            "country": "TW"
        }
    },
    ...
    "sellingEntity": {
        "id": "DR_TAIWAN-ENTITY",
        "name": "Digital River Taiwan"
    },
    ...
}

You can use sellingEntity.id to:

• Create a compliance element to display Digital River's required disclosures.

• Configure the get compliance details method, which returns individual disclosures that can be displayed on your front-end.

• Create a tax identifier element to validate the format of tax identification numbers entered by customers.

Multiple selling entity scenarios

A transaction can only be assigned a single selling entity. This means that if you submit a POST /checkouts or POST /checkouts/{id} that results in a checkout with multiple items[] that can't be handled by a single selling entity, then a 400 Bad Request with a code of selling_entity_not_found is returned.