For the complete documentation index, see llms.txt. This page is also available as Markdown.

Blackhawk Network

Accept Blackhawk Network gift card payments.

Blackhawk Network accepts gift card payments on the BHN Card Network as a single automatically captured redemption. Redemption takes two steps: a preprocessing call to verifyAccount returns an account ID, and the authorize request redeems against that ID. Hyperswitch does not drive this sequence for you. The connector leaves is_balance_check_flow_required() at its default false, so the router never runs the balance-check flow automatically, and BlackhawknetworkPaymentsRequest::try_from() fails with MissingConnectorRelatedTransactionID if no preprocessing step has supplied the ID. Mandates and refunds are not supported, so a card cannot be stored for reuse and a completed payment cannot be reversed through Hyperswitch.

Status and capabilities

Integration status: alpha

Category: payment gateway

Webhook flows: There's nothing declared in code

Payment method
Type
Mandates
Refunds
Capture methods
Countries
Currencies

gift card

BHN Card Network

not supported

not supported

automatic

-

-

Authentication

Supply Client Id, Client Secret, and Product Line Id, the labels shown in the Hyperswitch control center. Client Id and Client Secret are sent in a client-credentials token request, while Product Line Id is included in supported gift card requests. See BlackhawknetworkAuthType::try_from(), get_request_body() for access tokens, and BlackhawknetworkVerifyAccountRequest::try_from().

Before you start

  1. Register with Blackhawk Network at blackhawknetwork.com.

  2. Obtain Client Id, Client Secret, and Product Line Id from Blackhawk Network, then enter them during connector activation.

  3. If the activation flow asks you to select payment methods, choose only the gift card methods enabled on your Blackhawk Network account.

Follow Activate a connector on Hyperswitch, then return here for Blackhawk Network-specific behavior.

Webhooks

Blackhawk Network webhooks are unsupported, and neither is payment sync. There is no way to re-check a payment after Hyperswitch submits it, so treat the authorize response as the only status you will receive, and record it on your side.

The three webhook handlers (get_webhook_object_reference_id(), get_webhook_event_type(), and get_webhook_resource_object()) each return WebhooksNotImplemented. Four further flows reject the request outright with FlowNotSupported: payment sync, capture, refund execute, and refund sync.

Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch 9e5dd70d1cb4011bbcca3114862406008a0b61f8. See Blackhawk Network connector source and Blackhawk Network transformers.

Last updated

Was this helpful?