# Search Redeemer Profile
source: https://developer.mastercard.com/digital-redemptions/documentation/use-cases/redeemers-profile/search-redeemer-profile/index.md

## Overview {#overview}

This use case fetches a redeemer profile for a given BCN (Bank Customer
Number), BAN (Bank Account Number), or RANAC (Random Account). It returns the
RANAC for use in redemption API calls. It also returns household-level points
and the customer's role in the household. If you pass a valid
redemptionItemId, the response also returns the cost per point (CPP) configured
for the Rewards program.

### Why this endpoint {#why-this-endpoint}

Use `POST /redeemers/search` when the cardholder has just entered a card
number (BAN) or you hold a bank customer number (BCN) and you need to find
out whether the account is eligible and how many points it has. The search
is a POST rather than a GET because the identifiers are sensitive and must
travel in an encrypted request body. The response returns the RANAC, which
you then pass to every later call, so this is normally the first Digital
Redemptions call in a checkout flow. If you already hold the RANAC, use
[Get Redeemer Profile](https://developer.mastercard.com/digital-redemptions/documentation/use-cases/redeemers-profile/get-redeemer-profile/index.md),
which needs no encryption.

### Prerequisites {#prerequisites}

The following prerequisites apply to this endpoint:

* Your Sandbox or Production Client ID is mapped to the cardholder's Rewards program.
* Your client encrypts the request body with the Mastercard encryption key for the environment. Refer to payload encryption in [Use Cases](https://developer.mastercard.com/digital-redemptions/documentation/use-cases/index.md).

## Sequence diagram {#sequence-diagram}

Diagram search-redeemer-profile

##### Execution steps {#execution-steps}

1. The consumer signs into the customer application.
2. The customer authenticates the consumer.
3. The customer sends a signed request to Digital Redemptions for the cardholder's program points balance, conversion factors, and other profile details.
4. The Search Redeemer Profile request has optional fields. Refer to the field descriptions on the [API reference page](https://developer.mastercard.com/digital-redemptions/documentation/api-reference/index.md) for more information.

* **redemption_item_id** : Identifier for the Reward Item set up during partner configuration and shared with the Digital Merchant. To return conversionFactors in the response, redemption_item_id is required.
* **includes** : Attributes to include in the response that are not returned by default, such as preferences.
* **programId** : Program identifier in which the cardholder is enrolled.

5. The following are mandatory request parameters:

* **user_id** : The identifier used to identify a user uniquely.
* **user_id_type** : Type of the user or account identification. Supported identifier is RANAC, BAN, BCN.
* **redemptionType** : Supported redemptionType is CASHBACK, MERCHANDISE, TRAVEL.

6. Mastercard Network API Gateway authenticates and authorizes the customer and routes a valid request to Digital Redemptions.
7. The Digital Redemptions Service validates the request parameters received through the `POST /redeemers/search` endpoint.
8. The Digital Redemptions Service retrieves the available points balance.
9. The Digital Redemptions Service sends a `200` response with the program points balance, conversion factors, and other profile details.
10. The Digital Redemptions Service sends a 4xx or 5xx status code for an invalid request.

You will receive an error response for an invalid request or any missing request parameter. In that case, you need to update the input and perform step 3 again.

## Endpoint {#endpoint}


API Reference: `POST /redeemers/search`

## Points Values {#points-values}

Each program may have a different cash value per reward point, called the
conversion factor. The Get Redeemer Profile and Search Redeemer Profile
responses include the available points, their cash value and currency, and
the program's points name, such as "Miles" or "Program Points." The merchant
can show the cardholder how many points are available and how much they can
reduce the transaction total. For example: "Mary, you have 10,500 Accolade
Points worth $105.00 toward this purchase."