> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encorekit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# isClaimEnabled

> Turn off the claim call to action while leaving the rest of the offer sheet intact

Controls whether the claim call to action is clickable. Set it to `false` to turn off and
gray out the claim button while still showing the offer.

## Structure

```typescript theme={null}
Encore.isClaimEnabled: boolean   // default true; read and assigned directly
```

## When to use it

Turn it off when a claim would fail or conflict for reasons only your app knows, and
showing the offer unavailable beats hiding it:

* The user is mid-checkout in one of your own flows.
* Their account is in a state the advertiser rejects.
* You are running a maintenance window on your side of the integration.

```javascript theme={null}
// Entering a flow where claiming would conflict
Encore.isClaimEnabled = false;

// Leaving it
Encore.isClaimEnabled = true;

const result = await Encore.placement('cancel_flow').show();
```

## Behavior

| Aspect                     | Behavior                                                                                                                                                        |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rendering                  | The offer, copy, and imagery still render. Only the claim button changes: it grays out and no longer responds to a click.                                       |
| Coverage                   | Applies to both claim surfaces: the per-card Claim button in the `'reduceChurn'` carousel, and the single bottom call to action in `'rewardUsers'`.             |
| With a custom claim button | Applies there too. A [`claimButton` appearance slot](/publishers/web/guides/advanced-ui) is your styling, but the claim stays the SDK's, and so does this gate. |
| Dismissal                  | Always available. The reward composition's "No thanks", the close button, and backdrop dismissal are never affected.                                            |
| Reporting                  | A sheet shown with claiming off is a real presentation, and resolves through `show()` like any other.                                                           |

<Warning>
  The flag is read when the sheet is built, so it applies from the next `show()` onward.
  Assigning it while a sheet is on screen does not change the sheet in front of the user.
</Warning>

## Marking up your own claim button

If you supply your own claim button through the
[`claimButton` appearance slot](/publishers/web/guides/advanced-ui), the SDK still owns
whether it acts, and turning this flag off makes your element unavailable along with
everything else. It cannot carry the native `disabled` attribute, because that attribute
only means something on a `<button>` and your element is mounted inside a
`role="button"` host. The host carries `aria-disabled="true"` instead and leaves the tab
order, so assistive technology and keyboard users get the same answer as everyone else.

If you style the unavailable state yourself, target both forms:

```css theme={null}
/* The SDK's own button */
.encore-reward-cta-primary:disabled { opacity: 0.5; }

/* Your element's host, when you supplied a claimButton slot */
.encore-reward-cta-primary[aria-disabled='true'] { opacity: 0.5; }
```

## Related

* [`placement()`](/publishers/web/sdk-reference/placement): the sheet this gate applies to.
* [`show()`](/publishers/web/sdk-reference/show): the result contract, which this flag does not change.
* [Advanced UI](/publishers/web/guides/advanced-ui): supplying your own claim button, which this gate still applies to.