You can assign one of the following values for the
UseTransactionPool
parameter:
ANY
.
Address Verification
uses either production or test transaction pools based on the availability.
Address Verification
tries to use the production transaction pool first and uses the test transaction pool only if no production transactions are available. This is the default value.
PRODUCTION
.
Address Verification
uses only the production transaction pool.
TEST
.
Address Verification
uses only the test transaction pool.
Use the
UseTransactionPool
parameter if you have separate production and development environments. It is technically possible to use both kinds of transactions in either environment. Note that using test transactions for production purposes violates the Terms of Use. Using production (billable) transactions for testing reduces available transactions for the production environment.
If you use the
UseTransactionPool
parameter during development, ensure that you change the value to production when you deploy the application to the production environment. We recommend making this externally configurable, for example through a configuration file or Registry setting. Alternatively, you can use compiler switches or such code to distinguish the production environment from the development environment.