> 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-service/verify-redirect-response.md).

# Verify Redirect Response

## Overview

The `verifyRedirectResponse` method validates the authenticity of payment responses from redirect-based authentication flows (3DS, bank redirects, wallet callbacks).

**Business Use Case:** When a customer returns from a 3DS challenge or bank redirect, verify the response is legitimate before fulfilling the order.

## Purpose

| Scenario         | Benefit                        |
| ---------------- | ------------------------------ |
| 3DS completion   | Validate authentication result |
| Bank redirect    | Confirm payment success        |
| Wallet payment   | Verify token authenticity      |
| Fraud prevention | Prevent spoofed notifications  |

## Request Fields

| Field                        | Type   | Required | Description                 |
| ---------------------------- | ------ | -------- | --------------------------- |
| `merchantOrderId`            | string | Yes      | Your unique order reference |
| `requestDetails`             | object | Yes      | Redirect request details    |
| `requestDetails.headers`     | object | Yes      | HTTP headers                |
| `requestDetails.queryParams` | object | Yes      | URL query parameters        |
| `requestDetails.body`        | string | Yes      | Request body                |

## Response Fields

| Field                    | Type          | Description                   |
| ------------------------ | ------------- | ----------------------------- |
| `merchantOrderId`        | string        | Your reference (echoed back)  |
| `sourceVerified`         | boolean       | Whether response is authentic |
| `connectorTransactionId` | string        | Connector's transaction ID    |
| `status`                 | PaymentStatus | Current payment status        |
| `responseAmount`         | Money         | Verified amount               |
| `error`                  | ErrorInfo     | Error details if failed       |

## Example

### SDK Setup

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

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

### Request

```javascript
const request = {
    merchantOrderId: "order_001",
    requestDetails: {
        headers: {
            "Content-Type": "application/x-www-form-urlencoded"
        },
        queryParams: {
            payment_intent: "pi_3Oxxx...",
            payment_intent_client_secret: "pi_3Oxxx..._secret_xxx"
        },
        body: ""
    }
};

const response = await paymentClient.verifyRedirectResponse(request);
```

### Response

```javascript
{
    merchantOrderId: "order_001",
    sourceVerified: true,
    connectorTransactionId: "pi_3Oxxx...",
    status: "AUTHORIZED",
    responseAmount: {
        minorAmount: 1000,
        currency: "USD"
    },
    statusCode: 200
}
```

## Next Steps

* [capture](/integrations/prism/node/payment-service/capture.md) - Finalize payment after verification
* [get](/integrations/prism/node/payment-service/get.md) - Check payment status


---

# 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-service/verify-redirect-response.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.