> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/prism/node/payment-method-authentication-service/authenticate.md).

# Authenticate

## Overview

The `authenticate` method executes the 3D Secure authentication step. For frictionless flows, it completes silently. For challenge flows, it presents the bank's authentication page.

**Business Use Case:** After initiating 3DS with preAuthenticate, this handles the actual authentication, managing customer interaction with the bank's page.

## Purpose

| Flow Type    | What Happens                      |
| ------------ | --------------------------------- |
| Frictionless | Completes without customer action |
| Challenge    | Presents bank challenge page      |

## Request Fields

| Field                | Type          | Required | Description                            |
| -------------------- | ------------- | -------- | -------------------------------------- |
| `merchantOrderId`    | string        | Yes      | Your unique order reference            |
| `amount`             | Money         | Yes      | Transaction amount                     |
| `paymentMethod`      | PaymentMethod | Yes      | Card details                           |
| `authenticationData` | object        | No       | Existing 3DS data from preAuthenticate |
| `returnUrl`          | string        | No       | URL to redirect after authentication   |

## Response Fields

| Field                    | Type   | Description                    |
| ------------------------ | ------ | ------------------------------ |
| `connectorTransactionId` | string | Connector's authentication ID  |
| `status`                 | string | AUTHENTICATED, FAILED, PENDING |
| `authenticationData`     | object | 3DS results (ECI, CAVV)        |
| `redirectionData`        | object | Challenge URL if needed        |
| `statusCode`             | number | HTTP status code               |

## Example

### SDK Setup

```javascript
const { PaymentMethodAuthenticationClient } = require('hyperswitch-prism');

const authClient = new PaymentMethodAuthenticationClient({
    connector: 'stripe',
    apiKey: 'YOUR_API_KEY',
    environment: 'SANDBOX'
});
```

### Request

```javascript
const request = {
    merchantOrderId: "order_001",
    amount: {
        minorAmount: 10000,
        currency: "USD"
    },
    paymentMethod: {
        card: {
            cardNumber: { value: "4242424242424242" },
            cardExpMonth: { value: "12" },
            cardExpYear: { value: "2027" }
        }
    },
    returnUrl: "https://your-app.com/3ds/return"
};

const response = await authClient.authenticate(request);
```

### Response - Frictionless

```javascript
{
    connectorTransactionId: "pi_3Oxxx...",
    status: "AUTHENTICATED",
    authenticationData: {
        eci: "05",
        cavv: "AAABBIIFmA=="
    },
    statusCode: 200
}
```

### Response - Challenge Required

```javascript
{
    connectorTransactionId: "pi_3Oxxx...",
    status: "PENDING",
    redirectionData: {
        url: "https://acs.bank.com/3ds/challenge",
        method: "POST"
    },
    statusCode: 200
}
```

## Next Steps

* [postAuthenticate](/integrations/prism/node/payment-method-authentication-service/post-authenticate.md) - Validate authentication results
* [Payment Service](/integrations/prism/node/payment-service.md) - Process payment with auth data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/prism/node/payment-method-authentication-service/authenticate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.