Recommended Webhooks

BlueSnap offers a wide selection of webhooks to ensure that merchants stay informed about their transactions in real time. We understand that your business handles various types of transactions and you need timely updates to manage them effectively.

When you begin processing with BlueSnap, our implementation team provides guidance about which webhooks you should enable. As your business evolves, you might want to enable additional webhooks to meet your growing needs, or you might want to experiment with webhooks to see how you can improve your existing workflows.

In general, BlueSnap recommends that you enable webhooks for events that you do not initiate. For example, we recommend that all merchants enable the PAYOUT webhook because you would otherwise be unaware when BlueSnap sends funds to your payout account until you view your reports.

The recommended and suggested webhooks listed on this page are not definitive—there might be additional webhooks that you can integrate into your business workflows. For a description of all webhooks, see All Webhooks Name Reference.

API Integrations

Our Payment API gives you complete control over how you manage the shopper experience. Because you directly integrate each step of the transaction lifecycle, you typically know the outcome of important transaction events as they occur. You can instead leverage webhooks to share transaction information with your internal business processes. For example, you can send the CHARGE webhook to your shipping department so they can prepare purchased products for delivery.

Suggested

DECLINE
CC_STATUS_CHANGED
FAILED_PAYOUT_TRANSFER
PENDING_REFUND
REFUND
VAULTED_SHOPPER

Hosted Solutions

BlueSnap Checkout requires minimal coding and reduces your Payment Card Industry (PCI) burden to the lowest level, SAQ-A. Because so much of your shopper's experience is managed by BlueSnap, we recommend that you enable specific webhooks so that you are aware of all important transaction events.

Suggested

ACCOUNT_UPDATER
CC_STATUS_CHANGED
CC_CHARGE_FAILED
CHARGE_PENDING
FAILED_PAYOUT_TRANSFER
PENDING_REFUND
REFUND
RECURRING
VAULTED_SHOPPER

Subscriptions

BlueSnap Subscriptions let you set up recurring payments for your products with features that help you manage your shopper's experience to suit your business needs.

BlueSnap recommends the following webhooks for subscriptions that use the BlueSnap Subscription Engine. Merchant-managed subscriptions—third-party subscription solutions that process transactions through BlueSnap—should enable the webhooks described in One-Time Charges.

Suggested

ACCOUNT_UPDATER
CANCEL_ON_RENEWAL
CANCELLATION_REFUND
CC_STATUS_CHANGED
CONTRACT_CHANGE
FAILED_PAYOUT_TRANSFER
PAYMENT_METHOD_UPDATED
PENDING_REFUND
REFUND
SUBSCRIPTION_REMINDER
SUBSCRIPTION_CHARGE_FAILURE

One-Time Charges

Most transactions are processed as one-time charges. If you process merchant-managed subscriptions or use a 3rd-party subscription service, BlueSnap processes your transaction as a one-time charge.

The webhooks that you enable depend on the payment type for the transaction. For example, if you process ACH payments, you want to enable CHARGE_PENDING.

Suggested

CC_CHARGE_FAILED
CHARGE_PENDING
CHARGEBACK_STATUS_CHANGED
FAILED_PAYOUT_TRANSFER
PAYMENT_METHOD_UPDATED
PENDING_REFUND
REFUND
VAULTED_SHOPPER

Embedded Partners

Embedded partners rely on the following webhooks for critical updates during merchant onboarding :

Suggested

MERCHANT_PARTNER_STATUS