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

# Digital Virgo

Digital Virgo connector for alternative payment method.

Digital Virgo supports direct carrier billing for mobile payments. Refunds and automatic capture are declared, while mandates are not supported.

Digital Virgo is not offered in the control center, so the shared [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md) guide does not apply: it begins by picking a connector from a list this one is not on. See [Before you start](#before-you-start).

### Status and capabilities

**Integration status:** alpha

**Category:** alternative payment method

**Webhook flows:** None declared in code

| Payment method | Type                   | Mandates      | Refunds   | Capture methods                 | Countries | Currencies |
| -------------- | ---------------------- | ------------- | --------- | ------------------------------- | --------- | ---------- |
| mobile payment | Direct Carrier Billing | not supported | supported | automatic, sequential automatic | 48        | 37         |

{% hint style="warning" %}
Although the capability table lists sequential automatic capture, the connector does not implement the capture flow. A capture request returns a flow-not-supported error, so only automatic capture works with Digital Virgo.
{% endhint %}

### Authentication

Digital Virgo requires two credentials, which Digital Virgo provides when you set up your account with them: **Username** and **Password**. They are sent as HTTP Basic authentication, not in the request body: [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L124-L140) joins them as `<username>:<password>`, Base64-encodes the pair, and sends `Authorization: Basic <encoded value>`.

[`DigitalvirgoAuthType`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo/transformers.rs#L86-L101) maps them from Hyperswitch's `BodyKey` credential schema, which names how the two values are stored rather than how they reach Digital Virgo.

### Before you start

Dashboard setup is not offered for this connector in the current connector list; contact the Hyperswitch team. Have the credentials shown in the Authentication section ready before configuring the connector.

### Webhooks

Webhooks are not supported, so there is no event list and nothing to configure. All three handlers return `WebhooksNotImplemented`: [`get_webhook_object_reference_id()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L517-L522), [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L524-L530) and [`get_webhook_resource_object()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L532-L538).

Payment status can be tracked through the payment sync API, which Digital Virgo implements against its payment state endpoint. See the [payment sync implementation](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L314-L354).

Refunds are a different matter. The table above marks them supported, but neither refund flow works: [refund execute](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L487-L499) returns `FlowNotSupported` from `build_request`, so a refund fails before a request is sent, and [refund sync](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs#L501-L512) is unimplemented too. There is nothing to reconcile out of band, because no refund reaches Digital Virgo through Hyperswitch in the first place.

### Source reference

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