# Requirements and branding

What your integration must do. These requirements are checked at [certification](/certification).

## Eligibility and customer data

To enroll in Play+, customers must be UAE residents with a valid Emirates ID or passport, and must pass ADGT's identity (KYC) verification.

| Data | Provided by |
|  --- | --- |
| Member ID (your customer identifier) | Your platform – required |
| First and last name, email, mobile number, date of birth | Your platform, or entered by the customer |
| Residential address (street, area, city or emirate, country) | Your platform, or entered by the customer |
| ID document (Emirates ID or passport) | Captured by ADGT during identity verification |


The customer must be logged in and hold an established account on your platform before enrolling.

## Where to offer Play+

- Offer enrollment wherever customers deposit (buy in) and withdraw (cash out). These are the minimum.
- Show the Play+ option prominently on the cashier or payment page, visible without scrolling.
- Offer funding (top-up) from your site or app once the customer is enrolled.


## Branding and messaging

You receive the **ADGT Play+ Marketing Toolkit** with the assets and rules for every place Play+ appears: app, website, kiosk and marketing material.

1. Follow the toolkit's co-branding guidelines for the Play+ logo (for example *BRAND PLAY+*).
2. Use only the toolkit's approved messaging to describe the program.
3. Show the ADGT and regulatory disclaimers set out in the toolkit. They can differ by program; ADGT confirms the right toolkit version for you.
4. Recommended: link to the program FAQs wherever Play+ is mentioned.


All Play+ references – landing pages, cashier screens, user flows and marketing – must be approved by ADGT and, where applicable, the regulator.

## Member IDs

- Up to 20 characters, letters and digits only.
- Unique across **all** your platforms, brands and databases, and never reused. If several systems hold customer accounts, prefix the identifier per system, for example `JS12345` (sports), `CX12345` (Casino X).
- Where several platforms share one Play+ account and the identifier is not found, ADGT returns `ACCI-0001`; prompt the customer to enroll. ADGT detects the existing account and adds the new identifier to it.


## Credentials and multiple access points

A single Play+ account can fund many access points: locations, gaming types, brands or jurisdictions. ADGT enables each one through credential configuration, and settles in AED to each operator's bank account, net of deposits less cash-outs.

Build for this from the start:

- Credentials (ClientId and EntryCode) are configurable, not hard-coded.
- Your platform can hold several credential sets, each for a specific purpose, and sends the right set with every request.
- Scope these scenarios with ADGT early: multiple physical locations; several brands or sites sharing one Play+ program; a platform serving several operators that do **not** share a Play+ program.


## Balance and profile calls

BalanceInquiry and AccountHolderProfile may incur fees, so:

- Call them only when a transfer needs them – never on page refresh or automatically during a session. Optionally add a **View balance** button.
- The balance is also returned after every successful transfer.
- Do not show profile details to the customer. Use them only to complete a transfer.


## Transfers

**Play+ to gaming (Withdraw)**

1. Show Play+ as a clear option when the customer funds game play, a ticket or a kiosk.
2. Block amounts greater than the Play+ balance before calling ADGT.
3. On approval, post the funds to the Gaming Wager Account and show the confirmation; on decline, show the reason.
4. If the funds cannot be posted to the Gaming Wager Account after an approved Withdraw, send **Reverse** to return them to Play+, or push them to an exception queue where the customer can collect them.


**Gaming to Play+ (Deposit)**

1. Show Play+ as a clear option when the customer withdraws or cashes out.
2. Deposits to Play+ post immediately once approved. If your own review delays sending the request, show the customer the expected timeframe; it should not exceed 24 hours except in exceptional circumstances.
3. If declined, return the funds to the Gaming Wager Account or an exception queue, or offer another way to collect the winnings.


`merchantTransactionId` must be unique for every Withdraw, Deposit and Reverse; ADGT enforces idempotency on it.

## Changes after go-live

Every new feature and every change to an existing integration must be certified by ADGT before release. Regulatory or compliance changes may require changes to your integration; ADGT gives notice of what must change and by when.