---
title: Authentication Methods
slug: public-apis/authentication-methods
createdAt: 2026-03-10T15:00:50.325Z
---

::::ExpandableHeading
###

**Topic type: Constraint**

:::hint{type="warning"}
**Purpose**: Explain authentication methods used for Accertify APIs.

**Audience**: API integrators and client developers.&#x20;

**Applies to**: Accertify APIs that require authenticated HTTP requests.&#x20;

**Does not apply to**: Internal batch processing or non‑request‑based integrations
:::
::::

All Accertify API requests must be authenticated using one of the supported authentication methods. Authentication establishes the identity of the client and ensures that requests are processed under the correct integration context.

Authentication requirements apply uniformly across industries, endpoints, and fraud‑related lifecycle contexts.

The same authentication methods are used across Universal Fraud APIs, Dispute APIs, and Risk & Intelligence APIs unless otherwise specified.

## Supported Authentication Methods

Accertify APIs support the following authentication methods:

- **Basic Authentication**
- **OAuth 2.0 Client Credentials**
- **Mutual TLS (mTLS)**

Organizations use the authentication method configured for their integration during onboarding.

Authentication methods affect how a request is authorized but do not change how transactions are evaluated, scored, or processed.

::::ExpandableHeading
## Basic Authentication

Basic Authentication uses credentials issued by Accertify and is typically implemented during initial integrations.

**When using Basic Authentication:**

- Credentials are provided with each request.
- Credentials are transmitted in the HTTP Authorization header.&#x20;
- Credentials are tied to the integration configuration provided during onboarding.
- Requests must continue to comply with all field validation, hashing, and data integrity requirements.

:::hint{type="success"}
****<font color="#4f6228">**Example**</font>: `Authorization: Basic <base64(username:password)>`
:::

Accertify provides the credentials required for Basic Authentication during implementation.
::::

***

:::::ExpandableHeading
## OAuth 2.0 (Client Credentials)

OAuth 2.0 using the Client Credentials grant is supported as an alternative authentication method.

This authentication method uses short-lived access tokens rather than sending static credentials with every API request.

OAuth setup must be coordinated during onboarding. Contact Accertify Support or your implementation team if OAuth authentication is required.

### OAuth Token Endpoint

OAuth access tokens are requested from the following endpoint:

:::BlockQuote
https\://api.accertify.net/api/oauthV1/token
:::

### OAuth Authentication Flow

OAuth authentication follows this process:

1. Request an access token from the configured OAuth token service.
2. Receive an access token.
3. Include the access token in the Authorization header of API requests.
4. Obtain a new token when the existing token expires.

:::hint{type="success"}
****<font color="#4f6228">**Example**</font>: `Authorization: Bearer <access_token>`
:::

### Requesting an Access Token

OAuth access tokens are obtained using the OAuth 2.0 Client Credentials grant type.

**Method 1: Client Credentials in the Request Body**

Request body:

::::hint{type="success"}
****<font color="#4f6228">**Example**</font>:&#x20;

:::BlockQuote
grant\_type=client\_credentials
client\_id=\<client\_id>
client\_secret=\<client\_secret>
scope=\<RTD>
:::
::::

Where:

- `grant_type` must be client\_credentials
- `scope `is the scope assigned to the integration
- `client_id` is the API user name provided by Accertify
- `client_secret` is the API secret provided by Accertify

**Method 2: Basic Authentication Header**

Credentials may also be supplied in the Authorization header.

::::hint{type="success"}
****<font color="#4f6228">**Example**</font>:

Header:

:::BlockQuote
Authorization: Basic \<base64(client\_id\:client\_secret)>
:::

Request body:

:::BlockQuote
grant\_type=client\_credentials
scope=\<scope>
:::
::::

### Using the Access Token

After obtaining an access token, include it in the Authorization header for API requests:
`Authorization: Bearer <access_token>`

All subsequent API calls use the bearer token until the token expires or is replaced.

### When OAuth 2.0 Is Commonly Used

OAuth 2.0 is commonly selected when:

- Centralized credential management is required.
- Short-lived tokens are preferred over static credentials.
- Organizational security standards require token-based authentication.
- Enterprise integration standards require OAuth-based authentication.

### Integration Configuration

Authentication credentials, client identifiers, secrets, tokens, importer identifiers, and related configuration details are issued during onboarding.

Implementation details may vary by environment and integration type. Always use the authentication credentials and endpoints provided for your specific implementation.
:::::

***

:::ExpandableHeading
## Mutual TLS (mTLS)

Mutual TLS (mTLS) is supported for integrations that require certificate-based authentication.

Unlike Basic Authentication or OAuth 2.0, which authenticate requests using credentials or tokens, mTLS authenticates both the client and the server during the TLS handshake before the API request is processed.

### How mTLS Works

When using mTLS:

- The client presents a certificate during TLS negotiation.
- Accertify validates the client certificate before processing the request.
- Requests from clients without a valid certificate are rejected before application-level processing occurs.
- No additional authentication header is required beyond the mTLS configuration.

### When mTLS Is Commonly Used

mTLS is commonly selected when:

- Organizational security standards require certificate-based authentication.
- A higher level of trust is required between systems.
- OAuth or static credentials are not preferred.
- Security policies require mutual authentication at the transport layer.

### Certificate Provisioning

Client certificates must be provisioned and approved by Accertify as part of the implementation process.

Certificate requirements, exchange procedures, renewal processes, and environment-specific details are provided during onboarding.

Contact Accertify Support or your implementation team for certificate provisioning requirements.
:::

