- To designate the division to which a given transaction must be routed, you can use the name-value pair
vin:Division. - To route transactions based on currency, you can define a name-value pair in your merchant configuration and define a value for each currency that must be routed.
Routing Transactions Using the vin:Division Name-Value Pair
To route transactions to specified divisions within a payment processor, you must pass thevin:Division name-value pair in a Subscription, BillingPlan, Product, or Transaction object. If the name-value pair is passed in a Subscription, BillingPlan, or Product object, Suscribe automatically copies the name-value pair to the associated transaction. The name and its value are used to evaluate the division_name variable in merchant data name-value pairs.
For example, assume you are using Chase Paymentech and want to route transactions as follows:
- Route transactions for Product X to Chase TID 112233
- Route transactions for Product Y to Chase TID 445566
- Route all other transactions to Chase TID 999999
divisionNumber merchant configuration as follows:
vin:Division = gold, and for Product Y, the name-value pair vin:Division = silver.
Routing Transactions by Currency
To route transactions by currency, for example to send all transactions in CAD to one division and all transactions in all other currencies to another division, define a name-value pair in your merchant configuration with a default value, and then define a value for each currency. In the following example for Chase Paymentech, you define a routing rule with a blank value. In the name-value pairs that follow, the first entry directs Subscribe to check the currency field value. If an entry exists for a currency (Paymentech:divisionNumber:CAD), Suscribe routes the transaction to Division 123457. If the currency is not in CAD, Subscribe routes the transaction to the default, Division 123456. So, all transactions not in CAD are routed to Division 123456.
Parent topic:Payment Management

