Below is a list of the event types we currently send. Please note that additional event types may be introduced in the future, so your code should be flexible enough to accommodate new types as they arise. Our objective is to maintain a consistent and predictable event structure, making it easier to integrate and handle messages, along with the objects they affect.
v0.50.0-beta
and above. It was sent when there was an error related to the creation of an event.Schema exampleurl
field contains the checkout link that initiates 3D Secure (3DS) validation for your customers. The return_url
is the page displayed once the 3DS process is completed.Schema exampleprovider_error
field indicates the error code and message from the payment provider.Schema examplepay_in_advance
fee. Useful for fintech companies that need to create a statement of transactions without invoicing.Schema exampleprevious_plan_code
argument is filled if the subscription has been upgraded or downgraded.Schema examplenext_plan_code
argument is filled if the subscription has been upgraded or downgraded.Schema example