Review AI connection permissions

PayerOne shows the permissions requested by an AI connection before you approve it. Review the actual consent screen and select only the access you want to grant. Tools are constrained by the permissions recorded for that connection.

Read permissions

Read access can cover account details, analytics, orders, transactions, refunds, payment gateway availability, webhook endpoint origins and billing. Customer details require their own permission where offered. Some customer references remain masked without that permission.

Payment resolution is an action

**Check and resolve payments** can verify reported blockchain payments and start processing eligible funds for your merchant account. It can include other supported payments at the same receiving address. It does not change your payout destination. When you grant this action, eligible checks can start processing without a second approval for every payment.

If you want investigation without starting processing, grant the available read permissions and leave resolution actions unselected. A read-only connection cannot acquire an action just because the application later offers a new default. Review a new consent request if you need additional access.

What to share in chat

Provide order references, transaction hashes, supported explorer links and the relevant date or currency. Never paste merchant tokens, Private Keys, wallet seed phrases, provider secrets or OAuth tokens. The connector uses safe projections rather than exposing stored credentials.

Understand the answer

Ask the AI to distinguish recorded order state, provider status and blockchain settlement. Payment summaries can include amounts in several currencies; they must remain separate. A request to start processing is not confirmation that funds have settled or that your website credited a customer.

Use [Connected apps](https://dashboard.payerone.com/mcp/connections) to inspect the permissions for an existing connection or revoke that connection. The dashboard displays permissions from the server; a permission name in general documentation does not imply it is available or granted to your account.