Workflows enable you to build complete end-to-end payment flows without code for the first time. Primer's Workflows and Universal Checkout remove the traditional touchpoints for integrating distinct payment flows on both the front- and backend.
No more writing additional front-end code to incorporate 3D Secure, handle KYC, capture additional data like a CVV, or for any other front-end flow. It just works.
Build complex conditional routing to processors in order to optimize for cost and payment success.
Improve your risk mitigation efforts by connecting to fraud platforms and 3D Secure in a unified way.
Build sophisticated, dynamic payment flows in order to improve conversion based on rich payments data.
Improve operational efficiency by connecting to communication tools such as Slack and Zendesk for real-time notifications and alerts.
Create conditions based on payment methods and order data to determine the route of a payment through its lifecycle. Think of a Workflow as a simple tool for constructing your ideal payment — like building blocks.
Payment Workflows are triggered by payment requests. We'll soon be introducing other types of Workflows to give you even more power over your payments stack.
In this video, Thomas Pasterk (Product Manager for Workflows) takes you through building a payment Workflow end-to-end.
Each Workflow route starts with a set of conditions. You can base conditions on data derived from payment methods (such as BIN data), data submitted through Universal Checkout, or any other information passed in as part of the payment request, including metadata.
Conditions are considered in order from top to bottom. If you want to reorder them, just drag and drop!
A default route for
all other payments will remain at the bottom at all times. Use this to specify an ultimate fallback when there are no matches to the conditions you've specified.
Connections in Workflows have distinct capabilities, called actions. Each action has a set of responses which you can use to trigger subsequent steps, thereby building logical routes.
Every Connection in Workflows uses the following fixed responses in case of failure:
Missing required data. Check the Connection docs in the Dashboard, and pass the requested data in the clientToken or payment request.
The Connection could not perform the action due to service disruption or configuration issues.
When you add steps in Workflows, we'll even make "smart suggestions" to recommend subsequent actions based on rich data and analytics.
Workflows are versioned. A new Workflow is created as a draft, allowing you to safely work on it until it's ready to be published.
Each payment is tied to the version of the Workflow enabled at the time you created it, and you can see that when you view the payment in the Dashboard. Only payments created after a new version of your Workflow has been published will be impacted by the new version.