# Gaming

Some industries need extra steps for compliance and smooth payment processing. Check these requirements before you integrate gaming merchants.

## Required Fields for a Gaming Transaction

Card networks require gaming MCC (7994) transactions to include extra data for compliance. Here are the four required fields:

1. **IP Address:** A new field required when creating `Authorizations` and `Transfers`
2. **Email:** Existing optional field on the `Buyer Identity` will now be required
3. **Phone number:** Existing optional field on the `Buyer Identity` will now be required
4. **Name:** Existing optional field on the `Payment Instrument` will now be required


If your app includes a merchant with MCC 7994, all merchants must provide the four required fields. Finix will block any transactions missing these fields before they reach the card networks to keep you compliant.

## Operational Requirements

Once your account is approved, there are additional steps to register it with the card networks. Finix completes this registration process on your behalf and passes through the associated costs, which include both an initial registration fee and an annual renewal fee. Please contact your Customer Delivery Manager if you’d like more details or have any questions.

## Gaming Transaction Flow using the API

Follow these steps to process a compliant gaming transaction from buyer setup to payment completion.

### 1. Create a Buyer Identity

Begin by creating a buyer identity and include the required fields for gaming:

- `entity.​email`
- `entity.​phone`


Example
API Definition
If your request is successful, you’ll receive a `201 Created` status code and the buyer’s `Identity` in the response. Save the `id` for your next step.

### 2. Create a Buyer Payment Instrument

Now, use the buyer’s `Identity` ID to create their `Payment Instrument`. Make sure to include the required `name` field in the request body:

Example
API Definition
If your request works, you’ll get a `201 Created` status code and the buyer’s `Payment Instrument` in the response. Save the `id` for your next step.

### 3a. Creating a Transfer with Required Gaming Fields

After you’ve created the buyer `Identity` and `Payment Instrument` with the required fields, you can create a `Transfer`. To make it valid for gaming, include the `ip_address_v4` in the request body:

Example
API Definition
### 3b. Creating an Authorization with Required Gaming Fields

Just like with transfers, include the `ip_address_v4` in the request body to make the `Authorization` valid for gaming:

Example
API Definition