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

# Gigadat

Configure Gigadat Interac payments with Hyperswitch.

Gigadat brings Interac bank redirect payments to Hyperswitch. The route supports refunds and both automatic and manual capture. Payment and payout callbacks are processed, but their source is not verified by the connector.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** payments, payouts

| Payment method | Type    | Mandates      | Refunds   | Capture methods   | Countries | Currencies |
| -------------- | ------- | ------------- | --------- | ----------------- | --------- | ---------- |
| bank redirect  | Interac | not supported | supported | automatic, manual | -         | CAD        |

### Authentication

Provide the **Access Token**, **Security Token**, and **Campaign ID**. Also provide the required **Site where transaction is initiated** metadata. These fields come from [`gigadat connector configuration`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/connector_configs/toml/sandbox.toml#L8436-L8449), and [`GigadatAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat/transformers.rs#L154-L171) maps the credentials.

### Before you start

Create or sign in to your [Gigadat account](https://gigadatsolutions.com/) and obtain the **Access Token**, **Security Token**, and **Campaign ID**, plus the site value Gigadat registered for you. Gigadat appears in the control center payment-processor list ([`connectorList`](https://github.com/juspay/hyperswitch-control-center/blob/ecca16a27cb6acb336569ea30714fa05d867c765/src/screens/Connectors/ConnectorUtils.res#L89-L205)). Then follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md). Payouts use a separate connector account, `gigadat_payout`, with the same three credentials and site value ([`[gigadat_payout]`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/connector_configs/toml/sandbox.toml#L8448-L8461)).

### Webhooks

Gigadat handles payment and payout callbacks, but it does not verify their source: `verify_webhook_source` returns `false` ([`IncomingWebhook for Gigadat`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat.rs#L983-L1052)). Verification is not mandatory for this connector, so Hyperswitch accepts the callback, but it does not apply the status the callback carries; it treats the callback as a prompt and syncs with Gigadat instead ([unverified webhook handling](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/router/src/core/webhooks/incoming.rs#L537-L541), [sync instead of the callback content](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/router/src/core/webhooks/incoming.rs#L899-L914)). The sync covers payments and payouts: an unverified payout callback on a payout that is not yet final triggers a payout sync ([payout webhook action](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/router/src/core/webhooks/incoming.rs#L1177-L1186), [`ConnectorIntegration<PoSync>`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat.rs#L883-L952)). Only refund status cannot be synced, because the refund sync flow is not implemented ([`ConnectorIntegration<RSync>`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat.rs#L630-L632)).

The code handles nine flow codes and eight exact status values ([`GigadatFlow::get_flow()`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat/transformers.rs#L214-L232), [`get_gigadat_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/gigadat/transformers.rs#L234-L282)).

| Flow    | Wire values                       |
| ------- | --------------------------------- |
| Payment | `ETI`, `RFM`, `CPI`, `ACK`        |
| Payout  | `ETO`, `RTO`, `RTX`, `ANR`, `ANX` |

| Status wire value  | Payment effect                | Payout effect                |
| ------------------ | ----------------------------- | ---------------------------- |
| `STATUS_SUCCESS`   | Payment succeeds              | Payout succeeds              |
| `STATUS_FAILED`    | Payment fails                 | Payout fails                 |
| `STATUS_REJECTED`  | Payment fails                 | Payout fails                 |
| `STATUS_REJECTED1` | Payment fails                 | Payout fails                 |
| `STATUS_EXPIRED`   | Payment fails                 | Payout fails                 |
| `STATUS_ABORTED1`  | Payment fails                 | Payout fails                 |
| `STATUS_INITED`    | Payment remains in processing | Payout remains in processing |
| `STATUS_PENDING`   | Payment remains in processing | Payout remains in processing |

### Source reference

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