The consumer does not receive the Digital Right (serial number, unlock code, or download URL). Instead, the consumer is instructed to wait for an email that will contain the Digital Right.
When the Digital Right is fulfilled, the consumer will receive the email.
The consumer is charged until the Digital Right is fulfilled.
When you receive an unsuccessful response or experience communication issues (such as failed transports), the shopping process behaves as follows:
If the <isAutoRetriable> element is set to true, Digital River automatically retries the request every hour for 21 days. If there is no action after 21 days, the system "forgets" the order.
The consumer is not charged for the line item until the consumer receives a serial number, unlock code, or download URL.
The line item goes into a "failed digital rights" state. When this happens, the line item appears on the globalCommerce Integration Exception screen.
Using the details provided in the <returnMessage> element, you can use the globalCommerce Integration Exception screen to fix the issue and resubmit the line item.
When an unsuccessful Digital Rights response occurs:
If the <isAutoRetriable> flag is set to false, the <returnCode> element must contain a non-0 response. Also, the <returnMessage> element should explain what the value in <returnCode> means and contain an explanation of what is wrong with the request and, if possible, how to fix it.
An unsuccessful response occurs when the <key> element is missing or empty. In this situation, Digital River will try to fix the issue causing the non-successful response by using the <returnCode>, <isAutoRetriable>, and <returnMessage> elements and try again.
Response details for an unsuccessful scenario
In a successful scenario such as this, the <returnCode>, <isAutoRetryiable>, and <returnMessage> elements are ignored. These elements come into play in an unsuccessful scenario.
Note that the <item> element is unbounded. That means you can send multiple keys in response (in response to the <quantity> element in this <getKeyRequest>).
A successful Digital Rights request results in a response that contains a non-null, non-empty <key> element.
Response details for a successful scenario
When a shopper buys a product that has Digital rights, they get a key (serial number or unlock code) that they can use to access the product.
You can create keys and then associate them with products to deliver and manage Digital Rights. You can create as many keys as needed to satisfy your Digital Rights requirements.
Digital Rights is an outbound event.
Key Request
Key Revocation
The types of custom integrations for Digital Rights are as follows:
Digital Rights refer to the rights or permissions granted to a shopper by the publisher or manufacturer to use or access a software application, game, system, and so forth. Digital Rights protect the sale and distribution of copyrighted works. Use Digital Rights to enable and manage the serial numbers and unlock codes that control access to software and other digital products.
Digital Rights refer to the rights or permissions granted to a shopper by the publisher or manufacturer to use or access a software application, game, system, and so forth. Digital Rights protect the sale and distribution of copyrighted works. Use Digital Rights to enable and manage the serial numbers and unlock codes that control access to software and other digital products.
The types of custom integrations for Digital Rights are as follows:
Key Request
Key Revocation
Digital Rights is an outbound event.
You can create keys and then associate them with products to deliver and manage Digital Rights. You can create as many keys as needed to satisfy your Digital Rights requirements.
When a shopper buys a product that has Digital rights, they get a key (serial number or unlock code) that they can use to access the product.
Response details for a successful scenario
A successful Digital Rights request results in a response that contains a non-null, non-empty <key> element.
Note that the <item> element is unbounded. That means you can send multiple keys in response (in response to the <quantity> element in this <getKeyRequest>).
In a successful scenario such as this, the <returnCode>, <isAutoRetryiable>, and <returnMessage> elements are ignored. These elements come into play in an unsuccessful scenario.
Response details for an unsuccessful scenario
An unsuccessful response occurs when the <key> element is missing or empty. In this situation, Digital River will try to fix the issue causing the non-successful response by using the <returnCode>, <isAutoRetriable>, and <returnMessage> elements and try again.
If the <isAutoRetriable> flag is set to false, the <returnCode> element must contain a non-0 response. Also, the <returnMessage> element should explain what the value in <returnCode> means and contain an explanation of what is wrong with the request and, if possible, how to fix it.
When an unsuccessful Digital Rights response occurs:
The consumer is not charged for the line item until the consumer receives a serial number, unlock code, or download URL.
The line item goes into a "failed digital rights" state. When this happens, the line item appears on the globalCommerce Integration Exception screen.
Using the details provided in the <returnMessage> element, you can use the globalCommerce Integration Exception screen to fix the issue and resubmit the line item.
If the <isAutoRetriable> element is set to true, Digital River automatically retries the request every hour for 21 days. If there is no action after 21 days, the system "forgets" the order.
When you receive an unsuccessful response or experience communication issues (such as failed transports), the shopping process behaves as follows:
The consumer does not receive the Digital Right (serial number, unlock code, or download URL). Instead, the consumer is instructed to wait for an email that will contain the Digital Right.
When the Digital Right is fulfilled, the consumer will receive the email.
The consumer is charged until the Digital Right is fulfilled.
The Digital Rights process is a request/response-based process used for retrieving external digital rights. The process requests a serial number or an unlock code when a purchase occurs. A key request integration sends a request for a key (serial number of unlock code) when a shopper purchases a product set up to use the integration.
Notification—Global Commerce generates a Get Key Request and sends the request to your endpoint.
Required Response to Notification—Your endpoint must synchronously respond with a Get Key Response.
