# Segment Assign
source: https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/use-cases/assign/index.md

#### Overview {#overview}

Assigns benefits to a card by taking a card number, segment code and effective date in the input. The response is an array of bundles that are assigned to the card. At this time this endpoint supports exactly one segment code in the input. It is defined as an array for future support. The benefit allocation assign service can:

* Assign a segment to a card.
* Assign a segment code that has a bundle with a future effective date.
* Assign a segment code that has a bundle that has been expired in the past.
* Assign a segment code that has a bundle that has been expired in the future.

Diagram assign

### Use Case 1: assign segment to a card {#use-case-1-assign-segment-to-a-card}

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends a request with a card number, segment code and effective date as an input parameter.
3. Benefit Allocation Service API returns an array of bundles that are assigned to the card which contains segment benefit bundle codes assigned with effective and expiry dates of bundles.

### Use Case 2: segment code has a bundle with future effective date {#use-case-2-segment-code-has-a-bundle-with-future-effective-date}

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends request with card number, segment code and effective date as an input parameter
3. Benefit Allocation Service API returns an array of bundles that are assigned to the card which contains segment benefit bundle codes assigned with effective and expiry dates, segment bundle code with the future effective date will be applied with the future effective date.

### Use Case 3: segment code has a bundle that has been expired in the past {#use-case-3-segment-code-has-a-bundle-that-has-been-expired-in-the-past}

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends request with card number, segment code and effective date as an input parameter
3. Benefit Allocation Service API returns an array of bundles that are assigned to the card which contains segment benefit bundle codes assigned with effective and expiry dates, the segment expired bundle is not added.

### Use Case 4: segment code has a bundle with a future expiry date {#use-case-4-segment-code-has-a-bundle-with-a-future-expiry-date}

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends request with card number, segment code and effective date as an input parameter
3. Benefit Allocation Service API returns an array of bundles that are assigned to the card which contains segment benefit bundle codes assigned with effective and expiry dates, future expiration dates will get the future expiration date applied.

## Additional Information {#additional-information}

1. Look at the [API Reference](https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/api-reference/index.md) for information on how to implement this use case.
2. Look at the [Code and Formats](https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/code-and-formats/index.md) for acknowledgement responses.
