# Fee Collection
source: https://developer.mastercard.com/mastercom/documentation/use-cases/feecollection/index.md

## Fee Collection {#fee-collection}

The following use case demonstrates the process of a sender creating a fee collection and of a receiver responding.
Diagram createFeeCollectionEvent

1. **OPTIONAL STEP** : (Sender) [Get possible values for fee collection event](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#get-possible-values-for-fee-collection-event) to retrieve a structure containing possible values used to create a fee collection event.


API Reference: `POST /v6/claims/{claim-id}/fees/loaddataforfees`

2. (Sender) [Create fee collection event](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#create-fee-collection-event) to create a fee collection event.


API Reference: `POST /v6/claims/{claim-id}/fee`

3. (Receiver) [Retrieve claims from queue within date range](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#retrieve-claims-from-queue-within-date-range) to retrieve claims from the *FeeCollectionUnworked* queue.


API Reference: `POST /v6/queues`

4. (Receiver) Receiver can either accept or respond to the fee collection. If accepted, no further action is necessary. To respond and create a new fee collection event linked to the original fee collection event, the receiver can use the [Create fee collection event](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#create-fee-collection-event) endpoint.


API Reference: `POST /v6/claims/{claim-id}/fee`