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 guide does not apply: it begins by picking a connector from a list this one is not on. See 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

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.

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() joins them as <username>:<password>, Base64-encodes the pair, and sends Authorization: Basic <encoded value>.

DigitalvirgoAuthType 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(), get_webhook_event_type() and get_webhook_resource_object().

Payment status can be tracked through the payment sync API, which Digital Virgo implements against its payment state endpoint. See the payment sync implementation.

Refunds are a different matter. The table above marks them supported, but neither refund flow works: refund execute returns FlowNotSupported from build_request, so a refund fails before a request is sent, and refund sync 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 and Digital Virgo transformers.