Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
merchant:existing_merchant:selfcare_system:settings:routing_balancing [2018/04/24 06:01] 127.0.0.1 external edit |
merchant:existing_merchant:selfcare_system:settings:routing_balancing [2018/05/16 09:41] thiago123 Fixed based on issue #13649 |
||
|---|---|---|---|
| Line 60: | Line 60: | ||
| Balancing is not as granular as Routing. The choices made per transaction are made by the system, not by rules that a merchant can configure. There are 4 types of balancing: | Balancing is not as granular as Routing. The choices made per transaction are made by the system, not by rules that a merchant can configure. There are 4 types of balancing: | ||
| - | - Round Robin: Tries eligible processing terminals in sequential order (load balancing) | + | - Round Robin: Tries eligible processing terminals in sequential order (load balancing). |
| - Processed Value Ratio: Prioritizes processing terminals based on their “processed value/value limit” ratio (in reverse). This method effectively sends a transaction to whichever eligible processing terminal has used up the lowest percentage of it's value limit. | - Processed Value Ratio: Prioritizes processing terminals based on their “processed value/value limit” ratio (in reverse). This method effectively sends a transaction to whichever eligible processing terminal has used up the lowest percentage of it's value limit. | ||
| - Value Processed: Sends transactions to the processing terminal with the lowest value processed, regardless of limits. | - Value Processed: Sends transactions to the processing terminal with the lowest value processed, regardless of limits. | ||
| - | - Terminal Priority: Prioritizes one processing terminal. All eligible trans will get sent through this by default. If that terminal reaches it's value limit then the next highest priority eligible processing terminal will be used. Terminal Priority is configured to match your acquirer/processor maximum processing values (if they have maximum values, but most don't). To maintain consistency with the acquirer limits these values are only configurable by %CompanyName. For more information please contact our support help-desk at %SupportEmailAddress | + | - Terminal Priority: Prioritizes one processing terminal. All eligible trans will get sent through this by default. If that terminal reaches it's value limit then the next highest priority eligible processing terminal will be used. Terminal Priority is configured to match your acquirer/processor maximum processing values (if they have maximum values, but most don't). To maintain consistency with the acquirer limits these values are only configurable by %CompanyName. For more information please contact our support help-desk at <html><a href="mailto:%SupportEmailAddress?Subject=SDK%20Help"> %SupportEmailAddress</a></html>. |
| ==== Value Limits ==== | ==== Value Limits ==== | ||
| Line 82: | Line 82: | ||
| When the system is deciding what terminal should be used for balancing if follows this logic: | When the system is deciding what terminal should be used for balancing if follows this logic: | ||
| - | - Creates a list, ordered by Balancing Priority, of all terminals under the merchant that are participating in balancing | + | - Creates a list, ordered by Balancing Priority, of all terminals under the merchant that are participating in balancing. |
| - | - Filters out terminals that have reached their monthly transaction value limit | + | - Filters out terminals that have reached their monthly transaction value limit. |
| - | - Filters out terminals the do not support the transaction currency | + | - Filters out terminals that do not support the transaction currency. |
| - | - Filters out terminals that do not support the transaction Card Type | + | - Filters out terminals that do not support the transaction Card Type. |
| - | - Gets the Balancing Type of the Routing Terminal that the transaction was submitted to (Round Robin, Processed Value Ratio, Value Processed, Terminal Priority) | + | - Gets the Balancing Type of the Routing Terminal that the transaction was submitted to (Round Robin, Processed Value Ratio, Value Processed, Terminal Priority). |
| - Selects a single terminal based on this Balancing Type. If there are no longer any terminals in the list (they've all been filtered out above), then an error is returned to the merchant saying "Can't balance transaction". | - Selects a single terminal based on this Balancing Type. If there are no longer any terminals in the list (they've all been filtered out above), then an error is returned to the merchant saying "Can't balance transaction". | ||
| Line 108: | Line 108: | ||
| To access the rules editor once you are logged in you will have to: | To access the rules editor once you are logged in you will have to: | ||
| - | \\ | + | |
| - | \\ | + | |
| **1.** Switch to the appropriate Routing terminal from the Terminal Selection box in the top right of the %SelfCare (see across). | **1.** Switch to the appropriate Routing terminal from the Terminal Selection box in the top right of the %SelfCare (see across). | ||
| + | |||
| %gop_routing_rules | %gop_routing_rules | ||
| + | |||
| \\ | \\ | ||
| **2.** Select Settings -> Routing Rules from the menu. If either of these are not present then ensure that you have successfully selected a routing terminal (step 1) and that your user has “Allow Routing Terminal” permissions. | **2.** Select Settings -> Routing Rules from the menu. If either of these are not present then ensure that you have successfully selected a routing terminal (step 1) and that your user has “Allow Routing Terminal” permissions. | ||
| + | |||
| %gop_2routing_rules | %gop_2routing_rules | ||
| + | |||
| \\ | \\ | ||
| **3.** You will be displayed the rules editor page. Initially there may be “No rules defined”. To start creating a rule click “Add Routing Rule”. | **3.** You will be displayed the rules editor page. Initially there may be “No rules defined”. To start creating a rule click “Add Routing Rule”. | ||
| Line 124: | Line 127: | ||
| %gop_3routing_rules | %gop_3routing_rules | ||
| + | \\ | ||
| As you can see from above the first thing you must do is give the rule a name. This allows for easy reference later on if multiple rules are configured. | As you can see from above the first thing you must do is give the rule a name. This allows for easy reference later on if multiple rules are configured. | ||
| Line 132: | Line 136: | ||
| %gop_4routing_rules | %gop_4routing_rules | ||
| + | \\ | ||
| Next you must select the Operator that you need for the rule. That the list above are available for number based fields such as the Amount in this demonstration, but for strings another operator called LIKE is also available and operates the same way as the SQL LIKE string operator. Note that the IN operator will cause a preview to be shown in the value input box. Also note that strings are automatically converted to numbers and numbers to strings as necessary. | Next you must select the Operator that you need for the rule. That the list above are available for number based fields such as the Amount in this demonstration, but for strings another operator called LIKE is also available and operates the same way as the SQL LIKE string operator. Note that the IN operator will cause a preview to be shown in the value input box. Also note that strings are automatically converted to numbers and numbers to strings as necessary. | ||
| Line 138: | Line 143: | ||
| %gop_5routing_rules | %gop_5routing_rules | ||
| + | \\ | ||
| Once the comparison/identification part of the rule is complete you will see a logical synopsis of it in text at the bottom of the rule box. Now you need to define the action. | Once the comparison/identification part of the rule is complete you will see a logical synopsis of it in text at the bottom of the rule box. Now you need to define the action. | ||
| Line 148: | Line 154: | ||
| %gop_7routing_rules | %gop_7routing_rules | ||
| + | \\ | ||
| Once a rule is complete click “Save Routing Rule” and it will appear as above. They can individually be edited, disabled or removed using the links next to them. | Once a rule is complete click “Save Routing Rule” and it will appear as above. They can individually be edited, disabled or removed using the links next to them. | ||
| %gop_8routing_rules | %gop_8routing_rules | ||
| + | \\ | ||
| When multiple rules are configured you can re-order/prioritise then using __drag and drop.__ | When multiple rules are configured you can re-order/prioritise then using __drag and drop.__ | ||
| **Note that you must enable the “Enable Routing” checkbox is you want the ruleset to take affect!** | **Note that you must enable the “Enable Routing” checkbox is you want the ruleset to take affect!** | ||
| - | |||
| - | ===== Secure Cards with Routing and Balancing ===== | ||
| - | |||
| - | Secure Cards are only supported for Routing and Balancing if using [[merchant:existing_merchant:selfcare_system:secure_cards:multiterminal_secure_cards|Multi-terminal Secure Cards]]. Currently, as there is no step in the terminal selection to filter by terminals that support processing that specific Secure Card, it shuold only be used for Secure Cards that are supported by all terminals that are participating in balancing. If this is the case though, it will behave just like any other card. | ||
| - | |||
| ===== Features Not Supported ===== | ===== Features Not Supported ===== | ||