# Support
source: https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/support/index.md

## FAQ {#faq}

The Benefit Allocation Service allows issuers to segment cardholders to receive different card value propositions. After assigning a card account number to a segment, the next options available for the issuer would be to cancel or replace a segment on the account number, or if the card was lost or needed to be locked, the card can be frozen or the card can be replaced through a card replacement request in GBP. A segment is identified and used by an issuer to group a portfolio of cardholders who will receive a certain set of benefits. [Quick Start Guide](https://developer.mastercard.com/platform/documentation/getting-started-with-mastercard-apis/quick-start-guide/) Issuers are all potential consumers of this API. To test the Benefit Allocation Service API in the Sandbox environment, you create a project, generate sandbox keys, and use the test data. Refer to the Getting Started guide for details. The main use cases for these services include:

* Assign segments to a card
* Cancel segments from a card
* Replace segments from a card
* Replace a card
* Freeze/Unfreeze a card
The card number is the full 16 digit card number. The date for which benefits are to be determined. Defaults to the current date if not provided. Date format is yyyy-mm-dd.
* Canceling a segment on a card removes the personalization on the card and returns the cardholder to the regular card value proposition at the account range and product level.
* Freezing a card (in the case of lost, stolen or freezing an account), Mastercard will not allow the cardholder to receive benefits and will be asked to consult with their issuer.
The typical data format used in the Benefits Allocation Service APIs is JSON. Benefit Allocation Service API is a global product and is available for all markets. In order to start a project using the Benefit Allocation Service API, contact Mastercard Representative/Account Manager or send an email to [Global.Benefits.Platform.Product@mastercard.com](mailto:Global.Benefits.Platform.Product@mastercard.com) For pricing information on Benefit Allocation Service API, contact Mastercard Representative/Account Manager or send an email to [Global.Benefits.Platform.Product@mastercard.com](mailto:Global.Benefits.Platform.Product@mastercard.com) Please follow guide [here](https://developer.mastercard.com/benefit-allocation-service-mtls/tutorial/create-project/) for obtaining sandbox access. Please follow guide [here](https://developer.mastercard.com/benefit-allocation-service-mtls/tutorial/prod-access/) for obtaining production access. Please follow guide [here](https://developer.mastercard.com/platform/documentation/security-and-authentication/using-mtls-to-access-mastercard-apis/#1-before-you-start---getting-mtls-client-certificates-for-your-project) for obtaining certs. The request payload must be encrypted as it has PCI data, the response is not encrypted as there are no sensitive data in the response. Please find more details [here](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/). The PEM certificate for encryption can be downloaded from the project page under Client Encryption Keys -\> Actions -\> Download encryption key. Benefit Allocation Services is available through batch, API or the combination. It is another way to provide client signature verification Signing is entirely optional. We accept calls with or without signing. The average response time per endpoint is 0.468 seconds. The Throughput per Second (TPS) per customer is 36.75. While there is no throttling policy, Mastercard reserves the right to limit user's requests to preserve the reliability of the system for all users.

## Get Help {#get-help}

### Contact us for technical support. {#contact-us-for-technical-support}