Changelog

Introduced the Customer Update Action to enable updating customer information within a Business Processes.

Introduced the Metadata Action to allow passing custom metadata as part of the Business Process.

A cyclic execution issue was identified in the webhook service when the webhook destination was set to the Authvia Trigger API to create a business process, and the webhook type was configured as business_process:create or business_process:update. This document details the implemented solution to prevent infinite loops by introducing an origin header and execution checks.

We have enhanced the Payment Method Action by adding support for the accountType parameter, enabling merchants to define restrictions for ACH account types.

We have enhanced our Blueprints functionality by introducing the ability to cast parameters to :object or :array within a Blueprint payload.

We are excited to introduce the Reminder Action feature, which will enhance user engagement and ensure timely follow-ups within your business processes.

📘

AFTER December 31st 2024

It is now possible to define a qualifier on an Account Product record to establish conditions on not just 'when' it can be used, but to simultaneously have it be 'preferred' when that condition is met. This is very useful for more complex cases where merchants want to do tender steering with payments or similar automation.

In an effort to make our API more user-friendly, our pagination implementation has been standardized to facilitate usage from one endpoint to the next.

The schedule, expiration, status, and callback properties of a business process have more capabilities around being updated. These new features are available while updating or creating a business process.