# Replace Bundles
source: https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/use-cases/bundle-operations/replace_bundles/index.md

#### Overview {#overview}

**Actors:** Issuer developer, Mastercard Global Benefits Platform  

**Preconditions:** The old bundle is currently assigned to the card; the new bundle is pre-configured for the ICA; the effective date is today or a future date (past dates are not allowed)  

**Outcome:** The old bundle is expired the day before the effective date; the new bundle is assigned from the effective date  

**Endpoint:** `PUT /card-bundles-replacements` --- use this endpoint to swap one active bundle for a different one; use [Update Bundles](https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/use-cases/bundle-operations/update_bundles/index.md) if you only need to change the dates without changing the bundle code

Replaces bundles currently assigned to a card with the requested bundles. The request includes the card number and, for each replacement, the existing bundle code, the new bundle code, and the effective date. The service expires each existing bundle and assigns its replacement starting on the specified date. The response lists the bundles newly assigned to the card.
Diagram replace_bundles
API Reference: `PUT /card-bundles-replacements`

### Use Case 1: replace bundle associated with a card {#use-case-1-replace-bundle-associated-with-a-card}

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends a request with a card number, old bundle code, new bundle code and effective date as an input parameter
3. Benefit Allocation Service API returns the benefit bundle codes assigned during replace with effective and expiration dates.

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

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends request with a card number, old bundle code, new bundle code and effective date as an input parameter
3. Benefit Allocation Service API returns the benefit bundle codes assigned during replace with effective and expiration dates. bundle codes with the future effective date will be applied with the future effective date

### Use Case 3: replace bundle code that has a bundle that has been expired in the past {#use-case-3-replace-bundle-code-that-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 a card number, old bundle code, new bundle code and effective date as an input parameter
3. The Benefit Allocation Service API returns the benefit bundle codes assigned during replacement, along with their effective and expiration dates. A bundle that expired in the past is not added.

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

1. Cardholder requests a new benefit be associated with their card.
2. Issuer sends request with a card number, old bundle code, new bundle code and effective date as an input parameter
3. Benefit Allocation Service API returns the benefit bundle codes assigned during replace with effective and expiration dates, future expiration dates will get the future expiration date applied.