> 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/breadpay.md).

# Breadpay

Connect Breadpay through Hyperswitch.

{% hint style="warning" %}
**Alpha connector.** Breadpay is at alpha integration status, and refunds are declared but not implemented. Reach out on the [Slack Community](https://inviter.co/hyperswitch-slack) to check where it stands before you build on it.
{% endhint %}

Breadpay offers a pay-later redirect: the customer leaves your checkout to arrange financing with Breadpay and returns once it is settled. There are no webhooks, so payment status comes from syncing rather than callbacks.

### Status and capabilities

**Integration status:** alpha

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type     | Mandates      | Refunds   | Capture methods                         | Countries | Currencies |
| -------------- | -------- | ------------- | --------- | --------------------------------------- | --------- | ---------- |
| pay later      | Breadpay | not supported | supported | automatic, manual, sequential automatic | -         | -          |

The matrix declares refunds, but neither refund flow is implemented: `get_url()` returns `NotImplemented` for [refund execute](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs#L642-L648) and for [refund sync](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs#L726-L732), and both `build_request()` implementations call it, so a refund fails before it is sent. Capture is unaffected and works as declared. Tracked upstream as [issue 14373](https://github.com/juspay/hyperswitch/issues/14373).

### Authentication

Supply **API Key** and **API Secret**, the labels shown in the Hyperswitch control center. Breadpay sends them as HTTP Basic authentication in the `Authorization` header; the header builder also adds `Content-Type: application/json`. See [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs#L134-L148) and [`build_headers()`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs#L99-L110). The labels come from [`[breadpay.connector_auth.BodyKey]`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/connector_configs/toml/sandbox.toml#L7898-L7901).

### Before you start

1. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/).
2. Open Breadpay in the connector configuration form.
3. Enter the **API Key** and **API Secret** from your Breadpay account.

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

No provider registration URL was verified for this page.

### Webhooks

Breadpay does not support incoming webhooks. The object-reference, event-type, and resource handlers all return `WebhooksNotImplemented`, so use payment API syncs for status instead of waiting for callbacks. See [`IncomingWebhook`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs#L780-L804).

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7`. See [Breadpay connector source](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay.rs) and [Breadpay transformers](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/breadpay/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/breadpay.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.