> 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/connectors-integrations/payment-processor-capabilities/available-connectors/amazonpay.md).

# Amazon Pay

Accept Amazon Pay wallet payments.

Amazon Pay provides a wallet checkout route for customers using their Amazon account. The wallet route uses automatic capture and supports refunds. It does not declare mandate reuse or webhook handling.

### Status and capabilities

**Integration status:** beta

**Category:** alternative payment method

**Webhook flows:** None declared in code

| Payment method | Type       | Mandates      | Refunds   | Capture methods | Countries | Currencies |
| -------------- | ---------- | ------------- | --------- | --------------- | --------- | ---------- |
| wallet         | Amazon Pay | not supported | supported | automatic       | USA       | USD        |

### Authentication

Supply **Public Key** and **Private Key**, the labels shown in the Hyperswitch control center. Hyperswitch hashes the canonical request with SHA-256, signs the algorithm line and request hash with RSA-PSS-SHA256 using the Private Key, Base64-encodes the signature, and places the Public Key with the signature in the `Authorization` header. See [`AmazonpayAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay/transformers.rs#L323-L339), [`create_authorization_header()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L92-L130), [`create_signature()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L132-L184), and [`build_headers()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L209-L278).

### Before you start

1. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/).
2. Have four values ready, all of them required by the connector form:

   | Field           | What it is                                                     |
   | --------------- | -------------------------------------------------------------- |
   | **Public Key**  | The credential Hyperswitch sends in the `Authorization` header |
   | **Private Key** | The RSA key Hyperswitch signs each request with                |
   | **Merchant ID** | Your Amazon Pay merchant identifier                            |
   | **Store ID**    | The Amazon Pay store the payments belong to                    |
3. Enter all four during connector activation. Merchant ID and Store ID are wallet fields on the same form; activation without them is incomplete.

To connect Amazon Pay to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for Amazon Pay-specific behavior.

### Webhooks

Amazon Pay webhooks are not supported. Sync instead: payment sync for payment status, and refund sync for refund status, which this connector implements as a `GET` to `/refunds/{connector_refund_id}`. [`get_webhook_object_reference_id()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L727-L732), [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L734-L740), and [`get_webhook_resource_object()`](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs#L742-L748) each return `WebhooksNotImplemented`.

### Source reference

Authentication and webhook behavior on this page follows [Amazon Pay connector source](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay.rs) and [Amazon Pay transformers](https://github.com/juspay/hyperswitch/blob/9e5dd70d1cb4011bbcca3114862406008a0b61f8/crates/hyperswitch_connectors/src/connectors/amazonpay/transformers.rs).


---

# 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/connectors-integrations/payment-processor-capabilities/available-connectors/amazonpay.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.