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)	94 (full list)
wallet	Apple Pay	not supported	supported	automatic, manual, sequential automatic	not applicable	-	88 (full list)	52 (full list)
wallet	Google Pay	not supported	supported	automatic, manual, sequential automatic	not applicable	-	74 (full list)	54 (full 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 <encoded value> on connector requests. See BluesnapAuthType::try_from() and get_auth_header().

Webhooks

Configure a webhook merchant secret in Hyperswitch; the shared webhook verifier uses that value as the signature key. See verify_webhook_source(). 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().

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.

Activate BlueSnap with Hyperswitch

Before you start

1. Register with BlueSnap.

2. Create a Hyperswitch account.

3. Have the credentials listed in Authentication ready.

To connect BlueSnap to your Hyperswitch account, follow Activate a connector on Hyperswitch, then return here for what BlueSnap supports.

Source reference

BlueSnap connector implementation and BlueSnap data mappings