For the custom system that should react when money moves
Stripe and PayPal can raise the event. Provision access in your existing product through @bondi-labs/integration-sdk, or manage the operational account and entitlements in a complete Bondi system. Finance review, retries and audit stay in the same governed path.
From event to outcome
The provider event starts a workflow and the run matches the payer to the account. Rules you author separate paid, failed, refunded and above-threshold cases. The ordinary path either calls a typed provisioning action in your product or updates the account and entitlements held in Bondi. The exception path suspends for finance, and the event, decision and response remain inspectable together.
Configured human task
Context shown
The payment event, exception reason and requested account access.The provider event is valid, but the amount crossed the review threshold authored for this workflow.
Provisioning remains blocked, the payment exception stays owned, and no access is granted.
Where the records live
Keep one authoritative home for each business record. Choose the boundary that fits the process you are building.
Connection requirements
This is a worked example of a configurable workflow. Connections and decision rules must be set up for your system.
Explore integrationsA reviewed provider connector raises the event that starts the workflow.
Typed actions and events are published from code you control with the Integration SDK.
The wider operation
Explore the records, screens and other decisions that can stay connected to this process.
Start with your process
Name the starting event, the records involved and the decision that needs a person. Review the plan before building the workflow.
No credit card required.
