API authentication is the process by which an application programming interface confirms the identity of the system calling it before acting on the request. Payments APIs, where a forged call could move money, usually combine several methods.
The simplest is an API key, a secret string sent with each call. OAuth 2.0, using the client credentials grant, issues short-lived access tokens to server-to-server clients instead of relying on a permanent secret. Mutual TLS requires both sides to present certificates when the encrypted connection opens. Request signing, often with an HMAC calculated over the message and a timestamp, proves the request was not altered and helps block replays. Many providers also restrict calls to a whitelist of approved IP addresses. Read-only data APIs carry less risk than those that move funds. Authentication establishes who is calling; authorisation decides what the caller may do, while rate limiting and an idempotency key guard against abuse and duplicate payments.