For retailers
Protected downloads, without a platform migration
You already have search, a cart and a payment gateway. What you do not have is a licence server. That is the only part we supply.
The integration is small on purpose
A retailer with SOAP support and a static IP is three calls away from selling rights-protected books: confirm availability before payment, exchange your transaction ID for a download link after it, and regenerate that link later if the customer needs it again.
You keep the catalogue pages, the promotions, the checkout and the customer. The credentials sign every request server-side; the download link is encrypted and issued per transaction.
Talk it throughWhat you need
- A dynamic site
- Search, shopping cart and payment gateway in PHP, ASP or JSP.
- SOAP client support
- The ability to call a SOAP service and read the response.
- A static IP
- Allow-listed against your retailer account.
- Three credentials
- CommerceID, RetailerID and RetailerKey, issued on approval and kept server-side.
- Catalogue metadata
- Pulled from the reserve in XML and imported into your product pages.
What it removes from your roadmap
The work you are not doing is the point.
- No encryption to build
- No key management, no licence server, no device authorisation logic.
- No re-delivery support burden
- A lost download is a RegenerateDownloadLink call, not a refund.
- No transition project
- The ACS to ByteBooks change is handled on our side; your desk gets a script, not a migration.
Ask for the integration manual.
The Retailer DRM Web Services manual — syntax, samples, PHP reference code and the full error table — is issued with your retailer account.