Verification, permissions, and eligibility

Access depends on who makes the request, which resource it targets, and what the intended operation requires.

​

Authentication vs. permission

Authentication identifies your integration through its API credentials and request signature. Permission determines whether it can perform the requested operation. A correctly signed request can still be denied. See Authentication for request signing.

​

Identity verification vs. eligibility

Know Your Customer (KYC) checks establish a client’s identity. Eligibility determines whether a particular service or operation is available to that client or account. Opening or completing a hosted verification screen isn’t a verification decision. Requirements can change after onboarding. Use Get verification requirements for current requirements and access state.

​

Verified identity vs. destination ownership

A verified identity doesn’t establish ownership of every bank account or wallet. Bank links check the bank account holder against the verified identity. External wallets can require separate address-ownership verification. Conversion rules also require bank destinations to match the account’s verified identity. See Bank links and address-ownership verification.

​

Listed asset vs. available operation

An asset in the general catalog may be unavailable for a particular account, country, or action. Check the relevant account’s available assets, funding methods, and limits. Confirm country, currency, and payment-route support for your integration. An example using a currency or network doesn’t establish availability in another market. See Coverage.