BR-DGE Smart Routing provides you with many different ways to build, and customise your smart routing rules.

The following guide details the currently available Smart Routing Fragments, and how they work. If you are looking for a specific type of input, or output fragment that is not in the following guide please get in touch with our support team to discuss your requirements.

We also recommend that you check out our other Smart Routing guides to gain a full understanding of how BR-DGE Smart Routing works, and how you can manage your transaction rules.

• 📖 Smart Routing Introduction
• 📝 Managing Smart Routing

Input Fragments

Monetary

A Monetary Fragment allows you to configure different amounts and currencies to be routed to your different Payment Providers. For each fragment, you can select one currency and choose either one of the following trigger conditions:

BIN Metadata

You can configure and combine multiple trigger conditions in order to route payments to different payment processors.

A BIN Metadata fragment will be comprised of one, or a combination of, the following trigger conditions:

📘

BIN Metadata fragments can have multiple trigger conditions. All conditions must be met for the rule to be used in a transaction.

Payment Instrument

You can configure different Payment Instruments to route to different payment processors.

A Payment Instrument fragment can have one, or many payment instruments selected. This will match with any transaction that matches a single payment instrument.

The BR-DGE Portal will only display Payment Instrument Types that your selected retail channel is configured to support.

Merchant Metadata

The Merchant Metadata fragment allows you to create routing rules based on custom data sent with your transaction requests. This data is in the form of key-value pairs.

Within this fragment, you can:

• Specify Attribute Name and Value(s):
  You define the name of the custom metadata attribute and one or more values to match on. If multiple values are provided, the rule will be triggered if any of them match the values in the customMetadata object of your transaction request.
• Combine Multiple Attributes:
  You can specify different attributes within a single Merchant Metadata fragment. These attributes are evaluated using an "and" operator, meaning all specified conditions must be met for the rule to apply.

For more information on how to use Custom Metadata for transaction routing, check out our dedicated Custom Metadata guide.

Payment Rail

🚧

The Payment Rail fragment is currently only available in conjunction with a Payment Instrument Fragment set to Apple Pay

You can use Payment Rail Routing to route transactions made with a dual-branded cards to different processors.

This input fragment can be useful in regions where your customers are likely to pay with a co-branded card. Such as EFTPOS in Australia.

You may wish to send all your Visa & Mastercard traffic to Payment Provider 1, and your EFTPOS traffic to Payment Provider 2. The Payment Rail Input Fragment provides you this flexibility.

Adding multiple Payment Rails into a single fragment uses an OR operator so that if any of the selected rails match the payment, the rule can continue.

BIN

The "BIN" fragment is designed to match transactions based on specific Bank Identification Numbers (BINs). It works by either matching an exact 4 to 8-digit BIN, or by matching transactions that fall within a specified 4 to 8-digit BIN range.

The BIN input fragment currently supports the following matching types:

Output Fragments

Volume

Volume Fragments allow you load balance your payment routing between multiple providers. When a Volume Fragment is selected, BR-DGE will route your transaction to one of the Payment Providers based on your specified "Volume" fragment.

You can input percentages per Payment Processor to divide up the flow of your transactions. The inputted percentages across your processors must add up to 100%.

The fragment will allow you to select two or more processors to split by percentage.

💡

You can click the "Split Volume Evenly" button to quickly split the volume between all selected processors.

Processor Priority

Processor Priority Fragments allow you to route to a single Payment Provider, or have an ordered list of the providers you want a transaction to attempt, if it results in a failover to a secondary provider.

BR-DGE highly recommend you add a "Processor Priority" Fragment at the bottom of your Rule Set with no Input fragments specified. This can function as a "catch all" for your payments that have failed to match on any other rules. Allowing you to be confident that all your payments can be routed.