Using MappingPostProcessor to Modify ResultCode Values

You can use pricing specific denial codes returned by MATRIXX Engine after a ChargingDataRequest to alter the individual ResultCode in the multipleUnitInformation array.

You can configure pricing to use denial codes in the range of 400–9999. By default, denial codes in this range are mapped to ResultCode SERVICE_DENIED. You can use this feature to map the denial codes to different ResultCode strings, including non-standard, vendor-specific ResultCode strings.

You can use the MappingPostProcessor in the ChargingDataResponse mapping to modify the multipleUnitInformation.resultCode value if the ResultCode returned by MATRIXX Engine is unsuccessful (a nonzero value) and if the new MtxAuthDenialDetail field is set.

MappingPostProcessor Default Mapping shows how the MappingPostProcessor maps the denial code to the ResultCode:

Table 1. MappingPostProcessor Default Mapping
ResultCode MtxAuthDenialDetail New ResultCode Value
0 * No change
!= 0 not set No change
!= 0 between 1 and 99 END_USER_SERVICE_REJECTED
!= 0 between 100 and 199 QUOTA_LIMIT_REACHED
!= 0 between 200 and 299 RATING_FAILED
!= 0 between 300 and 9999 END_USER_SERVICE_DENIED
!= 0 between 10000 and 10099 QUOTA_MANAGEMENT_NOT_APPLICABLE
!= 0 less than 1 or more than 10099 No change

If you require more functionality, this post processor can be extended or replaced as required.