iTunes IAP

Overview

The eSuite iTunes importer reads each row and determines whether a match can be made to an existing eSuite subscription. The service must be configured as per the iTunes specification for the renewals to be successful. To read more, please visit the iTunes Native Billing page.

The Importer has the following conditions:

  • Each iTunes  subscription should only appear once in the import file, any duplicates found will result in a validation failure.
  • If the iTunes subscription has already been assigned to an eSuite subscription a validation failure will occur.

iTunes File Column Specification

A complete specification of the iTunes file is as follows.

Column Details Description
KeyField Required: Yes
Format: E | C
Validation: Must be one of the values above.
Case: Insensitive
E = Email
C = ClientUserId
Email Required: Yes_Alt
Format: Unicode string (max 255)
Validation: Length, Regex Email, Is Unique
Case: Insensitive. Cast to lower to persist.
User’s email address. Must be a valid email format. If client is using eSuite as the master for user authentication, this value must be provided, and must be unique. Note that if the value provided is identical to another account's email, the importer performs an update, rather than an insert.
ClientUserId Required: Yes_Alt
Format: Unicode string (max 50)
Validation: Length, Is Unique
Case: Upper and lower persisted. Uniqueness test will cast to lower.
Third party system’s identifier for the user account, if eSuite is not the master for account authentication.
ServiceId Required: Yes
Format: Integer
Validation
: Is Integer?, Does Exist?
The unique reference in eSuite HQ to the service that corresponds to the user’s subscription. (This reference must be set up in advance of the import.)
OriginalTransactionId Required: Yes
Format: Unicode string (max 50)
The Original Transaction Identifier for the purchase, will be the same on all receipts for a given subscription.
iTunesReceipt Required: Yes
Format: Unicode string
Encrypted iTunes receipt string