Status Feedback Workflow

Prepare matching reference

The ReadyToSend rule sequence contains the ApplyDecisionTableRule. This rule decides which field to copy to the reconciliation reference by determining the payment target format code and referencing the PrepareMatchRef table to see which reconciliation rule to apply.

Reconciling

The ReconciliationRule rule, used to reconcile status feedback messages with value objects and which updates these value objects with the appropriate ISO status and reasons, can be fine-tunes using following parameters :

matchingFactorycontrols the way payments and envelopes are looked up.

Not specified: the default relaxed matching is used which expects the filters to be expressed in XPath notation.

StrictPaymentMatchingFactory: a strict algorithm is used to match the payments and envelopes taking into account the matching reference of the parent.

com.trax.payment.matching.PaymentMatchingFactory (= default):a powerful relaxed matching which expects the filters to be expressed in HQL notation and the propagationClass to be: com.trax.payment.matching.PaymentPropagation.

com.trax.payment.matching.StrictPaymentMatchingFactory:a powerful strict matching which expects the filters to be expressed in HQL notation and the propagationClass to be: com.trax.payment.matching.PaymentPropagation.

propagationClassIf not specified the default propagation is used to propagate the reconciliation status through the envelopes and payments. If specified custom propagators can be used to control how the status is propagated. The com.trax.payment.matching.PaymentPropagation propagationClass should be used when using powerful relaxed or strict way of matching.

skipStatusCodes contains a comma separated list of ISO status codes which are skipped during reconciliation.