> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Working with Name-Value Pairs

For some objects, such as the PaymentMethod and Transaction objects, Subscribe automatically generates certain name-value pairs, designated by the prefix `vin:`. These pairs are listed and defined in the `nameValue` data member table for the specified object.

Subscribe also provides predefined name-value pairs for use within Subscribe. For these pairs, Subscribe populates the `name` and you populate the `value`. These pairs include:

* `vin:Division`:This name-value pair can be populated in an AutoBill, Transaction, or PaymentMethod object for validation. If used in conjunction with the `divisionName` name-value pair in your Subscribe setup, it sends Transactions associated with these objects to the specified division (ID) at the processor.

  `vin:Division` can be used to route Transactions to different payment processors, or to different merchant IDs configured at your payment processor in cases where you are not already routing by currency. (Note that use of the forward slash character (/) in merchant identifiers is not allowed. See [Merchant Identifiers](Merchant_Identifiers#) for more information.) The value you pass must match a value that has been configured in your merchant configuration in Subscribe. Work with your Vindicia Client Services representative to configure this option.

* `vin:OriginalDivisionNumber`: This name-value pair is provided for information purposes only. If you set a value for `vin:OriginalDivisionNumber` on a `migrationTransaction`, that value will be stored in the reference/reporting portion of the `auth` response—it will not affect the Division under which subsequent activities (for example, refunds) are processed. The `vin:OriginalDivisionNumber` name-value pair is useful, therefore, for storing obsolete or legacy Division identifiers for historical purposes.

* `vin:MandateFlag` and `vin:MandateVersion`: When creating an `AutoBill` with EDD as the Payment Method, use `vin:MandateFlag` and `vin:MandateVersion` to associate a mandate document with the AutoBill. For example, set `vin:MandateFlag`to `true`, and `vin:MandateVersion` to 1.02 to associate a mandate document version 1.02 with the AutoBill.

* `vin:MandateBankName`:The Bank Name for the EDD/SEPA Direct Debit Payment Method (required only in the Netherlands).

* `vin:ValidateFullAmt`: Use to pass whether full amount authorization needs to be done before charging. This must be enabled if the processor is Global Collect.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.