Locking fields

Some service providers support locking the token and wallet address fields within their widgets. To do this, simply pass in the lockFields param to the widget endpoint with the values of destinationCurrencyCode/sourceCurrencyCode (depending on buy vs sell flow), walletAddress, or both. Here are the service providers that support locking those fields in their widgets:

	Locking cryptocurrency	Locking wallet address
Banxa	Not supported	Not supported
BTC Direct	Supported	Supported
MoonPay	Supported	Always locked when passed in
Onramp Money	Not supported	Always locked when passed in
Ramp.Network	Supported	Not supported
Simplex	Supported	Supported
Transak	Supported	Supported
Sardine	Always locked	Always locked
Binance Connect	Always locked	Not supported
TransFi	Always locked when passed in	Always locked when passed in
Unlimit	Supported	Supported
Paybis	Not supported	Not supported
Fonbnk	Not supported	Supported
Koywe	Always locked when passed in	Always locked when passed in
Robinhood	Always locked when passed in	Always locked when passed in
Coinbase	Not supported	Not supported
Blockchain	Always locked when passed in	Always locked when passed in

Here's a sample buy request with both the token and wallet address fields locked:

{
    "sessionData": {
        "walletAddress": "2N3oefVeg6stiTb5Kh3ozCSkaqmx91FDbsm",
        "countryCode": "US",
        "sourceCurrencyCode": "USD",
        "sourceAmount": "100",
        "destinationCurrencyCode": "USDC",
        "serviceProvider": "TRANSAK",
        "lockFields": ["destinationCurrencyCode","walletAddress"]
    },
    "externalCustomerId": "test1",
    "externalSessionId": "test1"
}