Does a connected NEAR app necessarily have native transfer permission?

No. Its function-call key can be limited to specified contract actions and cannot transfer native NEAR.

Can I spend a function-call gas allowance as the exchange input?

That allowance limits gas spending under the key. It is not a separate transferable token balance or authorization to fund an exchange.

Should I give exchange support a full-access key to fix a payment?

No. Keep account credentials private and use the legitimate wallet’s transfer workflow. Describe the error without sharing control of the account.

NEAR to BTC: app access is not transfer permission

What did the connected application actually demonstrate?

It displayed the account and a balance: That observation identifies a view of the account. It does not prove that the application session can authorize a native NEAR payment. Keep account visibility separate from the permission needed for the action you intend to sign.
It completed an action in one contract: A NEAR function-call key can be scoped to one contract and permitted methods. Success there does not establish permission to send native NEAR to the exchange’s funding address. Do not diagnose the exchange as unavailable from an unrelated app action.
It showed an allowance denominated in NEAR: The function-call allowance concerns gas spending under that key. It is not a separate wallet balance that the application can transfer as an exchange payment. Read the underlying account and the actual wallet transfer review instead.

A limited app key has a narrower job than a sending wallet

NEAR’s official access-key documentation distinguishes Function-Call permissions from Full-Access permissions. Function-call keys permit scoped contract calls and prohibit native NEAR transfers. Full-access permissions can authorize transfers as well as other account actions. This is why an app can continue to work while a payment action is unavailable in the same session.

The distinction is explanatory, not an instruction to give an application broader authority. Do not share a full-access credential with the exchange, a website or support to make a payment work. Use the legitimate wallet’s own transfer workflow, or ask its provider to explain the available authorization path. No account-key change is part of this exchange page.

Match the observation to the question it can answer

Observation	Useful for	Not proof of
App login or connected-account label	Knowing which account the app recognizes	Permission to transfer native NEAR
Scoped contract-call success	Knowing that the allowed app action worked	A completed exchange funding payment
Function-call gas allowance	Understanding the key’s gas-spending limit	A saleable token inventory or payout amount
Native NEAR payment record	Tracing the actual input transfer	Receipt of the separate BTC output

A permission and evidence map. It contains no key material, account modifications or signing commands.

Resolve the sending workflow before relying on an exchange estimate

First identify the account holding the native NEAR and the wallet that legitimately manages it. Confirm that the wallet can present an ordinary transfer review for that account. Then review the exchange’s current funding instruction and the Bitcoin receiving details. An app’s permitted contract is not a replacement funding recipient.

If authorization fails, keep the displayed error and describe which action was attempted without including private credentials. If a transfer was already submitted, preserve its transaction reference and check that record before retrying. A failed app permission check alone does not establish that NEAR left the account, and a wallet transfer confirmation is not itself the BTC payout receipt.

Questions about the NEAR sending session

Does a connected NEAR app necessarily have native transfer permission?: No. Its function-call key can be limited to specified contract actions and cannot transfer native NEAR.
Can I spend a function-call gas allowance as the exchange input?: That allowance limits gas spending under the key. It is not a separate transferable token balance or authorization to fund an exchange.
Should I give exchange support a full-access key to fix a payment?: No. Keep account credentials private and use the legitimate wallet’s transfer workflow. Describe the error without sharing control of the account.

Official NEAR permission documentation

Reviewed: 2026-10-23