Payment Engine provides the following response categories for payment orders:

• 01 Postprocessing of payment order

  You can make manual changes to the payment order in accordance with the field selection control. The system can resubmit the payment order automatically for straight-through processing. If the processing period is exceeded, an end response type is determined.

• 02 Rejection of payment order

  Processing of the payment order stops. The system rejects or reverses the payment order, depending on the processing status.

• 04 Automatic postprocessing of payment order

  Similar to the response for postprocessing; however, the payment order can be fixed and reprocessed by a different system so that it can be resubmitted for straight-through processing externally.

• 05 Request payment order authorization

  Processing of the payment item stops. In the case of an ordering party item, processing of the whole payment order stops and the system requests authorization for the payment item to an external authorization system. The external system can forward feedback about the authorization to Payment Engine and the external system can trigger processing of the payment item to be continued.

   Note

  The enrichment and validation process in Payment Processing determines the following events:

  • Whether an authorization for a payment order is indicated.

  • Whether a lock is stored in the associated service level agreement.

  • Whether a configurable amount limit has been exceeded, even with existing authorization.

  For these events, Exception Control requests payment order authorization. For more information, see Enrichment and Validation.

  End of the note.

• 99 Further processing

  The system ignores the error and resubmits the payment order for straight-through processing. For more information, see End-to-End Payment Processing.

Payment Engine provides the following response categories for payment items:

• 11 Postprocessing of payment item

  You can make manual changes to the payment item in accordance with the field selection control. You can resubmit the payment item for straight-through processing.

• 12 Return payment item

  Processing of the payment item stops. The system performs a corresponding posting to the ordering party. For more information, see Processing of Active Returns.

• 13 Redirection of payment item

  The following redirection categories are possible:

  • Account substitution

    The system substitutes the account of a payment item with a different account using an account symbol.

  • No account substitution

    This redirection category does not involve any change of account. The system sets an indicator and rerouting takes place in Clearing Processing based on the setting of this indicator.

  • Transfer posting

    The system posts a recipient item to the ordering party account. The purpose is to cancel the effect of an already posted ordering party item by posting the money back to the ordering party account.

• 14 Automatic postprocessing of payment item

  Similar to the response for postprocessing; however, the payment item can be fixed and reprocessed by a different system so that it can be resubmitted for straight-through processing externally.

• 15 Reroute transaction type

  You can define a new transaction type for the payment item in Customizing.

• 16 Active return payment item

  The system returns the recipient item (of a payment order where the ordering party item has already been posted) to the account of the ordering party. For more information, see Processing of Active Returns.

• 17 Request payment item authorization

  Processing of the payment item stops. In the case of an ordering party item, processing of the whole payment order stops and the system requests authorization for the payment item to an external authorization system. The external system can forward feedback about the authorization to Payment Engine and the external system can trigger processing of the payment item to be continued.

   Note

  The enrichment and validation process in Payment Processing determines the following events:

  • Whether an authorization for a payment order is indicated.

  • Whether a lock is stored in the associated service level agreement.

  • Whether a configurable amount limit has been exceeded, even with existing authorization.

  For these events, Exception Control requests payment item authorization. For more information, see Enrichment and Validation.

  End of the note.

• 18 Trigger return for internal payment item

  The system initiates the return of internal payment items that have been posted to an account management system. For more information, see Passive Request for Cancellation.

• 19 Trigger return for external payment item

  The system initiates the return of payment items assigned to outgoing payment orders. For more information, see Active Request for Cancellation.

• 99 Further processing

  The system ignores the error and resubmits the payment item for straight-through processing. For more information, see End-to-End Payment Processing.