Skip to main content

Flow Settings

Define how each payment transaction will move between your services and features, based on your business needs, without any coding.

Flow Settings

Flow Overview#

Once you have your Services set up, you need to create at least one Flow to start processing payments with Tuna. We highly encourage you to create several flows and A/B tests to leverage your payment optimization solution better.

Setting up Flows#

In the Flows section at Console, you will define how each payment transaction will move between your services using our templates.

The templates required for each flow are:

The optional templates for each flow are::

  • Fraud Verification: one or more anti-fraud services will give feedback about how suspicious each transaction of this flow is. You can define actions to be taken based on the anti-fraud provider response.
  • Challenges: an additional verification in case you want to collect more information from the customer before deciding whether to capture the payment.
  • Custom services: a custom integration or feature developed for your flow (on demand).

Filters#

With Filters, you will define which transactions you want to process in the flow based on a set of criteria. You must include at least one filter, even if you want to apply it to all transactions that pass on this flow. Transactions that do not match the conditions of this flow will be evaluated by the next flow, as described here.

You can include several filters and combine them with AND and OR operators to define rules you want. See below an example of a filter:

If transaction matches with: Category.Name IN Smartphones, Alcohol Drinks AND Payment.Amount greater than 1.000,00.

It is common to add at least the Payment.method.type filter to define the Authorization Scheme that will process the payment, but there are several filter criteria available:

Filter NameTypeDescription
Category.NameStringItem category. Ex: Smartphones.
Operating.SystemStringThe Operating System of the customer. Ex: iOS, Android.
Login.TypeStringHow customers login on your site. Ex: Google Login.
Payment.AmountNumber (double)Value the customer paid in this transaction. Ex: $100,00
Method.AmountNumber (double)Value the customer paid with a specific payment method. Ex: $80,00
InstallmentsSelectNumber of installments of the payment. Picklist.
Payment.method.typeSelectName of the payment type. Ex: CreditCard.
BINNumberThe customer's Card Bank Identification Number. Ex: 4040.
Brand.NameStringThe customer's Card Brand. Ex: Master, Visa, Amex.
Customer.EmailStringThe customer's Email on this transaction. Ex: tinaturner@tuna.uy
Address.StateStringThe customer's Billing Address State. Ex: SC.
Address.CityStringThe customer's Billing Address City. Ex: Florianópolis.
Address.Postal_codeNumberThe customer's Billing Address Postal Code. Ex: 88035320
Custom.nameStringYou can set up any custom value from your integration. Ex: Custom.userid

Authorization Scheme#

The Authorization Scheme is the template for defining your strategy for payment service providers that will process the transaction. Therefore, you must include at least one authorization scheme. It will use at least one payment service. And, it must have been previously set up in the Service section in Console. Make sure you include as many authorization schemes as needed to cover all your business needs. You can also define your retries and volume allocation strategy between your payment services in the authorization scheme.

tip

If you have better service fees for Visa with a specific payment service provider, for example, you can define the authorization scheme to route all Visa card transactions to it.

Authorization is the process that evaluates whether a transaction can be approved or not. It considers information collected from the customer and the payment method itself.

tip

You can define when the authorization scheme authorizes the payment in your flow, also known as Capture.

A transaction is not authorized due to several reasons. In some cases, it can be reversed. Therefore, to increase your odds of having a better authorization rate, you can include up to two retries in your authorization scheme setup.

Fraud Verification#

Fraud Verification is the template for defining your strategy for the anti-fraud service providers. This setup is optional. But it is highly recommended to include at least one anti-fraud service provider to reduce fraud costs, such as chargebacks, and protect your checkout from attacks from malicious users or bots.

If you want to add the Fraud Verification template to your flow, you must have at least one anti-fraud previously set up in the Service section in Console. Then, you can define which actions should be taken, such as whether to capture the payment, depending on the feedback from your anti-fraud service provider.

Managing flows#

When you have more than one flow, you need to define the priority of each of them. The flow displayed on the top of your Flow section in Console has the highest priority, while the one at the bottom has the lowest.

Once a transaction is submitted, it will be evaluated first by the Filter of the flow on the top. If the transaction does not match the filter criteria, it will be evaluated by filters of the flow right below and so on. To change the priority of your flows, just drag and drop them until they reflect the order desired.

note

Filters defined in your Flows may not cover all profiles of a payment transaction. Thus, defining your Default Flow that is fixed at the bottom of your Flows is mandatory. that is fixed at the bottom of your Flows. A Default Flow is a Flow whose Filters will match all transactions.

Flow Metrics#

In the Flows section in Console, you will find five metrics to support you in evaluating each flow's efficiency. These metrics are updated frequently, and you can also see historical results based on the date range filter defined by you.

The calculation rationale of each metric depends on the payment method, also defined as payment service.

Transactions#

It informs the percentage of transactions processed by the flow. Therefore, the sum of percentages for all flows will be 100%. It also includes the total amount.

Net/Attempted (Income)#

It informs the ratio between your net revenue and all transactions processed by the flow, including those not approved. The net revenue considers the amount of the approved transactions after your service fees and fraud cost are deducted. This metric tells how much your margin is, but you can also see how much you get for each $1 processed in the flow.

It also includes the total net revenue.

Approved#

It informs the ratio between the amount of the approved transactions and all transactions processed by the flow.

It also includes the total amount of approved transactions.

Fees#

It informs the ratio between all service fees charged and the amount of all transactions processed by the flow, including fees applicable to transactions not approved. This result considers fees set up in Service Fees section for each service included in the flow. To ensure you have reliable results for this metric, keep all your service fees updated.

It also includes the total amount of all service fees charged.

Fraud Costs#

It informs the ratio between all your fraud costs, such as chargeback, and the amount of all transactions processed by the flow.

Chargeback is when a cardholder reports to the card issuer that the charge has not been recognized. But if it is a legitimate transaction, it is possible to be a disputing chargeback. Keep in mind that this process can be subject to additional charges on top of the transaction amount.