Selling entities
Gain a better understanding of selling entities and how to use them in your integration
Last updated
Gain a better understanding of selling entities and how to use them in your integration
Last updated
As the of your products and services, Digital River engages with .
These entities play a role in determining a transaction's eligible , payment processors, and fulfillment models. In addition, we use them when computing taxes and deciding whether and can be applied to purchases.
A sellingEntity
gets dynamically assigned during the :
How Digital River selects a sellingEntity
depends on whether the are . If items[]
contains physical goods, we compare the 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 to configure front-end methods that display required disclosures and validate customer-submitted data.
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
You can use sellingEntity.id
to:
Once Digital River has enough data points to decide, we populate the sellingEntity
.
Create a to display Digital River's required disclosures.
Configure the , which returns individual disclosures that can be displayed on your front-end.
Create a to validate the format of tax identification numbers entered by customers.
A transaction can only be assigned to a single selling entity. This means that if you submit a or that results in a with multiple 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.