# Guide for Partners (Clients) - Recipient
source: https://developer.mastercard.com/open-finance-us/documentation/participant-model/partner-linked/client/index.md

As an Open Finance partner you are able to obtain consent from your customer to allow a third party to access their banking data for a specific purpose - for example, to access their ACH routing details in order to make a payment.

To do this you must obtain the customer's consent using the Data Connect user experience, then create a third party access token (consent receipt) which specifies the access to be granted. You then share this consent receipt with your chosen third party processor so that they can make the necessary Open Finance API calls.

In order to do so, the third party processor must have a secure method of receiving the consent receipt from you, and must be onboarded in order to use Mastercard Open Finance APIs.

The following third party processors have support for Partner Linked access currently:

* Dwolla - see the Dwolla [Exchanges](https://developers.dwolla.com/api-reference/exchanges) documentation for details.
* Usio - see the Usio [ACH Payments](https://payments.usiopay.com/2.0/documentation/#ach) documentation for details.
* Highnote

If you have a relationship with other payment processors that you would like to use, they will first need to integrate with Mastercard Open Finance and provide a mechanism for sharing the consent receipt.

Read the following for more details:

* [Client (requestor) steps](https://developer.mastercard.com/open-finance-us/documentation/participant-model/partner-linked/client/client-steps/index.md)
* [Manage access keys](https://developer.mastercard.com/open-finance-us/documentation/participant-model/partner-linked/client/manage-access-keys/index.md)
* [Example - Using Dwolla for payment processing](https://developer.mastercard.com/open-finance-us/documentation/participant-model/partner-linked/client/example-dwolla/index.md)