engineer-payments

Transform payment and subscription events from Stripe, RevenueCat, and Recurly into Braze /users/track payloads.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-payments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-payments
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-payments
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-payments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Braze-powered teams often struggle to consistently ingest, normalize, and react to payment and subscription events from multiple providers. This Skill unit provides a production-grade blueprint for transforming webhook and lifecycle data from Stripe, RevenueCat, Recurly, Narvar, and Olo into Braze-ready payloads, enabling timely, personalized customer communications.

Core Features & Use Cases

  • Unified event ingestion and normalization for payment, billing, and subscription events across multiple partners.
  • Reliable identity resolution and external_id mapping to Braze profiles for accurate messaging.
  • End-to-end lifecycle handling, including subscription state transitions, event batching, and idempotent processing.
  • Support for multiple data sources and event types (webhooks, invoices, renewals, cancellations) to power targeted canvases and campaigns.

Quick Start

Describe and implement a Braze integration workflow that forwards payment and subscription events from Stripe, RevenueCat, Recurly, and related partners into Braze via the /users/track API.

Frequently Asked Questions about engineer-payments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map Stripe webhooks to Braze user profiles?

Normalize Stripe webhooks into Braze '/users/track' payloads by mapping inbound billing and subscription events to user profiles. This process applies identity resolution and external_id mapping for accurate messaging.

What is the best way to handle subscription state transitions across multiple payment providers in Braze?

Normalize lifecycle events from Stripe, RevenueCat, and Recurly into unified Braze payloads to handle subscription state transitions. This ensures idempotent processing and batch handling for reliable state management across providers.

Can I send RevenueCat subscription updates directly to Braze canvases?

Yes, transform RevenueCat subscription lifecycle events into '/users/track' payloads to send updates directly to Braze. This enables timely, personalized customer communications within targeted canvases and campaigns.

Does this approach support idempotent processing for recurring billing events?

Yes, the event ingestion process supports idempotent processing for recurring billing events. It ensures duplicate webhooks or invoices from payment providers do not create duplicate profile updates in Braze.

How do I unify checkout and renewal events from different payment partners into a single Braze workflow?

Apply a transformation layer to normalize checkout and renewal data from multiple partners into Braze-ready payloads. This handles event batching and identity resolution for consistent lifecycle messaging across providers.