Client-based purchases

OpenTV Video Platform's Purchase Service enables a client application to initiate the purchase of a product. It handles the client request and:

1. Calls the operator's CRM to inform it about the purchase and to get authorisation.

2. If the CRM authorises the request, it returns an approved or denied response. Optionally, this can include a request ID (purchaseAuthRequestReference) that the client app can use in the approved/denied message that it displays to the user.

3. The Purchase Service responds to the client request with a success response.

4. When the purchase is complete, the Purchase Service notifies the CRM.

If the CRM does not supply a purchaseAuthRequestReference in its approve/deny response, the Purchase Service uses the x-correlation-id from the initial call.

This following pages explain:

• Implementing the purchase endpoint (that is, the interface that the CRM must implement to enable this functionality)

• How the CRM subscribes to and handles purchase completion notifications

• Third-party CRM purchase authorisation API documentation

See also

Making a purchase for an explanation of how a client app initiates a purchase.