# Uploading First Presentment Test Data for Acquirers
source: https://developer.mastercard.com/mastercom-extended/documentation/additional-resources/uploading_first_presentment_test_data_for_acquirers/index.md

Acquirers receive Collaboration requests and respond to them in MTF for testing. The Mastercom Extended API supports testing for single message, non-switched, and authorization-only dual message transactions.

## Creating Test Data for Non-switched Transactions {#creating-test-data-for-non-switched-transactions}

To upload first presentment test data for non-switched transactions into MTF, acquirers follow these steps:

1. Create the first presentment test data.

2. Create a request to the POST /simulations/transactions endpoint using the test data.

3. Wait at least two hours for the data to appear in the Mastercom system.

4. Create a request to the POST /queues/{queue_id}/searches endpoint to locate the test data in the Acquirer Collaboration Unworked queue.

5. Respond to the Collaboration requests on the claims in the queue.

## Creating Test Data for Single Message System Transactions {#creating-test-data-for-single-message-system-transactions}

To upload first presentment test data for Single Message System transactions into MTF, acquirers follow these steps:

1. Using Mastercard Test Cards, create the first presentment test data (Financial Transaction Request/0200) and send it to the Mastercard Debit Switch in MTF.

2. Create a request to the POST /simulations/transactions endpoint using the test data that the acquirer previously staged in Mastercard Debit Switch.

3. Wait at least three days for the data to appear in the Mastercom system.

4. Create a request to the POST /queues/{queue_id}/searches endpoint to locate the test data in the Acquirer Collaboration Unworked queue.

5. Respond to the Collaboration requests on the claims in the queue.