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

# Fiuu

Configure Fiuu bank redirect, card, real-time payment, and wallet payments with Hyperswitch.

Fiuu combines Malaysian bank redirects and DuitNow with card and wallet payments. Its card routes support mandates, while every declared payment route supports refunds and multiple capture modes. Apple Pay and Google Pay require additional wallet metadata before they can be used.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** payments, refunds

| Payment method    | Type               | Mandates      | Refunds   | Capture methods                         | 3DS                 | Card networks                                          | Countries | Currencies |
| ----------------- | ------------------ | ------------- | --------- | --------------------------------------- | ------------------- | ------------------------------------------------------ | --------- | ---------- |
| bank redirect     | Online Banking FPX | not supported | supported | automatic, manual, sequential automatic | not applicable      | -                                                      | MYS       | MYR        |
| card              | Credit Card        | supported     | supported | automatic, manual, sequential automatic | supported, optional | Diners Club, Discover, JCB, Mastercard, UnionPay, Visa | 9         | 9          |
| card              | Debit Card         | supported     | supported | automatic, manual, sequential automatic | supported, optional | Diners Club, Discover, JCB, Mastercard, UnionPay, Visa | 9         | 9          |
| real time payment | DuitNow            | not supported | supported | automatic, manual, sequential automatic | not applicable      | -                                                      | MYS       | MYR        |
| wallet            | Apple Pay          | not supported | supported | automatic, manual, sequential automatic | not applicable      | -                                                      | MYS       | MYR        |
| wallet            | Google Pay         | not supported | supported | automatic, manual, sequential automatic | not applicable      | -                                                      | MYS       | MYR        |

### Authentication

Provide the **Verify Key**, **Merchant ID**, and **Secret Key** shown in the connector form. The labels and accepted signature-key fields are defined by the [`fiuu.connector_auth.SignatureKey` configuration](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L6581-L6584) and [`FiuuAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs#L73-L89).

Wallet setup requires these fields from the [`fiuu.metadata` configuration](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L6586-L6708):

| Wallet     | Required fields                                                                                                                                                                                     |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Pay | Google Pay Merchant Name, Google Pay Merchant Id, Google Pay Merchant Key, Allowed Auth Methods                                                                                                     |
| Apple Pay  | Merchant Certificate (Base64 Encoded), Merchant PrivateKey (Base64 Encoded), Apple Merchant Identifier, Display Name, Domain, Domain Name, Merchant Business Country, Payment Processing Details At |

For Google Pay, Allowed Auth Methods accepts `PAN_ONLY` and `CRYPTOGRAM_3DS`. For Apple Pay, Domain accepts `web` or `ios`, and Payment Processing Details At is set to `Hyperswitch`.

### Before you start

Have the Verify Key, Merchant ID, and Secret Key ready. Add the required wallet metadata when you enable Apple Pay or Google Pay. To connect Fiuu to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Fiuu supports.

### Webhooks

Configure the **Source verification key** shown in the connector form. Fiuu verifies payment and refund callbacks with MD5, using a different ordered message for each payload type. See [`fiuu.connector_webhook_details`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L6709-L6710), [`get_webhook_source_verification_algorithm()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu.rs#L798-L803), and [`get_webhook_source_verification_message()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu.rs#L834-L894).

The payment and refund status enums each define three named wire values and one fallback, for eight outcomes total:

| Payload | Wire value      | Effect                                            |
| ------- | --------------- | ------------------------------------------------- |
| Payment | `00`            | Payment succeeds                                  |
| Payment | `11`            | Payment fails                                     |
| Payment | `22`            | Payment remains in processing                     |
| Payment | Any other value | Callback is acknowledged without a payment update |
| Refund  | `00`            | Refund succeeds                                   |
| Refund  | `11`            | Refund fails                                      |
| Refund  | `22`            | Callback is acknowledged without a refund update  |
| Refund  | Any other value | Callback is acknowledged without a refund update  |

The wire values and fallbacks are defined by [`FiuuRefundsWebhookStatus`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs#L2107-L2120) and [`FiuuPaymentWebhookStatus`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs#L2142-L2155). Their merchant-facing effects come from the two [`IncomingWebhookEvent` mappings](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs#L2168-L2198).

### Source reference

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