Webhook subscription event is triggered even when gift subscription payment fails

[mert-ersoy]

Hello,

I would like to report an important issue I’ve identified regarding subscription-related webhook events.

During Gift Subscription transactions (and possibly other subscription flows), the webhook notification is being sent even when the card payment fails. I personally tested this behavior: although the payment was declined during the checkout process, the system still triggered and delivered a subscription webhook as if the transaction had succeeded.

Below is the exact webhook payload I received for this failed payment attempt:

{ "broadcaster": { "is_anonymous": false, "user_id": *****, "username": "******", "is_verified": false, "profile_picture": "******", "channel_slug": "*******", "identity": null }, "gifter": { "is_anonymous": false, "user_id": 35011031, "username": "XssMert", "is_verified": false, "profile_picture": "https://files.kick.com/images/user/35011031/profile_image/conversion/b39e942e-b02b-4de4-bbe7-89833a212d93-medium.webp", "channel_slug": "xssmert", "identity": null }, "giftees": [ { "is_anonymous": false, "user_id": ******, "username": "*******", "is_verified": false, "profile_picture": "", "channel_slug": "******", "identity": null } { "is_anonymous": false, "user_id": ******, "username": "*******", "is_verified": false, "profile_picture": "", "channel_slug": "******", "identity": null } { "is_anonymous": false, "user_id": ******, "username": "*******", "is_verified": false, "profile_picture": "", "channel_slug": "******", "identity": null } { "is_anonymous": false, "user_id": ******, "username": "*******", "is_verified": false, "profile_picture": "", "channel_slug": "******", "identity": null } { "is_anonymous": false, "user_id": ******, "username": "*******", "is_verified": false, "profile_picture": "", "channel_slug": "******", "identity": null } ], "created_at": "2025-12-13T12:44:09.298957865Z", "expires_at": "2026-01-12T12:44:09.298957938Z" }

The exact date and time are included in the payload above and should be verifiable in your logs.

The test was performed using my account: xssmert. However, I wanted to conceal the name of the broadcaster and the names of the viewers.

Although the payment was declined and the subscription was not successfully completed, the webhook was still sent. This can cause incorrect behavior for third-party systems that rely on webhook events to confirm successful transactions.

If you need any additional technical details, logs, or further test cases, I’d be happy to provide them.

[zachingle-easygo]

Hey @mert-ersoy,

Thanks for reporting this and giving such great details.

Would you be able to provide the type of payment used (e.g. Apple or Google Pay) and whether this was performed on desktop or the mobile app?

We'll investigate this and will provide updates here once we learn more.

[mert-ersoy]

Hi @zachingle-easygo,

Thanks for the response.

This test was performed on desktop (web).
The payment method used was direct credit card payment via the card form (not Apple Pay, not Google Pay).
The card used was a Turkish-issued credit card.

I haven’t tested the other payment methods yet, but I can do so if needed.

Additional detail: after entering the card details and clicking pay, the flow redirects to the 3D Secure authentication screen.
If the payment fails at this stage — for example by cancelling the 3D screen, entering an incorrect verification code, or the card having insufficient limit — a subscription webhook is still sent.

However, the subscription itself is not actually created. Only the webhook is triggered and delivered, even though the payment does not complete successfully.