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

# Flexiti

Configure Flexiti pay-later payments with Hyperswitch.

{% hint style="warning" %}
**Alpha connector.** Flexiti is at alpha integration status. The payment status mapping from Flexiti is incomplete: a completed purchase currently reports as authorized rather than captured, so a successful payment may show a `requires_capture` status even though no capture call is needed or possible. Manual capture, refunds, mandates, and webhooks are not supported. Use payment sync to check payment status, and confirm current behavior with the Hyperswitch team before relying on this connector in production.
{% endhint %}

Flexiti provides a redirected pay-later checkout through Hyperswitch. The payment is captured automatically when the customer completes checkout, so no separate capture call is needed. Manual capture is not supported. Refunds and mandates are not available for this payment route.

### 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      | flexiti | not supported | not supported | automatic       | CA        | CAD        |

### Authentication

Provide the **Client id** and **Client secret** shown in the connector form. The labels and accepted body-key fields are defined by the [`flexiti.connector_auth.BodyKey` configuration](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L7994-L7996) and [`FlexitiAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/flexiti/transformers.rs#L188-L199).

### Before you start

1. Register for a Flexiti account at [flexiti.com](https://www.flexiti.com/).
2. Confirm availability with the Hyperswitch team before enabling Flexiti.
3. Have the Client id and Client secret from your Flexiti account ready.
4. To connect Flexiti to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Flexiti supports.

### Webhooks

Flexiti webhooks are not currently supported. The object lookup, event lookup, and resource lookup methods all return `WebhooksNotImplemented`; use payment sync for payment status. See [`IncomingWebhook for Flexiti`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/flexiti.rs#L701-L724) and [`ConnectorIntegration<PSync>`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/flexiti.rs#L391-L452).

### Source reference

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