> 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/bluesnap.md). # Bluesnap Accept card and wallet payments through BlueSnap. BlueSnap is a payment gateway for card and digital wallet payments. Card payments support optional 3DS and several card networks, while Apple Pay and Google Pay provide wallet options. Refunds and automatic, manual, or sequential automatic capture apply to every declared method. Webhooks cover payment, refund, and dispute updates. ### Status and capabilities **Integration status:** live **Category:** payment gateway **Webhook flows:** disputes, payments, refunds | Payment method | Type | Mandates | Refunds | Capture methods | 3DS | Card networks | Countries | Currencies | | -------------- | ----------- | ------------- | --------- | --------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------ | | card | Credit Card | not supported | supported | automatic, manual, sequential automatic | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, JCB, Maestro, Mastercard, RuPay, Visa | 185 ([full list](https://hyperswitch.io/pm-list)) | 94 ([full list](https://hyperswitch.io/pm-list)) | | wallet | Apple Pay | not supported | supported | automatic, manual, sequential automatic | not applicable | - | 88 ([full list](https://hyperswitch.io/pm-list)) | 52 ([full list](https://hyperswitch.io/pm-list)) | | wallet | Google Pay | not supported | supported | automatic, manual, sequential automatic | not applicable | - | 74 ([full list](https://hyperswitch.io/pm-list)) | 54 ([full list](https://hyperswitch.io/pm-list)) | ### Authentication Supply an API Username and API Password in the connector configuration. Hyperswitch joins them as `api_username:api_password`, Base64-encodes the pair, and sends `Authorization: Basic ` on connector requests. See [`BluesnapAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap/transformers.rs#L768-L786) and [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap.rs#L130-L143). ### Webhooks Configure a webhook merchant secret in Hyperswitch; the shared webhook verifier uses that value as the signature key. See [`verify_webhook_source()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_interfaces/src/webhooks.rs#L266-L301). BlueSnap webhooks use HMAC-SHA256 verification: Hyperswitch reads the hex signature from `bls-signature` and verifies the `bls-ipn-timestamp` value followed by the request body. See [`get_webhook_source_verification_algorithm()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap.rs#L1105-L1129). The connector recognizes six webhook event values: | Event | Effect in Hyperswitch | | --------------------------- | -------------------------------- | | `DECLINE` | Payment is marked failed | | `CC_CHARGE_FAILED` | Payment is marked failed | | `CHARGE` | Payment is marked successful | | `REFUND` | Refund is marked successful | | `CHARGEBACK` | Dispute state follows `cbStatus` | | `CHARGEBACK_STATUS_CHANGED` | Dispute state follows `cbStatus` | For chargeback events, `NEW` and `WORKING` open the dispute, `CLOSED` expires it, `COMPLETED_LOST` marks it lost, `COMPLETED_PENDING` marks it challenged, and `COMPLETED_WON` marks it won. The wire names and mappings are defined by [`BluesnapWebhookEvents`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap/transformers.rs#L992-L1053). ### Activate BlueSnap with Hyperswitch #### Before you start 1. Register with BlueSnap. 2. Create a Hyperswitch account. 3. Have the credentials listed in [Authentication](#authentication) ready. To connect BlueSnap to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what BlueSnap supports. ### Source reference [BlueSnap connector implementation](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap.rs) and [BlueSnap data mappings](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/bluesnap/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/bluesnap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.