# Fee Collection for Debit Mastercard and Europe Dual Acquirers
source: https://developer.mastercard.com/mastercom/documentation/use-cases/feecollect_debit/index.md

## Fee Collection for Debit Mastercard and Europe Dual Acquirers {#fee-collection-for-debit-mastercard-and-europe-dual-acquirers}

The following use case demonstrates the process of a sender creating a fee collection and of a receiver responding. This use case applies only when the original transaction has a single-message issuer, dual-message acquirer, and a transaction without a PIN.
Diagram createFeeCollectionEventDebitMastercardEuropeDual

1. (Sender) [Create Debit MC / Europe Dual Acquirer fee collection item](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#create-debit-mc-europe-dual-acquirer-fee-collection-item) to create a fee collection event.


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

2. (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`

3. (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 Debit MC / Europe Dual Acquirer fee collection item](https://developer.mastercard.com/mastercom/documentation/test-cases/test-cases/index.md#create-debit-mc-europe-dual-acquirer-fee-collection-item) endpoint.


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