Handling Events
Handling actions & events in a billing page
Handling actions
The handleResponse function can be used to update user information in your database regarding the customers subscription information, to do redirects on signup, or present notifications.
Parameters
handleResponse will pass a variable which contains the following properties
Variable Name | Description |
event | The name of the event that occurred |
response | The response object returned from Stripe |
Events
Event Name | Description | Response Object |
pre_load | First thing run after the embed javascript loads, before any API calls have been made. Use to inject React components or tell when the embed has loaded. | Embed Configuration |
post_load | billingData: null — means the subscription portal is not loaded yet billingData: {no_user: true} — means the current email is not a customer productData: null — means pricing (products) are not loaded yet productData: [ … ] — means the pricing (products) are loaded | billingData currentConfig productData |
pre_subscribe | This event allows you to do some actions before creating a subscription. For example, you can use it for checking if a user exists in your system. Throwing an error here will prevent Billflow from creating a subscription. | service tier |
create_subscription | Triggered when a subscription is created from a billing page. Use this event to update your user system with the Stripe subscription ID and tier. Learn more on the install guide. | |
pre_change_plan | Triggered before when a user clicks on the confirm button, but before the API call is made to change plan. | service tier |
change_plan | Triggered when a user upgrades or downgrades using the Plan Picker. You can use this to update their tier information or create notifications. | |
select_plan | Triggered when a user selects a plan from the pricing page or plan picker. Use this to redirect to other pages or forms to create custom on-boarding flows. | Tier name & Plan |
pre_resubscribe | Triggered when a customer clicks on the resubscribe button, but before the API call is made to resubscribe. | |
resubscribe | Triggered when a customer resubscribes from the portal. This occurs when a customer was cancelled, they come back to the portal and choose to resubscribe to a plan. Use this event to update your user system with the Stripe subscription ID and tier. | |
pre_cancel | Triggered when a customer clicks on the cancellation button. Use this to create a custom cancellation flow. | |
cancel_subscription | Triggered when a customer requests a cancellation. Use this event to update subscription status for a user. | |
pre_change_card | Triggered when a customer clicks on change card button, but before the API call is made to change card. | |
update_card | Triggered when a customer updates their Credit Card information or enters it for the first time. Use for presenting notifications to the user. | Customer |
request_error | Triggered when any of our API requests failed. User for custom handling of any request failures. | The Request Error |
pre_update_quantity | Triggered before quantity is updated on a subscription from the customer portal | Price quantity subscription_id |
update_quantity | Triggered after a quantity has been updated from the customer portal | |
add_coupon | Triggered after a coupon has been added. Can be used to create custom coupon restriction logic. |
Sample Redirect on Subscribe
Redirect to a URL after subscription
Sample Redirect based on Tier Subscribed
Sample Pricing Page redirect for specific tier
Redirect to a URL after subscription
Sample Existing User check
Skip subscription creation if a user already exists
Sample Track conversions with Google Analytics
Use GA to track signups
Sample Coupon restriction logic
Use to prevent a specific coupon based on logic
Last updated