Configure Source Mapping

Configure source mapping for VIN, UnitNbr, CustomerUnitID fields

PaymentServices is a .NET SOAP Web Services application for requesting VFS payment authorizations and pre-authorizations.  Configuration settings are listed below.

• authMake: Source field in CUSTOMEROWNEDQEUIPMENTVIEW for the Make value sent in authorization requests.  Valid values are

  • MAKE from CUSTOMEROWNEDEQUIPMENTVIEW.MAKE

  • COMPANYNAME from CUSTOMEROWNEDEQUIPMENTVIEW.COMPANYNAME,

  • Company name for the CR2 vendor linked to the customer owned equipment manufacturer

  • Empty value 

• authModel: Source field in CUSTOMEROWNEDQEUIPMENTVIEW for the Model value sent in authorization requests.  Valid values are

  • MODEL from CUSTOMEROWNEDEQUIPMENT.MODEL

  • Empty value

• authUnitNbr: Source field in CUSTOMEROWNEDEQUIPMENTVIEW for the UnitNbr value sent in authorization requests.  And

• authVIN:  Source field in CUSTOMEROWNEDEQUIPMENTVIEW for the VIN value sent in authorization requests.  Valid values are:

  • MFGSERIALNO (Mfg Serial)

  • SERIALID (Asset ID)

  • CUSTOMEREQUIPNO (Customer Equip No)

  • Empty value

• failPONums: A CSV list of PO numbers that will produce an error code, if it is used for an authorization / pre-authorization. 

  • The setting is disregardded, if testingEnvironent is false.

• logFile: This setting overrides the default log file name.

  • Default filepath [app directory]\logs\CR2VFSettlement[DATETIME].txt. 

  • User should have ‘Write Privileges’ on this file’s directory.

• logLevel:  This field specifies the type of messages to be logged. Valid values are:

  • llNone

  • llException

  • llError

  • llInfo

  • llDebug

Config settings with Boolean Values

·       logVfwsRequests:  This specifies if the XML request data passed to VFS is written to the log file.

·       logVfwsResponses:  This specifies if the payment service response (adapted from the XML response data received from VFS) is written to the log file.

·       logVfwsResponsesText:  This specifies if the XML response data received from VFS is written to the log file.

For all the above, valid boolean values are:

o   True

o   False

Config settings with Boolean Values, and a default value

• retryInvalidToken:  This specifyies if a new token should be requested an an authorization retried after an invalid token response to an authorization request.  

  • For example: VFS gets an expired token due to payment service caching / network latency. 

  • Default Value = True.

• testEnvironment:  This specify if the installation supports testing diagnostics.

  • Also, in a “test environment”, a customer PO number of “next” is replaced with the next “seed” number. 

  • Default Value = False.

• validateAllManualAuthorizationfs:  This specifies if manual authorization numbers are validated.

  • Auth Number is in format XYYMMDD########

  • (i.e., confirmed to be in format, where X = "M", YYMMDD is a formatted date string within 1 day of the current date, and ######## is an 8-digit number).  If "true", manual authorizations are not validated (i.e., authorization numbers not matching the format are accepted). 

  • Default Value = False.

• authSuccessMsg: This specifies the return message for all authorization responses.

• manualAuthSuccessMsg: This specifies the return message for all manual authorization responses.

• manualPreAuthSuccessMsg: This specifies the return message for all pre-authorization responses.  

  For the above, in the return message:

  • [AUTHNBR] is replaced by Response authorization number

  • [AUTHAMT] is replaced by Authorization amount.

1. vfAppID:  Application ID passed in token and authorization requests to VFS

2. vfDealerCode:  VFS dealer code for ROMCO.

3. vfLocID:  VFS location code for ROMCO.

4. vfPassword:  VFS password for ROMCO (passed in token requests to VFS).

5. vfUserID:  VFS user id for ROMCO (passed in token requests to VFS).

6. vfwsTimeoutSecs:  Timeout for web requests to VFS web service.

7. vfwsAddress:  URL for VFS web service.

For file paths, the following run time substitutions are used:

• [DATETIME]:  substitute system date/time (in yyyyMMddHHmmss format) when file created.

• [DATE]:  substitute system date (in yyyyMMdd format) when file created