---
title: "Version 1.2.0 - Breeze Payment Gateway"
description: "Adds the Breeze payment gateway with server-to-server processing, tokenized rebills, risk signals, and webhook reconciliation"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sparkcrm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Version 1.2.0 - Breeze Payment Gateway

Released on June 30, 2026

This release adds Spark CRM support for the Breeze payment gateway, a server-to-server (S2S) integration with the Breeze Direct Payment API. Merchants can now process card payments directly through Breeze, store cards for recurring billing, forward fraud signals from the checkout, and keep transaction status in sync via webhooks.

## Key Features

### Breeze Payment Gateway
Process payments directly through Breeze without redirecting the customer:
- Sale and authorize via the Breeze Direct Payment API
- Capture, refund, and void handling aligned with Breeze's API behavior
- Connection testing to validate credentials before going live
- Selectable from the gateway management form, with a webhook URL hint and credential fields

### Tokenized Rebills
Saved payment methods store a reusable Breeze token rather than the card number, allowing subscription renewals (merchant-initiated transactions) without retaining sensitive card data.

### Risk Signals
The checkout's Breeze Risk JS SDK session id and browser signals are forwarded into the payment request for customer-initiated transactions, and omitted for merchant-initiated ones, in line with Breeze's fraud-screening requirements.

### Webhook Reconciliation
A dedicated endpoint at `/webhooks/breeze` verifies Breeze's HMAC-SHA256 signature and reconciles transaction status asynchronously for payments, captures, and refunds. Handling is idempotent and never downgrades a finalized transaction.

## Fixes & Safeguards

### Refund and Void Safety
Breeze refunds reject zero and partial amounts to prevent over-refunding (Breeze supports full refunds only), and `void` no longer issues unsafe refunds on payments that are not in a capturable state.

## Breaking Changes

None - this release is fully backward compatible.

## What's Next

- End-to-end validation against the Breeze sandbox
- 3DS challenge (redirect) completion flow

---

**Need Help?** Visit our documentation or contact support for assistance.

Source: https://docs.sparkcrm.io/changelog/v1.2.0/index.mdx