Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
merchant:existing_merchant:selfcare_system:settings:routing_balancing [2018/05/16 09:41] thiago123 Fixed based on issue #13649 |
merchant:existing_merchant:selfcare_system:settings:routing_balancing [2018/12/03 10:26] (current) |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ===== Introduction ===== | ===== Introduction ===== | ||
| - | The %CompanyName system is a secure server-based transaction processing service that will enable your business to authorize and process credit/debit card transactions online in real-time. The information needed to process the transactions is sent over a secure, encrypted internet connection. | + | The Nuvei system is a secure server-based transaction processing service that will enable your business to authorize and process credit/debit card transactions online in real-time. The information needed to process the transactions is sent over a secure, encrypted internet connection. |
| Large enterprise often have many strategies that require the use of multiple merchants accounts. This can be for: | Large enterprise often have many strategies that require the use of multiple merchants accounts. This can be for: | ||
| Line 21: | Line 21: | ||
| * Affiliate management | * Affiliate management | ||
| - | The %CompanyName routing and balancing functionality can be used for automation of all of these tasks across all of the acquirers that %CompanyName support. | + | The Nuvei routing and balancing functionality can be used for automation of all of these tasks across all of the acquirers that Nuvei support. |
| ===== Concepts ===== | ===== Concepts ===== | ||
| - | %CompanyName routing and balancing is based on the concepts of “Processing Terminals” and “Routing Terminals”. Both are 7-8 digit numbers beginning in your 4-5 digit Merchant ID. | + | Nuvei routing and balancing is based on the concepts of “Processing Terminals” and “Routing Terminals”. Both are 7-8 digit numbers beginning in your 4-5 digit Merchant ID. |
| ==== Processing Terminals ==== | ==== Processing Terminals ==== | ||
| - | Processing terminals are the same as standard Terminals (Terminal IDs) if you are familiar with basic processing through %CompanyName. | + | Processing terminals are the same as standard Terminals (Terminal IDs) if you are familiar with basic processing through Nuvei. |
| They can be thought of as having a 1:1 relationship to an acquiring Merchant Account. It is possible to have multiple processing terminals pointing at one merchant account though, if required. | They can be thought of as having a 1:1 relationship to an acquiring Merchant Account. It is possible to have multiple processing terminals pointing at one merchant account though, if required. | ||
| Line 49: | Line 49: | ||
| ==== Routing and Balancing ==== | ==== Routing and Balancing ==== | ||
| - | Routing and Balancing are two different but complimentary features in the %CompanyName system. A simple way to describe them is: | + | Routing and Balancing are two different but complimentary features in the Nuvei system. A simple way to describe them is: |
| * Routing rules are purely based on the data in the transaction being processed. They look at the data and depending on the rules configured in the routing terminal they decide which processing terminal to use for the transaction. They can be based on the card or order details or any custom fields/data that the merchant chooses to send in with the transaction, such as Product SKU, affiliate ID, etc. The rules are boolean and prioritized. They can also be used to automatically authorize transactions only for later capture, or decline transactions immediately. | * Routing rules are purely based on the data in the transaction being processed. They look at the data and depending on the rules configured in the routing terminal they decide which processing terminal to use for the transaction. They can be based on the card or order details or any custom fields/data that the merchant chooses to send in with the transaction, such as Product SKU, affiliate ID, etc. The rules are boolean and prioritized. They can also be used to automatically authorize transactions only for later capture, or decline transactions immediately. | ||
| * Balancing is more concerned with the bigger picture of overall acquirer volume management, high volume load balancing and high availability. | * Balancing is more concerned with the bigger picture of overall acquirer volume management, high volume load balancing and high availability. | ||
| Line 63: | Line 63: | ||
| - 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 <html><a href="mailto:%SupportEmailAddress?Subject=SDK%20Help"> %SupportEmailAddress</a></html>. | + | - 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 Nuvei. For more information please contact our support help-desk at <html><a href="mailto:ecomsupport@merchant-support.com?Subject=SDK%20Help"> ecomsupport@merchant-support.com</a></html>. |
| ==== Value Limits ==== | ==== Value Limits ==== | ||
| Line 93: | Line 93: | ||
| ==== Balancing ==== | ==== Balancing ==== | ||
| - | Balancing is purely configured by %CompanyName. If you have multiple merchant accounts and want to avail of our balancing functionality please contact our support help-desk at %SupportEmailAddress with the details of the configuration you are looking for. | + | Balancing is purely configured by Nuvei. If you have multiple merchant accounts and want to avail of our balancing functionality please contact our support help-desk at <html><a href="mailto:ecomsupport@merchant-support.com?Subject=SDK%20Help"> ecomsupport@merchant-support.com</a></html> with the details of the configuration you are looking for. |
| ==== Routing Rules ==== | ==== Routing Rules ==== | ||
| Line 100: | Line 100: | ||
| To enable configuration of routing rules you will require: | To enable configuration of routing rules you will require: | ||
| - | - Routing/Balancing enabled on the terminal by %CompanyName, | + | - Routing/Balancing enabled on the terminal by Nuvei, |
| - Access to a user login that has permission to modify the routing rules (“Allow Routing Terminal” permission). | - Access to a user login that has permission to modify the routing rules (“Allow Routing Terminal” permission). | ||
| Line 109: | Line 109: | ||
| 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 | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules-nu.png"/></html> | ||
| \\ | \\ | ||
| **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 | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules2-nu.png"/></html> | ||
| \\ | \\ | ||
| Line 125: | Line 127: | ||
| The images below and their descriptions describe how rules are created. The rules are boolean based and so should be very familiar in structure to anyone with any development experience at all, but even without that the interface is very straightforward. | The images below and their descriptions describe how rules are created. The rules are boolean based and so should be very familiar in structure to anyone with any development experience at all, but even without that the interface is very straightforward. | ||
| - | %gop_3routing_rules | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules3-nu.png"/></html> | ||
| \\ | \\ | ||
| Line 134: | Line 137: | ||
| Custom Fields can be sent either via the XML or Hosted Payment Page integration methods (please see integration documentation for more information). | Custom Fields can be sent either via the XML or Hosted Payment Page integration methods (please see integration documentation for more information). | ||
| - | %gop_4routing_rules | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules4-nu.png"/></html> | ||
| \\ | \\ | ||
| Line 141: | Line 145: | ||
| The next thing to do is to enter the string or amount or list that the transaction parameter you selected is to be compared to. Again this generally adheres to SQL comparison rules. | The next thing to do is to enter the string or amount or list that the transaction parameter you selected is to be compared to. Again this generally adheres to SQL comparison rules. | ||
| - | %gop_5routing_rules | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules5-nu.png"/></html> | ||
| \\ | \\ | ||
| Line 148: | Line 153: | ||
| You can: | You can: | ||
| * Route To Terminal: This will use a specific Processing Terminal to process the transaction. The Processing Terminal should be selected from the dedicated drop down box next to it (right). | * Route To Terminal: This will use a specific Processing Terminal to process the transaction. The Processing Terminal should be selected from the dedicated drop down box next to it (right). | ||
| - | %gop_6routing_rules | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules6-nu.png"/></html> | ||
| * Authorize Only: This will Authorize against a Processing Terminal chosen by the Balancing functionality. The transaction will not settle by default, but instead will appear in the Routing Terminals “Authorized Transaction Queue”. You will be able to see the Processing Terminal that was used in this list. This queue is used for merchants who need to manually flag transactions for settlement, such as merchants who perform delayed delivery of goods. | * Authorize Only: This will Authorize against a Processing Terminal chosen by the Balancing functionality. The transaction will not settle by default, but instead will appear in the Routing Terminals “Authorized Transaction Queue”. You will be able to see the Processing Terminal that was used in this list. This queue is used for merchants who need to manually flag transactions for settlement, such as merchants who perform delayed delivery of goods. | ||
| * Decline: Simply declines the transaction without going online. Again it will balance the transaction before declining it to determine which Processing Terminal it should be stored under. | * Decline: Simply declines the transaction without going online. Again it will balance the transaction before declining it to determine which Processing Terminal it should be stored under. | ||
| - | %gop_7routing_rules | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules7-nu.png"/></html> | ||
| \\ | \\ | ||
| 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 | + | <html><img class="imageReplace img_small" src= " |
| + | data/media/merchant/existing_merchant/selfcare_system/routing_rules8-nu.png"/></html> | ||
| \\ | \\ | ||
| Line 173: | Line 181: | ||
| The same applies for 3D Secure and for eDCC above. It is not available via XML but is available for Hosted Payment Page transactions on the Routing Terminal. | The same applies for 3D Secure and for eDCC above. It is not available via XML but is available for Hosted Payment Page transactions on the Routing Terminal. | ||
| + | |||
| + | |||