Know right away when transactions fail from your payment processor so you can restore your payment operations quickly to minimize downtime and lost sales

Notify Internal User About Failed Transactions

When a transaction fails at your default payment processor, automatically route them to another to save the sale

Increase auth rates by routing failed transactions to another payment processor

Look for transaction currency to send transaction to local processors. This can result in higher authorization rates and lower processing costs

Route transactions based on currency to reduce costs and increase auth rates

Schedule  a weekly sales report (or any report template you create in Insights) sent to you weekly

Automatically Receive Weekly Payment Reports

Risky transactions can spell trouble for your business. Using a Fraud Service Provider can identify high risk transactions and using this recipe you can automatically decline those transactions without sending the transaction to your payment processor

Decline high-risk transactions to reduce fraud and chargebacks

If fraud transactions score is high risk, authorize only 

Authorize and hold high-risk transactions to reduce fraud risk and refund costs

Add an extra layer of protection against fraud by using 3DS to authenticate high-risk transactions identified by your fraud provider. If a user is able to successfully pass 3DS step-up challenge, then you can confidently process the transaction knowing that the Issuer will assume any fraud liability. 

Trigger 3DS if 3rd Party Fraud service suggests a risky transaction

Retry a failed transaction on the same gateway can increase your conversion, however you must cap the number of retries in order to avoid punitive actions from your processor or card network

Retry failed transaction on default payment processor

This recipe notifies you whenever your Payment Processor changes the status of a dispute that requires your attention. Get notified and streamline your disputes operations

Notify me about Disputes that need a response

For any payment event, export payment object to external data warehouse

Export Payment Data to External Data Warehouse

Give yourself time to validate the authenticity of the transaction before capturing the payment. This still allows you to hold the funds and gives you the option to capture without declining the transaction

Capture transaction after fixed time

Triage inbound disputes, ask responsible stakeholders to either approve refund or open support ticket 

Triage inbound disputes - automatically refund or create support tickets 

A/B test two checkouts to see how the inclusion of certain payment methods impact conversion

A/B test checkout methods to see what drives higher conversion

Define what checkout payment options to show based on the location of your user. Show the most relevant checkout options specific to the users region to increase auth rates

Localise your checkout to show the most relevant payment methods

Use A/B test to run some transactions through your fraud provider and see what impact it has on your authorization rates

Determine if 3rd party fraud reduces authorization rates through an A/B test

Add 3DS action to some of your authorizations and compare what impact it has to your payment success rates

Determine if adding 3DS reduces authorization rates through an A/B Test

Route transactions to two different payment processors and see which one produces better payment results

Maximize processor authorization rates through A/B Test

Reaching out to failed high-value transactions can help you understand understand what happened and assist your customers in completing the sale

Generate a support ticket for failed high-value transactions

This is a standard process automation for Paypal. In certain instances, Paypal will hold a higher risk transaction that requires you to manually approve the transaction from your Paypal transaction dashboard, when this happens, this recipe will send you a notification so that you can quickly close the sale

Notify me when Paypal transaction requires manual review

Selectively enable 3DS step-up authentication based on card condition. This recipe helps you selectively deploy 3DS based on the country the card was issued in.

Trigger 3DS based on a location to reduce chargebacks

Identify internal users when a user fails 3DS; allows your team to identify legitimate customers and provide an elevated experience for them to complete their transaction

If a high value transaction fails because of 3DS, notify internal user

Only send large transactions to be scored by your Fraud service. Depending on your Fraud service, this can help you reduce fraud costs by only scoring higher risk / higher value transactions

Only send high-value transactions to Fraud service

Having an up to date CRM is a blessing for marketing teams, now you can automatically add users and their contact information to your CRM each time they make a successful payment on your website. 

Update CRM after a successful payment

When we receive a webhook, this automation will cancel an authorization regardless of which Payment Service Provider was used to authorize. Don't forget to define a JSON structure to include at least a PaymentID variable so we know which transaction to refund

Automatically cancel payment when webhook trigger is received

Speed up your back-office payment operations and refund users faster. When we receive a webhook, this automation will refund a customers payment regardless of which Payment Service Provider was used to authorize. Don't forget to define a JSON structure to include at least a PaymentID variable so we know which transaction to refund

Automatically refund payment when webhook trigger is received

Increase cart conversion by engaging with users to try alternative payment methods when transaction declined for insufficient funds

Send customer message in real time when payment declines

Automate your dispute operations by sending users an email template explaining your dispute process and what is required from them

Automatically send an email to the user when transaction disputed

After a successfully authorized transaction, notify downstream systems via a webhook. This allows for your operations to act immediately after purchase, triggering things like fulfillment, marketing and finance

When successful authorization, notify downstream system via webhook

Create more complex routing rules using our rules node to determine where to send your transaction. We’ve preconfigured brand and country to route to lower cost payment processors, but customize your rules to suit your business.

Processor routing on multiple condition to increase auth and reduce costs

Know right away when users dispute a transaction. This allows you to better manage the chargeback process and resolve the issue with your customers quickly

Notify internal users about newly opened disputes

Send your customers a confirmation email after any successful transaction

Send customer payment confirmation email

When a customer’s transaction declines, send them an email encouraging them to try again with another payment method

Encourage users to use another payment method when payment declined

Define card condition logic to determine where to send the transaction. This can result in higher authorization rates and lower processing costs when routed to local payment processors

Route transaction to best payment processor based on card condition

Capture a transaction after you’ve confirmed with the customer or provided the goods (via WhenThen API). Save on processor refunds costs and fight suspicious transactions using this capture recipe

Capture transaction when you confirm a good sale through API call

Capture a transaction after you’ve confirmed with the customer or provided the goods. Save on processor refunds costs and fight suspicious transactions using this capture recipe

WhenThen
Orchestrator

Join the
community

WhenThen Orchestrator

Join the community

WhenThen
Orchestrator

Join the
community