Understanding API Sales

What Is An API?

An application programming interface (API) regulates interactions between multiple software intermediaries. An API can be likened to a contract between two parties as it defines the kinds of requests that can be made, the process in which the requests are submitted, and the data formats the requests must satisfy. An API can be entirely custom, specific to a component, or it can be designed based on an industry standard to ensure interoperability.

How Does This Apply To Sales On JLP?

For JLP clients who resell on OzLotteries, an API can be implemented for sales. An API for sales across JLP instances removes the need to have different ticket allocations on each JLP instance and removes the reliance on flat/batch files in order to reconcile ticket sales between the JLP instances.

Key Business Outcomes

The implementation of API Sales between Oz Lotteries and a  instance will result in the following outcomes:

• OzLotteries will purchase directly from a JLP instance via API.
• When OzLotteries sends a remote request structured in the desired format, the LP instance will respond.
• The use of flat files will no longer be needed.
• The OzLotteries website and the JLP instance will share the same ticket allocation.
• OzLotteries sales purchased from a JLP instance via the API will appear in the accompanying JLP admin ticket search.
  • These sales will be marked as OzLotteries API Sales.
• Certain customer details are passed from OzLotteries to the accompanying JLP and will appear in bothJLP Admin customer searches.
  • • These customers will be marked as OzLotteries customers.
• The Channel Report in the accompanying JLP will show OzLotteries sales.

Purchasing Flow

Reconciliation Flow

Customer Scenarios For API Sales

Oz Lotteries Only Customers:

Scenario:
A sale is made through Oz Lotteries and the customer does not exist in the JLP instance.

Answer:
The customer is added in the JLP instance along with the customer name, phone number and address and marked as an ‘offline’ customer with ‘Oz Lotteries API Sales’ affiliation. The customer profile in the JLP instance will list the transaction amount as ‘accounts receivable for third-party sales of OZL’ in the customer’s transaction history on the JLP instance.

Scenario:
A sale is made through Oz Lotteries and the customer already exists in the JLP instance due to a previous Oz Lotteries purchase and has the same contact details.

Answer:
The purchase and third-party transaction will appear on the offline account with ‘Oz Lotteries API Sales’ affiliation that was created on the first API purchase.

Scenario:
A sale is made through Oz Lotteries and the customer already exists in the JLP instance due to a previous Oz Lotteries purchase but has different contact details (e.g. they updated their contact details in Oz Lotteries since the previous purchase).

Answer:
Customer details are updated and a new record is not created.

Existing JLP Instance Customers Buying Through Oz Lotteries:

Scenario:
A sale is made through Oz Lotteries and the customer already exists in the JLP instance due to a previous JLP purchase and has the same contact details.

Answer:
An offline account is created with customer details passed from Oz Lotteries, excluding the email address.

Scenario:
A sale is made through Oz Lotteries and the customer already exists in the JLP instance due to a previous JLP purchase but has different contact details.

Answer:
An offline account is created with customer details passed from Oz Lotteries, excluding the email address.

Existing Oz Lotteries Customers Buying Through A JLP Instance:

Scenario:
A sale is made through a JLP instance and the customer already exists as an ‘offline’ customer in the JLP instance due to a previous Oz Lotteries purchase and has the same contact details.

Answer:
A new customer account for the JLP instance would be created during the purchase flow:

• Website – Creating an account to sign in and purchase via the website.
• POS – Operator creating the customer account during the purchase flow.
• Mail – Created during operator purchase on JLP instance (customer would be prompted to create a password upon the first login).

Scenario:
A sale is made through a JLP instance and the customer already exists in the JLP instance due to a previous Oz Lotteries purchase and has different contact details.

Answer:
A new customer account for the JLP instance would be created during the purchase flow:

• Website – Creating an account to sign in and purchase via the website.
• POS – Operator creating the customer account during the purchase flow.
• Mail – Created during operator purchase on JLP instance (customer would be prompted to create a password upon the first login).

Two offline accounts can share the name, phone number and street address; but no account can share the same email address.

What Do API Sales Look Like?

OzLotteries Affiliation On The Customer’s Profile

Ticket Provider In Wager Information

OzLotteries

JLP Instance

Affiliated Deposit Listed In The Transaction History

Reports

Channel Report

Supplier Costs Report

If there is a desire to implement API Sales for your JLP instance, contact Customer Success or send an email to support@poweredbyjumbo.com.