Portal Community
All settings are optional. When a filter setting is not configured, no filtering of that type is applied and all received events pass through to the workflow. Events that fail any configured filter are discarded without starting a workflow run.

Security Settings

SettingTypeDescription
WebhookSecretstringStripe webhook signing secret (starts with whsec_). When set, BizFirst verifies the Stripe signature included in every webhook request. Events with invalid or missing signatures are rejected before any workflow starts. Obtain this value from the Stripe Dashboard under Developers > Webhooks after creating the endpoint. Strongly recommended for production.

Event Type Filter

SettingTypeDescription
AllowedEventTypesstringComma-separated list of Stripe event types to process. Supports wildcards — use charge.* to accept all charge events, or payment_intent.* for all payment intent events. Supported values: charge.succeeded, charge.failed, charge.refunded, payment_intent.succeeded, payment_intent.payment_failed, charge.dispute.created, charge.dispute.closed. Example: charge.succeeded,payment_intent.payment_failed.

Amount Filters

SettingTypeDescription
MinimumAmountlongMinimum charge amount in smallest currency unit (cents for USD/GBP/EUR). Events with an amount below this value are discarded. Set to 0 to disable the minimum filter. Example: 100 to filter out amounts under $1.00.
MaximumAmountlongMaximum charge amount in smallest currency unit. Events with an amount above this value are discarded. Set to 0 to disable the maximum filter. Example: 100000 to discard charges over $1,000.

Currency Filter

SettingTypeDescription
AllowedCurrenciesstringComma-separated list of ISO 4217 currency codes (lowercase). Only events with a matching currency will trigger the workflow. Supported values: usd, gbp, eur. Example: usd,gbp. If not set, all currencies are accepted.

Customer Filter

SettingTypeDescription
RequireKnownCustomerboolDefault: false. When true, only events that have a Stripe customer ID (cus_...) attached to the charge or payment intent are processed. Events without a customer — such as guest checkout payments — are discarded. Useful when your workflow logic depends on looking up the customer in your database.

Output and Deduplication Settings

SettingTypeDescription
IncludeFullEventObjectboolDefault: false. When true, the complete raw Stripe event JSON is included in the output as full_event_json. This provides access to all Stripe object fields that are not included in the standard parsed output fields.
EnableIdempotencyCheckboolDefault: false. When true, BizFirst deduplicates event deliveries using the Stripe signature. If an event with the same signature has been successfully processed before, the duplicate delivery is discarded without starting a new workflow run. Protects against double-processing when Stripe retries failed deliveries.

Wildcard Event Type Examples

AllowedEventTypes ValueWhat It Matches
charge.*All charge events: charge.succeeded, charge.failed, charge.refunded, charge.dispute.created, charge.dispute.closed
payment_intent.*All payment intent events: payment_intent.succeeded, payment_intent.payment_failed
charge.succeeded,charge.failedOnly successful and failed charge events
(not set)All 7 supported event types
Amounts are always in the smallest currency unit. For USD, GBP, and EUR: 100 = $1.00 / £1.00 / €1.00. A MinimumAmount of 5000 means $50.00. Configure amount filters with this in mind to avoid accidentally filtering out legitimate transactions.