# Pre-selected Source
source: https://developer.mastercard.com/ob-accept-payments/documentation/features/return-user-experience/pre-selected-source/index.md

Our pre‑selected source feature allows you to pass the PSUs existing bank account details (for example sort code and account number, or IBAN) directly in the Create Payment request, if you are already aware of them. Mastercard is then able to map these provided details to a particular ASPSP. There is also the ability to define whether you want to allow the PSU to be able to change the pre-selected source account in the payment flow, this is achieved via the 'allowAccountChange' field.

When a pre-selected source account is provided, the Mastercard payment flow will skip the bank selector screen, instead taking the PSU directly to a consent page displaying the merchant name, the masked pre-selected bank details, and the necessary consent.
**Note** - in markets where double strong customer authentication (SCA) is necessary, providing the pre-selected source account proceeds the PSU directly to the SCA for payment authorization, removing the first AIS SCA step that is required to collect account details. This greatly shortens the customer journey and simplifies the payment flow where you already know the customer's bank details

###### When you should use pre-selected source {#when-you-should-use-pre-selected-source}

You can use this when:

* You already know and store the customer's bank details (for exmaple, during signup or billing setup)
* The PSU has granted consent for the merchant to reuse these details
* You want to skip the bank selector and first SCA to reduce friction

<br />

This feature is of particular benefit when you have a recognised and accepted source account for your user, and want to lock the payment to that account, or for wallet/stored payment method experiences or for merchant loyalty apps where the user has pre-linked their bank. You may have the pre-selected source account information from previous payments, from a subscription the user has with you, or a variety of other methods.   

The following Figma diagram shows how the user payment flow is impacted when a preselected source account is passed in the create payment request.   

For the best viewing experience click the full screen option or zoom using the controls located on the right. How it works:   

**A note on edge cases**

Please note that there may be cases where Mastercard is unable to map the pre-selected source account to a unique ASPSP, but 2 or more ASPSPs. This usually occurs when there has been various M\&A activity involving the bank over time. In this instance, Mastercard will display an account disambiguation screen to the PSU, where they are able to select which of the 2 or more banks their pre-selected source account belongs to.

Please speak to your account manager for more information.